Get product resources, conference updates, along with access to an exclusive Slack channel by subscribing below.
When Jobs to be Done backfires
Stefano Zorzi reminds us that Jobs to Be Done is “a tool and it is not any better than the way it gets used”. And that you have to be careful to avoid the “outcome trap”. It’s one thing identifying an outcome (the hole, not the drill) for your product, but you are then faced with the prospect of having to actually deliver it.
Discovering why people buy your product (and why they fire it)
In his talk at INDUSTRY 2015, Chris Spiek of the Rewired Group spoke of how people decide to use, or not use, your product. This video provides hugely valuable tactics for getting to the heart of why people choose to buy things and will help you create messaging that works every time.
What I learned from doing 100 Jobs-To-Be-Done interviews
You cannot take a shortcut with JTBD interviews. The more you do, the better you get and the clearer insights and trends will become. After Amrita Gurney hit the 100 interviews mark, she made a note of what she learned during the experience.
A JTBD interview often jumps between being highly structured and very loose. It’s important that you allow the conversation to meander and to dig deep into talking points. But to understand the full timeline of the customer’s purchase event, you must ask all the right questions. Jason Evanish lists many great examples, along with general tips on how to approach interviews.
We, Product Collective, recently had the great fortune to work directly with Bob Moesta, one of the key architects of the Jobs to be Done (JTBD) framework, on a series of interviews with former attendees of our conference, INDUSTRY. We recorded the whole thing and wrapped it up in a three-part podcast where you’ll get to hear us preparing, conducting and dissecting the interviews.