Blog

Outcomes over Output: Problem Statements, Hypotheses and Jobs to Be Done

Give a team an outcome goal (a change in behavior), not an output (a feature): output is controllable but guarantees nothing, and impact is too far from the team. We frame Bookstore's 66.7% cart abandonment problem without jumping to a solution, covering a four-part problem statement, a falsifiable hypothesis format, guardrails, Jobs to Be Done and how job stories differ from user stories.