# Roadmap: Share a Public Plan of Priorities for Your Design System

> Learn how a design system team plans its work in Now, Next, and Later, sets priorities with evidence, and keeps a public roadmap honest.

**In short:** A design system roadmap is a public plan that sorts the team's work into Now, Next, and Later, set with evidence, and is a plan rather than a promise.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/roadmap

## What you will learn

A design system roadmap is a plan that the system team shares with everyone who uses the system. It shows which new parts, fixes, and improvements the team intends to deliver, and roughly when. Product teams read it so they can plan their own work around the system.

By the end of this lesson you will be able to sort roadmap items into Now, Next, and Later. You will see how a team decides what goes first, how to say no or not yet, and how to keep a public roadmap honest and up to date.

- **Design system:** A shared set of parts, rules, and guidance that product teams use to build their screens.
- **System team:** The small group that builds and looks after the design system.
- **Consuming team:** A product team that uses the system's parts inside its own products.
- **Component:** A reusable building block, such as a button or a date picker. A date picker is a box where users choose a date from a calendar.
- **Contributor:** Anyone who helps write, design, or test parts of the system.
- **Deprecation:** A planned step that marks an older part as going out of use, so teams can move to a replacement before it is removed.
- **Backlog:** The full list of requests and ideas that have not been done yet.
- **Horizon:** A time window on the roadmap, such as Now, Next, or Later.
- **Effort:** How much time, skill, and care a task will need.

## What goes on the roadmap?

A roadmap is not a list of every idea anyone has ever had. It keeps the bigger items that change what teams can build. Public roadmaps from government design systems show this clearly. They list a small set of current and planned work, not every request.

- **New components:** New parts the system needs or teams have asked for. GOV.UK's public roadmap has recently shipped a feedback component and a language navigation component, both released as trial parts first.
- **Deprecations:** Notices that an older part will stop being supported. A good entry names the replacement and gives teams time to move. Include the deprecation in the roadmap so no team is surprised.
- **Accessibility fixes:** Work that makes existing parts easier for people with disabilities to use. GOV.UK lists an accessibility audit of its code as work it has started now.
- **Tooling upgrades:** Changes to the tools that build, test, or share the system. GOV.UK's current work includes changes to its codebase so it can run on newer versions of the tools it uses.

Foundations such as colour rules, writing guidance, and spacing scales can also appear on the roadmap. Keep the whole list short enough that a reader can scan it in a few minutes.

### Why is a roadmap not a promise?

A roadmap states direction and priority. It does not lock in dates. GOV.UK says on its roadmap that some things may change, and that the purpose is to show what is coming so service teams can prepare and plan. The Ministry of Justice design system says its plans are not fixed and may change as the team learns more. Both pages treat the roadmap as a planning tool, not a contract.

> **Tip:** Put one plain line at the top of your roadmap that says plans can change, and explains why. Readers trust a roadmap more when it admits what it does not know.

## How do you sort work into Now, Next, and Later?

Many teams group roadmap items into three horizons. Now holds work the team is doing in the current period. Next holds work planned for the period after. Later holds ideas the team wants but has not scheduled. This format is simple, and it avoids false precision.

- **Now:** Work that has started, or is about to start, with a named owner and a clear scope. The Now column should be specific enough that someone can say what done looks like. Some teams use the current sprint or quarter as the length of Now.
- **Next:** Work the team expects to take on after the current work ends. Keep it in rank order, so the top item is first in line. Some teams use the following one to three months for Next.
- **Later:** Ideas worth keeping in view that have no firm slot yet. It can stay loose, because uncertainty about the far future is honest.

The idea of sorting parts into time columns is old and common. The method still works because it forces the team to choose.

### Why avoid exact dates?

Exact dates for work six or twelve months away are usually wrong. Other teams then plan around a date that moves, and trust falls. Horizons give teams enough detail to plan, without a promise the team cannot keep. The EightShapes article on design system roadmaps says a roadmap need not be exhaustive. It should show what comes next in a way teams can depend on.

> **Tip:** Review Now every sprint or two, and review Later every quarter. In each review, ask whether the Later items still match what users need, and whether old shortcuts in the code are now slowing down Now items.

