Forget the theory. As a PM leader who has hired and coached product managers at companies like Google and Meta, I can tell you the only jobs to be done template that matters is one you can use to make a decision this week. I’m giving you the downloadable Google Sheets and Notion templates I've personally used to turn ambiguous customer interviews into a clear, strategic roadmap that gets funded.
Your Actionable Jobs To Be Done Template
Let's get straight to the tools. The goal here is simple: give you a repeatable system you can implement within 24-48 hours. This is about moving from guessing what users want to knowing what problems they are struggling with so intensely they're willing to pay to solve them. This is how you differentiate yourself as a PM and get promoted.
Here’s a look at the template's structure. It's built for clarity and immediate use, pushing you beyond surface-level feature requests to the core of customer motivation.
This layout isn't just a place to dump notes. Think of it as a strategic document that maps customer psychology directly to product opportunities and, ultimately, revenue.
Shifting From Personas To Problems
The big mental shift with JTBD is moving away from who the user is and focusing obsessively on what they are trying to accomplish. Sure, a user persona template can be useful for go-to-market, but for product innovation, it often gives you correlation, not causation. Senior PMs at places like Stripe and Airbnb obsess over the 'job', not just the user profile.
"When we buy a product, we essentially 'hire' it to help us do a job. If it does the job well, the next time we're confronted with the same job, we tend to hire that product again." – Clayton Christensen, Harvard Business School Professor
This is the absolute heart of effective product development. A customer doesn't "hire" your SaaS tool because they are a "35-45 year old marketing manager in tech"; they hire it to solve a specific, frustrating problem that’s holding them back.
The Core Components Of The JTBD Template
To make this practical, my template is built around four pillars. Each one is designed to translate messy, human problems into clear, actionable insights for your roadmap. The table below breaks down each section and the crucial question it helps a PM answer.
Core Components Of The JTBD Template
| Template Section | Core Question It Answers |
|---|---|
| The Job Story | "What is the user trying to achieve in a specific context, and why?" |
| The Struggling Moment | "What was the specific trigger that made them finally seek a new solution?" |
| Desired Outcomes | "What does 'success' look like for the customer, in their own words?" |
| The Four Forces | "What psychological drivers are pushing and pulling them towards or away from a change?" |
Let's quickly unpack these.
-
The Job Story: This isn't a user story. It defines context and motivation using the "When ___, I want to ___, so I can ___" format. This simple structure forces you to capture the situation, the goal, and the ultimate outcome.
-
The Struggling Moment: This is where the magic happens. What was the specific trigger that finally pushed the customer to look for something new? This is where the real pain lives, and it's a goldmine for product opportunities.
-
Desired Outcomes: Think of these as the customer's metrics for success. They are solution-agnostic. They focus on the destination, not the car that gets them there. For example, a customer's desired outcome isn't "I want a dashboard," it's "I want to reduce the time it takes to understand project status."
-
The Four Forces of Progress: This model is indispensable for understanding the psychology behind a customer's decision to switch. It maps the pushes (problems with the old way), pulls (attraction to the new way), anxieties (fears about switching), and habits (inertia of the old way).
The Jobs-to-be-Done framework, first formalized by Clayton Christensen, was later quantified by Tony Ulwick's Outcome-Driven Innovation. A famous study of his found that 30% of tradesmen had 14 unmet needs for the simple job of "cutting wood in a straight line," which pointed to a highly specific and underserved market. Digging into the details like this is how you find your next big feature.
Conducting Interviews That Uncover The Real Job
A slick jobs to be done template is worthless without the right data. And that data comes from one place: high-quality customer interviews. This is the highest-leverage skill for any PM, especially those aspiring to leadership. It’s about learning to get past the surface-level chatter and feature requests to uncover the real, underlying “job” a customer is trying to get done.
Forget asking, "What features do you want?" That's a rookie move. Your real job is to become a detective of human motivation.
The goal isn't to walk away with a laundry list of desires. It’s to reconstruct a story—the story of their struggle. You need to map out their entire journey, from the very first moment they thought "there has to be a better way" all the way through their search for alternatives, to the moment they finally decided to "hire" your product. That narrative is where the gold is buried.
Finding The First Thought
Every search for a new solution starts with a specific moment of frustration. The catalyst. Your number one job in a JTBD interview is to pinpoint that exact moment.
To get there, I sidestep direct questions and use open-ended, storytelling prompts instead.
Here are a few I use all the time to get the ball rolling:
- "Take me back to the day you first realized you needed a new way to [solve the problem]. What was happening?"
- "Before you started looking for something like this, what were you using? Tell me about that."
- "Was there a specific event that made you think, 'Okay, this just isn't working anymore'?"
Notice these questions aren't about your product. They're about the customer's life, their context, and their struggle. You’re listening for the environment they were in and the emotions they were feeling. This is how product teams at places like Intercom and Basecamp build such an intuitive understanding of their customers' worlds.
The best JTBD interviews feel more like a casual conversation—maybe even a therapy session—than a formal Q&A. You're not interrogating; you're listening with intent, gently guiding them to re-live the journey that brought them to you.
This conversational style helps unearth not just the functional parts of the job, but the critical emotional and social drivers behind it. For instance, a customer might hire a project management tool not just to "organize tasks," but to "avoid looking unprepared in front of my boss." That social driver is a powerful insight for your product strategy.
If you want to go deeper on this, our guide on how to conduct user interviews has more frameworks and question patterns you can steal.
Listening For Job Stories, Not Feature Requests
As people tell their stories, they'll naturally start mentioning features. This is a classic trap. A less experienced PM will grab onto these requests. An expert PM, however, listens past them to hear the underlying job story. It's a subtle but crucial shift.
Here’s what you should be tuning your ears for during the interview:
- Energy and Emotion: When does their voice change? Do they sound frustrated, excited, or relieved when talking about certain moments? These emotional spikes almost always point directly to the biggest pain points and desired outcomes.
- Workarounds: Dig into the hacks, spreadsheets, and convoluted manual processes they cobbled together before finding a real solution. These workarounds are a treasure map. They show you exactly what job the customer was trying to do and where every other solution fell short. Your future feature roadmap is hiding in their messy spreadsheets.
- The Consideration Set: What other tools did they look at? Seriously, ask them. Understanding who they see as your competition (it’s often not who you think) reveals how they frame their problem and what they actually value in a solution.
By focusing on these signals, you graduate from being a feature-taker to a genuine problem-solver. You’re not just filling out a template; you're building a rich, qualitative model of your customer's reality. And that’s the foundation for any product that people truly connect with.
From Interview Notes To Actionable Insights
Your interview recordings and transcripts are a goldmine, but in their raw form, they're just noise. The real work begins now: turning that messy, qualitative data into a structured, strategic asset.
This is where your jobs to be done template comes in. Think of it as the bridge between what your customer is actually going through and what ends up on your product roadmap. It’s your best defense against confirmation bias and building based on gut feelings alone.
Let’s walk through this with a real-world B2B SaaS scenario. Imagine you’re a PM for a project management tool. You just got off a call with a new customer who recently ditched their chaotic system of spreadsheets and emails to manage their remote team. Your job is to fill out the template, field by field.
This process helps you visualize the customer's entire journey, from their first inkling of frustration all the way to the moment they decided your product was the answer.
Mapping this path—from recognizing a problem to actively searching for a solution—is absolutely critical. It’s how you uncover what truly motivates someone to change their behavior and try something new.
Synthesizing The Struggling Moment
Your first pass through the transcript is a hunt for the Struggling Moment. This isn't just a general annoyance; it's a specific event, a tipping point.
In our project management tool example, the customer might have said something like, "I spent two hours before our weekly status meeting just trying to figure out who was working on what. I looked completely unprepared in front of my VP."
That’s your moment. It’s emotionally charged and tangible.
Once you’ve gone through 8-12 interviews, you'll start seeing patterns emerge. Maybe four other customers bring up the agony of prepping for status updates. Now you can define the core struggling moment with real confidence: "Team leads feel anxious and appear disorganized because they lack a single source of truth for project status."
See the difference? This isn't just a generic problem statement; it's a powerful narrative.
Defining Measurable Desired Outcomes
Next, you need to translate their frustrations into Desired Outcomes. The key here is to keep them solution-agnostic and measurable. The customer isn’t hiring your tool to "use a Gantt chart." They're hiring it to get a result.
Based on the struggling moment we identified, you might synthesize these outcomes:
- Minimize the time I spend manually gathering project status updates.
- Increase my confidence when presenting project status to leadership.
- Reduce how often team members are unclear on their current priorities.
These outcomes become the foundation of your product strategy. They are what you will design for, build for, and measure against. Later, you'll use these to inform your product specs. If you want to go deeper on this, our guide on how to write product requirements provides a great, structured approach.
Getting the core job wrong can be catastrophic. Take higher education, for instance. A shocking 40% of first-time students fail to graduate within six years. Researchers found that schools were selling "education," but students were actually hiring universities for jobs like "help me find a better career" or "give me a structured place to grow up." This insight is now forcing entire university programs to rethink their value proposition.
Using AI To Map The Four Forces
The final, and most nuanced, step is mapping the Four Forces of Progress. This is where you unpack the psychological drivers pushing and pulling the customer toward a decision. Going through transcripts to manually categorize every snippet can be a real slog, but this is a task where AI assistants shine. As an AI PM, I use this tactic constantly.
You can feed a transcript into a tool like Claude or ChatGPT with a very specific prompt:
"Act as an expert Product Manager specializing in Jobs-to-be-Done research. Analyze the following customer interview transcript. Identify and categorize quotes into the Four Forces of Progress for switching to a new project management tool.
- Pushes: Pains with their old solution (spreadsheets/email). What frustrated them?
- Pulls: Attractions of the new solution. What were they hoping for?
- Anxieties: Fears or worries about making the switch. What made them hesitate?
- Habits: Inertia or comfort with the old way. What kept them stuck?
Present the output in a clear, four-quadrant markdown table with verbatim quotes from the transcript."
The AI will quickly surface quotes like "I was so tired of version control issues" (Push) or "I was worried about the team's learning curve" (Anxiety). This can shrink your synthesis process from hours to minutes, giving you a comprehensive map of the emotional landscape your customer navigated.
Of course, your job as the PM is to validate and refine this output, making sure the final insights are still grounded in your deep, human understanding of the customer's story.
Turning JTBD Insights Into A Winning Product Strategy
Great research is only useful if it actually drives the business forward. As a PM, your real job is to take all those customer struggles you've unearthed and translate them into a product roadmap that wins. A finished Jobs to be Done template isn't just a research artifact; it's your blueprint for making strategic calls that hit right at the core of customer pain.
This isn't about guesswork. It’s about building a clear, defensible logic that connects deep customer understanding to tangible business results. It’s how you move from a messy page of interview notes to a feature your engineering team is genuinely excited to build and your execs are ready to fund.
This is precisely how the best companies innovate. Think about it: Netflix didn't win by focusing on the job of "watching movies." They understood the real job was "effortless unwinding after a long day." This insight led directly to features like autoplay and hyper-personalized recommendations—things that nailed the deeper need.
Mapping Desired Outcomes to Metrics and Features
The "Desired Outcomes" section of your template is pure gold for strategy. These customer-centric statements are your direct line to building features that actually matter and defining metrics that reflect real value, not just vanity.
Each Desired Outcome should be mapped to potential features or improvements. It's a creative process, but a structured one.
- Desired Outcome: "Minimize the time I spend manually gathering project status updates."
- Potential Features:
- An automated weekly summary email.
- A real-time dashboard view of project progress.
- Slack integration for daily stand-up reminders.
This mapping exercise is critical. It ensures every single idea on your roadmap has a direct, traceable link back to a specific customer struggle. It cuts through the noise and forces you to prioritize from a customer-first perspective.
From there, you can turn these outcomes into your North Star metrics for OKRs.
Desired Outcome: Increase my confidence when presenting project status to leadership.
Potential Metric: A new "Executive Summary" dashboard is used by 75% of team leads at least once per week.
See the shift? You’re not just measuring feature usage; you're measuring how well you’re solving the customer’s core job. That creates a powerful feedback loop.
Translating The Four Forces Into Go-To-Market Messaging
The Four Forces of Progress (pushes, pulls, anxieties, habits) are a goldmine for your marketing and sales teams. This part of the jobs to be done template is basically a cheat code for crafting compelling messaging that hits on an emotional level.
-
Pushes & Pulls: Your ad copy, landing pages, and sales pitches should speak directly to the "pushes" (the pains of their old way) and the "pulls" (the promise of your new solution). If a customer's biggest push was "wasted hours in spreadsheets," your headline needs to scream about eliminating that exact pain.
-
Anxieties & Habits: Your onboarding, customer support, and case studies should directly squash the "anxieties" (fears about switching) and overcome the "habits" (the inertia of their old workflow). If customers worry about a steep learning curve, your onboarding has to be ridiculously simple and backed by crystal-clear guides.
This approach ensures your go-to-market strategy is perfectly in sync with the psychological journey your customers are actually on.
Building a Defensible Business Case
Suddenly, when you present your roadmap, you're not just saying, "I think we should build this feature." You're armed with a powerful, evidence-based narrative.
You can walk into any room and state with confidence: "Our interviews with 12 recent customers revealed a recurring struggling moment around preparing for status updates, causing anxiety and wasted time. We believe an automated reporting dashboard will directly address their desired outcome of minimizing prep time. We'll measure this by weekly usage, which aligns with our company's goal of increasing user engagement."
This structured, data-informed approach is what separates the top 1% of Product Managers.
If you're looking for more ways to connect research to strategy, there are many excellent product strategy frameworks that build on these principles. A solid product strategy, informed by JTBD, is also fundamental for successfully validating business ideas before you sink a ton of engineering resources into them. It's how you build with confidence.
Common JTBD Mistakes And How To Avoid Them
Even with a perfect jobs to be done template, a lot of product managers stumble when it comes time to actually execute. I've reviewed hundreds of research decks over the years, and I've seen the same handful of mistakes derail otherwise sharp teams, time and time again. These aren't just minor slip-ups; they're fundamental errors that lead to beautiful but ultimately useless research.
https://www.youtube.com/embed/yBYd5asXg
Mastering JTBD isn't just about filling in a spreadsheet. It's about knowing which traps to sidestep so your customer insights don't become strategic dead ends. The difference between a PM who gets it right and one who misses the mark often comes down to an awareness of these common pitfalls.
Confusing The Job With The Solution
This is, bar none, the most common mistake I see. A junior PM might define the job as "to get a project management dashboard," but that's a solution, not a job.
An experienced PM digs deeper. They know the real job is something more like, "to confidently report progress to my executive team without spending hours chasing down updates." See the difference?
Focusing on the solution locks you into a specific set of features. Focusing on the job opens up a world of innovative possibilities. Your product is simply one way to get that job done, and it’s always at risk of being "fired" if a better way comes along.
Only Interviewing Your Power Users
It feels great to talk to your happiest customers, doesn't it? They love your product, they validate your decisions, and they make you feel smart. The problem is, they are the absolute worst people to talk to if you want to understand why people switch.
Your best insights will almost always come from two very specific groups:
- Recent Switchers: People who just "hired" your product in the last 30-60 days. Their memory of the struggling moment that pushed them to look for something new—and the anxiety of making the switch—is still fresh.
- Recent "Firers": People who just left your product for a competitor or even reverted to their old workaround. Their pain points with your solution are acute, specific, and incredibly valuable.
Interviewing your loyal, long-term customers will only teach you how to keep happy people happy. Interviewing switchers is how you learn to grow your market.
Ignoring Emotional And Social Drivers
Product decisions are rarely made in a purely functional vacuum. A customer doesn't just hire a CRM to "store contacts" (the functional job). They hire it to "avoid looking disorganized in front of a major client" (the social job) or to "feel in control of their sales pipeline" (the emotional job).
When you map out the job, always ask yourself: What is the emotional fuel behind this decision? How does this choice make the customer look to their boss, their peers, or their team?
Ignoring these drivers is like trying to build a car with no engine. The most powerful products don't just solve a functional problem; they resolve a social or emotional tension. When you uncover these deeper needs, you're no longer just building software—you're offering progress.
This is the difference between a tool that is merely used and a tool that is loved. It requires moving past surface-level feature requests and challenging your core beliefs about what the customer is truly buying. A good way to pressure-test this is by using an example of an assumption map to make sure you're not operating on flawed premises.
A Quick Guide to Sidestepping Common Traps
I've put together a quick reference table to help you spot these issues before they derail your research. Think of it as a cheat sheet for turning common pitfalls into proactive, insightful practices.
| Common Pitfall | Correct Approach | Why It Matters |
|---|---|---|
| Defining the job as an action or solution (e.g., "get a dashboard"). | Define the job as the user's ultimate goal or desired progress (e.g., "confidently report progress to execs"). | Focusing on the "why" instead of the "what" opens up more innovative and effective solutions. |
| Interviewing happy, long-term customers. | Focus interviews on recent switchers (both to and from your product). | This is where you uncover the real friction and triggers that drive purchasing decisions and market growth. |
| Focusing solely on functional needs. | Dig deep for the emotional and social drivers behind the user's struggle. | Social and emotional factors are often the most powerful motivators and lead to products that customers love, not just use. |
| Accepting surface-level answers from users. | Use the "Five Whys" or similar probing techniques to get to the root cause of the struggle. | Users often describe symptoms, not the core problem. Your job is to uncover the underlying "job." |
Avoiding these mistakes isn't about being perfect; it's about being intentional. By consciously steering clear of these common traps, you'll be well on your way to gathering insights that actually drive product strategy forward.
Answering Your JTBD Questions
Even with a great jobs to be done template in hand, questions always pop up. Over the years, I've seen the same ones surface from aspiring PMs and seasoned pros alike.
Let's tackle the most common ones head-on so you can start applying this framework with confidence.
How Is A Job To Be Done Different From A User Persona?
This is the most critical distinction to get right. A user persona describes who the customer is—their attributes, demographics, and behaviors. In contrast, a Job to be Done defines the progress a customer is trying to make in a particular situation, totally independent of who they are.
Think of it this way: your persona might shift, but the underlying job is remarkably stable. The job of "getting a healthy meal on the table quickly on a busy weeknight" has been around for decades. The solutions people hire for that job—from frozen dinners in the 80s to meal kit deliveries today—are what change.
A persona tells you what a customer looks like. A Job to be Done tells you what they are trying to accomplish. For product innovation, the job is a far more reliable North Star.
By focusing on that stable, underlying motivation, JTBD gives you a much more powerful and lasting guide for building things people actually want.
How Many Customer Interviews Are Enough?
This is a classic PM question, but the answer isn't some magic number. The real focus should always be on the quality and depth of the interviews, not just the tally.
That said, most expert practitioners find that clear, actionable patterns start to emerge after just 8 to 12 in-depth interviews. The key is talking to the right people: customers who have recently "hired" or "fired" a product for the specific job you're studying.
You’ll know you’ve hit saturation when you can practically predict what the next person is going to say. When you start hearing the same struggling moments, motivations, anxieties, and desired outcomes over and over, you likely have enough data to build a solid strategy.
Is The JTBD Template Only For New Products?
Absolutely not. This is a common misconception that really limits the framework's power. JTBD is an incredibly versatile tool that's just as valuable for existing products as it is for new ventures.
Here’s how it plays out across the product lifecycle:
- For New Products: It helps you uncover genuinely unmet needs and underserved markets, giving you a solid foundation for innovation.
- For Existing Products: It’s a game-changer for growth and prioritization. By interviewing customers who recently switched to your product, you can sharpen your value proposition. And by talking to those who switched away, you can pinpoint critical weaknesses and competitive threats.
Using the JTBD template on a mature product helps you refine messaging, prioritize the right improvements, and make sure your roadmap stays locked on the core job your customers are hiring you to do.
Ready to build products that customers actually need? The insights and frameworks I share are designed for real-world application. Join thousands of PMs and subscribe to the Aakash Gupta newsletter for actionable advice delivered straight to your inbox. Learn more at https://www.aakashg.com.
