JTBD for Product Development: Build What Customers Actually ‘Hire’

What is Jobs to Be Done (JTBD)? A Paradigm Shift in Product Development

The landscape of product development is constantly evolving, and a core challenge remains the same: understanding what customers truly want. Traditional market research often focuses on demographics or feature requests, but these can be superficial. The Jobs to Be Done (JTBD) framework offers a powerful alternative. Instead of focusing on the customer’s attributes, JTBD centers on the ‘job’ a customer is ‘hiring’ a product or service to do. It’s a fundamental shift in perspective, moving from ‘who’ is the customer to ‘what’ problem are they trying to solve.

Think of it like this: when you buy a drill, you’re not really interested in the drill itself. You’re ‘hiring’ it to create a hole in the wall so you can hang a picture. The ‘job’ is hanging the picture. The drill is just the tool. JTBD helps product teams deeply understand this underlying ‘job’ and then design solutions that effectively and efficiently get that job done.

This framework is crucial for anyone involved in product strategy, design, and development, helping teams move beyond assumptions and build products with genuine market appeal. Understanding this can be a cornerstone of effective Product Lifecycle Management (PLM): Boost Profitability & Innovation.

Table of Contents

• What is Jobs to Be Done (JTBD)? A Paradigm Shift in Product Development
• The Core Principles of Jobs to Be Done
• Why JTBD Matters for Product Development
• JTBD vs. Traditional Approaches
  • A Comparative Look
• Applying JTBD in the Product Development Lifecycle
  • Step-by-Step Guide to Implementing JTBD
• Key Takeaways for Product Teams
• References

The Core Principles of Jobs to Be Done

The JTBD framework is built on a few key tenets that distinguish it from other customer-centric methodologies:

1. Focus on the ‘Job’: Customers don’t buy products; they ‘hire’ them to make progress in their lives. The ‘job’ is the progress a person seeks to make in a given circumstance.
2. Circumstance is King: The ‘job’ is not static. It’s defined by the specific context, situation, and struggles the customer is facing.
3. The Struggle is the Opportunity: Understanding the customer’s pain points, frustrations, and unmet needs in achieving their desired progress is where innovation opportunities lie.
4. Solutions Evolve: As customers’ circumstances and desired progress change, so do the ‘jobs’ they need done, and consequently, the products they ‘hire’.

This emphasis on progress and circumstance aligns with understanding the broader Product Development Lifecycle: From Idea to Launch.

Why JTBD Matters for Product Development

Adopting a JTBD mindset can fundamentally improve product development outcomes by:

• Reducing Development Risk: By focusing on validated customer ‘jobs,’ you reduce the risk of building something nobody wants.
• Driving Meaningful Innovation: JTBD uncovers unmet needs and frustrations that can lead to breakthrough product ideas, not just incremental feature updates.
• Improving Product-Market Fit: When a product is designed to perfectly execute a specific ‘job,’ it resonates deeply with the target audience, leading to stronger adoption and loyalty.
• Enhancing User Experience: Understanding the ‘struggle’ allows teams to design solutions that are intuitive and remove friction points.
• Guiding Prioritization: JTBD provides a clear framework for prioritizing features and development efforts based on what best serves the customer’s job.

JTBD vs. Traditional Approaches

Many product development teams rely on traditional methods that can sometimes lead them astray. JTBD offers a more robust and insightful alternative.

A Comparative Look

For instance, instead of asking a user "Do you want X feature?", JTBD might explore, "Tell me about the last time you tried to achieve Y outcome. What was difficult? What did you try before?" This aligns with the principles behind a Minimum Viable Product (MVP): The Ultimate Definition & Smart Applications, ensuring you build the core value first based on real needs.

Applying JTBD in the Product Development Lifecycle

Integrating JTBD isn’t a one-off activity; it’s a continuous thread woven throughout the product development process.

Step-by-Step Guide to Implementing JTBD

1. Identify the Core Job: Start by framing the problem you aim to solve. Ask: "What progress is a customer trying to make when they might seek out a solution like ours?"
2. Conduct JTBD Interviews: Move beyond surveys. Conduct in-depth interviews focused on the customer’s struggle and their past attempts to get the job done. Ask about their "struggle narrative" – the story of their efforts, what worked, what didn’t, and why.
3. Uncover Competing Solutions: Understand what customers are currently using to get the job done, even if it’s not a direct competitor. This could include manual workarounds, other product categories, or even simply doing nothing.
4. Map the Job & Circumstance: Detail the context, the steps involved in getting the job done, and the anxieties or anxieties associated with it.
5. Define the Desired Outcome: What does success look like for the customer? What are the functional, emotional, and social aspects of completing the job well?
6. Develop JTBD-Driven Personas: Create personas not based on demographics, but on the specific jobs they are trying to accomplish and the circumstances under which they hire solutions.
7. Ideate & Prototype: Brainstorm solutions that directly address the identified struggles and facilitate the desired progress. Build prototypes to test your hypotheses.
8. Validate & Iterate: Test your solutions with users who are actively trying to get the job done. Gather feedback and iterate based on how well your product enables them to make progress.

This iterative process is essential for creating products that are not only functional but also resonate deeply with users, contributing to Inclusive Design Principles: Creating Products for Everyone.

Key Takeaways for Product Teams

• Shift Your Lens: Think of products as solutions to customers’ ‘jobs,’ not just collections of features.
• Listen for the Struggle: The real insights lie in understanding customer pain points and unmet needs.
• Context is Crucial: Recognize that jobs are deeply tied to specific circumstances.
• Embrace the Competition: Understand all the ways customers are currently trying to get their jobs done.
• Iterate Relentlessly: Continuously refine your product based on how well it helps customers achieve their desired progress.

By internalizing the JTBD framework, product teams can move beyond guesswork and build products that customers not only adopt but actively ‘hire’ for their most important tasks. This approach can be further strengthened by adhering to Inclusive Design Frameworks: Build Products That Truly Serve Everyone, ensuring your solutions are accessible and valuable to a broad audience.

References

• Christensen, C. M. (2001). The Innovator’s Dilemma: When New Technologies Cause Great Firms to Fail. Harvard Business Review. scholar.google.com
• Ulwick, C. M. (2002). Turn customer needs into commercial success. Ivey Business Journal. hbr.org
• Clayton Christensen Institute. (n.d.). Jobs to Be Done. christenseninstitute.org
• Ries, E. (2011). The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business. amazon.com
• Doblin, R. (2013). Ten types of innovation: The disciplines of innovation. Innovation Management. doblin.com
• The Boston Consulting Group. (2016). The Jobs-to-be-Done Innovation Framework. bcg.com

Featured image by Thirdman on Pexels