There is a particular kind of manager who is deeply involved in everything and yet somehow never actually close to the work. They attend every meeting. They ask for constant status updates. They want to be copied on every email. They weigh in on decisions that are nowhere near their level. And yet, despite all of that involvement, they do not actually know what is going on. They are micro-managing from 50,000 feet — controlling everything in theory while understanding very little in practice.
I have seen this pattern more times than I can count. And I have seen the damage it does.
What It Actually Looks Like
Micro-managing from altitude is harder to spot than the classic version, where a manager is looking over someone's shoulder telling them how to type. The high-altitude version feels more sophisticated. The manager is "engaged." They are "across" the project. They are "asking the right questions."
But what they are really doing is creating drag. Every decision gets escalated. Every question waits for an answer from above. The team stops thinking independently because they have learned that it does not matter — someone will swoop in and redirect them anyway. People stop taking ownership. They stop bringing their full thinking to the work. Why would they? Their job has quietly been reduced to executing instructions.
This is what a top-down, leader-follower culture produces. Not bad people. Not lazy teams. Just people who have been trained — gradually, through daily experience — that the thinking happens somewhere else.
Turn the Ship Around
If you have not read Turn the Ship Around! by L. David Marquet, I recommend it without hesitation. It is one of those rare leadership books that earns its reputation.
Marquet was a U.S. Navy submarine commander who took over the USS Santa Fe — a nuclear-powered submarine that was performing at the bottom of the fleet. Morale was poor. Retention was the worst in the Navy. The crew was disengaged. By any measure, it was a troubled organization.
What he found when he got there was not a bad crew. It was a crew that had been conditioned to wait for orders. They had spent their careers in a leader-follower system — one where the person at the top knows all, tells all, and everyone else executes. When Marquet arrived, he had actually been trained on a different class of submarine. He did not have all the technical knowledge his crew had. That turned out to be exactly the wake-up call he needed.
Early on, he gave an order that was technically impossible on that submarine. His crew tried to follow it anyway. When he asked why, the answer was simple: because you told us to. That moment crystallized the problem. He had a crew of capable, experienced people who had switched off their own judgment in favor of following instructions. The system had done that to them.
Leader-Leader, Not Leader-Follower
Marquet's response was to flip the model. Instead of a leader-follower structure — where control and decision-making sit at the top — he moved toward what he called a leader-leader model. The idea is straightforward: push authority down to where the information actually lives. Stop moving information up the chain so that someone at the top can make a decision. Instead, move decision-making down to the people who already have the information.
One of the most practical changes he made was in language. He stopped his crew from saying things like "I request permission to..." and replaced it with "I intend to..." The difference is not trivial. The first phrase is a follower phrase. It puts the responsibility for the decision on whoever grants permission. The second phrase puts the responsibility on the person making the statement. They are telling you what they are going to do and why. You can engage with their reasoning, but ownership stays with them.
The results were not subtle. Within a year, the Santa Fe went from the worst-performing submarine in the fleet to one of the best. Performance improved. Morale improved. And perhaps most telling — in the years that followed, a disproportionately high number of officers who had served under Marquet on the Santa Fe went on to become submarine commanders themselves. The leadership model he created did not just fix a broken organization. It grew leaders.
What This Means for Software Teams
Software delivery teams are not submarines, but the dynamics are more similar than you might expect. The work is complex. The people doing it are often highly skilled and closer to the actual problems than anyone above them in the org chart. And yet, those teams are frequently led in a way that undercuts that expertise — through excessive approval chains, constant check-ins, and managers who are technically uninvolved but organizationally everywhere.
The result is the same thing Marquet found on the Santa Fe before he changed things. People wait to be told what to do. They stop volunteering information. They stop taking initiative. Not because they are incapable, but because the system has taught them that initiative is not really welcome.
Competence without authority is frustrating. Authority without competence is dangerous. Marquet argues that real leadership is about building both — making sure the people closest to the work have the knowledge to make good decisions and the authority to actually make them.
The Hard Part
The hardest thing about Marquet's model is that it requires the person at the top to let go. He is honest about that in the book. His instinct, every time something went wrong or felt uncertain, was to step in and take control. That instinct does not go away. You have to consciously work against it.
Most micro-managers are not villains. They are people who care about outcomes and are anxious about things going wrong. Staying in control feels like the responsible thing to do. But what they are actually doing is preventing their team from developing the judgment and confidence to handle things without them. And the team's ceiling becomes the manager's personal bandwidth — which is always limited.
Good leadership is not about being less involved. It is about being involved in the right things. Set the direction clearly. Make sure people have what they need. Remove the obstacles that the team cannot move on their own. And then trust the people you hired to do the work they were hired to do.
That is not hands-off management. That is what real leadership looks like.
Turn the Ship Around! by L. David Marquet is widely available and well worth your time, whether you lead a team of five or five hundred.
