Design Systems · For leads · 4 min read
A roadmap for the system
For leads: how to plan a design system's work so product teams can plan around it. Roadmap items as outcomes for products, the inputs that decide the order, a balance between new work and upkeep, and how to publish it and keep it honest.
A design system without a public roadmap gets one anyway: the list of things product teams think it will do, someday. Teams plan their quarters around what the system will ship. If they can't see the plan, they build their own date picker "for now", and now the system has one more thing to migrate. A roadmap is a promise about the next few months, and an honest "not yet" about the rest.
What you'll be able to do after reading:
- Write roadmap items as outcomes for products, not components to draw
- Order the work from real inputs, not from the loudest request
- Balance new work with upkeep and adoption support
- Publish the roadmap and keep it honest
1. Outcomes, not components
Nowthis quarter, committed
Nextnext quarter, planned
BannerHarbour 4.0.0, after the migration window. Done when no product imports it.Laterdirection, not a promise
Reviewed every quarter with the product leads. Anything moved is announced with the reason.
"Build a date picker" tells nobody when they can stop building their own, or how you'll know it's done. "Both products book dates with one picker, and the three custom ones are gone" does. Write each item with:
- Who it's for: which product, which people.
- What changes for them.
- Done when: something you can check, often an adoption or a deprecation count.
The three columns are levels of certainty. Now is committed. Next is planned, and can still move. Later is direction, and says so.
2. What decides the order
Five inputs, in roughly this order of weight:
- Product roadmaps. Skiff launches in spring, so the brand layer must be ready before. Sit in the product teams' planning, or ask for their roadmaps.
- Adoption data. Where products are not using the system, and why (see Measuring adoption).
- The contribution backlog, with the evidence attached to each request (see Contribution models).
- Quality debt: accessibility bugs, components with no dark mode, docs people complain about.
- Deprecations that are due, so the removal lands in a planned major release (see Deprecation and breaking changes).
If one product team is always first, ask whether that's because their need is bigger or because they ask louder.
3. Leave room for upkeep
A system's roadmap fills with new components because they are visible. The work that keeps it trusted is not: releases, migrations, bug fixes, answering questions, pairing with teams that are adopting. Plan it as roadmap work, with its own items, not as what happens in the gaps.
A simple check each quarter: of the items in Now, how many make the system bigger, and how many make it better or more used? If almost all are "bigger", the next quarter's support load will tell you.
4. Publish it
Brad Frost lists roadmaps next to changelogs as ways to keep a system visible to the people who use it (Atomic Design, chapter 5). The GOV.UK Design System publishes its roadmap as three sections, "Recently shipped", "Working on now" and "Future plans", with the date of the last update and a note that some things might change (GOV.UK Design System, Roadmap). Three details worth copying from it:
- Recently shipped first, so people see the plan turns into releases.
- A last-updated date, so people know whether to trust it.
- A plain warning that plans change, instead of dates you'll miss.
Put it where product teams already look: the docs site's home page, and a link in every release note.
5. Keep it honest
- Review it every quarter with the product leads, before they plan their own quarter.
- Announce every move: when an item moves from Next back to Later, say why, in the same place you announce releases.
- Close the loop on requests: when a backlog item makes it onto the roadmap, tell the person who asked.
- Remove what you won't do. A Later column that only grows is a wish list.
6. Common mistakes
- A list of components with no "done when".
- A roadmap only the system team can see.
- Dates on everything, missed, and trust lost with each one.
- No upkeep items, so maintenance happens in evenings or not at all.
- Ordering by the loudest team, not by evidence.
7. Try it (no tools needed)
- Write the three items your system is working on now.
- Rewrite each as an outcome: who it's for, what changes, done when.
- Ask one product lead whether those three are what they'd have chosen.
Reflection questions: Which product team would be most surprised by your roadmap? What's the one upkeep item you've been putting off that belongs in Now?
Checklist
Learn more
- GOV.UK Design System, Roadmap
- Brad Frost, Atomic Design, chapter 5: Maintaining design systems
- Nathan Curtis, Team Models for Scaling a Design System (EightShapes, 2015)
Books, courses and videos to go deeper
- Design That ScalesDan MallBook · Rosenfeld Media, 2023 (Amazon)
- Design SystemsAlla KholmatovaBook · Smashing Magazine, 2017 (Amazon)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
Funding and staffing a design system team · Showing the value of a design system · Measuring adoption · Deprecation and breaking changes · Defining success