Jim and I both agree that JTBD is a good common currency between #designers, #productmanagers, and #developers in creating a #sharedunderstanding of what our customers perceive as value. You might start with assumptions about what jobs your customers are trying to get done (heck, you might even want to start with ChatGPT!), but you have to talk to real humans and validate your assumptions! Jobs to be Done is not a brainstorming tool: if you really want to create human-centered products, you have to (as our good friend Tomer Sharon always says) “get out of the building,” either physically or metaphorically, and learn about the job performers. Here are some of the highlights of our discussion: Jim also gave us a sneak peek of his JTBD Canvas 2.0. We had some interesting questions and discussed the challenges of integrating JTBD into the product development lifecycle. Together, we delve into the essence of the Jobs-to-be-done ( #JTBD) framework and explore how it enables innovation to happen at more granular levels of product development, and to what extent #AI can help I recently had the opportunity to interview Jim Kalbach, author of The Jobs to Be Done Playbook and Chief Evangelist at Mural, during SAP’s UX Immersive Week. I wonder if Mr Ulwick (or any of his followers) can tell me where I went wrong. In 1990 I developed my Ripose approach with its Caspar software compiler (containing multiple 'canvas' templates) using my experiences in the following genres:įrom the 1st 12 I identified the 'things' that were needed to create the integrated Ontological & Taxonomical 13th approach. Ulwick must have been able to identify all the 'things' required to help others use the jtbd canvas In 2016 he released his 2nd second book titled “Jobs to be Done: Theory to Practice”. In 2002 the HBR published his article “Turn Customer Input into Innovation". I am curious to find out what experiences Tony Ulwick used to develop his Jobs-to-be-done Template.Īccording to my research (Google & Wikipedia) Mr Ulwich began working on innovation strategies in 1980 while working at IBM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |