How to Work with an Executive Assistant: The Complete Guide

You’ve made the hire. Or you’re about to. Either way, a question lingers: how do I actually make this work?

Working effectively with an executive assistant means building a partnership based on trust, clear communication, and structured systems. It’s not about offloading tasks – it’s about creating leverage. The best EA relationships transform how leaders operate, saving 40-60+ hours monthly while improving the quality of decisions, stakeholder relationships, and daily operations.

Part 1: The Mindset Shift

Many first-time users overthink this. They imagine complex delegation formulas or worry about being a “bad manager.” The reality is simpler: you already have the skills. You manage relationships, communicate expectations, and hold people accountable every day. Working with an EA is the same set of skills applied to a new context.

You Already Have the Skills

Talk to any founder who has an assistant, and you’ll rarely hear “I should’ve waited longer.” The regret almost always runs the other direction.

The Only Real Mistake: Waiting Too Long

The opportunity cost of managing your own inbox, coordinating your own travel, and following up on your own requests is compounding every week you delay. The question isn’t whether delegation is risky – it’s whether not delegating is worth more.

Letting Go Doesn’t Mean Losing Control

One of the top concerns from first-time users: “What if I lose control of my calendar?” “What if they miss something important?” “What if I don’t like how they organise things?”

Valid concerns. Control matters – especially when you’ve built your business from the ground up. But the difference between controlling outcomes and controlling execution is the mindset shift that makes great EA relationships work. Your EA handles the execution. You define the outcomes and boundaries.

Part 2: What Good, Bad, and Great Look Like

The difference between a mediocre and exceptional EA relationship isn’t the assistant – it’s the dynamic.

What a Bad Dynamic Looks Like

Kickoff: vague brief, no context. Task assignment: thrown over the wall with minimal explanation. Information flow: one-directional, reactive. Outcome: the CEO spends as much time reviewing and correcting as they would have spent doing the work themselves. The EA waits to be told what to do next.

What a Good Dynamic Looks Like

Kickoff: clear brief with context and goals. Task assignment: specific deliverables with deadlines. Information flow: structured updates, flagged blockers. Outcome: work gets done to standard, the CEO reviews briefly, provides feedback. The EA executes reliably and asks when uncertain.

What a Great Dynamic Looks Like

Kickoff: strategic brief where the EA helps shape the approach. Task assignment: the EA identifies next steps without being prompted. Information flow: proactive updates, risks flagged early, solutions proposed. Outcome: the CEO is informed but not in the weeds. The EA owns the process and brings it to completion.

The difference comes down to three things: trust, access, and alignment. All three can be built systematically in the first 30 days.

Part 3: Systems That Actually Work

Knowing how to work with an executive assistant effectively requires more than good intentions. You need systems.

1. Weekly Check-Ins

Consistency creates rhythm. Schedule a weekly check-in to review priorities, progress, and challenges.

• 15-30 minutes, same time each week
• Review completed items from previous week
• Align on priorities for coming week
• Surface any blockers or decisions needed

Even leaders who hate meetings find this one worth protecting. It prevents the constant back-and-forth that fragments both your days.

2. A Master Task List

One centralised place tracking every task and project. Not your head. Not scattered across email threads. One source of truth. Whether it’s a shared spreadsheet, Notion database, or project management tool – the format matters less than the discipline of keeping it updated.

3. Clear Delegation Framework

One of the biggest mistakes: assuming your assistant can read your mind. For every delegated task, provide:

• Outcome: What does “done” look like?
• Context: Why does this matter? What’s the bigger picture?
• Constraints: Deadline, budget, stakeholder sensitivities
• Authority level: What can they decide independently vs. what needs your input?

This takes an extra minute upfront. It saves hours of back-and-forth and rework.

4. Decision-Making Boundaries

Define what your assistant can handle independently versus what requires your input:

• Scheduling: They can book within defined rules; escalate conflicts
• Email: They can draft, flag, and archive; you review before sending on sensitive topics
• Spending: They can approve expenses up to a defined limit
• Hiring: They can screen candidates; you conduct final interviews

Clear boundaries build confidence on both sides. Your assistant knows when to act. You know what to expect.

5. Colour-Coded Communication

Simple visual system for your shared task list:

• Red: Urgent, needs your attention today
• Blue: In progress, no action needed
• Black: Waiting on external input or completion

This lets both of you scan quickly and focus on what matters.

6. Record Key Meetings

For important meetings, record them (with permission). Your assistant can review recordings to:

