> For example, if you add a QA step before work goes to production, you’re adding a whole set of work that needs to go back and forth before things can be relea

> For example, if you add a QA step before work goes to production, you’re adding a whole set of work that needs to go back and forth before things can be released. The reason that stuff goes back and forth between engineering and QA is that it didn't work. When choosing between "releases take a little longer", and "releases have bugs", taking the extra time is a no-brainer. Engineers don't like their code getting rejected, so it also teaches them to spend a little extra time not shipping obviously buggy code. Everybody wins.