As a Design Thinking facilitator and practitioner, I am often asked:
What is the difference between Jobs to Be Done and product features?
How would you distinguish between them in your own work?
More importantly, how does understanding Jobs to Be Done become an integral aspect of effective Design Thinking?
This article will reveal, in the simplest language, what this concept entails and why it is vital for creating meaningful and impactful solutions.
The Challenge of Distinguishing Jobs to Be Done and Features
Distinguishing between Jobs to Be Done and features is often easier said than done. It requires a discerning eye and a deep understanding of the underlying motivations of users. Have you ever found yourself adding features that seemed useful but didn’t truly address the customer’s needs? This is a common pitfall, and it highlights the importance of having a well-versed facilitator to guide the process. Such a facilitator can help you uncover the real “job” your product or service is being hired to do and ensure your efforts are directed toward creating value rather than complexity.
The Essence of Jobs to Be Done
The Jobs to Be Done theory, popularized by Clayton Christensen, focuses on the fundamental tasks or problems customers aim to solve. But have you ever wondered why customers choose one solution over another? These “jobs” are not merely tasks but underlying motivations driving customer behavior. They represent progress a customer seeks in a specific context.
Example: A parent buying a bedtime storybook is not just purchasing a book (product) but seeking to bond with their child and help them relax before sleep (job to be done).
Features: The Building Blocks, Not the Solution
Features are the tangible aspects of a product—functionalities, design elements, or specifications. Are your product features genuinely solving user problems, or just adding noise? While features add value, they should be developed with a clear understanding of the job they support. Without this alignment, features risk becoming gimmicks rather than meaningful enhancements.
Example: Adding interactive sound effects to the storybook might seem appealing, but if it overstimulates the child instead of calming them, it fails to fulfill the job of aiding relaxation.
Bridging the Gap with Design Thinking
Design Thinking emphasizes empathy, ideation, and iterative prototyping—a process perfectly suited for distinguishing between jobs and features. How can you ensure your next innovation is more than just a feature-packed product? Here’s how Design Thinking bridges this gap:
- Empathize: Engage with users to uncover their true motivations. What progress are they trying to make? What frustrations do they face?
- Define: Clearly articulate the core job to be done, avoiding premature focus on features. Are you solving the right problem, or just treating the symptoms?
- Ideate: Brainstorm solutions that directly address the job. Are your ideas directly aligned with your user’s needs?
- Prototype and Test: Develop minimal viable solutions and test them with users. Have you tested whether your features truly deliver on the user’s desired progress?
Practical Takeaways for Product Teams
- Start with the Job, Not the Feature: Begin product development by deeply understanding the user’s job to be done. Are you asking the right questions to uncover these jobs?
- Validate Feature Relevance: Continuously test whether features contribute to solving the user’s job or merely add complexity.
- Iterate Based on Feedback: Use prototypes to gather real-world insights, refining features to better support the job.
Conclusion
Incorporating the Jobs to Be Done framework within Design Thinking prevents the common pitfall of feature overload. Are you ready to shift your focus from building features to creating value? By focusing on the true progress users seek, product teams can create meaningful, user-centric solutions. Remember, features should serve the job—not the other way around. Aligning design efforts with user motivations ensures products that don’t just impress but truly matter.
Take the Next Step: Deepen Your Understanding of Design Thinking
Distinguishing between Jobs to Be Done and features is a skill that separates good designers from great ones. Are you ready to refine this skill and tackle complex challenges with confidence?
