In partnership with

My team is firing on all cylinders. I have 17 things waiting for my input right now. If I don't respond, I'm the bottleneck. If I do, I'm making a $500k call based on a 30-second skim. I just need to NOT get it catastrophically wrong. Does this get any easier?

CxO during a coaching session

There's a particular version of overwhelm making the rounds right now. 

A subset of "too much to do, not enough time," but this one is harder to name: AI is making your team more productive than ever, and the breakthroughs are real. Reports arrive faster, outputs are multiplying… The system is working!

And somehow that's the problem.

Being a CxO in an AI-powered era means you are on the receiving end of a system that is accelerating around you. The bottleneck that used to live in the middle of the process (in the collecting, the synthesizing, and the building) now lives at the end. At the moment when human judgment is required. At the moment when someone has to make the call.

The bottleneck lives at your desk.

The CxO Squeeze

What’s really happening? Are you just indecisive? Are you squandering too much time on distractions? No, it’s not that mundane. Rather, AI has collapsed the time between idea and execution. The 'middle' of the work has vanished, leaving you with the high-stakes edges.

These edges (the moment when you frame the real question at the beginning and when you commit and act at the end) have always belonged to the leader. The adage, “Your company moves at the speed of your decision-making,” was true ten years ago, and it's true today.

The difference is that AI has made it impossible to ignore. It's turned what used to be more or less a time management problem (“work is busy, too much to do”) into a more complex three-pronged monstrosity:

  1. Volume — too many things reaching you that shouldn't.

  2. Friction per decision — each decision costs more cognitive effort than it should.

  3. Decision fog — you're deciding among options that all look equally credible, so nothing quickly stands out as obviously right or obviously wrong.

That’s why the instinct to “just push through” doesn't work.

Jess, What Do You Mean By “Decision Fog?”

Remember this scene from The Devil Wears Prada? Miranda's team is presenting looks for a photo shoot. She asks for the belts. An overeager assistant hurriedly produces two and holds them up:

"It's a tough call. They're so different!"

Think of that assistant as AI (or your team powered by it): Questions get answered almost instantly, and deliverables arrive polished, well-argued, and grammatically pristine. Which means distinguishing "good option" from "perfect option" now requires genuine Miranda-level discernment.

In the scene, Miranda makes that call effortlessly. But imagine her surrounded by 17 assistants, each holding up an accessory, all waiting for a decision, with little to no context beyond “Thoughts?

You are like Miranda; remarkably capable, with genuinely good judgment. But too much volume and too much friction per decision erode the conditions you need to exercise that judgment clearly. 

The options stop being distinguishable. The belts start to look the same. That's the fog.

What does this moment call for?

The instinct is to work on yourself (get better at deciding, move faster, think more clearly under pressure, etc.). But if you only optimize your personal decision-making and leave the organizational conditions unchanged, you're just trying to be a faster bottleneck; the queue just refills faster. 

The more complete solution is to improve the conditions around the decision, not just the decision-maker. Here’s where to start: 

1. Frame before you generate

This is where most of the leverage is. The volume, quality, and impact of what reaches your desk is a direct function of how clearly the work was framed before it began. One question does most of the heavy lifting:

What does a useful output look like?

To answer effectively, you have to think through what question you're actually solving for, whether the work is worth doing, and whether you're just exploring or converging on a decision. 

Teach your team to ask it before they hit generate (and model it yourself when you delegate), because without it, you're the one who ends up doing the framing at the moment you can least afford to.

But Jess! What if I don’t know what I want?

When you genuinely can't establish criteria yourself (e.g., when a decision falls outside your domain expertise), borrow the discernment. Find out what someone with deep judgment in that area would prioritize, and use that as your benchmark. You don’t have to be Miranda Priestly in every domain.  

2. Filter what reaches you

Once the framing work is done, empower your team to make some of the calls. Build explicit decision rights: a clear, written description of what decisions belong to your team versus what belongs to you. “Spend under $X, hire for roles at this level, change the roadmap within these parameters — you decide, no approval needed.

Try developing your own two-way door rule:

If a decision can be reversed in X days for less than $X, I never want to see it. If it's a 'One-Way Door' (like a key hire or a brand pivot), put it in my batching window. 

[More on “batching” in a bit.]

The goal isn't to be less involved. It's to be involved in the highest-leverage decisions, which means being deliberately uninvolved in everything else.

3. Kill the “Thoughts?” email 

Even after you've reduced the volume, some decisions will and should land with you. The question is what shape they arrive in.

"So, what do you think?" puts the onus on you to figure out what the question actually is, what the options are, and what criteria matter—all before you've even started deciding! 

Try setting a standard where any decision that reaches you arrives as a recommendation, not a question:

Here's what we're optimizing for. Here are the options we considered. Here's what we recommend and why. Here's what we need from you (a yes, a redirect, or a specific concern). Here's when we need it.

This makes the difference between someone handing you a problem and someone handing you a shaped choice. The former takes twenty minutes. The latter takes two.

4. Clear the fog

Once you turn down the volume (steps one and two) and reduce the friction (step 3), it’s easier to identify the work only you can do: high-stakes bets and situations where the information is genuinely ambiguous or incomplete, yet someone has to make a call.

These deserve your full attention. The problem is that by the time most executives get to them, they've already spent energy triaging everything else.

Two habits that make a real difference here:

  1. Check Reversibility. Before you engage with any significant decision, ask: "If this turns out to be wrong, how hard is it to change course?

    If the answer is "not that hard," that's your signal to move with confidence rather than wait for certainty. Make this a habit, and soon, applying the same level of care to a vendor renewal as to a company restructure will be a distant memory.

  2. Practice Batching. Your brain isn't built to toggle between deep judgment and operational noise 100 times a day. 

    Protect two or three windows (ideally during the times of day when your thinking is sharpest)  for consequential decision-making. You're not optimizing for speed as much as you're optimizing for better cognitive conditions. Hard decisions considered with fragmented attention get deferred.  And deferred decisions pile up.

