Skip to main content

"Faster horse" vs customer development and market research


Yes, I will start from that quote by Henry Ford. The one has been quoted billion times, even though he probably never said that. Yet nowadays numerous people rely on that quote for their product strategy. Specifically, it's being used as an argument against market research.
- If I'll ask my customers what they want they will tell...
But you don't. You shouldn't ask your customers what they want. You should ask what their problems are.





Validating problems vs validating solutions

It's not either one or another. It should be both. You start with problems and then follow up with solutions.
You first need to answer why something needs to be build. Only after you need to figure out what exactly needs to be build.
Problem validation has its own techniques. Those might be: interviews, observations, feedback and data analysis. Solution validation has its own preferred methods: prototypes, MVPs, A\B tests.
Design Sprint is a great way to validate solutions, given that you have validated the problem in the first place. 

Popular posts from this blog

Fogg Behavior Model

Have you ever wondered why you do certain things? Why are some behaviors easy and joy to do while other not so? And your customers - have you ever struggled to understand their behavior?
BJ Fogg, from Stanford University, has created simple and powerful behavioral model for persuasive product design.


Product Vision: an elevator pitch for your product

On this blog, I write a lot about making data-driven decisions. But what if you just starting to think about your product? You have a vague idea and nothing more. No point to go for prototyping or even talking to customers as you don't know yet who to talk to and what to talk about. In such situation - start from creating a product vision.

2017: Less of How, more of What, and a little bit of Why

Focusing less on how (methodologies, frameworks, processes). For me, that was the most important product management trend in 2017. Surely, "Agile" talks are bottomless. Yet, I noticed a certain tiredness and dare I say, boredom among product community with regards to this topic.
- Maybe that's enough? Haven't we discussed that like thousand times? Shouldn't we all have that figured by now?