## How do items get prioritized?

Requests always outnumber the hours a team has. Prioritizing means choosing an order and then explaining it. Atlassian says it treats its design system like a product, with a roadmap, priorities, and feedback loops. The steps below show one way to make those choices visible.

1. **Collect input:** Ask consuming teams and contributors what they need, and write every request in one shared backlog. Ruttl's guide suggests talking with users first to learn their workflows, pain points, and expectations.
2. **Group similar requests:** Put requests about the same need into one theme. The GOV.UK team grouped survey answers into overall topics before it scored them.
3. **Weigh the impact:** Ask how many teams or users the item would help, and whether it reduces harm. GOV.UK's prioritising criteria include whether an item is used by the highest number of services or end users.
4. **Check adoption and fit:** Ask whether many teams would really use the part. GOV.UK gave extra weight to items that already appear in several departments' pattern libraries, and to items that could be built from existing components.
5. **Estimate effort:** Judge how long the work takes and how hard it is. Scoring methods such as RICE, ICE, or weighted scoring give each item points for impact and effort, so items can be compared fairly.
6. **Decide and publish:** Place the top items in Now, the next group in Next, and the rest in Later. Publish the reasons beside the list, not just the list.

Accessibility and risk deserve a clear place in the scoring. GOV.UK's essential component criteria include improving accessibility, providing security and trust through consistent design, and being in use across many services. For existing systems, Ruttl suggests putting usability and accessibility work first.

### Saying no or not yet

A roadmap is as much about what is left out as what is in. Not yet means the idea is valid, but the team has no room for it now. No means the team does not plan to build it, often because one product needs it and no one else does, or because a pattern built from existing parts already solves the problem. In both cases, give a short reason and point the team to another option.

> **Tip:** Write each not yet item with the condition that would move it up. For example: moves to Next when three more teams need it. The team then sees a fair path, not a closed door.

## Worked example: a date picker moving through the roadmap

The public GOV.UK Design System page uses a layout with Working on now, Next priorities, and a list of other ideas that the community can add to. This walk-through uses the same logic to show how one request could move. The dates and steps below are a teaching example. They are not a record of a real GOV.UK decision about a date picker.

1. **Day one: the request lands in Later:** A product team asks for a date picker. The system team logs it in the shared backlog with a short note about the problem. It has one request, a rough sketch, and no owner. It sits in Later with the note: needs more teams.
2. **Month three: it moves to Next:** Three more teams ask for the same part. The team checks its criteria. Many services need it, date entry affects accessibility, and the work is not too heavy on technical effort. Because it now scores near the top, it moves to Next. It has not started yet.
3. **Quarter start: it moves to Now:** The team names a designer and an engineer as owners. It agrees a clear scope: the calendar view, keyboard use, and clear error messages. Because the item is now in Now, the team checks its progress every sprint.
4. **After release: it leaves the roadmap:** When the part is ready, it moves off the active columns. GOV.UK keeps a recently shipped list on its roadmap, so readers can see finished work as well as current work.

> **Tip:** Keep a short note of why each item moved between horizons. Readers then see the reasoning, not only the result. That note is what makes the next decision easier to explain.

## Publishing and keeping the roadmap alive

A roadmap helps only when people can find it and trust it. Publish it where every user can see it, not in a private slide deck. The Ministry of Justice design system says its roadmap exists for transparency, to help decision making, and to encourage reuse. Teams can then plan their own work with more confidence.

- **Make it visible:** Link the roadmap from the front of the design system website and from the community pages. GOV.UK links its roadmap from its community section next to its list of upcoming components.
- **Update on a set rhythm:** Review the roadmap on a fixed schedule, and show the date it was last checked. GOV.UK and the Ministry of Justice both show a last updated date at the top of their roadmap pages.
- **Show what changed:** Record when items move, ship, or drop. The DWP design system keeps a latest updates page with dated entries, which helps teams see progress without reading every page.
- **Invite feedback:** Link each item to a place to discuss it. GOV.UK links its upcoming items to discussion threads, so contributors can add designs, code, or research.

