Operating model
Principles and memory of design work
Preserve evidence, decisions, prototypes and components without duplicating sources.
- Status
- Observed
- Last reviewed
- 2026-10-10
Where to keep the work
| Information | Canonical source |
|---|---|
| Design method and connections between stages | This playbook |
| Brief, research, observations and decisions | Initiative documents, with sources and dates |
| Audience, positioning and language | Project Product Marketing context |
| Stories, journeys, flows and scenarios | UX records in the repository or agreed space |
| Alternatives to compare | VariantHub, when used |
| Visual rules, tokens, components and states | Design system contract and Storybook |
| Proposed code change | PR with references to the design work |
| Current skill instructions | JADO files linked in the catalog, with provenance of the originals |
Use the team’s chosen coordination tools for priorities and progress. The playbook preserves the method and the reasons behind choices.
Principles
- Start from the need and formulate the question the prototype must answer.
- Distinguish observations, hypotheses and preferences; link claims to sources.
- Reuse project tokens and components; clearly identify explorations.
- Choose prototype fidelity according to the decision to make.
- Declare simulated data, incomplete paths and limitations of each test.
- Keep UX record IDs stable and update the decision’s source.
- Document what you learned, even when it leads to rejecting a proposal.
Shared boundary
The method concerns design work. Technical organization, development skills and release remain the development team’s responsibility. See roles and collaboration.