B2B jobs-to-be-done research: Five steps from interviews to messaging

Jobs to be done research asks what progress a buyer was trying to make when they chose a product, rather than what they say they want. In B2B, each person on the buying committee is trying to make different progress, so you interview several roles, code the forces behind each decision, and write one job statement per role.

You're an operating partner, or the CEO of a company you have just bought, and the buyers now entering the pipeline are not the ones the website was written for. Asking them what they want rarely settles it, because several people take part in a B2B purchase and each wants something different. This method shows what each is trying to get done.

Key takeaways

Why B2B buying decisions involve more than one job to be done

The theory behind jobs to be done treats a product as something a buyer hires to make progress in a particular situation. An operations director does not buy a scheduling system for its features. They hire it to keep the business running while they change how it works.

The interview method and four forces below come from Bob Moesta and Chris Spiek of the Re-Wired Group, within a theory associated with Clayton Christensen, and the four forces of progress are set out by their authors.

B2B adds a complication: The person who signs is rarely the only one deciding, and each role makes different progress. Research that talks to one role finds one job and misses the rest.

Map the buying committee before you start interviewing

Start with the roles that took part in recent purchases. These examples are illustrative, and your own list will come from the interviews:

RoleThe job they are trying to get doneWhat they worry about
Operations directorChange how the business runs without disrupting itA rollout that goes wrong on their watch
Finance leadSpend money they can defend to the boardA cost they cannot explain later
Technical reviewerAdd nothing that breaks security or integrationsA risk nobody else has noticed
Day-to-day userGet through the week with less reworkLearning a tool that adds work
CEO or sponsorHit the numbers in the planMissing the date

Roles such as the technical reviewer often never speak to sales, which is the gap what win/loss misses describes. Interviewing them is how you hear their job at all.

Interview 15 to 20 recent buyers across the roles, and reconstruct the purchase in order

Talk to people who bought in the last 6 months, while the story is fresh, and include a few lost deals. Ask each person to walk you through the purchase from the first thought to the decision: What was happening, what they tried, who else was involved, and what nearly stopped it. The question guide and the follow-up probes are covered in customer discovery interviews.

Read what you already own first. Recorded sales calls and support tickets give you a hypothesis to test, and voice of customer research sets out those sources. Record every call, because the exact phrasing is what you are collecting.

Stride runs this as the Validation Sprint, from EUR 5,500 over 6 to 8-weeks, with 15 to 20 buyer interviews and a jobs-to-be-done analysis.

Code every interview for four forces: Push, pull, anxiety, and habit

A purchase happens when the forces pushing a buyer forward outweigh the forces holding them back. For each interview, mark the quotes that show each force:

Teams tend to write most about pull, where the product's strengths sit. Anxiety and habit are the forces that stall deals, so they often hold the most useful findings.

Write one job statement per role, in the buyer's own words

A job statement has a simple shape: When this situation arises, I want to do this, so I can reach this outcome. Take the wording from the transcripts rather than from your own vocabulary. For the operations director in the table, it might read: When we outgrow our current system, I want to change it without disrupting live operations, so I can keep my team and my clients confident.

A useful test is whether the statement describes the progress the buyer wants to make without naming a particular product or solution. Different products may help buyers achieve the same job. Make the statement specific by including the situation that triggered the need and the outcome the buyer wanted. Statements supported by only one interview should remain hypotheses until another source backs them.

Turn each job statement into a message, a sales question, and a content brief

The statements pay off once they reach the people writing and selling, and each one produces 3 things:

Job statementMessageSales questionContent brief
Change the system without disrupting live operationsSwitch with the business running as normalWhat would have to be true for the change to feel safe?An implementation page that answers what could go wrong
Spend money I can defend to the boardA cost you can explain in one pageWho needs to approve this, and what will they ask?A one-page business case the buyer can forward

The messages then sit in the structure described in brand messaging framework, with each one tied to the evidence behind it.

How buyer interviews changed positioning at a 60-person software company

Take a newly acquired Nordic software company we work with: Around 60 people, 600+ customers, two marketers, no CMO. The product was strong, most deals arrived by word of mouth, and the website was written for the smaller customer the company was leaving behind.

Interviews with 15 to 20 of the larger buyers it was now winning, coded by role, showed that the job the website addressed was not the job those buyers were hiring for. The job statements became the brief for the positioning rewrite, with content and search following, then the systems work, and new markets held for later.

FAQ

What is jobs to be done research, and how does it work?

It is qualitative research that reconstructs a recent purchase to find the progress the buyer was trying to make. You interview recent buyers about the timeline from first thought to decision, then code what pushed them, what pulled them, what worried them, and what held them in place.

How is jobs to be done research different from win/loss analysis?

Win/loss runs every month against deals that reached a decision, to explain individual outcomes. Jobs to be done research runs at a turning point, covers the whole buying committee, and produces job statements that shape messaging. Win/loss analysis sets out the monthly routine.

How many interviews does jobs to be done research need at a company of 40 to 200 people?

Aim for 15 to 20, spread across the committee roles and across recent wins and lost deals. Positioning workshop or buyer interviews explains when a full round is needed and when a workshop is enough.

Can you run jobs to be done research without a specialist researcher?

Yes, if someone senior who was not on the deal runs the calls and codes them. The skill is staying on the timeline of what happened rather than asking what buyers want, and recording every call so the exact phrasing is kept.

What do you do with the job statements after the interviews?

Turn each into a message, a sales question, and a content brief, and check each against the evidence behind it. Statements only one buyer expressed stay as hypotheses until a second source supports them.

Turn buyer research into messaging your sales team can use

Map the roles, interview 15 to 20 recent buyers, code each conversation for push, pull, anxiety, and habit, and write a job statement for every role. Then hand each statement to writers and sales. No random acts of marketing.

If you need to understand why buyers choose a product before updating the positioning of a company you have acquired, explore how Stride approaches buyer research and positioning across a portfolio. The aim is to turn real customer evidence into a message your marketing and sales teams can use.

Ready to put your content to work?

Book a discovery call