A Jobs to be Done (JTBD) template is a strategic framework that helps founders understand why customers "hire" a product. It shifts the focus from demographics to the "job" a customer is trying to accomplish and the progress they seek. For a startup, this isn't just theory; it's a practical tool for digging into deep customer motivations to build products that solve real-world problems and drive sustainable growth.
Why Customer Personas Are Holding Your Startup Back
For decades, founders have leaned on customer personas. We've all seen them: "Marketing Molly, 34, lives in a city, loves yoga, and struggles with team collaboration." On the surface, these seem helpful. But these demographic snapshots often send product teams sprinting in the wrong direction, wasting precious venture capital.
Personas tell you who your customers are, but they rarely explain why they buy. Knowing Molly’s hobbies doesn't reveal the deep-seated frustration that finally pushed her to seek a new project management tool.
This gap between correlation and causation is a minefield for any early-stage company. It's where countless startups waste time and funding building features nobody ever asked for. The Jobs to be Done framework offers a sharper lens, shifting the focus from static profiles to the messy, real-life context of a customer's struggle. Instead of asking who the customer is, JTBD asks, “What progress is this person trying to make?”
Moving Beyond Demographics
That mindset shift is critical for a startup trying to optimize its burn rate and achieve product-market fit. It reorients the entire product development process around solving tangible problems.
The core idea, famously captured by Theodore Levitt, is that “people don’t want to buy a quarter-inch drill. They want a quarter-inch hole.” The focus is on the outcome, not the product.
Once you truly understand the "job," you can design a solution that customers don't just buy, but actively "hire" to make their lives better. This insight leads to better products, clearer marketing, and a much stronger competitive advantage.
A persona might tell you a customer is a 45-year-old manager, but a Job Story reveals they are trying to "reduce the anxiety of reporting project status to executives." The latter is an actionable insight a founder can build a feature for.
The Real Cost of Flawed Personas
Relying on personas alone is a recipe for expensive mistakes for a growing startup:
- Building Unwanted Features: You add bells and whistles that align with a persona’s theoretical interests but don’t solve their actual problem.
- Ineffective Marketing: Your messaging targets broad demographics instead of speaking directly to the pain points that trigger a search for a solution.
- Misaligned Teams: Sales, marketing, and product end up with different ideas of who the customer is, leading to disjointed strategies and internal friction.
Adopting a jobs-to-be-done template helps founders sidestep these common pitfalls. The framework gives your entire team a shared language to rally around a single, clear purpose: helping customers make progress. That clarity is invaluable for scaling a startup. Getting this right can even inform higher-level strategy, like how to structure customer advisory boards for targeted feedback.
To get started, it's helpful to break down what actually goes into a solid JTBD template. These are the core components essential for structuring customer interviews and capturing insights that truly drive growth.
Core Components of a Jobs to Be Done Template
| Component | Description | Example Question for Customer Interview |
|---|---|---|
| The Job to Be Done | The primary goal or progress the customer is trying to make in a specific situation. | "When you first started looking for a solution like ours, what was the main thing you were trying to achieve?" |
| The Situation/Context | The specific circumstances surrounding the customer's struggle. This is the "when" and "where." | "Can you walk me through what was happening in your business or work that made you realize you needed something new?" |
| Forces of Progress | The pushes, pulls, anxieties, and habits that influence a purchasing decision. | "What was so frustrating about your old way of doing things that made you finally decide to switch?" |
| Desired Outcome | The ideal future state the customer envisions after the "job" is done successfully. | "If our product worked perfectly for you, what would that look like? What would be different for your startup?" |
| Hiring Criteria | The specific functional and emotional requirements the customer uses to evaluate potential solutions. | "As you were comparing different options for your company, what were the most important factors in your decision?" |
This table isn't just a checklist; it's a guide for your conversations. Using this structure ensures you move beyond surface-level feedback and get to the heart of what drives customer behavior.
Building Your First Jobs to Be Done Template
Let's move from theory to practice. A solid template is a founder's secret weapon in customer interviews, turning vague feedback into sharp, actionable insights that build great products. The goal here is to create a flexible, go-to jobs to be done template you can reuse for any project.
To make this practical, let's use a composite example: a B2B SaaS company building a new project management tool. They’re targeting small agencies currently juggling projects with a messy mix of spreadsheets, shared docs, and Slack. The founder needs to figure out why an agency owner would finally "fire" their chaotic system and "hire" something new.
Core Structure of Your Template
A great template does more than just ask, "What's the job?" It digs into the entire story behind the customer's decision—their struggles, their hopes, and their anxieties about change.
This diagram is a great visual for how all the pieces come together for a full JTBD analysis.
As you can see, it's a flow. You start by identifying the core "job" and then uncover all the forces pushing and pulling a customer toward a new solution.
At a minimum, your initial template needs these key fields:
- Main Job to Be Done: The high-level progress the customer is trying to make.
- Example: "When client projects get chaotic, help me regain control so I can deliver work on time and look professional."
- Situational Context: The specific circumstances triggering the search for a new solution.
- Example: "We just onboarded two new clients, and my team is dropping the ball on tasks. I’m worried we’re going to miss a major deadline and damage our reputation."
- Desired Outcomes: The metrics the customer uses to judge success, independent of any product.
- Example: "Minimize the time it takes to see which team member is responsible for a task." or "Reduce the number of 'status update' meetings we need each week."
Mapping the Four Forces of Progress
To get inside a customer's head, you must understand the psychological forces at play during their decision. This framework is a cornerstone of the JTBD community and is critical for getting to the real "why" behind a switch.
The decision to adopt a new product is a battle between two opposing sets of forces. Your template must capture both the motivations pushing for change and the anxieties holding the customer back.
Add these four sections to your template to map these forces for every interview:
- Push of the Situation: What is so painful about the current situation that it forces them to act?
- Example: "I'm constantly stressed because I don't have a single source of truth for project status. Information is scattered across emails, Slack, and spreadsheets."
- Pull of the New Solution: What is so appealing about the idea of a new solution?
- Example: "The idea of a centralized dashboard where I can see everything at a glance is incredibly attractive. It promises peace of mind and operational efficiency."
- Anxiety of the New Solution: What fears, uncertainties, or potential hassles are holding them back from adopting a new tool for their startup?
- Example: "Will my team even use it? What if migrating all our current project data is a nightmare? Is it too expensive for our small budget?"
- Habit of the Present: What is the comfortable inertia that keeps them stuck with their current (imperfect) system?
- Example: "Everyone already knows how to use Google Sheets. It's free, and while it's messy, it's familiar."
When you fill these fields out after each customer conversation, you’re building a detailed story of their struggle. That story is pure gold—it’s what you’ll use to build a product strategy that truly connects with your target market.
How to Conduct Interviews That Uncover the Real Job
A well-structured jobs to be done template is only as good as the information you pour into it. The best insights don't come from analytics reports; they come from real conversations with customers.
The main goal of any JTBD interview is to get the customer's "job story." You’re reconstructing the narrative of their struggle, what prompted them to look for something new, and the pivotal moment they decided to make a change.
Think of yourself as a documentary filmmaker, not an interrogator. You're not there to validate your product idea or lead them to a specific answer. Your job is to reconstruct their decision-making timeline with the care of a detective, listening for the story behind their words.
Crafting Questions That Reveal the Truth
The magic lies in asking open-ended questions about past behaviors, not future hypotheticals. Steer clear of questions like, "Would you use a feature that…?" as speculation is unreliable. Instead, ground the conversation in reality.
Here are a few go-to prompts for peeling back the layers of their decision:
- To find the trigger: "Take me back to the day you first realized you needed a different solution. What was going on in your business?"
- To understand the struggle: "Before you switched, tell me about the most frustrating part of your old process."
- To identify fired solutions: "What other tools or workarounds did you try before you found us? What didn't you like about them?"
- To map the timeline: "How long was this problem on your mind before you decided to actively look for a solution?"
These questions are conversation starters designed to pull out rich, qualitative details that expose the real job. They help you pinpoint the exact "struggling moment" that created demand. Nailing this is a cornerstone of effective market research for startups.
The best JTBD interviews feel more like a casual chat than a formal interview. Your role is to be a curious journalist, not a salesperson. Gently guide them through their memory of the events that led to their purchase.
Don't Just Listen—Hear the Forces at Play
As your customer shares their story, your task is to listen for the Four Forces of Progress. Start mapping what you hear back to the fields in your template. For example, when they complain about the clunkiness of their old software, that's the Push. When they start describing the ideal future they imagined, that’s the Pull.
This way of thinking gained prominence after the late Harvard Business School professor Clayton Christensen popularized the theory. He provided a framework to see beyond surface-level demographics and understand true motivation, which became especially vital in complex B2B sales where multiple stakeholders have different priorities.
Turning Customer Insights Into a Winning Product Strategy
So, your jobs to be done template is packed with rich interview data. Now it's time to transform those individual stories into a product strategy that drives growth. The goal is to move past anecdotes and find the powerful patterns that will steer your startup.
As a founder, you are synthesizing findings to spot recurring themes in what customers want to achieve, why they "hire" a product, and where they get stuck. Do multiple customers bring up the same frustration? Are they describing their ideal outcome using similar words? Those signals point toward a real market need.
For instance, after just five interviews, you might notice every customer "hired" your tool to "impress their boss with organized reports." That single insight is pure gold. It should immediately shape your product roadmap, your marketing messages, and even how your sales team talks to prospects.
From Data Points to a Product Roadmap
Once you’ve identified these core jobs, you can map them directly to your product features. This isn't about building what customers ask for; it's about building what helps them achieve their desired outcome—a crucial distinction for any founder chasing product-market fit.
Here’s a great visual of how a team might lay out their JTBD findings to prioritize their work.
This kind of visualization helps your entire team see the landscape of customer needs, making it easier to draw a straight line from a specific feature back to the job it was hired to do. Your interview notes become a strategic blueprint.
A systematic approach called Outcome-Driven Innovation (ODI) was the first rigorous method for applying JTBD theory. According to research cited by its creators, companies using ODI can see innovation success rates over 70%, a significant jump from the typical sub-40% rate. You can learn more about its history in this deep dive on Outcome-Driven Innovation.
Prioritizing Features with Confidence
When you have a crystal-clear understanding of the job, prioritizing features stops being a guessing game and becomes a data-driven exercise. You can run every potential feature through a simple filter: "How well does this help our customer make progress on their core job?"
Let's return to the "impress the boss" example. Suddenly, a minor bug in the PDF export feature becomes a top-priority fix. A proposal for a new dashboard with executive-friendly charts jumps to the top of the list. Conversely, an engineer’s idea for a niche integration, while technically interesting, gets pushed down the backlog because it doesn't serve the main job.
This is how you build a product customers will gladly pay for. It ensures your limited resources are laser-focused on creating tangible value—the very heart of a strong product strategy.
Your jobs to be done template isn't just a research document—it's the foundation of your product roadmap. Every line item should be traceable back to a specific customer struggle or desired outcome you've uncovered.
Common JTBD Mistakes Most Founders Make
Adopting the Jobs to be Done framework can be a lightbulb moment for a startup, but it's surprisingly easy to misapply. In the rush to build and scale, founders often make common mistakes that undermine the framework's power.
Sidestepping these traps is key to turning JTBD insights into a genuine competitive edge.
One of the biggest hurdles is mixing up a "job" with a simple task or activity. A founder might say their customer's job is "to create a spreadsheet." That's a task.
The real job is the why behind the task. It's more like, "to organize project finances to feel in control before a board meeting." One is a function, but the other is about making meaningful progress. This distinction is everything—it's the difference between building a slightly better spreadsheet and building something that resonates on a deeper, emotional level.
Mistaking Jobs for Solutions
Another classic misstep is defining the job through the lens of your own product. If you run a scheduling app, it's tempting to define the job as "to book a meeting using our software." This circular thinking gets you nowhere.
The customer's actual job existed long before your startup did. It’s more likely something like, "to efficiently coordinate with busy colleagues to make a decision without frustrating back-and-forth."
When you frame it that way, your perspective shifts. You see that your real competitors aren't just other SaaS scheduling tools. They're email chains, Slack polls, and quick hallway conversations.
A job is what your customer is trying to accomplish, independent of any product. If your job statement includes your solution, you're not digging deep enough and are blinding yourself to the bigger competitive landscape.
Ignoring Emotional and Social Dimensions
Founders with a technical background are especially prone to this: focusing purely on the functional side of a job. They get caught up in what the product does and overlook how it makes the customer feel or how it makes them look to others.
This is a massive blind spot. Many, if not most, buying decisions are driven by powerful emotional and social needs.
- Emotional Jobs: Someone might hire a project management tool not just to track tasks, but to reduce the anxiety that comes from feeling disorganized.
- Social Jobs: A startup might choose a particular CRM to be perceived as a professional and modern business by clients and potential investors.
Your jobs to be done template must capture these non-functional dimensions. If it doesn't, you're only solving a piece of the customer's actual problem. Uncovering these deeper motivations is how you go from building a useful tool to creating a product that fosters loyalty and word-of-mouth growth.
Got Questions About JTBD?
Even with a solid framework, getting started with Jobs to Be Done can bring up practical questions. Let's walk through some of the most common ones we hear from founders. Clearing up these points can help you move from theory to confident execution.
How Is a Job Different from a Task or a Need?
This is the most important distinction to get right.
A task is an action, like "send an email." A need is a vague requirement, like "I need better communication." A job, however, is the progress someone is trying to make in a specific situation. It’s the full story.
For instance, the job isn't "to send an email." The job is "to communicate project updates to my team so everyone stays aligned and I feel in control." The job packs in the motivation, the context, and the desired emotional state. It’s the why behind the what.
How Many Customer Interviews Are Enough?
There's no magic number, but patterns emerge surprisingly fast. Most JTBD practitioners find that after 8-12 high-quality interviews for a specific job, you start hearing the same struggles and desired outcomes repeatedly.
The goal isn't statistical significance; it's thematic saturation. When you can predict what the next customer is going to say about their "struggling moment," you likely have enough data to move forward with confidence.
Start with a small batch of five interviews. Map what you've learned using your jobs to be done template, and then decide if you need to do more. The depth of the insights is far more important than the number of interviews.
Can JTBD Work with Other Frameworks like Personas?
Absolutely. They work brilliantly together. JTBD doesn't replace personas; it gives them purpose. A persona might describe who your customer is ("Project Manager Pete, 35"), but JTBD explains why Pete is searching for a solution in the first place.
Here’s how founders can use them together:
- Personas: Help you understand your audience's context, the language they use, and where to reach them. This is valuable for your marketing and messaging strategy.
- JTBD: Uncovers the deep-down motivations that drive their buying decisions. This is what you build your product strategy on.
Personas help you find where to talk to your customers, while JTBD tells you what you need to say. Combining them allows you to create a product and a message that resonates on every level.
Ready to build a product that customers can't live without? At Spotlight on Startups, we provide the frameworks and insights you need to turn customer struggles into your greatest growth opportunities. Dive deeper into our resources and build with confidence. https://spotlightonstartups.com/