Identifying User Needs with Product Context Analyzer
User Needs describe the information, access, and conditions a user requires in the context of performing a task, independent of any specific solution or technology. They capture what users must understand, obtain, or be provided with before and during task execution, rather than how a task is carried out. Teams use User Needs to derive and specify user requirements, ensuring that To-Be design solutions enable users to successfully perform their tasks.
Specify the activity you want to analyze. The activity can be a single task, a responsibility, or a multi-phase journey
Example: Order Pizza from a delivery service for a business meeting
Describe the activity in a single sentence without prescribing a particular product or solution.
Optionally include context such as who is performing the activity and under what circumstances.
Adding context helps make the analysis more domain-specific.
User Needs are identified from the tasks and subtasks included in the analysis.
The analysis takes several minutes depending on the scope and number of tasks identified
Select a task from the task hierarchy to explore its detailed context-of-use information
Example: Find Pizza Delivery Service
Describe the activity in a single sentence without prescribing a particular product or solution.
Optionally include context such as who is performing the activity and under what circumstances.
Adding context helps make the analysis more domain-specific.
User Needs are identified from the tasks and activities included in the analysis.
User Needs specify what users need to know, have access to, or be able to do in order to achieve a desired outcome
Information-related needs describe what users need to know in order to perform each subtask
Resource-related needs describe what users need to have access to in order to perform each subtask
Skill-related needs describe what users need to be able to do in order to perform each subtask
Use the identified needs as the basis for specifying user requirements
Generate multiple design ideas from explicit user needs without anchoring the team on a predefined feature or solution.
Work backwards from proposed features and ask which identified user needs they actually address—and which needs remain unsupported.
Trace existing user stories back to an explicit user need. If no corresponding need exists, question the story or investigate whether an important need is missing from the analysis.
Use the needs as a solution-independent checklist to identify where an existing design may not provide the information, access, or conditions users require.
Treat the generated needs as hypotheses and validate whether users actually require this information, access, or support when performing the task.
Turn validated needs into explicit statements of what a future solution must enable or provide while remaining independent of a specific design.
Keep conversations focused on what users need before the team starts debating how the product should satisfy those needs.