Leaders need proximity, not control

Dashboards, summaries, readouts, and executive meetings are necessary. No leader of a large organization can remain inside every detail. But distance has a cost when a dashboard becomes more trusted than the people who produce the result, or when a process map carries more authority than the experience of moving through it.

The answer is not to pull every decision upward or ask leaders to inspect every task. That creates a different failure: control masquerading as engagement. The real leadership discipline is proximity, the ability to remain close enough to reality to make sound decisions without taking ownership away from the people doing the work.

Information becomes cleaner as it travels upward

By the time work reaches an executive forum, uncertainty has often been converted into a status, friction into a sentence, and conflicting interpretations into one recommended path. That compression is useful. It is also dangerous when leaders forget what was compressed.

A metric can be technically correct and still conceal the behavior producing it. A green status can depend on heroic effort that will not scale. A clean process can work only because experienced people compensate for its flaws. An initiative can hit an activity target while losing the confidence of the people it was meant to help.

Proximity restores texture. It lets leaders ask not only whether the number moved, but how it moved, what it cost, what people had to work around, and whether the result can be repeated without the same intervention.

The goal is a better sensing system, not executive inspection

When leaders sense distance, the instinct can be to add reviews, approvals, or meetings. Those mechanisms may create visibility, but they can also slow the organization and teach teams to manage upward rather than surface what is true.

A better approach is to create multiple ways to encounter reality. Listen to the people closest to a critical handoff. Observe a workflow rather than only reading its documentation. Review a small number of real examples behind an aggregate measure. Ask what people are compensating for. Invite disagreement before a decision hardens.

These practices do not undermine accountability. They improve it by helping leaders distinguish an execution problem from a system problem, and by making it safer for teams to reveal the latter.

Implementation changes the quality of the question

Earlier in my career, I was close to the build: code, demonstrations, customer conversations, and implementation details. As my responsibilities grew, the questions shifted toward priorities, investment, operating models, and enterprise decisions. The scale changed, but one lesson remained: judgment weakens when it loses contact with how the work actually happens.

Building again has reinforced that lesson. At implementation distance, vague strategic language has nowhere to hide. Is the decision specific enough to act on? Does the workflow preserve the context people need? Are we reducing friction or simply moving it? Are we solving the actual problem, or producing a more elegant description of it?

Leaders do not need to stay in the weeds. They do need enough proximity to understand which weeds are preventing the work from moving, and which ones are simply part of the terrain.

Proximity should increase trust, not dependence

Healthy proximity leaves the team more capable. The leader brings curiosity, context, and help removing constraints. The people closest to the work retain expertise and ownership. Both leave with a more accurate view of the system.

Control produces the opposite result. People wait for the leader, edit the story for the leader, or solve for the leader’s preferences. The organization may look aligned while becoming less able to move without intervention.

The test is what happens after the leader steps away. If the work becomes clearer and ownership stronger, proximity served the system. If every answer now has to travel upward, it became control.