Frame the decision
Write what a person is deciding, the consequence and what evidence would make the choice responsible.
Evidence before interface.
A practical product-design sequence for complex services, from the first decision statement to the first normal update after release.
Trace the service
Map channels, actors, policies, dependencies and recovery—not only the ideal screen sequence.
Prototype the edges
Use realistic content, keyboard paths, narrow screens, errors and incomplete information.
Test comprehension
Ask what changed, what happens next and how someone would recover—not whether they like the colour.
Prepare ownership
Name who can verify, publish, maintain and reverse each consequential part of the release.
Measure selectively
Keep signals tied to decisions the team can still change, with destinations and expiry dates.
What a useful engagement leaves behind.
Not only polished screens: a traceable problem statement, decision evidence, service map, complete responsive prototype, content ownership, accessibility notes and release criteria.
The scope is shaped around the uncertainty that matters. A small comprehension prototype can be more useful than a complete visual redesign when the offer itself remains unclear.