Excluding EAs from the Planning Room Breaks the Rollout
It’s Friday at 10:00 AM. You’ve spent the week carefully locking in next week’s executive calendars—sequencing deep-work blocks, prep sessions, and other commitments across multiple time zones.
Then an email hits your inbox with a link to a massive communication rollout spreadsheet.
A senior executive—let’s call him Steve—is reorganizing senior managers reporting to four of his Directors (Joe, Jane, Ralph, and Rob). Teams and senior managers are shifting across org lines. The communication plan is complex, high-stakes, and final:
- Sunday: Calendar invites go out to teams across the planet so they don’t see mysterious 1:1s pop up over their weekend.
- Monday: Individual 1:1s between executives and impacted direct reports to deliver the news.
- Tuesday: Joint transition 1:1s with incoming senior managers, followed by new-org team meetings.
- Thursday: Org-wide email blast and Steve hosts and all-team meeting.
There was just one problem: none of the four EAs supporting those executives had been looped into the plan until 10 am Friday morning.
When the EAs pulled Steve’s Technical Advisor, Barbara, into an urgent sync, her explanation was simple: she assumed we already knew. Worse, when one EA pointed out that her executive’s Monday calendar was already packed wall-to-wall with no room to squeeze in sensitive 1:1s, the answer was predictable: the timeline cannot move.
To protect the weekend peace of the teams in other countries, four EAs had their own weekends hijacked and forced to dismantle already-confirmed Monday schedules to execute a plan they weren’t trusted to see two weeks earlier.
The Root Cause: Treating EAs as Execution Engines Instead of Operational Architects
When leadership teams plan reorgs, M&A transitions, or sensitive announcements in secret, they often confuse confidentiality with exclusion. They hold the details close until the final hour, assuming the operational logistics—calendars, room bookings, time-zone sequencing—can simply be handed off at the finish line.
That assumption breaks down for three reasons:
- Calendars aren’t blank slates. By Friday morning, Monday’s schedule is already cemented. Moving entrenched executive commitments on 6 hours’ notice doesn’t just create extra work; it signals instability across the org and fuels the exact rumors leadership was trying to prevent.
- Silence breeds leakage. When urgent, mysterious closed-door meetings appear between executives two weeks prior—without EAs managing the optics or using cover titles—people notice. Rumors start long before the communication plan is ever shared.
- Unacknowledged weekend labor erodes trust. Good EAs will always step up to protect the business when a true emergency hits. But a preventable planning omission isn’t an emergency—it’s a process failure.
Engineering the Mechanism: How to Prevent the Next Friday Fire
You can’t always control when an executive or key stakeholder forgets to loop in the EA team, especially across peer groups you don’t directly support. You can, however, build lightweight mechanisms with your own executive—and your EA peer network—to catch these tremors early.
1. The “Phantom Hold” Protocol
Train your executive (and their peers) on a simple rule: You don’t have to tell me the secret, you just have to tell me to clear the runway. When your leader is involved in sensitive, multi-week planning—like a reorg or headcount shift—establish a standing habit of placing placeholder holds (“Executive Hold / Internal Review”) on their calendar two to three weeks out. Even without knowing the details, having pre-cleared blocks gives you surgical room to drop in sensitive 1:1s without blowing up their entire week.
2. The EA Peer Early-Warning Network
In this scenario, urgent meetings had been happening between Steve, Joe and Jane for two weeks. When you spot sudden, unusual scheduling friction between your executive and specific peers, treat it as an operational signal. A quick, discreet check-in with your fellow EAs—“Hey, noticing heavy syncs between our leaders lately; do we need to keep next week’s calendars flexible?”—often surfaces shared patterns before a Friday fire drill hits.
3. The Post-Mortem Feedback Loop
Once the dust settles on Tuesday’s all-hands and Thursday’s announcement, don’t let the weekend fire drill quietly disappear. Wait until the adrenaline fades, then have a candid, matter-of-fact debrief with your executive (and if appropriate, the Technical Advisor):
- Focus on operational risk, not just personal inconvenience: “Because we weren’t looped in until Friday at 10 AM, Joe’s Monday calendar was already locked, which forced last-minute cancellations that risked tipping off the team early.”
- Propose the fix: “Next time a rollout like this is in motion, loop the EA group at least 10 days out—or have the executives ask us to hold blocks—so we can execute cleanly during business hours.”
The Bottom Line for Strategic EAs
Confidentiality is part of the EA job description. Keeping an EA out of a communication plan until the eleventh hour doesn’t protect the secret—it just guarantees a messy, high-stress rollout. Strategic EAs don’t just clean up Friday fires; they build the calendar buffers and feedback loops that stop them from starting in the first place.







