MVP, the right tool for complex system
Think about all systems you know about. Do you have an example of a system where the output comes back as an input?
This would be a complex system example. A system for which you should not make a static plan for obvious reasons: the input depends on the output (the system is routed back).
You just have to make a minimum planning. What is the initial thing you build to get you started?
The minimum effort to maximize the learning so you can make better informed decisions. This is the MVP, short for Minimum Viable Product.
The reality is: many systems around us are complex systems. And we are finally starting to look at these as complex systems. Finally we have learned a new set of tools to handle these systems.
For many decades we tried using non-complex systems tools for handling complex systems. But the geeks broke this vicious cycle. From the Silicon Valley a voice came out loud:
I really don’t know. Don’t ask me for a detailed plan. Instead I´ll build, measure and learn. Then I’ll repeat it as many times as needed.
Do you want a detailed plan? Sorry, I am not building a bridge, a building, or something I have done before. I am an entrepreneur. A real one. I am maximizing learning.
The system is complex, but you can work it out. It is quite simple. Keep the cycle small, so you can easily correlate input and output. But don’t stop there. You have to think about the next learning cycle. Given this output, what is the next input? What is the next MVP?