Design
Turn standards into consent-aware flows, escalation cues, and language a person can act on.
Where to start
Three moves, in order
Each ends somewhere you can act rather than somewhere you can read.
-
Model the burden of one flow
Score a real journey for time tax, step count, and exit availability, and read the report card as a design brief.
-
Place the interrupt where the harm is
Design the stop, slow, and escalate controls the flow needs when the system is wrong — reachable, not decorative.
-
Write copy people can act on
Use phrases a person can send, file, or read out — contestation language that works without the framework behind it.
Tools and standards
What to run and what to satisfy
The diagnostics that surface risk for this role, and the standards that bear on its work.
Diagnostics
What to attend to
The parts of the method that bear on your work
Not everything here is yours. These are the parts that are.
- Audit UI flows for stoppability, consent, and reversibility signals.
- Pair mechanism specs with interaction patterns and copy.
- Validate workflows with diagnostics before shipping.
What to open
Where the material actually is
- Mechanisms catalog — Design-ready specs with implementation guidance.
- Field notes — Applied examples and facilitation cues.
- Diagnostics — Decision-ready labs for flow validation.
- Glossary — Interaction language tied to standards.
First moves
- Select two mechanisms that map to your flow’s risk points.
- Run a diagnostic with the team to surface consent or burden gaps.
- Align UI copy with glossary anchors before release.
Other roles
If that was not you
Seven audiences, one page each. Picking the wrong one costs a click, not a detour.
- Engineering — You build or operate the system that makes the decision.
- Policy and compliance — You write the rules the system has to satisfy, or prove to a regulator that it does.
- Audit and assurance — You verify someone else's claims from the evidence their system emits.
- Operations — You run the appeals, the incident response, or the queues where the system's errors land.
- Research — You study these systems and publish about them.
- Executive — You decide whether to deploy, and you carry the liability when it goes wrong.
Or go back to Start, which asks the same question with all seven answers on one screen.