In the world of product development and user experience, asking the right questions is paramount. Too often, teams jump straight to solutions or focus on surface-level preferences, missing the deeper motivations that drive user behavior. This is where the Jobs-to-be-Done (JTBD) framework shines, offering a powerful lens through which to reframe our understanding of user needs and, consequently, our research questions.
JTBD shifts our focus from what customers *are* or *do* to what they are *trying to accomplish*. It’s about understanding the fundamental problem a user is trying to solve, or the 'job' they are 'hiring' a product or service to do. By adopting this perspective, we can craft research questions that uncover true needs, leading to more innovative and successful solutions.
What is Jobs-to-be-Done (JTBD)?
At its core, JTBD posits that people don't buy products; they 'hire' them to make progress in specific circumstances. A 'job' is not a task or an activity, but a higher-level goal or struggle a person is trying to resolve. For example, someone doesn't simply buy a drill; they hire it to make a hole, because the deeper 'job' is to hang a picture, or perhaps even to create a more personalized and comfortable home environment.
This framework encourages us to look beyond demographics or feature sets and instead concentrate on the functional, emotional, and social dimensions of a user's desired progress. It's about understanding the 'why' behind their actions, the obstacles they face, and the ideal outcome they envision when trying to get a particular 'job' done.
Why Traditional Research Questions Fall Short
Many traditional research questions inadvertently guide us towards incremental improvements rather than transformative insights. Questions like "Do you like this feature?" or "How often do you use X?" often yield data about existing solutions or preferences, but they rarely uncover the underlying struggles or the true 'job' the user is trying to get done. This can lead to building products that are technically sound but fail to resonate because they don't address a deep-seated need.
Focusing solely on current behaviors or stated desires can also be misleading. Users might articulate a need for a 'faster horse' when their real job is 'to get from point A to point B more efficiently.' Without understanding the 'job,' we risk optimizing the wrong thing or, worse, missing entirely new opportunities to help users make progress.
Shifting Your Perspective: From Features to "Jobs"
Reframing your perspective to JTBD means moving away from product-centric thinking to customer-centric thinking. Instead of asking what features customers want, ask what life improvements they are trying to make. A common way to articulate a 'job' is using a structured statement, for instance: "When I [situation], I want to [motivation], so I can [desired outcome]."
For example, instead of thinking about a video editing app's features, consider the job: "When I've captured a memorable family event, I want to quickly assemble a highlight reel, so I can easily share a polished story with loved ones without spending hours learning complex software." This highlights the situation, the core motivation (quick assembly), and the ultimate goal (easy sharing, polished story). This perspective immediately opens up different avenues for research and innovation.
Crafting JTBD-Powered Research Questions
Once you've identified potential jobs-to-be-done, your research questions should aim to validate and deepen your understanding of these jobs. They should explore the context, motivations, struggles, and desired outcomes associated with making progress on that job. The goal is to uncover the unmet needs and hidden challenges that existing solutions might not be addressing.
- What are the various situations that prompt you to try and [get job done]? (e.g., 'What prompts you to want to organize your digital photos?')
- What obstacles or frustrations do you encounter when you try to [get job done] today? (e.g., 'What makes it difficult to find the perfect gift for someone?')
- What are the emotional or social factors at play when you are trying to [get job done]? (e.g., 'How does it feel when you successfully teach your child a new skill?')
- What would a 'perfect' outcome or ideal scenario look like for you when trying to [get job done]? (e.g., 'Describe the ideal way you'd like to manage your personal finances.')
- What sacrifices or trade-offs do you currently make to [get job done]? (e.g., 'What compromises do you make to eat healthy on a busy day?')
- What are you currently doing or 'hiring' to help you [get job done], and what aspects of that solution do you find lacking?
These questions move beyond 'what' users do to explore 'why' they do it, 'when' they do it, and 'how' they feel about the entire process. They push you to uncover the full story of the job, revealing opportunities for truly innovative solutions.
Benefits of JTBD Framing
Leveraging JTBD to frame your research offers several significant advantages. Firstly, it provides a stable foundation for innovation. Jobs are enduring; solutions come and go. Understanding the core job means your insights remain relevant even as technology evolves. Secondly, it fosters a deeper empathy for users by focusing on their struggles and aspirations, not just their interactions with your product.
Furthermore, JTBD helps product teams align. When everyone understands the 'job' a product is meant to do, it clarifies priorities, streamlines decision-making, and ensures that all efforts contribute to a common, user-centric goal. It moves discussions from feature debates to value creation, leading to more impactful product strategies and superior user experiences.
Practical Tips for Implementation
To effectively apply JTBD in your research, start by observing users in their natural environments. Look for instances where they struggle, cope, or invent workarounds. These are often clues to unmet jobs. Conduct qualitative interviews where you don't just ask about product usage, but delve into their life context, their aspirations, and the journey they're on. Encourage them to tell stories about their experiences.
Remember, the goal is to understand the underlying progress they are trying to achieve, not just the steps they take. Be open to surprising insights and challenge your own assumptions about why people use products. Continuously iterate on your JTBD statements and refine your research questions as you gather more data. This iterative process will deepen your understanding and lead to more precise and impactful product decisions.
Sources & Further Reading
- How to Formulate Great UX Research Questions — Interaction Design Foundation
- User Motivation: How to Understand What Drives Your Users — Interaction Design Foundation
- Qualitative research — Wikipedia








