There is a particular kind of Monday standup that looks healthy from the outside. Everyone has something to say. Tickets moved from in progress to in review. Two pull requests merged over the weekend. The dashboard is green, the call ends on time, and people go back to their screens feeling productive. And yet, if you stopped any one person afterward and asked a quieter question — where are we actually trying to get to this quarter, and why does it matter? — you might get a pause, a careful sentence about the current sprint, and not much beyond that.
I have sat in many of those standups, on both sides of the screen. The board was full. The direction was quiet. For a long time I assumed that if the work was organized and the numbers looked healthy, the team was in good shape. It took me a while to notice that a team can be carefully managed and still, slowly, lose its way.
Two different jobs, not two levels
John Kotter has a line that quietly reorganized how I think about this. Management is about coping with complexity. Leadership is about coping with change. A large system — a product, a team, a codebase — will drift into chaos without management: planning, budgeting, structure, the steady control that keeps a hundred moving parts consistent. And the same system will slowly ossify without leadership: someone setting direction, aligning people around it, and keeping them moving when the ground shifts.
What helped me most was to stop picturing these as a ladder, with the manager on a lower rung and the leader above. They are not levels of seniority. They are two different systems of action a team needs at the same time. Kotter is blunt about the danger of imbalance: strong leadership with weak management is not automatically better, and is sometimes worse, than the reverse. A team that is all vision and no follow-through burns out on grand plans that never ship. A team that is all process and no direction keeps shipping, neatly, in a circle.
A full board and an empty horizon
The symptom is easy to miss because it wears the costume of health. Everyone is busy. Every ticket has an owner. Velocity is steady. The trouble is that busyness and direction are not the same thing, and from the inside they can feel identical.
It reminds me of a long road trip where everyone in the car is busy and competent. One person watches the fuel gauge, another minds the speed, a third keeps refreshing the map for traffic. The car runs beautifully for hours. And then someone finally asks where exactly we are heading, and it turns out no one ever quite agreed — we just kept driving because driving felt like progress. You can be efficient and lost at the same time, and a team rarely notices the second part while the first part is going so well.
There is a simple way to hear the gap. Management tends to answer two questions very well: how are we doing this, and when will it be done. Leadership answers two different ones: what are we really trying to change, and why does it matter — to the people doing the work and the people it is for. A team can be full of confident answers to how and when while no one has said a clear sentence about what and why in months. That is what being over-managed and under-led feels like from inside: organized, occupied, and quietly unsure where it is all going.
Why we drift toward over-managing
I do not think this happens because managers are lazy or shallow. It happens because management is the safer instinct, especially under pressure. The how and when questions are measurable, urgent, and closeable. You can move a ticket. You can update an estimate. You can end the day with a visibly tidier board and feel that you did your job.
The what and why questions are none of those things. They are ambiguous, slow, and a little uncomfortable. They rarely close inside a single sprint. So when a deadline is breathing on our neck, we reach for the lever that moves — control — and quietly defer the one that asks us to sit in uncertainty. It is the difference between tidying your desk and deciding what the desk is for. Tidying feels productive immediately. Deciding feels like staring out a window. Both matter, but only one of them is comfortable to do at four o'clock on a Thursday.
What leading actually looks like on a Tuesday
For a long time I thought leadership had to look like a moment — a town hall, a memorable speech, a slide with a mountain on it. That picture kept me from doing the actual work, because no ordinary Tuesday ever felt grand enough to qualify.
What I notice now in the people I admire is far less dramatic. They repeat the why until it is boring to them — which is roughly the point at which most of the team is hearing it clearly for the first time. They draw the picture of where the team is going in small, ordinary settings: the framing of a task, the first two minutes of a planning meeting, an honest one-line answer to "why are we even doing this" instead of a defensive one. And they spend a surprising amount of energy removing the quiet fears that stop people from moving — fear of being wrong in public, fear of breaking something, fear of asking a question that might reveal they were lost.
None of that is a single visible event. It is quiet accumulation, the same way trust or a healthy codebase is built: one small, unglamorous interaction at a time, mostly underground, until one day the direction is simply there in how the team talks about its own work.
A small way to rebalance
If you suspect your team is over-managed and under-led, you do not need a reorg to start correcting it. You need a small, repeatable nudge in the questions you ask.
One that has worked for me: in your next planning session or one-on-one, for roughly every three how and when questions, ask one what or why. Make the destination visible somewhere the team actually looks — a pinned message, the top of the board, the first line of the sprint goal — not buried in a strategy deck no one reopens. And every so often, instead of telling people why the work matters, ask them to tell you. If they cannot, that is not a performance problem. That is the gap, showing you exactly where the leadership has gone quiet.
How this shows up at different altitudes
This is not only a manager's concern. As an individual contributor, you lead every time you connect your slice of the work to the larger why for the people around you — in a pull request description, in how you frame a trade-off, in the question you raise that nobody else wanted to. As a team lead or engineering manager, the balance tilts: more of your job becomes the what and why, though abandoning the how and when entirely is its own failure mode — the subject of the next piece in this series. And the higher you go, the more the risk flips: too much horizon, not enough ground, a leader so far above the details that the vision stops connecting to anything real.
A full board is not the same as a clear horizon. The quiet, unglamorous work of leadership is making sure people know not just what they are doing today, but what it is in service of — and that they would still believe the answer on a hard week. When was the last time you felt over-managed and under-led: busy, organized, and quietly unsure where it was all going? I would genuinely like to hear what was missing for you, and what — or who — helped the direction come back into focus.