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.
Quick take
If you want to understand what users are trying to get done, not just what they do, map the job.
Related Services
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.
Before you start, be clear on what the core job is, who the user is, and the glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term in which the job exists.
Base this on serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service, not assumptions.
Run the method.
Job mapping is structured and functional.
Define the core job statement. Break the job into stages (e.g. define, prepare, execute, monitor, complete). Map what users need to do at each stage. Remove references to specific products or solutions. Identify desired outcomes and glossaryConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term.
Focus on the job itself, not how it is currently solved.
Capture and make sense of it.
The value comes from abstraction.
Look across the job to identify unmet needs or inefficiencies, points of glossaryFrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term or failure, opportunities for innovation, and gaps between current solutions and ideal outcomes.
Use this to guide glossaryProduct StrategyProduct strategy defines how a product will achieve business goals by solving user problems in a focused and sustainable way. It sets direction, priorities, and trade-offs to guide decision-making.Open glossary term and design.
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 glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term 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?
guideTask AnalysisBreaking down a specific task into steps, decisions, and dependencies so complexity can be reduced and workflows improved.Open guide focuses on current glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, 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.