All the best engineering advice I stole from non-technical people
&gt; <i>Effective teams need trust. That’s not to say that frameworks for decision making or metrics tracking are not useful, they are critical — but replacing trust with process is called bureaucracy.</i><p>A thousand times this. Highly effective teams have super high levels of trust and mutual accountability.<p>The moment you lose trust, you now have to replace trust with some other type of mechanism. This leads to process&#x2F;bureaucracy.<p>Trivial example for those that don’t “get it”: think about why do we need code reviews? If we knew people would write perfect code every time, they would never be needed. However, we hold them because we know that even in our own “best code” we may miss something&#x2F;forget some detail.<p>However, think about your own process, at least for me, depending on a feature&#x2F;the engineer, my code review might be cursory rather than super line by line. The difference? How much I trust that engineers ability in that specific type of code.<p>But that was a digression, my main point is that hight trust means high speed, low trust causes slow speeds. The more you can build up trust and eliminate&#x2F;prevent process, the better your organization will be.<p>For anyone that wants more details on this, I highly recommend the book “The speed of trust” by Stephen Covey.