Jobs-to-be-Done Meets the Journey Map: Two Lenses, One Experience

Jobs-to-be-done (JTBD) and customer journey mapping answer different questions, so they aren't substitutes for each other. JTBD identifies the stable, solution-agnostic job a customer is hiring something to do; the journey map shows how that job actually unfolds in one specific experience, complete with steps, channels, and emotional highs and lows. Combine them by aligning job steps to journey stages, then scoring each overlap for opportunity.

Quick answer: JTBD tells you the job — timeless and solution-agnostic. The journey map tells you how that job is actually being executed right now — situated, emotional, specific. Align job steps to journey stages, score the gaps with Ulwick's Opportunity Score, and use the emotion curve to find where an unmet job step is quietly costing you customers.

Two Lenses, Not One Map

Jobs-to-be-done and customer journey mapping operate at different altitudes and answer different questions, so treating them as interchangeable is where most teams go wrong. JTBD names the stable, solution-agnostic job a customer hires something to do; the journey map traces how that job is actually executed today, including every emotional peak and trough.

The confusion is understandable — both use words like "steps," and both claim to represent the customer's experience. But Jobs-to-be-Done, as formalized by Tony Ulwick and popularized by Clayton Christensen, is deliberately solution- and time-agnostic. The job of "getting a work day's worth of energy into the body between 7 and 8 a.m." hasn't changed in decades, even though the products competing for it have — coffee, energy bars, kale smoothies.

The job, defined: a stable pursuit of progress in a given context, separate from any specific product, feature, or interface.

Alan Klement, another well-known JTBD practitioner, frames a job the same way in When Coffee and Kale Compete — as a person's pursuit of progress, not an attachment to any particular solution.

That framing is why Christensen and Bob Moesta's often-cited milkshake study for a fast-food chain still holds up as the field's clearest illustration. A surprisingly large share of milkshakes turned out to be bought by solo morning commuters, not afternoon dessert-seekers, who were hiring the milkshake to make a boring drive tolerable and stay full until lunch — a job the marketing team had never framed correctly because they were staring at the product, not the progress underneath it.

A journey map, by contrast, is intentionally solution-bound and time-bound. It documents a specific persona moving through a specific experience — this checkout flow, this onboarding sequence — capturing touchpoints, channels, and an emotion curve that rises and falls with the friction of that particular execution. For the full mechanics of building one, see our complete guide to customer journey mapping.

If you need the fuller JTBD grounding — job statements, the job map, desired-outcome statements — our complete guide to jobs-to-be-done covers it before you attempt the overlay below.

It also helps to know why the two get conflated in the first place. Ulwick built his Outcome-Driven Innovation (ODI) methodology in the 1990s explicitly to give strategy teams a segmentation tool that didn't decay every time the product roadmap changed. A job statement written for a bank in 1995 still describes a real job today, even though online banking didn't exist yet.

Journey maps were never meant to carry that weight. They're closer to a snapshot: accurate for this release, this channel mix, this competitive set, and due for a refresh the moment any of those shift.

Aligning Job Steps to Journey Stages

Alignment works because both frameworks are secretly sequential: JTBD's Job Map breaks the job into eight universal steps (Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, Conclude), and a journey map breaks the experience into stages (Awareness, Consideration, Onboarding, Usage, Support). Overlaying the two rows on one timeline reveals where each job step is actually attempted, or missing entirely.

A simple five-step method turns this into a repeatable exercise:

1. List the job steps from your JTBD synthesis — Ulwick's eight, or your own condensed version.
2. List your actual journey stages for the specific experience under review.
3. For each job step, ask where in this journey a customer attempts it right now.
4. Flag any job step with no matching journey stage — that's an unserved step, not a UX bug.
5. Flag any journey stage carrying more than one job step at once — that's a likely overload point.

Job steps rarely run in a straight line. Monitor frequently loops back into Modify and Execute as customers reassess their progress mid-journey, which is why a job map behaves more like a system with feedback loops than a checklist. If your journey keeps circling back on itself in ways a linear diagram can't explain, our guide to systems thinking is the better lens for the causal loops underneath.

One caveat: this alignment happens on the customer-facing journey map, not an internal service blueprint. If you need the frontstage-backstage view of who inside your company handles each step, see service blueprint vs journey map for when to reach for which artifact.

None of this is a new idea in isolation — Jim Kalbach's Mapping Experiences describes "alignment diagrams" that stack two different data types on a shared timeline for exactly this reason, and job-map-onto-journey is a direct application of that pattern. What's specific to JTBD is the second row you're stacking: not another view of the current experience, but a stable, external reference for what "done" looks like, independent of your product's current shape.

Scoring the Overlap: Ulwick's Opportunity Score Meets the Journey

Alignment tells you where a job step lives on the journey; Ulwick's Opportunity Score tells you how underserved it is there. The formula — Importance + (Importance − Satisfaction) — turns two customer ratings per desired outcome into one number, and scores above roughly 15 (on a 20-point scale) flag outcomes worth building for.

In practice, you rate each desired-outcome statement ("minimize the time it takes to...", "increase the likelihood that...") for importance and satisfaction, both on a 1-10 scale, across your customer base. High importance paired with low satisfaction produces a high opportunity score — a job the market cares about that nothing currently does well. Attaching each outcome statement to the journey stage where the job step actually happens turns a flat priority list into a map of where to fix it.

