Products
Distinct histories and workflows
Case study / 03Close ×
03FgForge
One system.
Many products.
System map Synthesized04 layers / 05 methods
Forge began with a question larger than a component library: how might a broad software organization create coherence without forcing every product—and every team—to become the same?
Scroll to decomposethe system ↓
The condition / before
A design system starts as a study of difference.
Across a large product portfolio, similar needs had produced many local answers. The work was to understand why those answers diverged before deciding what should become shared.
Patterns
Repeated solutions with local variation
Teams
Different tools, tempos, and constraints
Code
Duplicated implementation decisions
01 / Method
Inventory
Collect the visible interface patterns and the invisible decisions beneath them. Treat duplication as evidence, not merely inconsistency.
02 / Method
Decomposition
Separate visual style, interaction behavior, content, accessibility, and implementation so each part can be evaluated on its own terms.
03 / Method
Principles
Find the smallest set of shared rules capable of guiding many products without erasing their legitimate differences.
04 / Method
Synthesis
Recombine those rules as reusable components, language, documentation, and contribution paths—a system teams can actually use.
05 / Method
Adoption
Make the system social as well as technical. Governance, feedback, and local participation allow coherence to grow over time.
The proposition / afterA shared foundation.
A shared foundation.
Not a finished answer.
Forge reframed consistency as infrastructure: a common layer of decisions that product teams could inherit, question, and improve. The outcome was not uniformity. It was more intentional variation.
04GovernanceParticipation + evolution
03GuidanceDocumentation + language
02ComponentsInteraction + implementation
01FoundationsType + color + space + access
“A system becomes real when teams can see themselves inside it.”
Design systems are often presented as libraries of finished objects. Forge made the organizational truth visible: the durable system is the relationship between standards, contributors, product realities, and change.
That lesson continues to shape Helium’s practice. We decompose complex conditions to discover what must remain distinct—then synthesize only what becomes stronger when held in common.
Source material
Next / Selected workReturn toThis Helium case study is adapted from Mathias Burton’s original project archive.
View original case study ↗the portfolio↗