Wardley mapping for designers

Wasted craft

A team spent three months hand-crafting an account creation flow. Custom illustrations, bespoke animations, micro-interactions on every field. Six months later, account abstraction commoditized the entire pattern. The flow they polished became a one-click SDK integration. Nobody mapped it. Nobody asked where the component sat on the evolution curve. The craft was real. The investment was wasted.

The evolution curve

Simon Wardley's mapping framework plots every component of a system along two axes: visibility to the user and evolutionary stage. The stages move from genesis — novel, uncertain, requiring exploration — through custom-built, into product, and finally into commodity. Each stage has different characteristics. Genesis components are unstable and poorly understood. Commodity components are stable, standardized, and interchangeable. The design treatment should differ at each stage, but most teams apply the same level of craft uniformly.

Craft on commodity is waste

Over-investing is the more common failure: spending months of craft on a component that is approaching commodity status. The account creation example. The settings page that got a full redesign when a standard pattern would have served. The dashboard that was custom-designed from scratch when an off-the-shelf charting library matched user needs perfectly. Craft on commodity is waste, no matter how beautiful the result.

Template on genesis is negligence

Under-investing is the mirror failure: applying a template or standard pattern to a component that is still in genesis. The novel interaction that needed exploration got a Bootstrap dropdown. The new mental model that needed its own language got recycled copy from an existing feature. Template on genesis is negligence, because the component needed original thinking and received none.

Strategy is allocation

The designer who connects design investment to business evolution is operating at staff level. Not because Wardley mapping is a senior skill in itself, but because it requires thinking about where the business is going, not just what the screen looks like today. Strategy is allocation. Knowing where to spend craft and where to conserve it is the design strategy question most teams never ask.

Follow the curve

Design investment should follow the evolution curve. Know what is forming. Know what is flattening.