UX framework doc
All user-facing stuff like features, needs, goals etc should have similar docs attached to the tasks. Not everything mentioned in doc should be executed. Select what is doable and applicable to the problem. Simplify.
Why are we doing this?
What problem/need/pain does it solve?
Is it a vitamin or painkiller?
What is the severity of this problem/need/pain?
Does it require immediate solution?
What is the root cause of this problem/need/pain?
Have we done enough research to validate this problem/need/pain?
What category does it fall into based on Kano Model: Basic (essential feature), Performance/Satisfier, Excitement/Delighter, Indifferent attributes, Reverse attributes.
Understand the perspective of the target audience/customer to identify and address the problem at hand. Cast aside all assumptions (because assumptions can stifle innovation!) about the problem, the consumers, and the world at large.
1.1 Empathy map
1.2 User scenarios
Who – details of the persona/behavioural archetype
What their goals are.
When they might perform tasks (including obstacles).
Where they might do these tasks (including obstacles).
Why they want to do things, must perform subtasks, etc.
Accumulate the information gathered during the Empathise stage. Analyse observations and synthesise them to define the core problems you and your team have identified.
2.1 Problem statement
Describe the problem you're trying to solve by doing this work.
2.2 Business success criteria
The criteria that must be met in order to consider this feature a success.
2.3 User success criteria
The criteria that must be met in order to consider this experience a success.
Look for ways to view the problem and identify innovative solutions to the problem statement you’ve created.
- Task analyses
- Where it fits within the journey map
- Simple user flows
- Any other idea input