Product UX term
Jobs to be done: meaning, examples, and expert terminology.
Frames the user's goal as progress they are trying to make, not just a feature request.
What it means
Plain meaning
Frames the user's goal as progress they are trying to make, not just a feature request.
Aliases
JTBD, job statement, customer job
People say / experts say
People usually say
- why users need
- customer pain
- outcome
- motivation
- what problem it solves
Experts usually say
Jobs to be done, Switching trigger, Outcome, User interview
When to use it
Use it when
Your rough ask sounds like: why users need, customer pain, outcome. The term gives your design critique a clearer problem shape.
When not to use it
Do not use this term as generic UX polish. Use it when the product decision, user behavior, or interface risk needs to be named clearly.
Copy-ready handoff phrase
Before and after examples
Prompt upgrade
Weak ask: Improve this why users need.
Exact Terms ask: Rewrite this as jobs to be done with situation, motivation, desired progress, and current alternatives.
Handoff examples by use case
UX critique
Review this product experience using Jobs to be done and related UX concepts: Switching trigger, Outcome, User interview. Name the user confusion and the fix.
Redesign brief
Create a redesign brief centered on Jobs to be done; include the current user expectation, the friction, and the smallest interface change.
AI feedback prompt
Act as a product designer and critique this screen for Jobs to be done, then rank the most important improvements.
Common mistake
What goes wrong
Asking for a prettier UI before naming the user confusion or product mechanic.
Better move
Use Jobs to be done with the related vocabulary trail: Switching trigger, Outcome, User interview.
Related terms
Missing a better term?
Turn feedback into vocabulary
If this page almost names your problem but misses the exact term, send the rough phrase and the term you expected. Accepted feedback becomes a better trigger, explanation, comparison page, or new term.