Each one sets out a problem, a possible fix and a way to test it.
Example scenario · Patient portal
Making appointment information easier to understand
Group the essential appointment details, explain preparation in plain language and distinguish a request from a confirmed change.
Example scenario · E-commerce checkout
What does the customer need to know before paying?
Show the known total and explain any amount that still depends on location. Make guest checkout visible and keep error recovery close to the affected field.
Example scenario · Customer feedback
Turning feedback into a decision somebody can act on
Group feedback by the task affected, retain source context and distinguish frequency from severity. Turn unclear themes into research questions.
Example scenario · B2B permissions
Let administrators see the consequences before changing access
Compare permissions in plain language, preview affected access and provide an explicit recovery route appropriate to the underlying system.
Example scenario · Travel disruption
Make the next step clear when a journey changes
Lead with the change and its practical consequence, then present available alternatives, refund information and help in a predictable order.
For real client work, see the case studies.