About our work

Component maturity scale

The component maturity scale is a way to indicate the level of robustness of any component or asset within the Draft U.S. Web Design Standards. Best practices for agile delivery include releasing software incrementally, before it’s perfect. We can (and should) release new items in the Standards following this principle, and we assess each component independently of every other component or the library as a whole.

We communicate the robustness of each new pattern in two ways: by displaying its maturity level in the UI for each particular component, and by indicating its maturity in release notes and other documentation.

For more information on how a component moves from one maturity level to the next, please review our draft design contribution guidelines. They define, in detail, the assessments and activities our team conducts to determine whether a component is ready to move to the next level.

Our system is inspired by the USAJOBS Design System maturity scale, which uses similar labels on its individual component pages.

Hypothesis

Definitions of done

Proposed

Definitions of done

Includes everything from the hypothesis phase, as well as:

Alpha

Definitions of done

Includes everything from the proposed phase, which has been reviewed by the design team, as well as:

Beta

Definitions of done

Includes everything from the proposed and alpha phases, as well as:

Definitions of done

Includes everything in the proposed, alpha, and beta phases, as well as:

Deprecated

Definitions of done

This is the end of the line, folks.