Progress as the Unit of Analysis
Jobs to be Done (JTBD) in UX research generally involves investigating the "progress" an individual seeks to make in a specific circumstance, transitioning from their current state to a desired one. Unlike traditional personas that often focus primarily on who the user is, JTBD focuses on what the user is attempting to resolve. The core concept suggests that people do not merely buy products; they "hire" them to do a job. For instance, hypothetically, a user might not hire a meditation app just to hear sounds, but to achieve a state of calm before a stressful meeting. This hypothetical scenario does not prove user behavior, but it illustrates how the research focus can shift toward the struggle for improvement, helping to identify where current solutions might fail to provide that breakthrough.
The Forces Shaping Change
To better understand why a user might decide to change behavior or tools, a UX researcher can investigate four commonly proposed forces: the Push of the current situation (existing pain points), the Pull of the new solution (the promise of progress), the Anxiety of change (fear of the unknown), and Habit or Allegiance (the comfort of the status quo). In contextual research practice, as suggested in general methodology guides like Contextual research and observation — GOV.UK, observing the user in their natural environment often allows for the identification of potential friction between these forces. However, for example, highly secure or remote environments might require alternative methods like diary studies instead of direct observation. It is generally advisable to distinguish between stated desires and observed behavior, as the latter may indicate the strength of habit hindering new adoption.
The Timeline of the Hire
Applying JTBD typically benefits from a chronological analysis of the decision-making process, though this is a suggested procedure rather than a universal rule. The researcher can map the journey from the "first thought" that something isn't working, through passive and active searching, to the moment of the "switch." During interviews, a common goal is to reconstruct the scene of the last time the user sought a solution. Design decisions based solely on statistical correlations may fall short if they ignore potential causality: what specifically triggered the search for progress? When you Know Your Customers’ “Jobs to Be Done” — Harvard Business Review, defining hypotheses about these temporal triggers can help avoid extrapolations based on superficial data.
Critical Boundaries and Distinctions
Practitioners generally advise against confusing JTBD with a feature list. The "Job" is often considered stable over time, while technology evolves. A common analytical mistake is treating behavioral associations as direct causality; just because users of a certain profile use a specific feature does not mean that feature caused their engagement or success. Research should aim to rigorously separate aspirational talk (such as a hypothetical user claiming, "I want to be more productive") from immediate functional and emotional needs. JTBD provides a useful framework for understanding context, but it does not replace usability testing. Usability tests remain a recommended procedure to help validate whether the proposed solution actually enables progress without creating new, unforeseen friction points.
Sources
- Contextual research and observation — GOV.UK
- Know Your Customers’ “Jobs to Be Done” — Harvard Business Review
Related reading
Your next discovery begins with a question.
Test an idea, observe the experience and bring evidence to your team.
Create my first studyFree · 1 study · 50 responses/month · no card
