2
0 Comments

A concrete "Jobs to be done" example

Jobs to be done style interviews always struck a cord with me. I've found examples of how to do interviews, but not many examples of actual output or next steps after the interviews.

We've started doing sales calls at LaunchNotes. As part of my notes process I'm using the "forces diagram" tool from JTBD to understand where people are in their buying journey and what they need to make progress with LaunchNotes.

I thought it'd be useful to share the forces diagram from a recent call with real data.

Each quadrant is a force that's influencing someone's ability to make progress in their current situation. Our job is to address any negative forces and help map our product offering to positive forces. A breakdown of the forces are below:

Push: What's happening in this person's life such that the status quo is no longer working?

Pull: What have they identified as a possible solution to the progress they want to make?

Habit (of the present): What do they need to leave behind or let go of to make this change?

Anxiety: Now that they know about a potential solution what are they worried about?

Taking notes in this way has been extremely useful in understanding specifically how people can switch. It's something I'm referring back to constantly for subsequent conversations with evaluators.

Hope this is useful!

on December 19, 2019
Trending on Indie Hackers
AI runs 70% of my distribution. The exact stack. User Avatar 180 comments I'm a solo founder. It took me 9 months and at least 3 stack rewrites to ship my SaaS. User Avatar 143 comments I used $30,983 of AI tokens last month in Claude code on $200/mo plan User Avatar 45 comments We could see our AI bill, but not explain it — so I built AiKey User Avatar 25 comments AI coding should not turn software development into a black box User Avatar 24 comments my reddit post got 600K+ views. here's exactly what i did User Avatar 19 comments