When Monday Rewrites Friday
One Monday morning, I opened Slack and saw nearly two dozen beautifully designed web pages dropped into the website updates channel.
They were polished. Intentional. Clearly, the product of real effort.
They were also a surprise.
My first reaction was not about the quality of the work. It was about the context I lacked.
Why had a senior leader done the redesign work personally? What conversation led to this direction? Why had a service area we had been discussing suddenly become the centerpiece of the company’s effort?
Then came a second surprise. Apparently, we were no longer pursuing a full-time marketing hire. That mattered because the marketing team had been preparing landing pages and waiting to launch them in support of that plan.
Leadership and I had met several times over the previous weeks. Not once did anyone, even in passing, say that the decision had changed.
So I walked into the next conversation already behind.
Not because I had ignored something. Not because I had failed to prepare. Because decisions had moved, and the context had not been shared.
That is one of the quiet struggles of remote leadership.
The Real Problem Is Not Distance
Remote leadership is often framed as a problem of geography or time zones. Those are real constraints, but they are not usually the deepest problem.
The deeper problem is uneven access to context.
When leaders and team members who share a physical space can have informal conversations, test ideas in the hallway, and make sense of changing conditions together, decision-making naturally gathers around the room. That is human. It is also risky.
Because the people who are not in that room do not just miss a conversation, they miss the sequence.
- They miss the observation that triggered concern.
- They miss the tradeoffs that shaped the thinking.
- They miss the moment when an idea stopped being exploratory and became real.
By the time the update appears in chat, the decision may look clean and obvious. But for the remote leader who was not included, it lands as a discontinuity.
Friday said one thing. Monday says another.
And now the job is no longer leadership. It is a reaction.
What This Costs
At first, these moments can feel small. A missed comment. A side conversation. A quick pivot made in the name of urgency.
Over time, the cost becomes harder to ignore.
Trust begins to erode. Not necessarily because anyone intended harm, but because repeated exclusion changes what the pattern means. What once felt accidental now feels dismissive.
Respect starts to fray. If a leader has already said, clearly and directly, that they often feel out of the loop, and the pattern continues anyway, the issue is no longer just a process issue. It becomes relational.
Credibility weakens. A remote leader cannot confidently support the company’s direction when that direction keeps shifting outside their awareness. They cannot help their team stay aligned if they themselves are piecing together what changed.
Ownership drops. When decisions arrive fully formed from above, people may comply, but they rarely commit. The work gets done, yet belief in the work thins out.
Narrative drift spreads. One leader tells a team one story on Friday. Another signal appears on Monday. Now, team members are left sorting out which version is current, which creates confusion at all levels below leadership.
This is how distributed organizations lose alignment without ever naming the cause.
Yes, the Market Is Changing
Leaders who move quickly are not wrong about the pressure.
Markets change. Positioning evolves. Service lines rise and fall in importance. Competitors move. Customers ask new questions. Waiting too long can be its own kind of failure.
I agree with that.
What I do not agree with is the idea that urgency justifies bypassing alignment.
There is a difference between responsive leadership and restless leadership.
Responsive leadership recognizes what is changing and creates enough structure for the right people to think together before the organization commits. Restless leadership feels the pressure of change and rushes toward visible action before shared understanding catches up.
One builds confidence.
The other creates motion that looks decisive but often leaves the people responsible for execution unconvinced.
In organizations that say they want empowered people, ownership, and initiative, this distinction matters. You cannot ask people to own what they had no voice in shaping. You can ask for compliance. You can demand output. But ownership grows where people understand the why, help define the what, and then have room to own the how.
Without that sequence, empowerment becomes branding.
What Good Remote Leadership Looks Like
Good remote leadership is not leadership that includes everyone in everything. That is fantasy, and it would render any organization irrelevant.
Good remote leadership is intentional about inclusion at the moments that matter.
For me, the clearest structure is still simple.
- Leadership helps define the why.
- Managers work together to clarify what.
- Teams own the how.
That sequence works only when the story remains coherent from one layer to the next.
It requires leaders to do more than announce conclusions. They need to provide clarity. They need to listen, not just tell. They need to create enough safety that observations, disagreement, gratitude, and concern can all be expressed without defensiveness. They need to educate people on how decisions are being made, not merely deliver outcomes after the fact.
In remote environments, this means shared context has to be treated as a leadership responsibility.
Not an administrative extra. Not a nice-to-have. A responsibility.
Because clarity allows someone in another city or time zone to support the direction with confidence rather than guessing at intent.
Decision Windows
The practical habit I want more senior leaders to adopt is this: create decision windows.
A decision window is the space between noticing a possible shift and declaring a new direction.
It does not need to be long. It does need to be real.
Inside that window, leaders can align on a few essential things:
- What are we actually responding to?
- Why does this matter now?
- What is still exploratory, and what is close to a decision?
- Who needs to weigh in before this affects execution?
- When will we decide?
That last question matters more than people admit.
When there is no mutually understood decision window, every strong opinion can become an immediate pivot. Ideas get treated like commitments. Experiments start looking like mandates. And people who were not in the original conversation are left trying to interpret how serious the change really is.
A decision window protects against that.
It allows urgency and thoughtfulness to coexist.
It gives distributed leaders a fair chance to contribute perspective, raise risk, support the eventual direction, and prepare their teams to move. It also creates a natural boundary between discussion and commitment, which reduces confusion across the organization.
In short, it helps the story arrive before the consequences do.
This Is About Inclusion, but Not in the Way People Sometimes Mean It
I am not talking about inclusion as symbolism. I am talking about inclusion as operational integrity.
If a remote leader is expected to reinforce strategy, guide a team, protect morale, and maintain momentum, then that leader needs more than updates. They need context early enough to make sense of what is changing.
Otherwise, they become a relay point for decisions they did not understand, do not fully believe in, or cannot confidently explain.
- That is not fair to the leader.
- It is not fair to the team.
- And it is not good for the organization.
The irony is that many senior leaders do not intend this outcome. They are trying to help. They are trying to move fast. They are trying to respond to the market with energy and conviction.
But good intent does not erase impact.
In distributed leadership structures, exclusion often happens through momentum, not malice. That is exactly why it must be named.
A Gentle Challenge to Senior Leaders
If you are a senior leader working closely with others in the same location, ask yourself a hard question:
Are we making decisions quickly, or are we making them visibly?
Those are not the same thing.
When a direction changes in a local conversation and the rest of the leadership learns about it only after work has already started, you may feel efficient. To others, though, it can feel like trust has narrowed to the people in the room.
That perception carries consequences.
- If you want remote leaders to act with confidence, include them before execution begins.
- If you want them to support the message, let them hear the reasoning while it is still forming.
- If you want ownership, do not hand them only the aftermath.
A short message that says, “We think this may be shifting. Let’s discuss by tomorrow and decide by Thursday,” can protect far more trust than a polished announcement on Monday morning.
Small behaviors like that are not bureaucracy.
They are respect made visible.
Shared Context Is a Leadership Practice
Markets will keep changing. Pressure will not disappear. New ideas will keep emerging at inconvenient times.
None of that is going away.
But if remote leadership is going to work well, then shared context cannot remain accidental.
It has to become a practice.
- Not because every leader needs equal airtime.
- Not because every decision requires consensus.
- But because people who are asked to carry the story need access to it before they are expected to defend it.
That is why decision windows matter.
They give leaders time to align on the why and the what before pushing teams into the how. They reduce narrative drift. They strengthen trust. They help remote leaders lead instead of react.
Speed matters.
Shared context matters more.
Leave a comment