Jobs Beat Demographics: Personas Built on the Purchase, Not the Person

Two customers with nothing demographic in common can be buying the same product for the same job, and they will respond to the same page. Two identical demographics buying for different jobs will not.

Demographic personas describe who bought. Job based personas describe what the purchase was hired to do, and the second description predicts what a page should say far better than the first. The jobs to be done research associated with Clayton Christensen's school of thinking keeps landing on the same finding: a retired engineer and a young renter buy the same drill, the same paint, the same storage boxes when the job matches, a room ready for a baby, a landlord inspection survived, a move completed in one weekend. Their demographics would put them in different personas with different creative. Their job puts them on the same page, asking the same questions in the same order: will it fit, how long will it take, what else do I need, what happens if it goes wrong. Build the persona around the job and the page writes itself from the job's anxieties. Build it around age and income and you get tasteful creative that answers questions nobody on the page is asking.

The job has a situation, a struggle, and a success picture

A usable job statement is specific enough to exclude people. Not improve my home, but get a room ready before a deadline, with a budget ceiling, while living in the room during the work. The situation supplies the constraints the page must respect, time, money, mess, skill. The struggle supplies the content order: the thing most likely to go wrong is the thing the page should address first, not the brand story. The success picture supplies the proof: not a happy customer portrait, but the finished state described the way the customer describes it to themselves.

Interview for jobs by interviewing about the last purchase, in forensic detail. First thought, search, shortlist, the moment of doubt, what nearly stopped the sale, what the product replaced. People cannot tell you their persona. They can tell you that story, and the job is sitting in the middle of it, usually attached to a date and a trigger event.

Related reading on this site: PersonaRail and Personas Expire at Life Events, Not at Quarter End cover the neighbouring problems in more depth.

Where demographics still earn their place

Jobs do not erase demographics, they demote them. Media buying still needs reachable audiences, and language, channel, and price presentation still flex by who the customer is. Compliance and accessibility needs are demographic in part. The error is ordering: demographics as the persona's skeleton and the job as decoration produces segments that are easy to buy media against and impossible to write for. Job as the skeleton, demographics as targeting metadata, produces pages that convert and campaigns that can still be bought.

Watch for the job that splits by budget in the middle. Same job, same anxieties, but one customer's success picture includes hiring help and the other's includes doing it alone over two weekends. That is one job persona with a fork in the path, not two personas, and the page should fork visibly rather than averaging the two customers into a third who exists nowhere.

Test a job persona by what it deletes

A good persona's practical value is mostly deletion. It tells the landing page which five questions matter and, more usefully, which twenty do not. If a proposed job persona cannot get anything cut from the page, it is a mood board, not a persona. The drill job above deletes brand heritage, deletes the professional range's story, deletes three feature blocks, and promotes a size guide, a time estimate, and a what's in the box list to the top. That is a persona earning its keep in the only currency that matters: decisions that would otherwise have gone the other way.

Frequently asked questions

What is a jobs to be done persona?

It is a customer profile built around the job the purchase is hired to do: the situation, the struggle, and what success looks like for the customer, rather than demographic traits. Customers with different demographics often share a job and respond to the same information in the same order.

How do you research a job based persona?

Interview customers about a specific recent purchase in detail: what triggered it, how they searched, what they shortlisted, what nearly stopped them, and what the product replaced. The job and its anxieties emerge from that story more reliably than from asking customers to describe themselves.

Do demographic personas have any remaining use?

Yes, as targeting and presentation metadata: media audiences, channel choice, language, and accessibility needs. The weakness is using demographics as the core profile for message and page decisions, where the purchase job predicts behavior better.

How can you tell if a persona is useful?

By whether it changes decisions, especially deletions. A useful persona determines which questions a page answers first and which content gets cut. If nothing would be built, ordered, or removed differently, the persona is decoration.