I’ve been in the move fast and break things domain. Unsurprisingly, things are often broken there too.
You have a valid point about red tape, but does it really amount to 2 steps forward, or is it the same one step, but 2 forward, 1 back?
I work in environments where moving fast is usually bad (Enterprise/Healthcare), so I'm honestly asking.
Knowing where you want to go and keeping your focus on that direction is probably the most important aspect of any environment. Iterating fast is a double edged sword that both allows quick fixes to happen while also encouraging an environment where those quick fixes are needed.
Iterating more meticulously feels a lot slower but can produce just as fast… sometimes a lot faster. For me, there is also an inherent stability component to slower iteration.
Perhaps, the best is neither approach on their own but a clever combination of the two?
I work in Healthcare, so the needs are a little different.
I'm glad I work in the field I do. I'm not sure my personality lends itself to move fast and break shit.
Like all things, YMMV. :)
Thanks for answering my question.