How Great Operators Protect an Executive's Time and Focus

Takeaway: Build the calendar around agreed priorities, leave room to prepare and recover, and define which requests you can handle, route, or bring to the executive.

Your executive has a strategy review at ten. The personnel conversation before it ends at 9:59, and the review's pre-read is still unopened. Every meeting fits on the calendar. The preparation doesn't.

That kind of gap is where an EA, executive business partner, or chief of staff can make a useful change. Start with what the executive needs to accomplish, then schedule the work around the meetings as deliberately as the meetings themselves.

What interruption research can tell you

Gloria Mark and colleagues studied interrupted work and found that participants compensated by working faster, while reporting more stress, frustration, effort, and time pressure. The study doesn't establish how every executive responds to a busy calendar, but it gives a reason to examine the cost of interruptions rather than count only completed tasks. (UC Irvine)

Sophie Leroy's research on attention residue examines how thoughts about a previous task can affect performance after a switch. It supports taking transitions seriously. It doesn't supply a universal number of minutes needed between meetings. (Leroy, 2009)

Meeting surveys point to another question worth asking. In an HBR survey of senior managers, 65 percent said meetings kept them from completing their own work. That is a report from the surveyed group, not evidence that your executive feels the same way. Ask what their current calendar is making difficult. (Perlow, Hadley & Eun)

Use the research to form a practical test: which changes help this executive arrive prepared, make decisions, and complete work that needs sustained attention?

Start with the priorities and constraints

Before moving recurring meetings, agree on what the calendar needs to protect. Identify the work only the executive can do, the commitments that are difficult to move, and the preparation each requires.

A useful conversation covers:

• the few outcomes that matter most this month;
• important decision deadlines;
• customer, board, employee, and external commitments;
• preparation and follow-up time;
• travel, meals, breaks, and personal constraints; and
• which decisions you can make about scheduling.

Ask when the executive prefers concentrated work and which meetings need a buffer. Their preferences won't settle every conflict, but they give you a starting agreement you can use when requests arrive.

If a priority has no time allocated to it, point out the gap. “The planning proposal is due Friday, but the only working block is Thursday afternoon” is a concrete observation. It gives the executive a choice about what needs to move.

Plan the work around each meeting

A meeting's duration is only part of its demand. A board discussion may require a pre-read, a briefing, travel, and decisions afterward. A difficult conversation may need a pause before the next appointment.

Schedule those dependencies where they matter. You might try 25- or 50-minute defaults to create a short transition, then adjust where the work requires a longer session. Treat those lengths as a planning convention, not a scientifically established optimum.

Grouping related meetings can also be worth testing. Several operating reviews together may reduce repeated preparation. Several demanding conversations without a break may create a different problem. Look at the content and the executive's feedback rather than applying batching to every category.

For a week with several important deadlines, walk through the calendar in sequence. Can the briefing be completed before the meeting? Is the travel time realistic? Does a decision arrive early enough for the team that depends on it? Those checks often reveal problems that an availability view misses.

Give recurring meetings a periodic review

Recurring commitments need an owner and a purpose. Their place on the calendar shouldn't depend only on how long they've been there.

For each meeting in the operating cadence, ask what it produces and who uses the result. Consider whether it should stay as it is, become shorter or less frequent, involve a different representative, or move to a written update.

Keep useful meetings. A recurring one-on-one may provide context that doesn't appear in a status report. A leadership review may be the right place to resolve a cross-functional conflict. The aim is to match the format to the work, not to achieve the smallest possible meeting count.

When a meeting changes, tell participants how its work will be handled. Canceling a review without another decision route can save an hour on one calendar while delaying several teams.

Agree on a route for incoming requests

Scheduling becomes easier when requests arrive with enough information. Ask for the purpose, deadline, required participants, and decision or outcome sought. For a sensitive matter, use an appropriate private channel rather than requiring details in a broadly visible form.

Then route the request within your authority:

• Handle it: a matter you've been authorized to resolve.
• Connect it: work another person can own or decide.
• Prepare it: a brief or draft for the executive to review.
• Batch it: a non-urgent item for an agreed update.
• Escalate it: a time-sensitive or consequential decision that needs attention now.

Confirm what qualifies for immediate attention. Don't infer that all board requests need an instant interruption or that all internal requests can wait. Context and the actual deadline matter.

For items that need the executive, frame the decision. State the options, your recommendation where appropriate, and when a call is needed. If you don't yet know enough to recommend an answer, say what you're checking and when you'll return with it.

Test the arrangement with one real conflict

Imagine the executive has a protected planning block when a request arrives for a customer meeting at the same time. Before accepting or declining, establish what the customer needs and when.

Perhaps the account lead can resolve the issue. Perhaps a short executive call is necessary, with the rest handled by the team. Or perhaps the customer decision genuinely takes priority and the planning block needs another home.

Bring that choice with its consequence. If the change falls within an agreed rule, make it and update the executive. If it doesn't, ask for the decision. Protecting time is a shared operating agreement, not a private contest between you and the person requesting access.

Check that the filter still lets information through

A calendar can look calm while the executive loses touch with the organization. Ask for feedback on what was routed away, what arrived too late, and what didn't need their involvement.

Requesters also need to know how to raise an exception. If they repeatedly bypass you, find out whether the route is unclear, a response is too slow, or an important category is missing from the rules.

Managing up includes making these expectations explicit. Learn from the executive's preferences, but don't rely entirely on guessing which decisions they'll approve afterward.

Your own capacity belongs in the arrangement too. If filtering requests requires constant availability, discuss coverage and response expectations. A dependable executive office should have a plan for leave and after-hours issues.

Review what improved

After trying a change, compare it with the problem you meant to solve. Did the executive complete the planning work? Were pre-reads available in time? Did fewer meetings have to be rearranged at the last minute? Did teams get their decisions when needed?

Use observations and records you have. You don't need to claim a precise productivity gain to show that a working block was used or a recurring conflict stopped. Keep the changes that help and revise the ones that shift the burden elsewhere.

Frequently asked questions

How much focus time should I protect?

Start with the actual work and deadlines, then agree on blocks the executive can use. There isn't one number that fits every role or week. Review whether the arrangement produces the intended work.

What if everything is described as urgent?

Ask what happens if the request waits and who needs the result by when. Where priorities genuinely conflict, bring the tradeoff to the person who can settle it. A label alone doesn't establish the deadline.

Can I decline meetings without asking?

Within explicit delegated authority, yes. Agree on the categories, exceptions, and update expectations. For a request outside those boundaries, prepare a recommendation.

How do I avoid becoming a bottleneck?

Give people a clear route, respond reliably, and provide a way to raise exceptions. Track whether the executive and the teams around them receive information and decisions in time.

For more practical guidance on executive-office work, join The Brief.