Most products start out as a response to a problem. An inconvenience is slowing people down, a situation is diminishing quality of life, and either no solution exists or the one that does exist is insufficient.
Something new is needed. So creative people come up with an original or improved way to fix the problem.
All product development teams start with the problem. But many become so enamored with their solution that they lose sight of the problem they’re solving during the development process.
They come up with new ideas to work into the product and functionality that’s “cool,” and they build the product the way they think users want it.
But the end result is a product that, while mostly meeting the need they set out to fill, misses the mark for the intended audience. The team said “yes” to the wrong things while neglecting some essential right things.
WHERE PRODUCT DEVELOPMENT TEAMS GET DERAILED
The traditional model for minimum viable product (MVP) development is Build, Measure, Learn. You quickly push something out into the marketplace that’s based on your best guess about what the market wants. You then measure how it performs, and then iterate based on what you’ve learned.
The problem is that measuring performance doesn’t really provide you with the information you need to iterate effectively. If you start with an MVP that doesn’t really match up with what the market needs, you’re left floundering. Measurement tells you what isn’t working, but it doesn’t tell you why it’s not working.
STAY FOCUSSED ON THE PROBLEM TO BUILD AN IDEAL SOLUTION
Product development teams can avoid this dilemma if they stay focused on the problem throughout the process. Before development even starts, dig deep into the problem your product will solve.
What consequences result from the problem? What ancillary problems are created by the main problem? What factors affect potential solutions?
The best way to fully understand the problem is to talk to those who deal with it on a regular basis. Interview people in your target market.
Find out as much as you can about the problem from their perspective:
- How do people in the target market describe their problem?
- What frustrates them the most about the problem?
- What have they already tried?
- What are must-haves that they can’t function effectively without?
- What’s not imperative to them?
Through the interview, you’re looking for qualitative data that you can’t get via quantitative measurement.
You’re looking for nuances, how target users feel, what they see as most important.
A NEW MODEL FOR MVP DEVELOPMENT
Without first building a foundation (of thoroughly understanding the problem), measurement and iteration will be insufficient to create a successful product. I recommend tweaking the traditional model of MVP development:
Interview > Build > Measure > Interview > Learn
The interview process is essential at the beginning in order to build an MVP that can later be iterated into something successful. And it’s essential after the MVP is released, so you know what and how to iterate.
Also Read: Top three signs you’re done with your MVPs
In post-mortem evaluations of over 100 startups, CB Insights discovered that the primary cause of startup failure (in 42 per cent of cases) was “no market need.”
Almost half of these startups built a product before they understood the need for it or talked to the people they thought would buy it. Only running out of cash (the cause of 29 per cent of failures) and not having the right team (causing 23 per cent of failures) come anywhere close to downing as many startups.
When CB Insights asked startup founders to evaluate where they went wrong, the founders overwhelmingly said that they were more focussed on solving an interesting version of the problem, rather than solving the real problem as it existed.
The team at Patient Communicator wrote, “I realised, essentially, that we had no customers because no one was really interested in the model we were pitching. Doctors want more patients, not an efficient office.”
The only way to find out what your target market really wants is to talk to them.
The article Building a Better MVP: How to Say “No” to the Wrong Things So You Can Say “Yes” to the Right Things first appeared on Startups.co.