### Keeping trust when plans change

Plans will slip, and some items will be dropped. Trust depends on how the team handles that. Move the item, say why, and say when the list was last checked. Do not hide a missing item. A quiet removal damages trust more than a visible delay with a clear reason.

> **Tip:** Each quarter, ask two questions. Does Later still reflect what teams need? Is any Now item blocked by older shortcuts in the work, often called technical debt? Put the answers in the change note.

## Check your understanding

Each question below gives a new situation. Use the ideas from this lesson to choose the best answer.

**Quick check:** Three product teams each ask for a different new component. Team A wants a date picker used in three of its five products, and its current date fields fail an accessibility check. Team B wants a multi-step form for one new service. Team C wants a colour swatch picker for one internal tool. The system team can build only one item this quarter. Which placement is best?

A. Put the multi-step form in Now, because Team B has the most detailed plan and an owner ready to start.
B. Put the date picker in Now, because several teams use it and it has an accessibility problem. Put the multi-step form in Next and the swatch picker in Later, each with a short reason.
C. Put all three in Now, so every team sees progress this quarter.
D. Put the swatch picker in Now, because it is the newest idea and the easiest to explain.

**Answer:** B. Now holds the work the team can start first. Reach across several teams and an accessibility problem weigh more than one detailed plan or a single internal tool. The other two items stay on the roadmap with reasons and conditions for moving up.

**Quick check:** A team lead sees an item in Next that has not moved for eight months. Teams keep asking when it will ship. What should the roadmap owner do?

A. Remove the item quietly so the list looks clean.
B. Give a firm delivery date for the item, so teams can plan around it.
C. Add a short note that gives the reason it has not moved, the date the list was last checked, and what would move it up.
D. Move the item to Now at once, even though no owner has been named.

**Answer:** C. Honest notes keep a roadmap useful. The reason and the review date show that the team is watching the item. A firm date risks a broken promise, a quiet removal hides the change, and moving to Now without an owner breaks the rule that Now items need clear owners.

## Key takeaways

- **A plan, not a promise:** A roadmap shows direction and priority. Use horizons instead of exact dates, and say that plans can change.
- **Order by evidence:** Gather input, group requests, weigh impact and fit, estimate effort, and explain the order. Say no or not yet with a reason.
- **Keep it public and current:** Make the roadmap easy to find, review it on a schedule, show the last checked date, and explain every change.

## Sources

- [GOV.UK Design System: Upcoming components and patterns](https://design-system.service.gov.uk/community/upcoming-components-patterns/)
- [GOV.UK Design System: Roadmap (last updated 21 October 2026)](https://design-system.service.gov.uk/community/roadmap/)
- [GOV.UK Design Notes: How we prioritise additions to the GOV.UK Design System (2022)](https://designnotes.blog.gov.uk/2022/09/07/how-we-prioritise-additions-to-the-gov-uk-design-system/)
- [Ministry of Justice Design System: Roadmap (last updated 24 February 2026)](https://design-patterns.service.justice.gov.uk/roadmap)
- [DWP Design System: Roadmap](https://design-system.dwp.gov.uk/community/roadmap)
- [DWP Design System: Latest updates](https://design-system.dwp.gov.uk/about/latest-updates)
- [EightShapes: Roadmaps for Design Systems](https://eightshapes.com/articles/roadmaps-for-design-systems/)
- [Big Human: How to Build a Product Roadmap Your Team Will Actually Use](https://www.bighuman.com/blog/how-to-build-a-product-roadmap)
- [Atlassian Inside: Atlassian Design System, building the context engine for the AI era](https://www.atlassian.com/blog/ai-at-work/atlassian-design-system-building-the-context-engine-for-the-ai-era)
- [UXPin: How Can You Create a Design System Roadmap?](https://www.uxpin.com/studio/blog/design-system-rodmap/)
- [airfocus: 5 Basic Roadmap Design Tips With Examples](https://airfocus.com/blog/5-basic-roadmap-designs-tips-examples/)
- [Ruttl: Steps To Build Design System Roadmap](https://www.ruttl.com/blog/design-system-roadmap)
