The Jobs To Be Done Framework
Customers don't simply buy products or services; they pull them into their lives to make progress.
The Jobs To Be Done Framework reframes innovation around the 'job' a customer is trying to accomplish, not their demographics or product features. Developed by Harvard Business School professor Clayton Christensen and codified in 'Competing Against Luck' (2016), it provides a prescriptive workflow — from identifying the struggling moment to writing job statements, mapping job steps, and diagnosing switching behavior — that turns customer insight into actionable innovation strategy.
“We make a project management tool for small agencies. People sign up when they're getting overwhelmed with client work — too many projects, too many…”
Your customers aren't buying your product — they're hiring it to make progress
JTBD centers on a single reframe: the 'job' — not the customer segment or product feature — is the correct unit of analysis for innovation. A job is the progress a customer is trying to make in a specific circumstance. The workflow begins with identifying the Struggling Moment (the circumstance that triggers a search for a solution), then producing a canonical Job Statement in the format: 'When [situation], I want to [motivation], so I can [outcome].' Every job is then analyzed across three dimensions: functional (what needs to be accomplished), emotional (how the customer wants to feel), and social (how they want to be perceived). The Four Forces of Progress diagram maps why customers switch solutions — push from the existing situation, pull toward a new solution, anxiety about changing, and habits holding them in place. Finally, a Job Map breaks the job into sequential steps (Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, Conclude) to identify exactly where friction and innovation opportunities live.
Most product teams optimize around customer demographics and feature lists — but demographics don't explain why someone buys, and feature comparisons don't explain why they switch. The result is innovation theater: teams build what customers say they want, not what they actually hire. JTBD reveals the real unit of analysis — the job the customer is trying to get done in a specific, triggering circumstance — so teams can stop guessing and start building solutions that get hired.
Identify the exact job your customers are hiring your product to do — and diagnose whether you're fulfilling it better than the workarounds, non-consumption, and competitors they're currently settling for.
- A product, feature, or business idea you want to validate or improve
- A specific customer situation or struggling moment you've observed
- Knowledge of your current customers' behavior — even rough or anecdotal
- An open question about why customers are or aren't switching to your solution
- A written Job Statement in the canonical When / I want to / So I can format
- A Three-Dimensional breakdown separating the functional, emotional, and social job layers
- A Four Forces diagram showing what pushes customers to switch and what holds them back
- A Job Map annotated with friction points and ranked innovation opportunities
Watch the methodology work.
Three specimens from a single real session: the same situation, before and after, the full transcript, and the skill answering live in the channel where the work happens.
Your product team just shipped three features customers requested in surveys. Activation is flat. Your NPS sits at 31. Marketing is running 'project management for agencies' campaigns with messaging identical to five competitors. You've done focus groups and keep hearing 'it's fine, just not sticky.' No one on the team can articulate why customers who sign up don't come back — or what they're hiring instead.
You've written a Job Statement: 'When I'm managing 4+ active clients and deadlines are compressing, I want to see every commitment in one place, so I can give clients confident status updates without calling an all-hands.' You know the functional, emotional, and social dimensions. The Four Forces analysis revealed that migration anxiety — not feature gaps — is your real conversion blocker. Your job map shows the 'Confirm' step (verifying ownership before a client call) is where your product wins or loses the hire. Your next sprint has a testable hypothesis, not just a backlog.
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
Job Statement Crafting
Transforms a vague customer problem into a precisely structured Job Statement using Christensen's canonical format: 'When [situation/circumstance], I want to [motivation], so I can [expected outcome].' This creates a testable, iterable artifact that keeps teams focused on progress-making rather than feature delivery.
Three-Dimensional Job Analysis
Breaks any job into its three essential layers: functional (what the customer needs to accomplish), emotional (how they want to feel during and after), and social (how they want to be perceived by others). Missing any layer produces incomplete solutions that customers don't fully hire.
Four Forces of Progress Diagnosis
Maps the four forces acting on a customer's switching decision: the push of dissatisfaction with their current solution, the pull of attraction toward a new solution, anxiety about changing, and the gravitational pull of existing habits. Diagnosing all four forces reveals why customers with a real need still fail to act.
Job Map & Friction Identification
Decomposes the job into eight sequential phases — Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, Conclude — and identifies exactly where customers experience friction, workarounds, or unmet needs at each step. Produces a ranked map of where innovation will have the highest leverage.
Competing Hires Audit
Catalogs every solution a customer currently 'hires' to do the job — including direct competitors, indirect substitutes, makeshift workarounds, and non-consumption. Reframes competitive analysis entirely by asking not 'who else makes this product?' but 'what else gets hired for this job?'
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
Job Statement
A precisely written statement in the canonical format: 'When [situation], I want to [motivation], so I can [outcome].' Serves as the foundational artifact — the testable hypothesis that anchors all downstream product and marketing decisions.
Three-Dimensional Job Profile
A structured breakdown of a job's functional, emotional, and social dimensions. Surfaces the layers of the job that features alone never fulfill — and reveals where competitors are systematically underinvesting.
Four Forces Diagram
A diagnostic mapping the push, pull, anxiety, and habits acting on a customer's switching decision. Identifies exactly why customers with a real unmet need still fail to change behavior — and what it would take to move them.
Job Map with Friction Annotations
A step-by-step breakdown of the job from Define through Conclude, with each phase annotated for friction points, current workarounds, and innovation opportunity score. Turns qualitative customer research into a ranked product roadmap input.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Clayton Christensen
Clayton Christensen (1952–2020) was the Kim B. Clark Professor at Harvard Business School and one of the most influential business thinkers of his era. His 1997 book 'The Innovator's Dilemma' transformed how executives think about disruptive technology; The Economist named it one of the most important management books ever written. He developed the Jobs To Be Done Framework over two decades of HBS research and case studies, most fully codified in 'Competing Against Luck' (2016), co-authored with Taddy Hall, Karen Dillon, and David Duncan. The Christensen Institute, a nonprofit think tank, continues his research program.
Competing Against Luck: The Story of Innovation and Customer Choice (2016)
Kim B. Clark Professor, Harvard Business School; author of The Innovator's Dilemma (1997) and Competing Against Luck (2016); founder of the Christensen Institute.
Put it to work.
agent-skills runs as MCP — connect it once and The Jobs To Be Done Framework works in Claude, ChatGPT, Cursor, or any MCP-compatible client. Sign in to see your config and accept the terms.