Ulwick's format for a well-formed outcome statement is worth internalizing before you start rating anything: a direction of improvement (minimize/increase), a unit of measure (time, likelihood, number of errors), an object of control (the thing being acted on), and, optionally, a contextual clarifier. "Minimize the time it takes to confirm a data source is correctly connected" is well-formed; "make onboarding easier" is not — it's a solution-shaped restatement of the problem, and it can't be scored or attached to a journey stage with any precision.

Notice what this table does that a plain outcome-statement list can't: it tells you not just which outcomes are underserved (Execute, scoring 15) but exactly which stage of the lived experience to redesign. A checkout example makes this concrete — see our breakdown of an ecommerce checkout journey for how a Confirm-stage outcome statement, like "minimize the chance of choosing the wrong shipping option," maps onto a single screen most teams dismiss as "just a form."

Forces of Progress: The Emotional Physics Behind the Curve

The emotion curve on a journey map shows something dips, but not why. Bob Moesta and Chris Spiek's Forces of Progress — push of the situation, pull of the new solution, anxiety about the new solution, and habit of the present — describe the competing pressures at each step, and anxiety plus habit usually explain the sharpest dips.

Push and pull tend to explain why a customer starts moving at all; anxiety and habit tend to explain why they stall right before committing. Mapped onto a journey, that split lines up almost exactly with where teams see abandonment.

This is why an emotional low at checkout or during first setup so often isn't a copy or layout problem — it's anxiety spiking against the pull that got the customer there in the first place, with habit quietly pulling them back to whatever they used before. Turning a felt dip into a scored, sequenced backlog item is its own discipline; we cover the mechanics in from emotion curve to prioritized backlog.

The same forces resurface later in the journey, which is easy to miss if you only apply them near the first purchase. In a B2B subscription journey, anxiety and habit reappear at renewal — a competitor's pull is weighed against the anxiety of migrating data and the habit of a workflow the team already built around your product.

If your emotion curve has a second, quieter dip near a renewal or contract-review stage, it's worth screening it against the same four forces rather than assuming it's simply "expansion friction."

From Theory to Practice: A Worked Example and a Repeatable Workflow

The payoff of combining both lenses shows up when an emotional dip turns out to be a job-step problem, not a UX problem. Consider a hypothetical B2B analytics onboarding journey: the emotion curve dips hard on "connect your data source," and the fix that actually works is rarely the one the interface team reaches for first.

Say the team's first instinct is to treat this as a UI problem and polish the connector wizard — clearer copy, a progress bar, fewer clicks. The emotion score ticks up slightly, then drops again next release. Overlaying the Job Map shows the dip actually sits on the Confirm step ("confirm I've made the right choice before committing more time and risk"), not the Execute step the team kept polishing.

The desired outcome underneath is something like "minimize the risk of connecting an incomplete or wrong data source," scoring importance 9, satisfaction 3, for an opportunity score of 15 — solidly underserved by Ulwick's threshold. The forces confirm it: anxiety about the new solution ("what if I break something or waste a week") is overpowering the pull that got the customer to sign up, while habit — sticking with the spreadsheet they already trust — is winning by default.

The fix that follows isn't more UI polish. It's a preview step letting the customer see sample results from a small, low-risk data sample before committing to the full connection — directly serving the underserved Confirm step. That's the practical value of running both lenses together: the journey map showed the team where the dip was; the JTBD overlay showed them which job step was actually failing there.

A Repeatable Workflow

In practice, the two lenses combine in six steps:

1. Run JTBD interviews to build job statements and desired-outcome statements — start with our complete guide to jobs-to-be-done if you're new to the format.
2. Map the specific customer journey for the experience in question, including an emotion curve.
3. Overlay job steps onto journey stages to spot unserved steps and overloaded stages.
4. Score each relevant desired outcome with Ulwick's Opportunity Score at the stage where it actually lives.
5. Interpret every emotional peak or dip through the four Forces of Progress, not assumption.
6. Prioritize where high opportunity scores coincide with emotional lows — that intersection is your backlog, not either artifact alone.

This is the workflow Prodinja's Customer Jobs tool is designed to support: it walks you through drafting job statements and desired outcomes, applies Ulwick's opportunity-scoring formula, and prompts you to weigh each job against the four Forces of Progress.

Paired with the Customer Journey tool's emotion curve, you can drop job steps onto the stages where they're actually executed and see, in one view, where an underserved job coincides with a felt low — instead of keeping the two artifacts in separate documents that never talk to each other.

Key Takeaways

• Jobs-to-be-done is solution-agnostic and stable over time; a journey map is solution-bound and specific to one experience — they answer different questions, and neither replaces the other.
• Overlay JTBD's Job Map steps onto your journey stages to find job steps with no matching journey stage (unserved) or journey stages carrying too many job steps at once (overloaded).
• Ulwick's Opportunity Score — Importance + (Importance − Satisfaction) — tells you which desired outcomes are underserved; aligning it to journey stages tells you where to fix them.
• Moesta and Spiek's Forces of Progress (push, pull, anxiety, habit) explain why the emotion curve dips, especially around commitment points like purchase and onboarding.
• An emotional low on a journey map is not automatically a UX bug — check which job step it maps to before prescribing a fix.
• Treat JTBD and journey mapping as two views of the same underlying reality, scored and overlaid together, rather than two separate deliverables produced by different workshops.