Jobs to be done product strategy consultant

Jobs-to-be-done is the most useful strategy lens in product management and the most frequently reduced to a slogan. Teams put "people don't buy drills, they buy holes" on a slide, rename their personas "jobs," and change nothing. Practicing JTBD means doing forensic interviews about real past decisions and letting the answers redraw your competitive map, which is the part teams flinch from.

What JTBD looks like when it's real

At WisOwl AI, the assumed job was "help recruiters find candidates," with other hiring platforms as the competition. JTBD interviews, walking recruiters through the last three roles they actually filled hour by hour, showed the real hiring workflow ran on WhatsApp groups, personal networks, and a spreadsheet. The real job was "fill this role this week without staking my reputation on an unknown." Our semantic matching engine mattered less than trust signals and speed-to-shortlist. We rebuilt onboarding and agent behavior around that, and it's a large part of how the platform reached 10,000+ jobseeker signups and 10+ recruitment-firm and startup customers organically.

At CaaStle, the same lens applied to subscription commerce. Many customers hired a clothing subscription for the recurring feeling of newness on a bounded budget, more than to own more clothes. That framing shaped retention features in ways a demographic persona never could have.

What a jobs-to-be-done engagement includes

• Switch interviews: 10–15 forensic conversations about real purchase and churn decisions: what triggered the search, what almost stopped it, what the product replaced.
• Job map and forces analysis: the progress your customers are trying to make, and the anxieties and habits holding them in place.
• Strategy translation: turning the job into positioning, onboarding design, roadmap bets, and a competitive map that includes the spreadsheets and WhatsApp groups you're actually up against.

Four to six weeks, and it pairs unusually well with a GTM or PMF engagement, since all three are ultimately the same question: what is your product hired to do, and how strong is the evidence?

Frequently asked questions

How is JTBD different from personas?

Personas describe who people are; jobs describe what they're trying to accomplish and why they'd switch to you. The same person hires completely different products in different circumstances, and the circumstance predicts behavior better than the demographic does.

How many interviews does a JTBD study need?

Ten to fifteen well-chosen switch interviews usually reach saturation: recent switchers in, recent churners out. Rigor comes from interview quality and case selection more than sample size.

Does JTBD work for B2B products?

Exceptionally well, because B2B purchases have traceable decision histories: triggers, evaluation committees, vetoes. Mapping the functional job alongside the buyer's personal job ("don't let this procurement embarrass me") explains most stalled B2B deals I've seen.

What do we do with the findings afterward?

The deliverable is built to be used: positioning language tested against the job, an onboarding critique, roadmap implications ranked, and the interview library itself, which teams keep quoting in decisions for a year afterward.

Related pages