JTBD framework

The JTBD framework is an analysis approach that focuses on the 'job' a user wants to do rather than the user's characteristics: what they are trying to achieve, in what context, what functional, emotional and social aspects this 'job' has, by what criteria they choose a solution and what dissatisfies them with current ones. We formulate job statements, identify unmet needs. Honestly about the nature of JTBD, this is key: JTBD is a useful lens and thinking tool, NOT a magic formula or a guarantee. It helps see deep motivation ('what they really want') and find opportunities, but by itself it does not create a successful product — it is an input for decisions that still need to be implemented and verified. Honestly about reliance on data: JTBD works on real user research (943), not armchair guesses about 'jobs'. Invented jobs are as harmful as invented personas — they cement assumptions. We derive jobs from real data, and if there is none — we will honestly say research is needed first. Honestly about 'one of the approaches': JTBD is not the only correct truth and not a replacement for everything. It complements personas (944) and CJM (946) well: personas are about 'who', JTBD is about 'why/what job'. We apply JTBD where it is genuinely useful for your task, not because it is trendy. Honestly about the effect: it helps understand motivation and find product opportunities, but it is an analysis tool, not a result guarantee. Honestly about access: research data (or conducting it) is needed. An important boundary: this is JTBD; research (the basis) — 943; personas — 944; CJM — 946. Picture this: instead of 'adding features blindly' — understanding what job people really solve with your product. The base price starts from 30,000 ₽ (assumes research data exists).

• It is unclear why people REALLY use the product.
• A focus on demographics, not the user's real task.
• Features are added blindly, without understanding motivation.
• It is not visible where unmet needs and opportunities are.

• Analysis of the 'jobs' a user solves
• Functional, emotional, social aspects of the job
• Formulating job statements and choice criteria
• Identifying unmet needs and opportunities
• Reliance on real research (943), not guesses
• Honest boundaries (a lens/tool, not magic/not a guarantee; one of the approaches)
• A link with personas (944) and CJM (946)
• Handover and review with you

• Understanding users' deep motivation
• Visible opportunities (unmet needs)
• A focus on the user's task, not just demographics
• Honest boundaries (an analysis tool; not a result guarantee)

• We take research data (943); analyze the 'jobs'
• We formulate jobs and choice criteria, identify opportunities
• We hand over conclusions, honestly set boundaries (one of the approaches) with you

• Does JTBD guarantee the product will be successful?

  No, honestly: JTBD is a useful lens and thinking tool, not a magic formula or a guarantee. It helps see deep motivation and find opportunities, but by itself it does not create a successful product — it is an input for decisions that still need implementing and verifying. We give an understanding of 'why', and the result depends on execution, as with any analytical tool.

• Can JTBD be applied without research?

  Better not, honestly: JTBD works on real user data (943), not armchair guesses about 'jobs'. Invented jobs are as harmful as invented personas — they cement assumptions and create false confidence. We derive jobs from real data; if there is none, we will honestly advise research first rather than composing job statements from the head.

• Is JTBD better than personas? What to choose?

  It is not 'better/worse' but different views, honestly. Personas (944) are about 'who the user is', JTBD is about 'what job they solve and why'. They complement each other well rather than exclude. JTBD is one of the approaches, not the only truth. We will honestly suggest what is more useful for your task (or their combination) rather than impose a trendy framework for its own sake.