You already know “collaboration” sits in the top three answers for why companies win. Ask any senior leader and you’ll hear some version of: our people, our culture, our collaboration.
Then, you look at how work actually flows in your org and realize you’ve built an impenetrable fortress.
Especially at the top.
For COOs and CIOs in large enterprises, this isn’t a “soft” problem, rather, it’s an operating system flaw: you’ve raised the barriers to reach the people who control critical-path decisions, and the bill shows up as project delay, margin leakage, disengagement, and talent loss.
Let’s walk through how this happens, why executive-access “sludge” is so expensive, and what a better model looks like, including how an Agentic Collaboration OS fits in.
The Collaboration Paradox: “My Door Is Open”… But Good Luck Getting In!
Here is a sad reality: modern enterprises preach openness while operationalizing blockage.
Executives:
- Sit in back-to-back meetings,
- Guard their calendars with layers of approvals,
- Route almost everything through an Executive Assistant (EA),
- Respond instantly “up” the hierarchy,
- And let “down” and “across” wait.
- Sit in back-to-back meetings,
For Western “individualistic” leaders, it feels rational: I’m protecting my time so I can focus.
But here’s the catch: your personal productivity is irrelevant if the system you lead is stuck waiting on you.
Research backs up how fragile this balance is:
- Executives spend nearly 23 hours/week in meetings on average, more than double the 1960s. Harvard Business Review
- McKinsey finds executives spend ~40% of their time making decisions, and more than half of that time is used ineffectively. McKinsey & Company
- Bain’s work on “organizational drag” shows companies lose 20%+ of productive capacity to unnecessary processes, misaligned approvals, and slow decisions. Bain
Now layer in your own barriers: if collaboration is king, the royal court is oddly hard to reach.
Upward Open, Downward Closed: How Leaders Become Bottlenecks
In most large orgs, the observed pattern is painfully consistent:
- When someone above you pings, you’re available.
- When someone below you pings, they’re told to:
- “send an email,”
- “put time on the calendar,” or
- “coordinate with my EA”.
- “send an email,”
- When someone above you pings, you’re available.
This is usually defended as “protecting focus” or “being disciplined with time.”
However, in a healthy organization, your performance is not measured by how responsive you are to your boss; it’s measured by the outcomes of the sub-organization you lead:
- Are initiatives shipping on time?
- Are dependencies cleared fast?
- Are teams confident and moving, or stuck and guessing?
Every barrier you create – no matter how rational it feels – extends the time between “we’re blocked” and “we’re unblocked”. That delay is pure cost: missed revenue, slower customer responses, wasted engineering cycles, regulatory risk left hanging, key hires stalled, etc.
Decision latency theory and multiple studies in project and portfolio management are unambiguous: delayed decisions directly correlate with project overruns and value leakage. Kanban Agile Tools+2Data Center Dynamics+2
And that’s before you factor in the human side.
The Hidden Tax of the Executive Assistant as Firewall
Let’s talk about the Executive Assistant (EA) model in this context.
A great EA is high leverage. But in many enterprises, the EA is unintentionally weaponized as a filter, not an amplifier:
- You must constantly “program” your assistant on priorities.
- Priorities change hourly.
- The EA rarely has full context to judge which “quick ask” would unblock $5M of pipeline vs. which is noise.
- Workers needing you now have to:
- craft the ask,
- “sell it” to the EA,
- wait for a slot that might be 2-3 weeks out.
- craft the ask,
- You must constantly “program” your assistant on priorities.
On top of that, there’s direct coordination cost.
Let’s use a conservative assumption: an executive, in a 65-hour week, spends ~10% of that time aligning and iterating with their EA on schedules, messages, and approvals. That’s 6.5 hours/week (almost a full day) consumed just to maintain the barrier, instead of resolving decisions that hundreds of people are waiting on.
In other words: you are funding friction.
“Talk to My EA”: A Masterclass in Demotivation
Inside your org, the sludge is visceral:
- A director Slacks you: “Got 5 min today to unlock X for the [customer/regulator/program]?”
- You see it, you reply instantly: “Loop in my EA to find time.”
- Context was fresh for both of you. A 3-5 minute conversation could have happened right there.
- Instead, you’ve:
- added days/weeks of delay,
- exported the problem to someone without decision rights,
- signaled: “My time is more important than your work”.
- added days/weeks of delay,
Multiply that by hundreds of interactions:
People prepare for a meeting booked two weeks in advance, only to see it bumped last minute for the latest escalation from above. They stop believing their time matters. They stop escalating when they should. They wait. They guess. They ship the wrong thing.
That’s not “protecting executive productivity”. That’s burning organizational energy to preserve calendar aesthetics.
“Office Hours” and Open-Door Myths: Better, But Not Enough
Some leaders are experimenting with more porous models.
NVIDIA and Jensen Huang are frequently cited for an open-door, high-access culture where employees can surface ideas directly to leadership. Clover HR
Other CEOs run walk-in or skip-level office hours. It’s a meaningful step: it sends a strong cultural signal that access matters.
But structurally, there are limitations. In fact, open office hours:
- Batch decisions into narrow time slots,
- Force people to wait days for something blocking work today,
- Create queues and performative “pitch lines” instead of fast, surgical conversations.
- Batch decisions into narrow time slots,
Better than nothing, yes. A true solution to decision latency? Not even close.
What Buffett and Musk (Actually) Signal About Access
Two famous counterexamples are often misunderstood but directionally instructive:
- Warren Buffett
Buffett is known for an intentionally light calendar – Bill Gates has talked about being shocked at how empty it was – which reflects a ruthless defense of unstructured time for thinking and a refusal to be owned by meeting requests. Inc.com+1
The lesson for COOs/CIOs is not “do nothing”; it’s: own your time so you can focus on the few decisions that truly matter and be available when those decisions are needed. - Elon Musk
Musk has publicly said he largely manages his own schedule and, per reporting on both his biography and interviews, has at times operated with minimal assistant support after proving to himself he could absorb the work. Business Insider+1
Again, the point isn’t the drama; it’s the principle: if your scheduling infrastructure adds more drag than leverage, rewire it.
- Warren Buffett
Neither model scales 1:1 into a Fortune 500 matrix, but both underline a hard truth:
The way you design executive access is a strategic choice, not an accident.
Right now, most enterprises are choosing bottlenecks.
What High-Performance Executives Should Do Instead
Whether you’re a COO, CIO or any other executive, your job is to optimize decision throughput, not to cosplay as a celebrity whose time is “protected” at the expense of everyone else’s.
Three shifts change the game:
1. Increase the “Resolution” of Your Day
Your calendar is full of 30-60 minute blocks that should have been 5-10 minute conversations.
Move from:
“If it’s important, send a calendar invite”
To:
“If it’s important and I’m free for 5 minutes, we’ll handle it now with the right 2-4 people”
High-resolution days = more, smaller, context-rich interactions that unblock work without ceremony.
2. Stop Using EAs as Gatekeepers
Your EA should:
- Orchestrate,
- Prep you with context,
- Protect you from true noise,
- Orchestrate,
Not prevent critical-path people from reaching you.
If someone is accountable for a major customer, program, or risk area, they shouldn’t have to “pitch” your assistant for access. Default to direct micro-touchpoints; use the EA to make those touchpoints smoother, not rarer.
3. Design for Decision Speed, Not Meeting Volume
McKinsey’s data is blunt: organizations that make and execute decisions quickly and well are about twice as likely to deliver strong financial performance. McKinsey & Company+1
That doesn’t come from more steering committees.
It comes from:
- Clear decision rights,
- Fewer layers between the work and the decider,
- Lightweight ways to convene exactly the right people at the right moment,
- Clear decision rights,
Systems that remove “calendar Tetris” and/or slot negotiations as a prerequisite for talking.
Enter Agentic Collaboration: How Tweelin Changes the Equation
At Tweelin, we believe the next productivity unlock is reclaiming coordination time and redeploying it into faster, high-quality decisions, without flooding calendars.
Tweelin is an Agentic Collaboration Operating System that:
- Spots when 2-6 specific people need to talk to move a decision forward.
- Checks their real-time availability signals across tools.
- Spins up application/device-agnostic instant micro-conversations on the fly, without:
- Back-and-forth scheduling,
- EA mediation,
- Or another 30-minute block.
- Back-and-forth scheduling,
- Does all this without calendar bloat, while respecting priorities and guardrails you define.
- Spots when 2-6 specific people need to talk to move a decision forward.
What this means for you:
- You become more accessible without becoming an interruptible chaos.
- Your direct reports and their teams get answers in minutes, not weeks.
- Your EAs refocus on leverage work such as briefing, follow-through, strategic support, instead of inbox and calendar gatekeeping.
- Your org feels the cultural shift: “our leaders are findable when it matters”.
- You become more accessible without becoming an interruptible chaos.
This is not about being “nice”. It’s an operating decision:
Reduce decision latency → increase throughput → ship faster → waste less → retain better people.
Make the Barrier Fall Without Losing Control
If you recognize any of this in your org:
- Projects stalling “waiting on Steve’s sign-off”,
- Managers rolling their eyes at “talk to my EA” replies,
- Teams quietly optimizing around access, not impact,
- Projects stalling “waiting on Steve’s sign-off”,
Then your collaboration barrier is no longer a quirk. It’s a cost center.
The good news is: you control that design.
If you want to see what an agentic, zero-coordination-cost model could look like in your environment – and how to increase access without sacrificing focus – let’s talk.
👉 To discuss your specific needs, contact us via the form at tweelin.com/contact-us.