Frame the problem before the requirement

The idea

A request such as “add a new onboarding screen” is a proposed solution. First identify the unmet need, who experiences it, the current process, constraints and how success will be measured. Record assumptions separately from evidence. This creates a shared problem statement before scope is committed.

Example

Instead of “Build a document-upload page,” write: “Applicants abandon identity verification when they cannot resume after an interrupted upload. We need to reduce abandonment without weakening controls.”

Illustrative BA scenario

Fictional banking example: interview operations, compliance and recent applicants; map the current journey; compare drop-off by device; then decide whether resumable upload, clearer instructions or a policy change addresses the cause.

Try it yourself

1. Rewrite a feature request as a measurable problem statement.
2. List three stakeholders and what each needs to decide.