Even Steve Blank came around to the idea that something was missing. The fuzzy front end of innovation requires targeting data. Only then does prototyping become more effective, and precise.
I encourage you to look beyond Jobs-to-be-Done 'light' and immerse yourself in ODI or one of the adaptations that have recently emerged (Strategyn Alums) that make it faster, cheaper and even more effective.
Thanks Mike. I appreciate you sharing these resources.
The point I'm trying to make here is that you can test things before you build something, not that you'd start with random stimulus or prototypes in the hopes of getting to an answer. In a previous post I did break down how we define a problem (including a user, functional need and deeper need), which is fairly systematic.
This post definitely does not cover the whole process for innovating on something new.
Even Steve Blank came around to the idea that something was missing. The fuzzy front end of innovation requires targeting data. Only then does prototyping become more effective, and precise.
I encourage you to look beyond Jobs-to-be-Done 'light' and immerse yourself in ODI or one of the adaptations that have recently emerged (Strategyn Alums) that make it faster, cheaper and even more effective.
ODI = Outcome-driven Innovation
Thanks Mike. I appreciate you sharing these resources.
The point I'm trying to make here is that you can test things before you build something, not that you'd start with random stimulus or prototypes in the hopes of getting to an answer. In a previous post I did break down how we define a problem (including a user, functional need and deeper need), which is fairly systematic.
This post definitely does not cover the whole process for innovating on something new.