Hybrid work gets blamed for a lot. Misalignment. Poor communication. Lack of visibility.
All true, but not the root of the problem. The deeper issue is simpler. Decisions don’t hold across distance.
What changed when we left the room
In co-located teams, decisions live in conversation. People hear the same thing. They remember it together. They correct each other in real time. A decision can feel settled without being written anywhere (maybe on the whiteboard).
In hybrid, that disappears. People join at different times. They miss parts of the conversation. They interpret things on their own. Schedules don’t overlap cleanly. Work moves forward in pieces.
Unless a decision is built to hold without shared presence, it fades. And when it fades, it comes back.
How this shows up
You don’t need a diagnosis. You can feel this is true. You sit in a meeting and hear something that sounds familiar. “I think we should revisit this.” And suddenly you’re back on ground you thought was settled.
Or someone asks a simple question. “Where are we on this?”
And the answer depends on who you ask.
So you add more check-ins. As a leader, you stay closer to the work than you should have to. You try to keep context alive through effort. Not because you want control, but because nothing holds without you there.
At the same time, people are doing real work. But if the decisions around that work aren’t clear and preserved, the work doesn’t build.
Effort goes up. Progress does not.
This is a design problem
Modern work introduces three conditions:
- Absence
- Change
- Asynchronous work
People are not always there. People change roles or join midstream. Work advances without everyone present. If your decisions cannot handle those conditions, they will not hold.
So the team compensates with more meetings, more summaries, more oversight. None of that fixes the underlying issue.
The Practice
Modern work, especially hybrid or distributed work, does not need perfect coordination. It needs decisions that can stand firm without it.
A real decision survives:
- time passing
- a new person joining
- a key person being out
- pressure on scope or timeline
If it can’t handle those conditions, it was never settled in the first place.
What makes a decision hold
This is not heavy process. It’s completeness.
A decision that holds includes three things:
- What was chosen Not the discussion. The actual call.
- What remains true The constraints and assumptions that must still hold
- When it gets reopened Specific conditions that justify revisiting it
That last one matters more than most teams expect. If you don’t define how a decision can be reopened, it can be reopened in an infinite number of ways. At that point, it never really closed. And if it never closes, it can’t survive change.
Why this matters now
When work happens across time zones and partial overlap, you don’t get to rely on shared memory. You need decisions that carry their own context. If they don’t, every handoff becomes a reinterpretation. And every reinterpretation creates drift from your desired path.
Close
If your team keeps revisiting the same ground, if progress depends on who is present, if alignment fades between touchpoints,
It’s not a hybrid problem. It’s a decision design problem.
Try this
Pick one decision this week.
Write down:
- what was chosen
- what remains true
- what would justify reopening it
Then step away.
If the work continues without you, it’s working.
If not, you’ve found the gap.
If you want a simple structure to make this repeatable, I’ve put the decision guide in the Work Library. It walks through how to capture what was chosen, what remains true, and when to revisit, so decisions don’t get reopened by default.
Start there: https://amykennedyleadership.com/start/