User interviews are a cornerstone of effective UX research, offering direct insight into the minds of those we design for. However, simply asking users what they want, or what they think of a specific feature, often yields superficial or misleading data. To truly understand user needs and motivations, we need a more profound approach – one that moves beyond surface-level desires to uncover the underlying reasons for their actions.

This is where the Jobs-to-be-Done (JTBD) framework becomes incredibly powerful. By adopting a JTBD lens, designers and product managers can structure interviews that dig deeper, revealing the fundamental 'jobs' users are trying to accomplish, the struggles they face, and the progress they aspire to make. This article will guide you through applying JTBD principles to your user interview process, helping you uncover richer, more actionable insights.

Understanding Jobs-to-be-Done (JTBD)

At its core, Jobs-to-be-Done posits that people don't simply buy products or services; they 'hire' them to get a specific 'job' done. This 'job' isn't just a task; it's a fundamental problem a user is trying to solve, a goal they want to achieve, or a desired change in their life circumstances. For instance, someone doesn't want to buy a quarter-inch drill bit; they want a quarter-inch hole. But even that's not the full job – they want to hang a picture, display art, and ultimately improve the aesthetics of their living space. The product is merely a means to an end.

The JTBD framework shifts our focus from product features or user demographics to the circumstances, motivations, and desired outcomes surrounding a user's decision to seek progress. By understanding the 'job' and the context in which it arises, we can design solutions that truly resonate and deliver value, rather than simply adding more features that might miss the mark.

The JTBD Interview Mindset

Approaching an interview with a JTBD mindset means moving away from asking direct questions about your product or hypothetical scenarios. Instead, the goal is to elicit stories about past experiences. Users are generally poor at predicting future behavior or articulating abstract needs, but they are excellent at recalling what they did, why they did it, and what they struggled with in the past.

Think of yourself as an investigative journalist, not a salesperson. You're trying to understand the full narrative of a user's journey to accomplish a specific job. What triggered them to start? What obstacles did they encounter? What alternatives did they consider? What was the desired outcome? This narrative-driven approach helps uncover the emotional and functional dimensions of the job, providing a rich tapestry of insights that mere feature feedback cannot.

Crafting Your JTBD Interview Questions

The art of a JTBD interview lies in asking open-ended questions that encourage detailed storytelling. Avoid leading questions or those that can be answered with a simple 'yes' or 'no'. Focus on the 'who, what, when, where, why, and how' of their past experiences related to the job you are investigating. Here are some question types and prompts to get started:

  • "Walk me through the last time you tried to [achieve a goal related to the problem space]. What led up to that moment?"
  • "What initially triggered you to start looking for a solution or a better way to do this?"
  • "As you were trying to accomplish this job, what were the biggest challenges or frustrations you encountered?"
  • "What did you ultimately hope to achieve or improve by doing this? How would you define 'success'?"
  • "What alternatives did you consider, and what trade-offs did you make when choosing a solution?"
  • "How did you know when you had successfully completed the 'job'? What did that look or feel like?"

Remember to follow up on interesting tangents, probe deeper into moments of struggle or delight, and use techniques like the '5 Whys' to uncover root causes and motivations behind their initial statements.

Exploring the 'Forces of Progress'

A key concept within JTBD is understanding the 'Forces of Progress' that influence a user's decision to switch from an old solution to a new one, or to adopt a solution in the first place. These four forces are: the push of the old situation, the pull of the new solution, the anxiety of the new solution, and the habit of the old solution. By asking targeted questions, you can uncover these forces at play.

For example, to understand the 'push,' ask about frustrations with their current approach. To uncover the 'pull,' ask about the desired benefits they imagine with a better solution. 'Anxiety' might be revealed by questions like, "What worries did you have about trying something new?" or "What might hold you back from making a change?" Finally, 'habit' can be explored by asking, "What keeps you sticking with your current method, even with its imperfections?" Understanding these forces helps you identify barriers to adoption and design solutions that effectively overcome them.

Practical Tips for a Successful JTBD Interview

Beyond question structure, successful JTBD interviews rely on strong interviewing skills. Practice active listening: be present, avoid interrupting, and pay attention to both verbal and non-verbal cues. Let the user talk, even if it means silence. Don't be afraid to ask for clarification or to rephrase a question if you sense confusion. Recording the interview (with consent) and transcribing it afterward is invaluable for detailed analysis, allowing you to focus on the conversation rather than extensive note-taking.

Focus keenly on moments of 'struggle' or 'workarounds' – these are rich indicators of unmet needs and opportunities for innovation. Interviewing multiple users for the same job helps you identify patterns and commonalities, distinguishing individual quirks from widespread needs. The goal is to collect enough detailed stories to build a robust understanding of the job and the context surrounding it.

Beyond the Interview: Synthesizing JTBD Insights

Collecting rich JTBD data is only the first step. The real value comes from synthesizing these insights. After your interviews, look for common 'job stories' – concise statements that capture the user's situation, motivation, and desired outcome (e.g., "When I am [situation], I want to [motivation], so I can [desired outcome]"). Identify recurring struggles, the forces at play, and the metrics of success from the user's perspective.

These synthesized job stories and insights become powerful tools for guiding product strategy, feature prioritization, and design decisions. They ensure that your team is building solutions that truly help users make progress in their lives, rather than simply adding more features to an existing product. By consistently applying a JTBD lens to your user interviews, you'll uncover deeper truths, leading to more impactful and user-centric designs.

Sources & Further Reading