“Customers are not interested in your solution. They are only interested in their problems” So what job is your product, service solving? Which need is it addressing? You've been learning about the Jobs To Be Done framework and are excited to start using it for your own products. Great! But … how do you actually do it?
How do we take what we've learned about our customers and convey it to the rest of our team & organisation? What if the rest of your team has never heard of Jobs To Be Done? What if they just wanted you to dump everything into Personas & User Stories … or ever worse … a product requirements document?
Deeply inspired by Alan Klement’s New York meetup (even the text above is partly stolen) we want to exchange experiences with Berlin partitioners. Which related tools are you using to understand and document your users’ Jobs To Be Done? How do you apply the framework in product definition, hypothesis validation and design execution? How do you sell it others? In this informal meetup we look forward to connect anyone who’s interested in the framework and learn from each other.