Thread by @imightbemary

The push to execute quickly--to "move fast and break things" is easy to vilify. It thrashes the team, leads to accumulating tech debt, and tends to be motivated by poorly weighed risks-reward tradeoffs. But IMO, speed is not the enemy as much as a lack of humility is

If you're moving fast to test hypotheses and figure out what works in practice vs. theory, you're going through a helpful exercise of reducing risk. It prevents you from investing a ton of effort into scaling something that leads you straight into a dead end

If you DON'T have a hypothesis or you're not willing to accept that you may be wrong, that's when speed is the enemy

I get that there's a certain amount of bluster necessary in business. Sometimes you gotta put on a brave face to instill confidence in ideas that seem crazy but have the chance to work. They might not, but it's easier to convince people of things if you seem like you believe them

But even if this IS what you're doing, if you plan to just rush through to the end without any thought for how you'll evaluate your progress as you're going... well, there's a good chance you'll get what you deserve

A circular, iterative workflow might actually end up being faster if done right, at least in that it will help you course correct earlier and more reliably steer towards a good outcome

The hardest part about that, it seems, is valuing that outcome above your own ego

So by all means, move fast! But if you do, you better pay attention and have a destination in mind other than "I was right"