Jobs to be done for designers
Frame features around the progress people are trying to make.

Zander Whitehurst
7 min read
People do not buy products. They hire them to make progress in their lives. That idea, at the heart of jobs to be done, is one of the most useful mental models a designer can learn. It shifts your focus from features to the outcome people actually want.
The classic example is the drill. Nobody wants a drill. They want a hole in the wall. Actually, they want a shelf. Actually, they want their books off the floor so their partner stops complaining. Somewhere in that chain is the real job, and that is what you should be designing for.
What a job actually is
A job is the progress someone is trying to make in a specific situation. It is not a task and it is not a feature. It usually has three parts:
- The situation. When I am in this context.
- The motivation. I want to achieve this.
- The outcome. So that this improves for me.
Written together, a job statement might look like: "When I finish a client meeting, I want to share clear next steps quickly, so that nothing gets forgotten and I look organised."
Why it helps designers
Jobs keep you focused on what matters. Instead of asking "what features should this have?", you ask "what progress is this person trying to make, and what gets in their way?"
That question opens up far better solutions. In the example above, maybe the answer is not a fancy notes feature. Maybe it is a one click summary that sends itself.
Jobs also help teams align. When everyone agrees on the job, debates about features become easier, because you can ask which option helps people make that progress best.
How to discover jobs
Jobs come from understanding real behaviour, not guesses. In interviews, focus on moments of change:
- What was happening when you started looking for a solution?
- What were you using before?
- What made you switch?
- What almost stopped you?
These questions reveal the situation, the motivation and the anxieties that shape decisions. Switching moments are especially revealing, because people remember them clearly.
Look for the competition you did not expect
Jobs often reveal surprising competitors. Your project management tool might be competing with a spreadsheet, a WhatsApp group or a notebook. If those are what people currently hire for the job, those are what you need to be better than.
I love this part. It is humbling and incredibly useful. Our biggest competitor in one project turned out to be a sticky note on someone's monitor. We designed something simpler as a result, and it worked far better.
Write job statements
Turn your research into a small number of clear job statements. Keep them specific and grounded in real situations. Avoid mentioning your product or any particular solution.
Good: "When I am planning a busy week, I want to see what really needs my attention, so I can stop feeling overwhelmed."
Not so good: "I want a dashboard with priority filters."
Use jobs to guide design
Once you have job statements, use them throughout the design process:
- Prioritise features that help with the most important jobs
- Design flows around the situation people are in
- Remove anything that does not help people make progress
- Test whether people can complete the job, not just use the feature
Jobs also make great review criteria. Put the job statement at the top of a design review and ask whether each screen helps.
Keep it practical
Jobs to be done can become very theoretical very quickly. You do not need complex frameworks or long documents. A few clear job statements, grounded in real conversations, are enough to change how a team thinks.
Start with the next feature you are working on. Write one job statement for it. Then ask whether your current design truly helps someone make that progress. You might be surprised by the answer. We use jobs like this to frame discovery in our AI Product Management Bootcamp.
Memorisely