JTBD Job Map

Use it when you need a clear, step-by-step breakdown of how users make progress on their core ⊘job.'

Category

Problem Discovery & User Insight

Problem Discovery & User Insight

Originator

Chris Spiek & Bob Moesta

Chris Spiek & Bob Moesta

Time to implement

1 week

1 week

Difficulty

Beginner

Beginner

Popular in

User research

User research

Strategy & leadership

Strategy & leadership

What is it?

The JTBD Job Map is a tactical blueprint for breaking a customer's job-to-be-done into a sequence of actionable steps.

Developed by Chris Spiek and Bob Moesta, it shifts your focus from personas to the real progress your users are trying to make, layer by layer. Instead of guessing motivations, you map out seven core stages, Trigger, Find, Prepare, Confirm, Execute, Monitor, Modify, that every user experiences when tackling a job. Each stage reveals explicit actions, pain points, and desired outcomes, helping you spot friction, unmet needs, and opportunities for innovation.

Unlike generic journey maps, the Job Map is governed by the fundamental logic of progress: it works for B2B and B2C, digital and physical products, and both simple and complex workflows. By capturing every step in the user's workflow, you get a strategic playbook to prioritize features, craft messaging, and align your team around high-impact experiments.

Why it matters?

When you nail every step your user takes, you stop guessing and start building solutions that actually move the needle. A clear job map points straight to the friction that kills retention, the confusion that derails conversions, and the gaps that block premium upgrades. That focus cuts wasted dev cycles, amps up user satisfaction, and fuels repeatable growth loops.

How it works

Growth co-pilot turns your toughest product questions into clear, data-backed recommendations you can act on immediately.

1

Define the Core Job

Pinpoint the main job-to-be-done, what progress the user truly seeks. Drill into the problem context and desired outcome before anything else.

2

Break Into Seven Stages

Lay out the universal stages, Trigger, Find, Prepare, Confirm, Execute, Monitor, Modify, so you cover the full life cycle of user progress.

3

Detail Actions & Struggles

For each stage, list specific user actions, common obstacles, and emotional reactions. Attach direct quotes from customer interviews to ground every point.

4

Identify Desired Outcomes

Translate struggles into measurable outcomes. Ask: “What would make this stage faster, cheaper, or more reliable?” to fuel solution ideas.

5

Spot Friction & Gaps

Use your map to highlight where users get stuck or drop off. Those bottlenecks are your next high-leverage experiments.

6

Brainstorm & Prioritize

Align your team on which stages offer the biggest ROI. Use quantitative and qualitative data to rank opportunities.

7

Iterate & Validate

Turn your top ideas into prototypes or A/B tests. Revisit the Job Map after each cycle to refine and scale what works.

Frequently asked questions

Growth co-pilot turns your toughest product questions into clear, data-backed recommendations you can act on immediately.

What's the difference between a JTBD Job Map and a customer journey map?

A journey map tracks emotional highs and lows across channels. A Job Map zeroes in on the logical steps everyone goes through to make progress, so you spot unmet functional needs instead of just pain points.

What's the difference between a JTBD Job Map and a customer journey map?

A journey map tracks emotional highs and lows across channels. A Job Map zeroes in on the logical steps everyone goes through to make progress, so you spot unmet functional needs instead of just pain points.

How many customer interviews do I need to build a reliable Job Map?

Aim for 12–15 in-depth, qualitative interviews. You'll start seeing consistent patterns by interview 10–12, which is enough to map out universal steps and pain points.

How many customer interviews do I need to build a reliable Job Map?

Aim for 12–15 in-depth, qualitative interviews. You'll start seeing consistent patterns by interview 10–12, which is enough to map out universal steps and pain points.

Can I use the Job Map for both digital and physical products?

Absolutely. Whether you're shipping code or crafting a tangible good, every customer has a progress chain. The seven stages work across industries and delivery models.

Can I use the Job Map for both digital and physical products?

Absolutely. Whether you're shipping code or crafting a tangible good, every customer has a progress chain. The seven stages work across industries and delivery models.

How often should I update my Job Map?

Revisit it after major feature releases or quarterly business reviews. Use fresh user data to validate assumptions and ensure your map stays aligned with evolving workflows.

How often should I update my Job Map?

Revisit it after major feature releases or quarterly business reviews. Use fresh user data to validate assumptions and ensure your map stays aligned with evolving workflows.

What's the best way to prioritize opportunities from the Job Map?

Rank opportunities by potential impact on key metrics (e.g., time saved, error reduction) and ease of implementation. Then focus on high-impact, low-effort stages for fast wins.

What's the best way to prioritize opportunities from the Job Map?

Rank opportunities by potential impact on key metrics (e.g., time saved, error reduction) and ease of implementation. Then focus on high-impact, low-effort stages for fast wins.

You've mapped your user's job-to-be-done, now crush the hidden friction points before they become churn. Plug your Job Map into the CrackGrowth diagnostic to uncover the experiments that rocket conversion and lock in retention.