A Job to Be Done (JTBD) is what a potential customer is ultimately trying to accomplish, framed independently of any solution they are currently using. In BRI Associates' methodology, JTBDs are the anchor for understanding why customers act, which outcomes they actually value, and what would make a new product or business compelling enough to switch to. A well-formed JTBD is solution-agnostic — 'get groceries home,' not 'use a delivery app' — and stable over time: the job 'keep my home comfortable' outlived fireplaces, furnaces, and smart thermostats. BRI states every working JTBD in a three-part syntax — verb + object of the action + clarifying context — for example, 'reduce time-to-decision when evaluating a new strategy hypothesis.'
A JTBD is not the activity a customer performs, the solution they use, or the steps they take. Each of those locks thinking into the current way of doing things; a solution-agnostic job opens the design space to better alternatives. BRI classifies each job by a single job type — Functional, Emotional, or Social (situations that span more than one are expressed as related JTBDs, not a single job wearing three hats) — and by the performer who holds it. In enterprise settings the four performers — primary user, purchase decision maker, technical/compliance approver, and admin user — are rarely the same person, which is precisely why deals stall when a job analysis covers only the primary user and misses the decision maker's and approver's distinct jobs.
JTBD is the methodological entry point to BRI's Strategy Framework. Jobs are defined across the nine phases of the customer journey — Discovery through Retirement/Exit — and then translated, through a direct and traceable mapping, into the Market Requirements a whole solution must satisfy. Three connections make the job the load-bearing input:
Inside Growth Forge® Software, JTBDs are the first structured input that flows into the evaluation and portfolio decisions the platform supports, drawing on BRI Associates' decades of practitioner experience.
The idea has deep, citable roots. Harvard's Theodore Levitt seeded it in the 1960s with the observation that customers don't want a quarter-inch drill — they want a quarter-inch hole. Clayton Christensen formalized "jobs to be done" as innovation theory in The Innovator's Solution (2003) and Competing Against Luck (2016). Tony Ulwick built the most granular school, Outcome-Driven Innovation (What Customers Want, 2005), decomposing each job into dozens of fine-grained outcome statements.
BRI's contribution is not a new definition but a calibration. BRI positions its practice as a deliberate middle path between Ulwick's high-resolution decomposition and the coarse single-main-job treatments common in practice: four canonical pieces per job (syntax, journey phase, job type, performer), one job type per JTBD, and a direct JTBD-to-Requirement mapping with the measurement attributes living on the requirements, not the jobs. The result is enough structure to drive real solution decisions without more analytical overhead than a project's stage warrants.
BRI's contribution extends past articulation into operationalization. Where a concept like JTBD is instantiated in Growth Forge® Software, it is delivered not as a static template but as an interactive, guided tool — with structured, inline guidance and built-in AI assistance — that walks a practitioner through framing jobs correctly and carrying them downstream into requirements and evaluation. Embedding that practitioner experience directly in the tool, rather than leaving it in a consultant's head or a slide deck, is itself part of what BRI adds.