Rigidity vs Flexibility Mapping | Design System Tactics

Decide where your organisation needs consistency and control, and where it needs freedom and adaptation. Rigid approaches favour predictability, compliance, and shared standards, while flexible approaches favour autonomy, experimentation, and speed. Most organisations need a deliberate balance that reflects how they actually operate.

Use this workshop with or without an existing design system. Ground it in insights from a Maturity Assessment so decisions reflect business reality rather than aspiration. The output helps define how opinionated your system should be across foundations, components, contribution, and guidance.

This tactic was inspired by Ben Callahan's book Maturing Design Systems

Steps

Set business context

Share relevant outcomes from your Maturity Assessment, such as delivery culture, risk tolerance, autonomy, and leadership support.
Define the spectrum

Explain what rigid, flexible, and a balanced midpoint mean in practice, keeping the explanation outcome-focused rather than theoretical.
Plot by system area

Create separate spectra for foundations (brand, accessibility, tokens), components and patterns, contribution and governance, and guidance and documentation, then individually plot where the organisation needs to sit today for each area.
Interpret implications

For each area, capture what the placement means in practice for design, build, and decision-making, focusing on trade-offs, constraints, and where friction is likely to appear.
Re-plot and align

After discussion, re-plot each area and note where views changed, aligned, or remain contested.
Define principles

Translate the final positions into clear principles that guide how foundations are defined, components are built, contributions are reviewed, and guidance is written.
Revisit over time

Use the map and principles to guide future decisions and re-run the workshop as part of future Maturity Assessments as the organisation and system evolve.