DO, DELEGATE, DISMISS

Running an Executive Calendar in the Agent Era

“The moment you open your email, you are operating on someone else’s priority.” — Codie Sanchez

Sixteen years. Four companies, all of which eventually rolled up into the one I’m at now. Sixteen years of newsletters, cold outreach, vendor pitches, distribution lists, and “just checking in” follow-ups layered on top of the email that actually matters.

I’ve thrown every tool in the stack at it — Exchange rules, Checkpoint Harmony, filters, labels, unsubscribe sweeps. They help at the margins. They don’t solve it. Because the real problem isn’t volume. The real problem is that every person who has ever had my email address holds a standing claim on my attention. And the moment I open the inbox — before strategy, before delivery, before coordination — I am operating on someone else’s priority.

That’s the trap. A polite, well-lit, calendar-shaped trap, with an inbox-shaped side door.

What changed when I started building agents

Meetings used to be where decisions got made. That was the whole point of gathering humans in a room — you’d pool the context, argue it out, and leave with a direction.

Then I started building agents.

Now meetings are something else entirely. They are context gathering sessions. I walk into a meeting with three or four sharp questions I need answered, I probe, I listen, and the moment the meeting ends I feed the raw material into the agents that do the actual work downstream. The meeting is an input stream. The decision — and more often, the execution — happens afterward, and it doesn’t need me in a chair.

That single reframe changes the math on every invite I see.

The three buckets

I run every inbound ask — email, Teams, meeting invite, Slack, voice note — through the same filter. Three buckets. No fourth.

DO. Things that require my authority, my context, or my relationships. Decisions where the cost of delay exceeds the cost of my attention. The work nobody else in the org can do because it sits on me by design.

DELEGATE. Things someone on my team can do — and nine times out of ten, better than I can. Here’s the real test: if I don’t trust my team to own the work, why do I have a team? I didn’t hire them to do their jobs so I could redo them. I hired them because I trust their judgment and their decision-making. Delegation is how I honor that trust, not how I offload work. If you can’t delegate, you don’t have a delegation problem — you have a hiring problem, or a letting-go problem. Both are on you, not them.

DISMISS. The invite with no agenda. The “circle back” email. The CYA cc. The recurring sync that outlived its purpose six quarters ago. The bid that only exists because nobody declined it last time.

The uncomfortable part: DISMISS is the biggest bucket, and it’s supposed to be. If it isn’t, you’re drowning.

One up, one down — and a green light for everyone else

Andy Grove argued that a manager’s time belongs to two groups: the people above you, who need alignment, and the people below you, who need development. That’s still right. I give the bulk of my calendar to one layer up and one layer down, and I protect that time like a physical asset.

For peers and cross-functional partners, the default is different. Cross-functional work is real work — I’m not pretending otherwise. But how many of those meetings could have been a ten-minute Teams call, or a three-paragraph email while my light was green?

So I keep a green light. When my Teams status shows open, come find me. Ping me. Call me. I’ll answer in minutes, not days, and I’ll give you a focused answer so we can both move on.

What I won’t do is default to a thirty-minute calendar hold where four people half-listen while one person talks. That isn’t collaboration. That’s the theater of collaboration.

Empty calendar is not freedom. It’s an invitation.

Here’s a rule I wish I’d been taught a decade ago: an open block on your calendar is not free time. It’s a vacancy. And vacancies get filled — not by you, by everyone else.

If my calendar shows three hours of white space on Tuesday afternoon, I will lose at least two of them by end of day Monday. Somebody will drop a thirty-minute sync. Somebody else will extend a standing meeting because “we have the time anyway.” HR will schedule a listening session. By the time Tuesday arrives, the white space is gone and so is any chance of strategy work.

So I build blocks. Deep work blocks. Delivery review blocks. One-on-one prep blocks. And yes — thinking blocks, explicitly labeled as such, because if I don’t name the time I need to think, I won’t protect it. These blocks aren’t theater. They have outputs. They produce the strategy, the architecture calls, the difficult emails, and the coaching I owe the people who report to me.

The rule is simple: if you don’t claim the time, someone else will claim it for you. Your calendar is a market, and nature abhors an unpriced asset.

This isn’t coldness. It’s respect.

I have to be careful here, because the risk of all of this is that it reads as transactional or dismissive. It isn’t — or at least, it shouldn’t be.

A sharp, focused ten-minute answer is more respectful of someone’s time than a distracted thirty-minute meeting where I’m half in my email. Declining an invite without an agenda is more respectful than attending and contributing nothing. Telling someone “this doesn’t need me, but here’s who it does need” is more useful than nodding through it and creating the false impression that I’m engaged.

The goal isn’t to give less. It’s to give better — to the right people, at the right depth, at the moments that actually matter. My team knows my door is open. My peers know my status is honest. And the people I report to know I come to them with answers, not updates.

Meet Hermes

The framework would be aspirational if I hadn’t automated it. So I built an agent. I call it Hermes.

After sixteen years of rules, filters, and appliance-grade email security, Hermes is the first thing that actually worked — not because the tech is new, but because it’s the first tool I’ve deployed that understands my priorities instead of someone else’s sender reputation.

Hermes runs on a cron. Every morning before I’m awake, it reads my inbox, triages every message, and drops each one into one of three folders: DO, DELEGATE, or DISMISS. The DO folder is small and high-signal — five to ten items, typically, that truly require me. The DELEGATE folder comes with a suggested owner and a draft handoff. The DISMISS folder I scan once a day for about five minutes, purely to sanity-check Hermes’s judgment. I almost never overrule it.

Hermes doesn’t replace me. It amplifies me. It takes the triage work — which used to eat an hour of my morning and leave me already behind — and compresses it into the minutes it takes me to drink coffee. By 7 a.m., I know what my day is actually for.

The next version of Hermes will do the same for meetings. Context in, decisions and drafts out. That’s where this is heading for every executive who’s paying attention.

What I’m actually defending

When I tell my team I’m defending my time, I’m not defending it for me. I’m defending it for the work that only I can do, and for the people who only I can develop.

The inbox isn’t your to-do list. The calendar isn’t a vote on what matters. The rituals you inherited aren’t sacred.

You get one unit of executive attention per day. Spend it on the thing that compounds — your manager, your team, the two or three bets that define the year — and let the agents run the rest.

DO. DELEGATE. DISMISS. In that order, every day, without apology.