Move Fast and Break Things

Who said that

Mark Zuckerberg did.

Moving fast enables us to build more things and learn faster. However, as most companies grow, they slow down too much because they’re more afraid of making mistakes than they are of losing opportunities by moving too slowly. We have a saying: “Move fast and break things.” The idea is that if you never break anything, you’re probably not moving fast enough.

I totally agree on the idea. However, like doing startups, the idea is important but what really matter is execution. How do you interpret “move fast and break things” affects the direction of the team. If you are in the wrong direction and move fast, there is no guarantee that you can go back to where you were even you “move fast” again.

Be able to move fast

Depends on the scale of your product, there should be different way to move fast. For new product or just a prototype, you should collect user feedbacks, move fast, break things, get on the right direction as soon as possible. That is the speed you needed to survive in the industry.

What’s next? You have some users, using your app everyday, but not yet the giant scale. To get more users, you need to keep moving and this is another type of moving fast. This time, you cannot just move fast and break things like the time when you start. From development point of view, as the code complexity increase, unless you have a good infrastructure, you will find that it is getting harder and harder to add features on top of it. When you add one feature, you may introduce two bugs, and slowed the app down at the same time. Beside that, there is a cost when you break things, maybe get some bad rating, maybe pissed off some users.

This does not mean you should not move fast, but you have to do it smart. You have to be clear on what you want to achieve from moving fast. If you want to try out new interface and get user feedback, it does not need to be 100% polished, but don’t rollout a 20% done ugly version, all you can get is bad rating instead of constructive feedback about the new features.

I agree on moving fast, but I also believe in “less is more” (slow is fast?). At the end of the day, it is all about what the users want, new features may boost your number a little bit, but sometimes quality is what makes the users come back and use your app and not switching to other competitors.

Instead of running on your foot, isn’t it better to get a bike or a car if you want to move fast?

When you break things

Please, fix it, before you break another thing.

Reference

Comments