Measuring the cost of context switching in an executive calendar

Key takeaways

• Time each interrupted work block from the interruption to the point the executive actually resumes the task.
• Separate scheduled meetings from unplanned approvals, because they require different calendar fixes.
• Report the median, the longest recovery, and the work that was lost, not only an average.
• Test one calendar change for three weeks and compare the same blocked-work measure.

Question and scope

This study asks how much productive time an executive loses when the calendar forces a switch between meetings, approvals, and travel. The unit is one interrupted work block, not the whole day or the number of meetings. The review records the block's purpose, its planned length, and the time needed to resume it. It does not judge whether the meeting was necessary, because that question belongs to the operating review.

Set the scope to one executive and four consecutive weeks. Record the calendar, the approval queue, and the travel schedule as they existed at the start of each day. If the executive changes role or the meeting cadence changes during the window, separate the periods. A narrow sample with complete records is more useful than a broad survey that cannot distinguish a busy month from a broken process.

Record the executive's role and the types of work the calendar is meant to protect. A CEO, a CFO, and a general counsel have different uninterrupted work, and a single benchmark would hide that difference. Name the work that matters most before counting interruptions. The review is more credible when the executive agrees that the protected block was worth protecting.

What the sources establish

Microsoft's Work Trend Index describes how much of the working day is spent in email, chat, and meetings, which establishes the volume of switching but not its cost. Harvard Business Review's meetings research discusses preparation and follow-through, which are often the work that gets displaced. BLS occupational data provides context on the executive assistant role but not a local benchmark. GAO guidance on data reliability is useful for documenting sources and limits. None of these sources defines a context-switching cost for a specific office.

The study therefore uses local observation rather than a borrowed multiplier. A calendar full of meetings may be appropriate for a leader whose job is coordination, while the same calendar may be destructive for a leader writing a strategy. The measure should describe the interruption and the recovery, not assume that every switch is waste. That distinction keeps the review credible with an executive who values meetings.

Use the sources to frame the questions, not to supply the answer. Ask whether the office can identify the work that gets displaced, whether the interruption was avoidable, and whether the recovery time was longer than the interruption itself. Those questions turn a general concern about busy calendars into a local test. They also keep the review from becoming a complaint about meetings.

Definitions and measures

Define a work block as at least thirty minutes reserved for one substantive task, such as writing, review, or a decision requiring sustained attention. Define an interruption as any scheduled event that begins before the block is complete and cannot be moved without a trade-off. Define recovery time as the minutes between the end of the interruption and the resumption of the original task. Write the definitions down so two reviewers classify the same day the same way.

Measure the number of blocks, the number interrupted, the length of each interruption, and the recovery time observed. Record whether the block was rescheduled, abandoned, or completed later. Use the calendar and a short end-of-day note from the executive rather than memory alone. A simple count of interrupted blocks is easier to defend than a composite score that hides which part of the day failed.

Record the source of each timestamp, because a calendar entry, a badge record, and a message log may disagree. Use the calendar for the planned block and the message log for the interruption. Note the time zone for every entry. A consistent source rule prevents a small clock difference from looking like a large recovery gap.

Sampling and collection

Sample working days across the month, including weeks with board preparation, travel, and ordinary operations. Review every block on the selected days rather than only the blocks that were interrupted. A sample limited to difficult days will overstate the problem, and a sample limited to quiet days will miss it. Record the days that were excluded and why.

For each block, capture the calendar entry, the actual start and end, and any message or approval that arrived during it. Ask the executive to rate the difficulty of resuming the task on a three-point scale. That rating is subjective, so report it separately from the clock time. The combination shows whether a short interruption caused a long recovery or whether the block was already fragmented.

Choose days that represent the real mix of work rather than a convenient sample. If the executive travels every other week, include a travel week and a home week. If board preparation dominates one week, include it and label it. The comparison between weeks is often more useful than a single monthly average.

Analysis and reporting

Report the interrupted blocks by type and by time of day. Show the median recovery time and the longest recovery, not only the average. Separate interruptions that were scheduled in advance from those that arrived without notice. A meeting booked a month ago and a sudden approval request may both break a block, but they call for different fixes.

Compare the interrupted blocks with the work that was due that week. A block that protected a board paper may matter more than one reserved for routine email. Rank the fixes by the consequence of the lost block, not by the number of interruptions. Share one table with the executive and choose one change for the next month.

Keep the executive's own account beside the clock data. A block that looks interrupted on paper may have been effectively completed before the meeting began. A block that looks protected may have been spent on messages instead of the intended task. The two views together give a more honest picture than either one alone, and they help explain an unusual week.

Limits and sources of error

The study cannot prove that fewer interruptions would improve the quality of a decision, because many other factors shape executive judgment. Recovery time is also partly self-reported, and an executive may undercount the time spent returning to a complex task. Report those limits beside the result. Do not turn a small local sample into a general claim about productivity.

Calendar records may not show the work that happened outside scheduled blocks, and a canceled meeting may hide an interruption that never occurred. A travel delay can make a block look protected when the executive was actually working from an airport. Use the end-of-day note to flag those cases and mark them as uncertain. A transparent count is more useful than a false precision.

Do not use the result to compare one executive with another. The sample is one person, and the calendar reflects a specific role, team, and season. Use the result to compare the same executive before and after one change, with the same definitions and the same document types. That comparison is fairer and more likely to produce a decision than a ranking across the leadership team.

Review and next action

Choose one change, such as a protected morning block, a shorter approval window, or a rule that moves nonurgent meetings to the afternoon. Test it for three weeks and repeat the same measures. Do not change the whole calendar at once, because then the next review cannot tell which change helped. The [daily brief routine](/blog/building-a-daily-executive-brief-that-survives-a-busy-morning/) may support the protected time by moving decisions earlier.

Close the review when the office can show which blocks were protected and which interruptions remain unavoidable. Report the result to the executive in one page. Keep the note with the calendar template so the next review starts from evidence rather than memory. The goal is a realistic calendar that reserves attention for the work only the executive can do.

Write down what the change will not fix, such as a regulatory deadline or a recurring board cycle. That note keeps the review honest and prevents the next month from being judged against an impossible standard. Review the change with the executive and the assistant together. Both people experience the calendar, and both need to agree that the trade-off was worth it.

Sources

1. Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
2. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
3. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
4. Business Formation Statistics, U.S. Census Bureau.
5. Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
6. Productivity Statistics, OECD Data Explorer.
7. World Development Indicators, World Bank DataBank.
8. ILOSTAT Labour Statistics, International Labour Organization.
9. 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
10. The economic potential of generative AI, McKinsey Global Institute.
11. Creating helpful, reliable, people first content, Google Search Central.
12. Search Engine Optimization Starter Guide, Google Search Central.
13. Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
14. Microsoft 2024 Work Trend Index Annual Report.
15. Harvard Business Review, meetings.
16. BLS, Secretaries and Administrative Assistants.
17. GAO, Assessing Data Reliability.

Related research

• Researching calendar conflict rates across executive time zones
• Handling Executive Calendar Conflicts Across Multiple Time Zones
• Building a Daily Executive Brief That Survives a Busy Morning

Apply the research

Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.