Deriving User Requirements with Product Context Analyzer
User Requirements describe the capabilities and conditions an interactive system must provide to satisfy identified user needs in the context of performing a task. They specify what the system must enable, present, or support from the user's perspective, without prescribing specific design solutions or interface details. Together, they form a bottom-up pool of user requirements that teams can review, consolidate, prioritize, and adopt into the solution roadmap.
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 suubtasks 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
User Requirements are derived for each subtask within the selected task
User Requirements specify what users must be able to recognize, select, or input when interacting with a system to meet the identified user needs
Use the requirements as a bottom-up pool of what a solution should enable or provide
Review, consolidate, and prioritize requirements before adopting them into your solution roadmap
Export requirement lists for further grooming in ALM systems or other requirements management tools
Translate solution-independent user needs into explicit statements of what a future system must enable, present, or support.
Start with a bottom-up pool of requirements derived systematically from user needs, then consolidate, refine, prioritize, or reject them with your product team.
Identify requirements your current specification may be missing and question existing requirements that cannot be traced back to a user need.
Check whether a proposed or existing design actually provides the capabilities and conditions required to satisfy the identified user needs.
Move selected requirements into your established requirements-management workflow for further grooming, traceability, and implementation planning.
Give downstream teams explicit statements of what the solution needs to support without prematurely prescribing how it should be designed or implemented.