• Extract action items
• Update the project list
• Prepare follow-up communications

This ensures nothing gets missed and removes you as the bottleneck for information transfer.

7. Build a Playbook

From day one, have your assistant document:

• Your preferences (communication style, scheduling rules, pet peeves)
• Recurring workflows (how you handle expenses, travel, board prep)
• Key contacts and relationships
• Tools and system access

This playbook becomes invaluable – for your assistant’s effectiveness, and for continuity if you ever transition to someone new.

Part 4: The Assistant’s Perspective

Understanding how great assistants think helps you build a better partnership.

What Top EAs Focus On

• Anticipation over reaction: They’re thinking two steps ahead – not waiting to be asked
• Understanding context, not just tasks: Why does this matter? Who are the stakeholders? What could go wrong?
• Building trust through reliability: Consistency and follow-through over time, not one impressive result

What Assistants Need From You

• Access: Calendar, email, key contacts – the more context they have, the more effective they are
• Clarity: Clear outcomes, not just task descriptions
• Feedback: Specific, timely, constructive – both when things go well and when they don’t
• Trust: Allow them to operate without constant check-ins; intervene on outcomes, not methods

Part 5: Common Challenges (and How to Solve Them)

“I Can Do It Faster Myself”

This mindset kills delegation. Yes, you can do many tasks faster in the short term. But you’re sacrificing long-term leverage. An EA who takes 30 minutes to do something you’d do in 10 is still saving you 10 minutes – and the next time, they’ll do it faster with less context-setting from you.

Solution: Measure the relationship over months, not individual tasks. Track total time recovered, not task-by-task efficiency.

Lack of Clarity on Roles

Confusion about what your assistant can or should do creates friction. They hesitate when they should act; you step in when you shouldn’t have to.

Solution: Build the decision-making boundaries document in week one. Revisit and expand it monthly.

Trusting Someone with Sensitive Information

Trust doesn’t happen overnight. Starting with less sensitive work before expanding to confidential matters is normal and appropriate.

Solution: Start with calendar and scheduling access. Add email access after two to three weeks of demonstrated reliability. Expand to sensitive communications and documents as trust develops.

Misaligned Priorities

You’re working hard, but on different things. Your EA is busy with work that doesn’t match what matters most this week.

Solution: The weekly check-in exists specifically for this. Use it to re-align priorities every week, not just in the first month.

Communication Breakdowns

Miscommunication derails even strong partnerships. Define how you communicate for different types of interactions:

• Quick updates: Slack or text
• Task handoffs: Email or task system
• Strategic discussion: Scheduled calls

Resistance to Feedback

Feedback feels uncomfortable but enables growth. One source of truth for tracking work prevents the “I thought you knew” misunderstanding.

Solution: Create a feedback protocol: specific, not personal; focused on the work, not the person; tied to the outcome you’re trying to achieve.

Part 6: The First 30 Days

If you’re working with an executive assistant for the first time, here’s a practical roadmap:

Week 1: Foundation

• Share calendar access and key systems
• Establish communication channels and response expectations
• Have your assistant shadow your week – observe meetings, email patterns, priorities
• Start the playbook document

Week 2: First Delegations

• Hand off 3-5 recurring tasks (scheduling, inbox triage, travel bookings)
• Provide extra context and check work closely
• Daily quick syncs to answer questions
• Introduce to key contacts who should know to work with your EA

Week 3: Expand Scope

• Reduce check-in frequency to every other day
• First weekly review meeting
• Establish the weekly check-in format that will continue
• Hand off more complex tasks based on demonstrated capability

Week 4: Build Rhythm

• Create decision-making boundaries
• Feedback session: what’s working, what needs adjustment
• Mindset check: are you letting the EA own work, or still micromanaging?
• Systems check: is the task list working? Is the playbook updated?

By end of month one, you should feel the weight lifting. Not everything is perfect, but the system is taking shape.

The leaders who get the most from their EAs aren’t delegation experts. They’re system builders. They invest the upfront time to create structures that compound over time.

Filip PesekFounder & CEO, DonnaPro

Filip Pesek spent more than seven years building delegation systems the hard way: through trial, error, and eventually a complete rethink of how founders should work with assistants. Before DonnaPro, he founded Spark, a marketing agency, and wrote the bestselling book Pisma za Leona. DonnaPro grew directly from the systems Filip developed for himself, and later shared with the founders and CEOs who kept asking how he managed to work the way he did. He writes about delegation, founder leverage, and building businesses that do not depend on the person at the top holding everything together.