How do you know it’s working? Cultivate decision awareness. 

One more thing worth building is a simple weekly decision log. Note what decisions are live, when they need to be made, and what's blocking each one. At week's end, look at what moved and what didn't.

Look for a pattern: Are decisions stalling because you're waiting for information? Or because you're waiting for certainty that isn't coming? Are decisions sitting with you when they should have been routed elsewhere? Are decisions being presented in high-friction formats?

The log doesn't tell you how to decide; it tells you where the system is breaking down. The former helps you become a faster bottleneck; the latter helps you remove the bottleneck entirely

But Jess… I did the thing. It didn’t work!

When I sit across from a client in the thick of this “too many decisions too fast” problem, it doesn't present as a straightforward systems failure. Those tend to bring out curiosity and problem-solving energy. 

Instead, it presents as frozenness; a hesitation to act:

Yeah. I mean. I guess. I dunno. Worth a shot, I suppose.” 

That's how overwhelm actually manifests: as a stress response that makes action feel impossible.

So, while I’ve done my best to pack this issue with practical, minimally invasive solutions, they may not stick. Why? Hidden internal narratives could quietly undercut your efforts: 

Mindset Trap 1: Solving for the old role

AI didn't just accelerate your team's output; it changed your job description — without announcement, without ceremony, and without any kind of onboarding.

There was no moment when someone said, "You are now primarily a high-throughput decision-making engine." It just started being true.

Which means many executives are still approaching the bottleneck problem by asking, “How do I guide, develop, and oversee more effectively?” 

With the “I’m a director” mindset, absorbing decisions just feels like part of the job: If making calls for your team is what good oversight looks like, then having 17 things waiting for your input is evidence you're needed. Which makes it very hard to want to fix.

The suggestions in this issue make more sense (and stick more easily) once you accept that absorbing decisions isn't the same as leading well.

Mindset Trap 2: Not asking for what you need

Quick — what is your gut response: 

A deliverable lands on your desk; polished, well-reasoned, asking for a speedy decision. But you don’t have enough background knowledge or context to confidently make a call. 

What do you do? For most high-performers, the honest answer is: you scan what’s in front of you, hedge where you can, make your best call, and project confidence.

Because admitting you need more support before you can decide feels like a failure of leadership. Like you should have been more on top of it. Like a competent executive wouldn't need to ask.

Intellectually, it’s straightforward: AI is compressing the middle of the work, and no human brain is built to absorb everything that's being generated. Needing additional support makes sense. 

But if it were that cut and dry, the temptation to perform omniscience wouldn’t be so strong. You wouldn't keep absorbing the "Thoughts?" emails in silence. 

Instead, asking for what you need—more time, a recap, another primer, a shaped choice —feels like asking for spoon-feeding; like admitting that otherwise you can't handle the job.

You can. And you can also dial down unnecessary friction. Those aren't in conflict.

Mindset Trap 3: Taking being wrong too personally

Pre-AI, it was easier to find a way to spread the blame for poor choices: The data was incomplete. The process was flawed. The option that looked good at the time turned out not to be. There was usually something external that shared the weight of being wrong.

But now, when everything arrives polished and well-reasoned, when all the options have been pressure-tested, and none of them are obviously flawed, a wrong call can only mean one thing: your judgment missed. 

For executives whose sense of worth is tied to being right (and many of us landed in the C-suite precisely because we were reliably right), a wrong call doesn't just carry operational or professional risk; it carries identity risk. And the stakes are often messily intertwined. 

These hidden narratives are neither right nor wrong, good nor bad. They just are. And the moment you name them, they lose some of their impact. 

So, however these mindset traps show up for you, notice your self-talk and treat it as information rather than a verdict. That’s how you regain the capacity and energy to attack the bottleneck problem with your typical confidence and curiosity. 

REFLECTION

  • What's currently sitting in your inbox tagged "Thoughts?" — and should it be there at all?

  • Think of a decision you've been sitting on. Is it stalled because you need more information, or because you're waiting for certainty?

  • Of the consequential decisions on your plate right now: which are actually irreversible, and which just feel that way?

Keep reading, keep leading,

Jess

P.S. If The Left-Hand Column has resonated with you, consider supporting my work by clicking on one of the ads below. It's a small action that has a big impact!

Thank you for subscribing!

For more, follow me on LinkedIn

Speak naturally. Send without fixing.

Wispr Flow turns your voice into clean, professional text you can send the moment you stop talking. Not rough transcription you have to clean up. Actual polished text — ready for email, Slack, or any app.

Speak the way you think. Go on tangents. Change your mind mid-sentence. Flow strips the filler, fixes the grammar, and gives you text that reads like you spent five minutes writing it.

89% of messages sent with zero edits. Millions of professionals use Flow daily, including teams at OpenAI, Vercel, and Clay. Works on Mac, Windows, and iPhone.

Gladly Connect Live '26. May 4–6 in Atlanta.

The room you want to be in. This is where CX leaders are tackling the hard AI questions and sharing what's actually working. For CX and ecommerce leaders. Atlanta, May 4–6. Space is limited — secure your spot now.

Build Webinars That Keep Working After You Stop

Webinars drive major results when they're built to perform. The Wistia Webinar Guidebook breaks down how to plan, promote, and run webinars that actually convert. Get more sign-ups, increase engagement, and turn every session into a consistent source of pipeline.

Keep Reading