Users often describe a desired screen when they are really expressing an underlying problem. Clarifying that problem can reveal a simpler solution.

The decision to make

Ask what task is difficult, what information is missing and what a successful result looks like. Avoid committing to the first suggested implementation.

Practical checklist

  • Record the user role and context.
  • Define inputs, outputs and exceptions.
  • Write acceptance examples in plain language.

An illustrative example

A request for another dashboard may mean the existing report cannot be filtered by team. The requirement is the decision the user needs to make.

Your next step

Review requirements with users and implementers before treating a feature list as an agreed scope.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.