Jobs-to-Be-Done Research

Switch interviews, job statements, job maps and outcome surveys that show what progress customers are trying to make, what they hire instead of you and what makes them switch.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Jobs-to-Be-Done Research, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

🧩 Product Management

Jobs-to-Be-Done Research

Using the jobs-to-be-done lens to learn what progress customers are trying to make, what they hire products for and what makes them switch.

  1. Choosing your jobs-to-be-done method
  2. First core functional job statement
  3. Job performer, buyer and supporting roles
  4. Research brief for the first job study
  5. Recruiting recent switchers for interviews
  6. Interview consent, recording and incentive set-up
  7. Switch interview guide and timeline sheet
  8. Job research repository and tagging scheme
  9. Team assumptions about why customers buy
  10. Weekly switch interview rhythm
  11. Monthly four forces synthesis
  12. Firing interviews with recent cancellations
  13. Mining sales calls and tickets for job evidence
  14. Quarterly job map review
  15. Customer job language glossary
  16. Monthly job research readout
  17. Hiring and firing log across the product
  18. Annual job landscape study
  19. Practising switch interviews in mock sessions
  20. Reconstructing a purchase timeline
  21. Writing desired outcome statements
  22. Uncovering emotional and social jobs
  23. Asking about past behaviour, not hypotheticals
  24. Coding a transcript into the four forces
  25. Building a universal job map
  26. Telling big hires from little hires
  27. Outcome importance and satisfaction survey
  28. Choosing which underserved outcomes to target
  29. Competing solutions and non-consumption list
  30. Outcome-based segments from survey data
  31. Job stories in place of user stories
  32. Reducing anxiety and habit in the purchase path
  33. Job fit review of the next roadmap bets
  34. Defining the market by the job
  35. Struggling feature re-examined through its job
  36. First ten switch interviews in 30 days
  37. Job synthesis workshop with the product trio
  38. Teaching the job lens to sales and support
  39. Job findings at the annual planning session
  40. Two-week job sprint before a major bet
  41. Founder-led job interviews before product-market fit
  42. Lone researcher supporting several product teams
  43. Job research across a B2B buying committee
  44. Job research on a small team with no budget
  45. Inheriting someone else's job research
  46. Pivot check through recent customer switches
  47. Demand-side sales script from switch stories
  48. Choosing a job-based growth strategy
  49. Tracking the job across product generations
  50. Measuring the four forces with a switching survey

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Choosing your jobs-to-be-done method

Jobs-to-be-done is really two traditions sharing a name: the switch interview school associated with Christensen and Moesta, which studies the moments people change solutions, and Ulwick's outcome-driven innovation, which measures dozens of desired outcomes by survey. Mixing them without deciding produces interview guides that ask for both and deliver neither.

First tasks

  • Write down the product decision this research must help you make
  • Read one primer from each school and note what each produces
  • Pick the primary method and write two sentences on why
  • Share the method choice and glossary with the product trio

First core functional job statement

Good job statements name the progress a customer wants, not your product: a verb, an object and a context, as in 'get a supplier invoice approved before the payment run'. Teams that skip this keep describing jobs as features, such as 'use the dashboard', which ties all later research to today's solution.

First tasks

  • Write three versions of the core job, each starting with a verb
  • Strike out any word that names your product, a feature or a technology
  • Test each version against the twenty-year stability check
  • Log the strongest draft as hypothesis one in the repository

Job performer, buyer and supporting roles

In many purchases the person getting the job done is not the one choosing or paying: a nurse uses the device that procurement buys, a teenager uses the app a parent pays for. Naming the job performer, the purchase decision maker, whoever installs or sets up the product and whoever supports it keeps each interview aimed at the right person for the right question.

First tasks

  • List everyone involved from first search to daily use for one recent customer
  • Mark who performs the core job and who signs off the spend
  • Write the buyer's own job in one line
  • Set how many interviews each role gets in the first batch

Make it yours.

Install Jobs-to-Be-Done Research, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.