How to use the Jobs To Be Done Statement Generator.
A job statement describes progress in a situation, not a demographic persona. Use interview evidence to identify the underlying motivation.
Make the workflow fit your task.
Describe the situation that triggers a need, the progress the person seeks and the outcome that matters. Use observed behavior and existing alternatives rather than defining the job as using your proposed feature.
- What you provide
- Customer interview evidence.
- What you get
- Situation, motivation and desired-outcome statements.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A retailer checks updates before opening the shop to avoid selling at outdated prices.
Completed example
When a supplier sends new prices, I want to identify relevant changes before opening so I can sell with accurate information.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a job statement name the product solution?
Focus on the progress sought. Naming the solution too early can hide alternative ways the person already accomplishes the job.
Why does the statement sound like a demographic profile?
Replace identity details with the triggering situation and desired progress. Demographics belong only where evidence shows they affect the job.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