Protocol
Observe the friction before designing the solution
Design work improves when the team can describe the user’s task, context and failure before proposing the feature. Start from observed friction, then separate need from solution.
Before you use it
- Use when
- You are designing a product, service or workflow for other people.
Keep this limit in mind
- Empathy exercises do not replace real evidence, accessibility work or domain expertise. Avoid inventing “user needs” from imagination alone.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Design work improves when the team can describe the user’s task, context and failure before proposing the feature. Start from observed friction, then separate need from solution.
Steps
- Identify the user and the job they are trying to complete.
- Observe or gather concrete examples of where the task becomes difficult.
- Write the need without embedding your preferred solution.
- Generate several solution directions.
- Prototype the smallest one that can test the riskiest assumption.
Check your result
A solution candidate is tied to observed task friction and a testable assumption.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingObserve the friction before designing the solution
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaTurn a skill into a small testable offer
Evidence and sources
First-party source of this practical exercise.
Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.
Start by Understanding a Person or a Group of · data/life-os-content/design-thinking-playbook.json
All sources (1)
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12