If you like this content, consider joining the Newsletter to get access to all the podcasts, videos, content, articles, original and curated in your inbox.
– Jobs remain the same, the products we hire to do those jobs change. It’s true but much more complicated than that – Alan’s viewpoint and maybe we need to rethink that.
– JTBD in making software products. Jobs Data vs Usability/User Experience Data.
– While making software products, how to find jobs that people would hire your product to do?: Feedback Loops, Catalysts, Constraints.
– Why User Persona is flawed, not with their intent, but as a model. Behaviour & Motivations are demographic agnostics.
– Replacing User Story with the Job Story: When ____, I want to ____, So I can ____
Another way Alan is using Job Story is making them for products that don’t exist.
– How to do Switch Interviews or Jobs To Be Done Interviews. Difference between Switch Interview & Customer Development Interview.
– How to prioritize for multiple Job stories people are hiring your product for?
– Jobs to be Done is not a series of steps to be done, but a theory to understand how the market operates, what causes consumers to buy & use products.
– What is JTBD and what it is not?
Resources mentioned:
Book: “Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days” by Jake Knapp, John Zeratsky & Brad Kowitz
Book: “When Coffee and Kale Compete: Become great at making products people will buy” by Alan Klement
Book: “Competing Against Luck: The Story of Innovation and Customer Choice” by Clayton Christensen, David Duncan, Karen Dillon, & Taddy Hall
If you like this content, consider joining the Newsletter to get access to all the podcasts, videos, content, articles, original and curated in your inbox.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRead More
