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
-
-
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
Show this thread -
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
Show this thread -
The hardest part about that, it seems, is valuing that outcome above your own ego
Show this thread -
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"
Show this thread
End of conversation
New conversation -
-
-
Yeah I think this is super important. In the good version of "Iterate fast, fail fast" it should reduce the amount of bluster necessary to get people to try something, because you've got structures that lower the costs of running experiments. If you keep the bluster, though...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

