Early in a project, I once sat in a kickoff where someone senior unrolled a genuinely beautiful vision. Big market, clear story, the kind of slide that makes a room sit up a little straighter. Then a quiet engineer asked a practical question — something about how one particular integration would actually work, given a constraint everyone in the room already knew about. The senior person smiled and said, "That's an implementation detail. Let's not get into the weeds." The vision stayed beautiful. But I watched a few people in that room quietly stop believing it.
I have been on both sides of that moment, including the wrong side. For years I assumed the highest form of seniority was to operate purely at the level of direction and leave the how to other people. It took a few painful projects to notice that the leaders I trusted most were never the ones standing furthest from the work.
Do things right, or do the right thing
Warren Bennis gave us one of the cleanest lines in all of management writing: managers do things right; leaders do the right thing. Management is about efficiency — process, control, doing the current work well. Leadership is about effectiveness — choosing the right work in the first place. It is the difference between climbing a ladder quickly and making sure the ladder is leaning against the right wall. As a way of seeing, it is genuinely useful, and the previous post in this series leaned on a cousin of it.
But a distinction this clean has a side effect. It is so satisfying that it can quietly turn from a lens into a hiding place.
When a true idea becomes an excuse
Robert Sutton, who studies how organizations actually function, made an observation I have never been able to un-see. Some of the least effective senior people use the very distinction between "leadership" and "management" as cover — a respectable-sounding reason to avoid the execution details they are, in fact, obligated to understand. "I'm a leader, I think about the big picture" becomes permission to stop learning how the work really gets done.
You can feel it in a room. Someone sketches a grand shape in the air — all dragons and phoenixes, as the Vietnamese saying goes — and then waves off the first hard question about how any of it would ship. The vision is not wrong, exactly. It is just floating, untethered from the craft that would have to make it real. And people who do the actual work can always tell the difference between a leader who has earned their altitude and one who is merely hiding up there.
Sutton's quiet correction to Bennis
Sutton rewrote Bennis's famous line in a way I find more honest: to do the right thing, a leader must understand what it takes to do things right. You cannot reliably choose the right direction if you do not understand the cost, the constraints, and the trade-offs of the path. A roadmap drawn without any feel for the work is not a plan; it is a wish with dates on it.
It is a little like planning an ambitious dinner party when you have never really cooked. On paper, the five-course menu looks wonderful, and everyone nods. It is only in the kitchen — one oven, one pair of hands, a dish that quietly needs two hours of its own — that you find out which parts of the plan were always a fantasy. The menu is the what; the kitchen is the how; and a menu written by someone who has never felt the heat of the stove tends to promise an evening the kitchen cannot actually deliver. Choosing the right wall sounds like pure judgment, something you can do from a distance. But you cannot choose well if you have no sense of how heavy the ladder is, how far it reaches, or how many people it takes to move it.
The skill is the bounce, not the altitude
The leaders I have learned the most from were not the ones who stayed highest. They had a fluid ability to move between the wide view and the smallest detail and back again, many times a day. Steve Jobs is remembered for sweeping product decisions, but he also argued about the spacing of fonts on the first Macintosh. Great film directors hold the whole story in their head and still adjust a single frame.
The point is not that everyone should obsess over kerning. The point is that their judgment stayed real because they never fully left the ground. This is worth separating clearly from micromanagement, because the fear of one often produces the other. The skill is the bounce — the willingness to drop into a detail when it matters and rise back out — not the altitude you cruise at.
Staying grounded without taking the keyboard
There is a real difference between understanding the details and owning them. Micromanaging is owning them — taking the keyboard, dictating the how, leaving people no room to think. Staying grounded is understanding them — enough to ask a sharp question, to feel in your gut when an estimate is fantasy, to make a trade-off that survives contact with reality.
You can hear the difference in a single sentence. "Help me understand the trade-off here" keeps you close to the craft while leaving the work in the hands of the people doing it. "Just do it the way I said" pulls the work into your hands and the thinking out of theirs. One earns trust over time. The other slowly empties the room of the very people who could have made the vision real.
Why this gets harder as you rise
The trap is not evenly distributed. It grows with altitude. The higher you go, the easier and more socially acceptable it becomes to float — to speak only in outcomes and themes, to let "I'm at the strategy level now" quietly excuse you from understanding the work underneath. The discipline is to keep one foot in the craft even as the other foot moves toward strategy: still reading some code, still sitting in on a real design discussion, still letting yourself be corrected by someone closer to the ground than you.
Doing the right thing and doing things right are not a hierarchy with one perched above the other. They are two ends of a rope you have to hold at the same time. The leader who lets go of the craft does not rise; they slowly lose the authority to choose the direction at all, because they no longer understand what the direction will cost. When has staying close to the details quietly changed a decision you made — or when did floating too high end up costing you something? I would love to hear the version of this you have lived.