Skip to interview prep
Apexed

31. What should a useful problem statement establish before detailed requirements begin?

EasyNeeds & requirements

Technical
Show model answer

I'd identify the affected user, task, current difficulty and consequence using relevant evidence. The statement should bound the situation without committing the team to a particular screen, vendor or technology merely because one was suggested.

I'd agree improvement evidence and record uncertainty. Don't invent urgency or assume one account represents every user or cause; revise the statement when new evidence challenges its original boundaries.

What interviewers listen for

  • Identify user and consequential difficulty
  • Avoid premature solution commitment
  • State evidence and uncertainty
What should a useful problem statement establish before detailed requirements begin — Business analysis interview question — Apexed