Roadmap A high-level summary of the work the design system team plans to focus on in the 2026-27 Fiscal Year. The roadmap is subject to change as we gather new information. We will communicate updates to ensure product teams can align and plan their work accordingly. For more details on our priorities and day-to-day activities, see our design system backlog.

Q1 (April - June)

Focus: Drive design system adoption momentum.

Design system adoption and satisfaction measurement

Objective: Establish reliable design system adoption tracking and reporting, and pair it with satisfaction signals from designers, developers, and end users to understand whether the updated design system is improving service outcomes as teams upgrade. Benefit: Enables accurate progress reporting and provides evidence that the updated design system is improving usability, accessibility, and experience quality, not only adoption. Examples:
  • Create a mechanism to reliably collect and report adoption rate
  • Track upgrade progress against the adoption schedule
  • Capture qualitative signals from teams (developer and designer feedback themes)
  • Capture end-user feedback where available (citizen or worker satisfaction, accessibility and usability feedback)

Product acceleration enablement

Objective: Provide prescriptive guidance and resources that help teams get to screens, prototypes, and working experiences faster using the updated design system. Benefit: Reduces time to first screens and improves consistency by helping teams start from proven patterns instead of building from scratch. Examples:
  • Create resources that show how to quickly prototype with design system components and examples
  • Provide contextual starting points for teams using Public form and Workspace templates
  • Pilot the updated design system with teams to generate strong examples to share
  • Create and publish migration success stories

Vue support decision

Objective: Explore and define the minimum work required to confidently state the design system officially supports Vue, including scope, constraints, and support model. Benefit: Prevents unclear commitments and reduces strategic risk by enabling an informed investment decision aligned to organizational needs. Examples:
  • Define what “official Vue support” means
  • Outline the minimum supportable scope
  • Identify implications for documentation, maintenance, testing, and support

Q2 (July - September)

Focus: Improve the core Public form and Workspace experience and execute on the chosen Vue direction.

Public form next phase

Objective: Build on the existing public form offering to make it faster to implement and easier to use, while preserving the flexibility product teams need. Benefit: Unlocks downstream public form capability work and reduces the effort required for teams to build consistent, high-quality public-facing services. Examples:
  • Identify gaps and opportunities in the current public form offering
  • Determine what needs to be built, adapted, or improved to better support the public form use case
  • Deliver improvements so teams can build on a more complete and supportable foundation

Public form and Workspace capability improvements

Objective: Enhance key Public form and Workspace capabilities based on adoption needs and workflow requirements. Benefit: Improves feature sets and reduces the need for custom one-off solutions by making common workflows easier to implement with the updated design system. Examples:
  • Build the review, revise, resubmit feature
  • Navigation pattern for multi-step Workspace workflows
  • Comments component for Workspace
  • Combined Public form and Workspace playground

Vue follow-through

Objective: Based on Vue discovery, either implement formal Vue support or clearly position Angular and React as the recommended approach for teams using AI-assisted workflows. Benefit: Provides clear direction to product teams and reduces uncertainty, enabling progress on a supported path while keeping support sustainable for the design system team. Examples:
  • Publish Vue support guidance and expectations
  • Implement agreed scope if approved
  • Publish recommended alternatives if Vue support is not pursued

Q3 (October - December)

Focus: Mature reusable patterns and examples, and reduce adoption friction through better library packaging and tech stack upgrades.

Examples and pattern maturity

Objective: Expand and refine examples and position them as adaptable reusable assets that teams can apply with confidence. Benefit: Improves self-serve success and product consistency, reducing implementation variance and support demand over time. Examples:
  • Continue expanding and refining examples
  • Show how components and examples combine into larger contexts and workflows

Library packaging and tech stack upgrades

Objective: Reduce friction in how design system assets are bundled and adopted across libraries and update important tech stacks. Benefit: Lowers setup and upgrade complexity, and keeps the design system up to date with the latest supported versions. Examples:
  • Improve how code libraries are bundled together (React, web components, tokens)
  • Update to Svelte 5

Q4 (January - March)

Focus: Support design system version updates and improve documentation and communications quality to support scaling and sustainability.

Documentation and communications improvements

Objective: Improve how teams access and understand design system guidance, and communicate design system value areas like accessibility more clearly. Benefit: Increases trust, improves reuse, and supports self-serve adoption by making guidance easier to consume and share. Examples:
  • Add markdown file download to website documentation
  • Articulate accessibility work more clearly (what is covered and how it supports teams)

Targeted capacity support for design system version updates

Objective: Provide targeted design system team capacity to help remaining product teams complete the design system version update. Benefit: Accelerates adoption progress and unblocks teams facing more difficult migrations, supporting adoption targets while keeping support sustainable through a focus on teams most in need. Example:
  • Focus migration support on late adopters facing systemic barriers to upgrading