Take Writing a Job-To-Be-Done statement from exercise to real work in Product Design.
A realistic scenario
You're mid-project and the situation calls for writing a Job-To-Be-Done statement. It's easier to keep moving on autopilot — that's exactly the moment to apply it on purpose.
Walk it through
1. Pause and read the room. Decide that writing a Job-To-Be-Done statement is the right move right now. 2. Set the bar. Out loud or in writing, state the outcome you're aiming for. 3. Execute the rep. Write 'When… I want to… so I can…'. 4. Make it visible. Share what you did and why, so the value is seen — not just done. 5. Reflect. Capture what worked so it becomes a default next time.
Avoid the common trap
⚠ Taking the feature request at face value and skipping the "why." Watch for it, and course-correct early.
Level up
- Do it when nobody asked you to.
- Teach it to a teammate — explaining it cements it.
- Stack it with the other skills in Product Design.
You've completed the Writing a Job-To-Be-Done statement track. Put it to the test with a real-world challenge.