Strategy
Job Mapping
A practical UX and product strategy method for breaking down the underlying job to be done so teams can design around real needs instead of current solutions.
How to use job mapping to understand the core job, identify unmet needs, and uncover product opportunities beyond the way people solve things today.
What it is
Job mapping is a UX and product method used to break down a “job to be done” into its core stages.
It focuses on what users are trying to achieve at a functional level, independent of any specific product or solution.
The job is mapped as a sequence of steps, from defining the goal through to completing and evaluating it.
Unlike guideTask AnalysisBreaking down a specific task into steps, decisions, and dependencies so complexity can be reduced and workflows improved.Open guide, which looks at how users complete tasks today, job mapping focuses on the underlying job itself, removing current solutions from the equation.
It is closely linked to guideJobs To Be Done (JTBD)Identifying the functional, emotional, and social jobs users need done to guide product and UX decisions.Open guide thinking.
The goal is to identify opportunities to improve or redesign how a job is completed.
Job mapping is most useful when the team needs to stop thinking about the current product and start thinking about the real outcome people are trying to achieve.
When to use it
Use this method when you want to understand user needs at a deeper level.
It is most useful when:
It is less useful when:
Job mapping is often used early in product strategy and discovery.
Key takeaway
Use job mapping when the opportunity lies in understanding the job itself more clearly, not just optimising the current way it gets done.
How to run it
Set up properly
Be clear on the core job, who is doing it, and the glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term it happens in. A job is what somebody is trying to achieve, stated without reference to any solution.
Resist writing the job around your product. "Choose the right plan on our site" is a task; "get covered before the deadline" is a job.
Run the method
Job mapping breaks a job into the stages anybody must go through to get it done, independent of how they currently do it. That independence is what makes it useful for finding opportunity.
- Define the core job statement in solution-free language, and test it by checking a competitor could serve the same statement.
- Break the job into stages: typically defining, locating, preparing, executing, monitoring and concluding.
- Map what somebody needs to do at each stage, including the parts that happen away from any product.
- Strip out references to particular products or tools. Anything solution-specific has drifted from job to task.
- Identify desired outcomes and glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term at each stage, expressed as things people are trying to maximise or avoid.
Keep it solution-free. The moment a stage mentions your glossaryInterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term, the map stops describing the job and starts describing your product.
Capture and make sense of it
The value comes from seeing the whole job. After mapping, document:
- The stages of the job and what has to happen at each
- Stages currently unsupported by anything you offer
- Outcomes people are trying to achieve, stated measurably
- glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term that shape how the job gets done
Use this to find opportunity outside your current product boundary. Most of the value in job mapping is in the stages you were not addressing.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If it’s tied to a solution, it’s not job mapping.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you design around what people are trying to achieve, not just what they currently do.
Get in touch
If this sounds like something you need, we can help you define the real jobs your users are trying to get done and design better solutions around them.
No guesswork. No assumptions. Just clarity that drives better products.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is job mapping in UX?
It is a method used to break down a job into stages and understand what users are trying to achieve.
When should you use job mapping?
Use it when defining products or uncovering new opportunities.
How is it different from task analysis?
Task analysis focuses on current behaviour, while job mapping focuses on the underlying goal.
What is a job to be done?
It is the outcome a user is trying to achieve, independent of any product.
Does job mapping improve UX?
Yes. It helps design better solutions based on real user needs.
Quick take
If you want to understand what users are trying to get done, not just what they do, map the job.
Related Services
