This is the map the system runs on: each business signal points to a screen zone, a set of UX-theory causes, and the design-system patterns that answer them. Pick a signal to trace the path.
Select a signal, then a cause, to see how judgement narrows into concrete, token-scoped patterns.
1Candidate causesUX theory
2Design directionshow to express
Select a cause to see directions.
3System tokensconsistency
Directions resolve to named design-system tokens.
How to read this. The framework encodes the part of design work that usually stays tacit: the reasoning from a number to a screen.
1Cause: why the metric might have moved, drawn from UX principles. The designer decides which apply.
2Direction: how to express the chosen cause on screen. Several options; the designer can add their own.
3Tokens: the named design-system pieces each direction uses, so any generated screen stays consistent.