Journal / Practice

Why strong systems leave room for surprise.

A practical note on creating identities that stay coherent without becoming rigid.

Ada Vale · 8 min read · 11 July 2026

A design system should create confidence, not compliance.

Start with decisions, not components

Before defining buttons and cards, define what the organisation repeatedly needs to communicate.

Make variation intentional

Strong systems distinguish between fixed principles and flexible expressions.

Consistency is useful when it protects meaning, not when it protects habit.

Document the why

Teams adopt systems more confidently when the rationale is visible alongside the rule.

About the author

Ada Vale is a fictional strategy director created for the Arcframe template.

Related articles

Prototypes as conversations
Motion needs a reason
A better first workshop
Link copied