The delegation problem nobody writes about

Most executives fail at delegation not because they can't let go, but because they don't know how to break down their own work. They hand over tasks that feel like complete units to them but arrive as confusing fragments to their executive assistant.

I've watched dozens of founder-EA relationships collapse over this exact issue. The founder thinks they're delegating "manage my calendar." The EA receives what feels like 47 different, contradictory mini-jobs with unclear priorities and no context about why any of it matters.

Your brain runs on context your EA doesn't have

When you decide to "quickly reschedule Tuesday's calls," your brain processes this request against everything you know about those calls. You know Sarah's call is about the Q4 budget review and needs to happen before the board meeting. You know the vendor call can slide a week because you're still waiting on their proposal.

Your EA knows none of this. They see "reschedule Tuesday's calls" and have to guess which calls matter, when they need to happen, and what constraints exist. They make their best guess, reschedule everything for next week, and accidentally push your budget review past the board meeting.

You get frustrated because the "simple" task was done wrong. Your EA gets frustrated because they followed your instructions exactly as given. Both of you are right, and both of you are missing the real problem.

The invisible work of thinking through tasks

Every task you delegate comes with invisible thinking work that you've already done in your head. You've prioritized, contextualized, and made dozens of micro-decisions before you even realize you're working on something.

Take "book my travel to Austin." In your mind, this connects to the client meeting on Thursday, the fact that you prefer morning flights, your status with United, the hotel where your team is staying, and your dinner plans with the potential investor.

Your EA gets "book travel to Austin" plus maybe dates. Everything else they have to reverse-engineer or guess. They book you on Southwest because it's cheaper, pick a hotel downtown because it has good reviews, and schedule return flights that conflict with meetings you haven't told them about yet.

The solution isn't micromanaging every booking. The solution is recognizing that delegation requires you to externalize your thinking process, not just your tasks.

Most delegation advice gets this backwards

Standard delegation wisdom tells you to "clearly communicate expectations" and "provide all necessary information." This sounds right but misses the deeper issue. You can't provide information you don't realize you're using.

Better advice: spend 10 minutes mapping out why you're doing something before you delegate it. Not how to do it, but why it exists and what success looks like in the context of your other priorities.

For the Austin trip example, that might sound like: "I'm going to Austin Thursday-Friday for the Johnson Industries pitch. This is our biggest potential client this quarter. I need to be sharp for Thursday's presentation, so prefer arriving Wednesday night. The whole sales team will be at the Hilton downtown. I have dinner with Sarah Chen from Benchmark on Thursday night, she's considering leading our Series A."

Now your EA can make smart decisions. They know the stakes, understand the constraints, and can optimize for what actually matters to you.

Why "just figure it out" doesn't work

Some executives think the solution is hiring an EA who can read their mind. They want someone who will "just figure out" what they mean and anticipate their needs without explanation.

This approach fails because it requires your EA to become an expert in your business, your preferences, your relationships, and your strategic priorities. Even if they could do this, it would take months of trial and error. Most EA relationships don't survive that learning curve.

The executives who succeed at delegation don't find mind-reading EAs. They get better at externalizing their decision-making process. They learn to share not just what needs to happen, but why it needs to happen and how it connects to everything else.

The context document that changes everything

One CEO I know solved this problem with what she calls her "context document." It's a living Google Doc that contains:

• Her top three business priorities this quarter
• Key relationships and why they matter
• Her preferences for different types of decisions
• Common scenarios and how she typically handles them
• Projects currently in flight and their status

She doesn't expect her EA to memorize this. She expects her EA to reference it when making decisions on her behalf. When delegating something new, she adds relevant context to the document and references the specific section.

This isn't about creating more work for yourself. It's about doing the thinking work once, writing it down, and then reusing that context for months of better delegation.

Start with decision frameworks, not task lists

The best-delegated tasks come with decision frameworks, not detailed instructions. Instead of "reschedule my Tuesday calls," try "I need to move Tuesday's calls because of the board meeting. Priority order: anything budget-related needs to happen before Thursday, client calls are second priority, internal meetings can slide to next week."

This gives your EA the information they need to make trade-offs you'd be happy with. They might come up with solutions you wouldn't have considered but that still achieve your actual goals.

The hard part is recognizing that your brain makes dozens of these micro-decisions without conscious thought. Learning to delegate well means learning to catch yourself in the act of thinking and then sharing that thinking with someone else.

Most executives who think they're bad at delegation are actually bad at noticing their own decision-making process. Fix that, and delegation becomes much simpler.