The work behind the leader.

A leadership meeting ends with a decision. By the following afternoon, two teams are acting on different versions of it. A customer has heard a promise nobody checked with delivery. The person expected to move the work is waiting for authority that was never made explicit.

The decision was made. The business has not yet caught up with it.

Between a leader deciding something and a company doing it, there is a body of work that rarely gets much attention. Someone has to remember the reasoning, connect the people involved and notice when a commitment has started to drift.

The work between decisions

A priority can sound clear in the room and become ambiguous as soon as people return to their desks. What comes first? Who can make the tradeoff? What has already been promised? Which other team will have to change its plans?

Answering those questions requires a view across the business. It involves following a decision through the points where it depends on another person, another department or information nobody has shared yet.

An owner may carry all of that context at first. As the work becomes more complex, it can be shared with a trusted operator or a leadership team. The important question is whether anyone is responsible for keeping the pieces connected.

Context is part of the job

A tracker can record an owner and a deadline. It cannot explain, on its own, why the commitment matters or what should happen when the circumstances change.

That context is often held by someone who remembers the conversation before the conversation: the customer concern, the earlier attempt, the constraint the owner did not repeat because everyone was assumed to know it.

When that knowledge stays private, every exception travels back to the leader. When it is shared, other people can make a sound decision without recreating the entire discussion.

Responsibility needs authority

It is possible to make someone responsible for follow-through while giving them very little power to secure it. They can chase an update, but they cannot resolve the conflict behind the delay. They can repeat a priority, but nobody knows whether the owner will support it when another request arrives.

“Responsibility without authority turns operating work into a long series of requests.”

The owner has to make the mandate clear: which commitments this person can coordinate, which tradeoffs they can resolve and which decisions still need to come back. The team needs to see that mandate hold when it is inconvenient.

Trust has to run both ways

The person connecting the work needs the leader's confidence and the team's credibility. Becoming a private channel for the owner's changing wishes can undermine both.

Trust grows through ordinary behavior: representing a decision accurately, surfacing a problem early, keeping sensitive information where it belongs and saying plainly when a plan no longer fits the facts.

It also requires a leader who can hear that a commitment is unrealistic, or that their own change of direction has created the delay. A role built only to reinforce the owner's view leaves the business with fewer useful signals.

What becomes visible

When this work is done well, its effects are easier to see than the work itself. Teams leave with the same understanding. Problems reach the right person sooner. A decision survives beyond the meeting in which it was made.

The leader still sets direction. The business becomes less dependent on the leader personally carrying every promise from one conversation to the next.

That is part of how an organization develops: its ability to act becomes something people can rely on, rather than something one person has to keep assembling.