The Accelerator and the Brakes
Mastering Feedback Loops
In my article on Donella Meadows’ Leverage Points, we explored how engineering leaders are, in essence, system designers.
We shifted away from low-leverage interventions (like tweaking Jira story points) to high-leverage moves like shifting cultural paradigms.
But there is a middle layer that deserves an article entirely of its own: Feedback Loops and Information Flows.
As an engineering leader, we actively manage feedback loops every single day. We bounce between two extremes: offering vague, unhelpful praise or delivering relentless “constructive” criticism that grinds our teams down.
To build an autonomous, high-performing engineering culture, you have to understand the difference between Reinforcing Loops, Balancing Loops, and the critical process of Amplification.
The Two Loops of Leadership
In systems thinking, there are two types of feedback loops that govern how a system behaves.
1. Reinforcing Loops (The Accelerators)
Reinforcing loops compound. They amplify a behavior or result. In software, it’s tech debt (bad code makes it harder to write good code). In leadership, it’s how you scale culture. When you praise an engineer for writing excellent documentation, they write more of it, others see it, and a culture of documentation grows.
The Trap: Vague Reinforcement. Saying, “Hey, good job on that release” is empty calories. The engineer feels a momentary ego boost, but the system doesn’t learn what specific behavior to repeat.
The entire article is available only for paid subscribers. You can use the training budget (here’s a slide for your HR). Thanks for supporting Practical Engineering Management!
