There is a myth that moving fast means writing bad code. In practice, the fastest teams are often the most disciplined. They ship quickly because they have clear boundaries, not because they ignore them.
What slows you down
Meetings that could be messages. Approval chains that add days but not value. Bikeshedding over variable names while the feature request sits untouched. Most slowness is organizational, not technical.
What actually helps
Small pull requests. Automated tests for the paths that matter. Deploying to production multiple times a day so each change is small and easy to roll back. The goal is not to be reckless. The goal is to reduce the cost of each individual change so you can make more of them with less risk.
Ship small, ship often, and fix forward.