In Part 1
we discussed a process for realizing product market fit that begins with the bottom of the pyramid: understanding your market, defining your target user/customer and understanding their needs.
Now we’ll move to the top of the pyramid and discuss a method for defining your product.
Define your value proposition
A value proposition is a promise to your users that illustrates how your product will address customer needs better than any alternative. Out of all the potential customer needs your product could address, which ones matter most.Which will have the biggest impact and take the least amount of time and effort to produce?
The value hypothesis defines the what, the who, and the how:
What: the product you are building
Who: the user with a significant need for the product is desperate for
How: the business model employed to deliver the product; the marketing strategy used to drive growth
Specify your minimum viable product (MVP)
Now that you’ve defined the value you intend to deliver, you need to specify how to deliver that value as quickly and simply as possible. This means saying no to a myriad of great ideas and having the evidence to establish the confidence you need that what you say yes to has a high probabilistic outcome of providing significant user value.
You can’t afford to spend months developing a large number of features, only to discover that your base hypothesis simply isn’t resonating in the market. By that time you’ve burned through your capital and it’s time to call it quits.
The MVP approach is aimed at building only what is needed to create enough value in the eyes of your target customer to validate that you are heading in the right direction.
It’s relatively easy to enumerate a laundry list of customer needs, but a hell of a lot harder to reduce that list to just the one or two needs you will tackle first.
Steve Jobs once said:
“People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. I’m actually as proud of the things we haven’t done as the things I have done. Innovation is saying no to 1,000 things.”
You need to figure out how your product will be substantially different from what is already in the market. What will make your product great, immediately obvious to whoever uses it? What unique features of your product will users praise?
This is the essence of product strategy.
Customers, co-workers, bosses, the media, and investors will tell you that your MVP is lacking this and that. And they aren’t wrong. These gaps will be filled over time. One needs to combat these remarks by reminding stakeholders that the questions you are seeking to answer are the following: a) is our value proposition resonating in the market?; and b) is our hypothesis right and are our base features instilling trust with users and confidence that we are on the right path?
Create a prototype
Most companies skip this step, which is costly and foolish. No matter how much research you’ve done, you simply do not know how your product will be received until people are actually using it (or not).
To mitigate risk, create a functional, but non-production ready prototype so you can, as quickly as possible, get a facsimile of the product in front of real users. Don’t worry about scalability or architecture. Focus entirely on the user experience and functional capabilities, as experienced by the user.
Today there are a handful of excellent products that make the process of creating usable prototypes relatively painless and easy. InVision and other product design tool companies are innovating in this area at an incredible pace. So there is no excuse to skip this critical step.
Assuming that you received valuable feedback from your prototype testing and have the confidence that your MVP will work, it’s time to build the actual product. Again, I wouldn’t worry too much about scalability and elegant architecture design at this stage. You still haven’t proven you have something people want, so why worry about scale?
Consider providing pre-release access to a small number of qualified users, and just like with the prototype, instrument the product and provide channels for qualitative feedback. Keep iterating with this group until you’re confident that you’re ready to go broad and launch the product with the necessary marketing and communications muscle to get the word out.
About 30 days after shipping your MVP, do a deep and objective analysis of the impact. What’s working? what’s not? what features should we add or lose? The answers to these questions constitute your roadmap and the iterations to come.
After analyzing the customer feedback, you may want to revise your hypothesis based on what you learned and loop back to an earlier step in the process. The feedback will determine which step you should return to. If you only need to improve your UX design, then iterate on that. But if your hypothesis is fundamentally flawed, or target customer needs have changed, be honest with these shortcomings and go back to step one.
You may conclude that in order to achieve higher levels of product-market fit you need to pivot (change one or more of your major hypotheses).
Ideally, customers love your product, consider it easy to use, and find it of great value. Congrats, you now have a real business. You have validated your key hypothesis and have designed a product with a strong product-market fit. With this knowledge, you should feel comfortable raising and investing the resources required to scale your product to meet demand in other parts of the world, or in adjacent industries with similar problems.
Thanks for reading. In the next issue I’ll kick off a multi-part series on product planning & impact analysis using OKRs (objectives & key results).