July 5

Graduating from an MVP

Working on an MVP is somewhat like going to college. In both cases the goal is to learn things that position you to earn in the future. When you graduate from college you start a job, start a business, or go back to grad school. When you graduate from an MVP, you add to your product so that you can sell it, or you realize you have more to learn and change your direction. Here are some perspectives on how to go from learning to earning.

Moving Beyond MVP: Feedback, Features and Pricing Building a minimum viable product (MVP) helps you validate product hypotheses and attract new users to your service. But how do you expand your product beyond MVP? How do you price your platform appropriately when you aren’t sure of the right mix of features and value for users? Geoff Wilson explains how his team moves past an MVP in their digital products and shares how you can do the same.

(via @geoff352)

I Have my MVP ready  – what’s next? The goal of an MVP is not to produce half a product or to deliver a product quickly. The goal of the MVP is to help you understand what your target customer is looking for. Once you understand what your customers are looking for, you can move beyond the MVP to a more full featured minimum marketable product (MMP). Swarnendu De explains the concept of the MMP and how to take what you learned from your MVP to deliver a product your customers will love.

(via @swarnendude)

How to go From a minimum viable product to a minimum marketable product. When you’re delivering a new product, the minimum viable version of your product helps you understand your customers’ needs. The minimum marketable version helps you understand if it’s worth it to help your customer satisfy those needs. The folks at Snyxius explain that while going from MVP to MMP is “not a cake walk” there are some things you can do to make the move easier.

(via @snyxius)

Maybe your project could benefit from a “release map.” After Adam Piel & Shanfan Huang released an MVP of their iPhone app in 38 work days they stalled out. They weren’t sure what to build next. To help get them going they decided to refer back to the build measure learn loop. They asked “what do we want to learn?” and then “what can we measure?” in order to determine what to build. They created a physical release map to track their progress through those questions. Here’s the story of how they built that release map and used it to move past their MVP.

(via @chitchy)

This is what a pivot feels like. The next move after your MVP is not always a straight line to something you can sell. Sometimes you learn things from MVP that tell you you need to solve your customers’ problems in a different way, or you need to solve a different problem. Nino Lancette shares his recent pivot experience to help you make it through a similar experience.

(via @ninonline)

Kent J McDonald

About the author

Kent J McDonald writes about and practices software product management. He has product development experience in a variety of industries including financial services, health insurance, nonprofit, and automotive. Kent practices his craft with a variety of product teams and provides just in time resources for product people at KBP.media and Product Collective. When not writing or product managing, Kent is his family’s #ubersherpa, listens to jazz and podcasts (but not necessarily podcasts about jazz), and collects national parks.


You may also like

Deep-Dive: AI for Product Managers

Deep-Dive: AI for Product Managers

Deep-Dive: Product Operations

Deep-Dive: Product Operations