Why are visible role models of quiet leadership so rare, given that it's more effective?
I mean, look at historical proof: we have had great leaders in the industry that were quiet types, almost hidden in plain sight. A lot of great companies you don't really hear about in the news, yet, their products are ubiquitous in the every day life of many. The trick? They don't make a fuss, they just keep showing up with the goods.
And that's both the good and bad thing with this style of leaders: you don't necessarily hear about them, and thus, you don't know how good they are at their job.
Until you are in the room with them, until you are in one of their shop or factory, you don't know they are there. Their work and the culture they have instilled has made their product a staple, something you expect to have, and yet you have no idea how it came in your possession really.
Who do we hear from though? The loud mouths, the ones spending so much time talking on a megaphone and stand that you absolutely know their name and hear they come even if you are not in their industry.
So why does this matter in software?
Because building good software is fundamentally incompatible with loud leadership. Software is built through consensus, craft, and emergence — three things that wilt under force. You cannot shout a system into being elegant. You cannot compress a team into producing their best work by announcing urgency louder.
I've watched this play out. A co-founder tells the team a five-day piece of work can be done in three. He calls it "wartime mode." The engineers hear something different. They hear: your estimate doesn't matter, your craft doesn't matter, what matters is that I feel like we're moving fast. The work gets done in three days. It's brittle. It ships. Six weeks later someone else pays for it.
The quiet leader in the same situation does something invisible: they prepare. They build the planning rhythm so that when the real emergency arrives — and it will — the team already knows how to respond. They don't need to shout because the structure does the work. "Don't Panic" isn't a slogan. It's what happens when you've prepared what can be planned, so you can handle what can't.
The visibility trap
But here's the thing — nobody writes a case study about the incident that didn't happen. Nobody profiles the leader whose team just... delivered. Consistently. Without drama.
This is the structural attention bias at work. Loud leadership is legible. You can see it. You can photograph it. You can put it on a conference stage. Quiet leadership is invisible until you've lived inside a team it has shaped. It's not rare because it's absent. It's rare because it's hard to see.
And because it's hard to see, it's hard to replicate. Junior engineering managers look for role models and find the forceful ones — the ones whose names they know. So they copy what's visible: the decisiveness, the authority, the speed. Not the patience. Not the kindness. Not the persistence.
Actually, we do have a few examples
Captain D. Michael Abrashoff took command of the USS Benfold — one of the worst-performing ships in the US Navy's Pacific Fleet — and turned it into the best. He didn't do it by shouting louder than the previous captain. He did it by listening. He interviewed every single sailor on the ship. He asked them what was broken and what they would change. Then he changed it.
The results were extraordinary. Retention went from the worst in the fleet to the best. Combat readiness scores went up. The ship won awards. And Abrashoff's method was almost comically simple: treat people like they have something worth saying, then act on what they tell you.
The Navy — not exactly a quiet institution — noticed. But here's what's telling: Abrashoff's story only became visible because the results were so dramatic they couldn't be ignored. If he'd taken a mediocre ship and made it good, we'd never have heard of him. The quiet approach needed an extreme outcome just to become legible.
That's the trap. Quiet leadership produces steady, compounding results. But steady and compounding doesn't make the news. It doesn't get the keynote. It doesn't go viral. So the examples exist — they're just buried under the noise of everyone else performing urgency.
The hardest test comes from above
And this is where quiet leadership faces its hardest test — not from the team, but from above.
Because quiet leadership doesn't look like much is happening. The planning rhythm is in place. The team is building confidence in a new way of working. Estimates are getting more honest. Delivery is becoming more predictable. But it's the first cycle. Maybe the second. The pattern hasn't had time to compound yet.
And so the founder walks into the room and says: "Why aren't we moving faster?"
Not because the team is failing. Because the progress is invisible to someone who measures speed by how much motion they can feel. They've seen two cycles of a new approach and already they're reaching for the lever. Switch the process. Add more pressure. Try something else. Three weeks isn't enough patience for a methodology that needs three months.
What they don't see is that every time they pull that lever, they reset the clock. The team was just starting to trust the rhythm. Now it's gone. A new one will come next quarter. The engineers learn the real lesson: don't invest in the process, it'll change before it matters. And so they stop trying to make it work. They just wait for the next one.
This is what quiet leadership is up against. Not a lack of evidence — a lack of patience from the people who hold the authority to let it run. The irony is sharp: the very leaders who ask "why aren't we faster?" are the ones ensuring they never find out.
The cost is quiet too
Engineers leave managers, not companies. This isn't new data. But it's worth asking which managers they leave. The ones who create clarity and space? Or the ones who create urgency and noise?
The loud manager gets results that look like velocity. The quiet manager builds the team that's still there in eighteen months — still shipping, still learning, still suggesting improvements because someone actually listens.
Thomas Riboulet is a Fractional VP of Engineering working with European tech companies. He writes about engineering leadership, team structure, and sustainable delivery at insights.wa-systems.eu.