the minimum viable product.
the most misunderstood concept in the world of lean startups.
and one of the most critical to get right.
why time to build doesn’t matter
in thispost about prioritizing,i argue that time to build shouldn’t be taken into consideration when deciding what to build next. you should always build the idea that will have the biggest impact onyour goalnext.
but what if you have a short runway or the most important thing also requires the biggest upfront investment?
this is where the concept of the mvp comes in handy. you can take any idea and distill it down to an mvp, something that you can iteratively test and refine over time.
your initial idea may be big. it should be. you should always start from the ideal. what is the best thing i can build to drive progress toward my goal?
bear in mind, there is a difference between “what are all the things i can build to drive progress toward my goal?” and “what is the best thing i can build to drive progress toward my goal?” at this point, we are focusing on a single idea.
getting to an mvp
now take that idea and ask yourself the following questions:
- what is the heart of this idea?
- how does the user derive value from this idea?
- what is the smallest piece of work we can do to capture that value?
remember, the smallest is different from the easiest. sometimes you have to tackle hard problems directly. but capture as much of the value as you can first.
this is where people go wrong with the idea of an mvp. the goal is to learn. not to learn just anything, but to learn what creates value. too often the value gets thrown out and replaced with something easy. the problem is, the easy idea might not offer much value. you have to balance minimum with viable.
minimum forces you to think small, viable forces you to create value. you have to do both in an mvp. –tweet this
so reduce as much as you can, but always do so in the context of delivering value.
you might think you’ve distilled your idea down to its simplest form. do it again.
and yet again.
for each element or user story, ask yourself, “how can i make this idea work if we didn’t build this?” if you can come up with an answer, cut it.
this can be hard. as you reduce the scope, remind yourself, it’s not that you won’t build that, it’s that you aren’t building it now.
i like to think of these as tomorrow problems. repeat after me, “that’s a tomorrow problem.”
too often, we don’t reduce scope because we think it’s now or never. this type of thinking will slow down development and kill your product. it’s not now or never. it’s now or tomorrow.
if you don’t get now right, you won’t have a tomorrow. be ruthless. –tweet this
keep reducing the scope as engineers build
steve blank likes to say, “no plan survives first contact with customers.” that’s true.
this is also true: “no requirement survives first contact with engineers.”
you cannot hand off requirements to your engineering team and think your job is done.
as they start to build, they will get a much better understanding of the job to be done than they could ever have while sitting around talking about it conceptually.
they will uncover hard problems. they will ask to change the scope. sometimes broader. sometimes narrower. they will need your help. stay involved.
what to do when something is impossible
your ideal might be impossible. but i guarantee a close approximation is not. it’s your job to find that close approximation.
there will be times when your engineers come to you and say that something is impossible. this isn’t what they mean. here’s what you should hear instead: the way they are currently thinking about this problem makes what you want impossible. you need to hep them think about the problem in a way that makes what you want possible.
there are a lot of debates about whether product people need to know how to code.
you don’t need to know how to code. but you do need to know how to make the impossible possible. –tweet this
you have to be able to hold your own in an engineering discussion. you need to know how to push back, to question assumptions, and to reframe the problem over and over again until it becomes solvable.
if you don’t have the ability to do this, you will not be a good product manager.
what to do when the scope grows
inevitably as engineers build, the scope will grow. bit by bit, they will ask, what about this corner case, can’t we add this or this, it will only take a couple of hours.
these are tempting. be ruthless.
i know this sounds counterintuitive. don’t dot your “i”s, don’t cross your “t’s.
you aren’t building a perfect product. you are trying to deliver as much value in as short of a period of time as possible.
always be asking yourself, “can i do that tomorrow?” if the answer is “yes,” do it tomorrow.
this flies in the face of everything you learn about planning ahead and productivity.
but your goal isn’t to get a lot done. your goal is to get the right things done. be ruthless. –tweet this
never stop looking for short cuts
it takes a lot of work to distill your requirements. it takes even more work to reign in the scope as engineers start to build. you need to create a culture around “less is more.” and you always need to be looking for how you can do less.
not because you are lazy. not because you can’t do more. and not because your team can’t do more.
but because your users don’t want more. they don’t want more features. they don’t want more options. they want value.
relentlessly focus on delivering that value.
are you up to the challenge? share your experience in the comments below.
on thursday, we’ll move on to look at how to measure success. don’t miss out.subscribe to the 瑞士vs喀麦隆水位分析 mailing list.