The 4-minute mental model behind Writing a Job-To-Be-Done statement.
The idea in one line
On the surface, Writing a Job-To-Be-Done statement can look like a single technique you either know or you don't.
Why it's worth your time
Building the right thing beats building the thing right.
How to recognise it in the wild
1. Spot the moment. Notice when *writing a Job-To-Be-Done statement* is the move the situation is asking for — usually when it's tempting to skip it. 2. Name the goal. Say, in one sentence, what a good outcome looks like here. 3. See the core move. The heart of Writing a Job-To-Be-Done statement is simple: write 'When… I want to… so I can…'. 4. Know you're done. You've got it when this stops feeling like a technique and starts feeling like instinct.
What "good" looks like
- You separate the literal request from the underlying job.
- You can name who the user is and what they're really trying to do.
- You prioritize by impact, not by what's easy.
Next: try the step-by-step tutorial to actually run the rep.