Insights · Strategy

Jobs to be Done: what your customer actually hires your brand for

Most Jobs-to-be-Done projects end with a deck full of personas, which is precisely what the framework was invented to kill. The unit of analysis is a situation, not a person - and once you get that right, the list of who you compete with changes, usually uncomfortably.

Most Jobs-to-be-Done projects end with a deck full of personas, and personas are precisely what the framework was invented to kill. Somewhere between the interview guide and the workshop, "what progress is this person trying to make" quietly becomes "who is this person", and the output turns into a description of a buyer rather than an explanation of a purchase. The distinction sounds academic until you notice what it costs: a persona tells you who to target, a job tells you who you are actually competing against - and those answers are usually incompatible.

A job is a situation, not a person

The unit of analysis in Jobs-to-be-Done is a moment of struggle with a desired outcome attached. Not a demographic, not an attitude, not a segment. The same person has different jobs on a Tuesday morning and a Friday night, and will hire different products for each without any change in who they are. This is why segmentations built on customer attributes keep failing to predict behaviour: they hold constant the thing that varies and vary the thing that holds constant.

Get the unit right and a useful discipline follows. You stop asking what people want, which produces polite fiction, and start reconstructing what happened: what were they doing before, what triggered the switch, what did they compare, what almost stopped them, what did they stop doing once they started with you.

The fire and hire ledger

The most productive question in a JTBD interview is not about your product at all. It is: what did you stop doing when you started using this? The thing that got fired is the real competitor, and it is frequently not in your category, not in any category, or simply "carrying on as before".

Run this on thirty recent switchers and count the answers. If more than half name something outside the category you compete in, your category map is wrong and every share number built on it is measuring the wrong denominator. That is not a research finding; it is a strategy finding, and it usually arrives as an unwelcome surprise to whoever owns the market-share chart.

Ask what they stopped doing, not what they like. The thing they fired is the competitor your category map does not contain.

Why the wider competitive set changes decisions

Once the real alternatives are on the table, three decisions move. Pricing stops being benchmarked against the nearest branded rival and starts being benchmarked against the cost of the fired behaviour, which is often zero. Product roadmaps stop optimising attributes nobody was comparing and start removing the friction that nearly stopped the switch. And communication stops describing the product and starts depicting the situation, which is what makes a brand come to mind at the moment the job arises.

That last point connects JTBD to how brands actually grow. A job well understood is a category entry point made concrete - the situation, trigger and outcome that should cue your brand. We have argued separately that brands grow by reaching more buyers in more situations, and jobs are how you find out which situations are worth being present in.

Where JTBD misleads you

Two honest limits, because the framework is oversold. First, JTBD explains switching, not scale. It tells you why someone chose you in a moment; it does not tell you how many such moments exist or how to reach them. Teams that treat a well-articulated job as a growth plan end up with beautifully argued products in front of too few people.

Second, articulated jobs are not always the operative ones. People rationalise. The interview reconstructs a story that has already been edited for coherence, and the reported trigger is sometimes a post-hoc justification for a habit. This is why the ledger question - what did you stop doing - outperforms the aspiration question: behaviour leaves evidence, intent does not.

What a usable job statement looks like

A job you can act on names the situation, the progress and the constraint, in that order, and contains no adjectives about your product. "When a supplier misses a delivery window, help me tell the client before they notice, without admitting fault in writing." That sentence sets the competitive set, the success test and the design brief at the same time. Compare it with "customers want better communication", which sets nothing and survives every workshop because it offends no one.

How we run it

This is Insight Booster work: switch interviews reconstructed as timelines rather than opinion surveys, the fire and hire ledger built from what changed in behaviour, and jobs written to the situation-progress-constraint standard above. Second Sight then tests the resulting map against what the category data actually shows, because a job set that no purchase pattern supports is a hypothesis, not a finding. The point of the exercise is never the language. It is a corrected list of who you are competing with, which changes price, roadmap and message at once. Our strategic advisory page explains how this sits in a wider engagement, and the competitive consequences are the subject of challenger go-to-market.