Goodbye MVP, Hello V1

You've done it! It all started with an idea and two people in your garage. After weeks of coding and tweaking, you've proven that your business idea is the greatest thing since sliced bread. You used the Build, Measure, Learn cycle to find out what your customers want, and you're pretty sure you have a product market fit.

Now what?

It's time to build your V1. In the post, we'll look at how to take the most important lessons from the information you've gleaned during the MVP stage of your product's lifecycle and apply them to building the first full release of your product.


Read More

Actually MVP

In the startup world, there is a lot of talk about building Minimum Viable Products (MVPs). At this point, the concept has become so well-accepted that it has almost become a kind of unquestioned dogma. Yet there is a lot of disagreement about what MVP is exactly, and how to carry it out. Many people in the software industry assume that they know what MVP means, and claim to be using the process, but their production workflow tells a different story.

When it comes to building software, it is often tempting to take an approach akin to building a skyscraper: write the blueprints, obtain the necessary prequisites, then build it to spec. But software is a quickly shifting market. A businessperson may think she knows what the market wants, and plan and begin a project to meet that desire. But by the time the product is built, the needs of consumers have often morphed in a direction that she could never have foreseen.

In this post, we'll take explore some common misconceptions about MVP, some different ways to approach building one in software, and how to best use this tool if you're the CEO or CTO of a startup, a product manager for an established company, or a consultant.

Read More