Oh this is nothing new “ uncover a high-priority problem that a significant segment of specific customers are struggling to solve today.”
What’s really tricky is how that plays out in real life especially if, like many founders, the whole business idea was seeded as an insider’s pain.
I am my target audience so I know the pain.
Which is not always the case. And even if so, it’s more multi-faceted than expected so we are really dealing with a package of inter-related maybe problem that need a lot, a lot of work to transform into valid, usable problem statements.
I believe you shared how OpinionX discovered that after months of sticking with what you thought was THE right direction.
I am facing that right now, and need to get back to the drawing board (granted I have not started the real user interviews yet!)
Thanks again for another excellent article, so much learning here.
I don't think I have saved these many articles of a single creator before. This was brilliant. It's a bit beyond my understanding but it was helpful nonetheless. I'll be coming back to refer your articles in the future.
"Match, Identify, Pitch, Assure" -- really great way to frame all of this. Big fan of splitting apart customer, product, and sales discovery.
What I am taking away is that when you perform discovery research, the context matters ALOT. More specifically the outcomes you wish to achieve. But it's tricky because the methodology & approach will be the same (talk to customers) and not knowing what you want to do with your findings can mess things up.
Quick question: Have you had any experience with JTBD (or outcome-driven innovation)? If so, how has it gone for you? If not, is there a particular reason why you stayed away from it?
Oh this is nothing new “ uncover a high-priority problem that a significant segment of specific customers are struggling to solve today.”
What’s really tricky is how that plays out in real life especially if, like many founders, the whole business idea was seeded as an insider’s pain.
I am my target audience so I know the pain.
Which is not always the case. And even if so, it’s more multi-faceted than expected so we are really dealing with a package of inter-related maybe problem that need a lot, a lot of work to transform into valid, usable problem statements.
I believe you shared how OpinionX discovered that after months of sticking with what you thought was THE right direction.
I am facing that right now, and need to get back to the drawing board (granted I have not started the real user interviews yet!)
Thanks again for another excellent article, so much learning here.
I don't think I have saved these many articles of a single creator before. This was brilliant. It's a bit beyond my understanding but it was helpful nonetheless. I'll be coming back to refer your articles in the future.
"Match, Identify, Pitch, Assure" -- really great way to frame all of this. Big fan of splitting apart customer, product, and sales discovery.
What I am taking away is that when you perform discovery research, the context matters ALOT. More specifically the outcomes you wish to achieve. But it's tricky because the methodology & approach will be the same (talk to customers) and not knowing what you want to do with your findings can mess things up.
Quick question: Have you had any experience with JTBD (or outcome-driven innovation)? If so, how has it gone for you? If not, is there a particular reason why you stayed away from it?