In other words, if this feature falls flat, we learned that we need to pivot. That is a good thing! Stop investing in something that doesn’t produce results.

In order to provide that level of safety, I need clean and transparent automation and controls. When Etsy has a developer release code on the first day of employment, it’s not (necessarily) because that code will revolutionize the business. It communicates to that developer that you will make an impact every day, and we are not fearful of you making mistakes.

There are many things that we can dig into on team structure, transparent communications, etc., but I hope that’s a bit of a start

We learn most effectively in production.

This is why I spent a little time discussing cognitive load. Another way to frame that same topic is “risky.” If I’m reponsible for absolutely everything, then I feel at risk. I will move much slower. So, can my automation and best practices, audit and compliance by asserted via intentions at build? Then code delivery takes that load and risk off of the table for me. I think that’s where we are moving.

I was working with a very hierarchical org and the executive really made it a point to say over and over “we will fail, but we will fail forward.” And then backed that up with revamped information sharing on learning objectives, etc.