Measuring Executive Calendar Fragmentation After a Meeting-Policy Change

Key takeaways

• Measure interrupted blocks, recovery time, and displaced work together.
• Compare the same executive cohort before and after the policy change.
• Report the tail of the distribution, not only the average.
• Keep the executive's experience separate from the measured result.

Question and scope

This study asks whether a change in meeting policy reduces fragmentation in an executive's calendar without simply moving the work to another part of the day. The unit is one executive work block, not one meeting or one week. The review records the block's purpose, the interruptions, the recovery time, and the work that was displaced. It does not judge whether the meetings were necessary.

Set the scope to one executive cohort and a fixed period before and after the policy change. Record the calendar system, the meeting cadence, and the approval rules in force. If the executive changes role or the team changes size during the window, separate the periods. A policy change during a reorganization cannot be evaluated as if the organization were stable.

Name the work the calendar is meant to protect. Writing, review, decision preparation, and relationship time are different blocks with different interruption costs. A single fragmentation score across all types can hide the block that matters most. The executive should agree on the protected work before the baseline is collected.

Record the meeting policy version in force at the start and end of each period, because a mid-quarter clarification can change what counts as an allowed meeting. Keep the policy document with the review file. If the rule changed without a version, note the date the office began applying it. The analysis should not assume that the written policy and the practice were the same.

What the sources establish

Microsoft's Work Trend Index describes the volume of meetings, email, and chat in the working day, which establishes the pressure but not the local cost. Harvard Business Review's meetings material discusses preparation, follow-through, and the work that meetings can displace. BLS occupational data describes the assistant role but not a benchmark for one executive. GAO data-reliability guidance supports careful documentation of operational records.

The sources do not establish that fewer meetings improve executive performance or that a particular meeting policy is effective. A calendar with fewer meetings can still be fragmented by approvals and messages. The study therefore measures the observable block structure and the displaced work, not a borrowed productivity multiplier.

Use the sources to frame the questions: which blocks were interrupted, what recovery time was needed, and where did the displaced work go? Those questions keep the review grounded in the executive's actual week. They also prevent the analysis from becoming a general argument about meeting culture.

Definitions and measures

Define a work block as at least thirty minutes reserved for one substantive task. Define an interruption as a scheduled event or a required response that begins before the block is complete. Define recovery time as the minutes between the end of the interruption and the resumption of the original task. Define displaced work as the task that was moved, shortened, or abandoned.

Measure the number of blocks, the number interrupted, the length of each interruption, and the recovery time observed. Record whether the block was completed later or abandoned. Use the calendar for the planned block and a short end-of-day note for the actual work. A calendar alone cannot show whether the executive returned to the task.

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

Record the executive's planned start and end time for each block, not only the calendar entry. A block that was planned for ninety minutes and used for forty is a different result from one that was fully used. The difference matters when the policy is meant to protect depth. Report the planned and actual length side by side.

Sampling and collection

Sample working days across the before and after periods, including weeks with board preparation, travel, and ordinary operations. Review every block on the selected days rather than only the interrupted blocks. A sample limited to difficult days will overstate the problem, and a sample limited to quiet days will miss it. Report the two types of day separately.

Record the days that were excluded and why. If the executive was traveling or on leave, the calendar structure may not represent the policy's effect. Keep those days in a separate category rather than dropping them silently. A transparent exclusion is better than a clean sample that hides the context.

Collect the calendar, the meeting policy, the assistant's notes, and a short executive log. Ask the executive to note one sentence at the end of each sampled day about the work that was displaced. That note is subjective, but it helps the analyst see what the timestamps cannot. Keep the note separate from the quantitative measure.

Collect the meeting invitations for the sampled weeks so the analyst can see who requested the interruption. A recurring request from the same team may be a design issue rather than an executive preference. Record the requester by role, not by name in the analysis file. That pattern is often more actionable than the total meeting count.

Calculating fragmentation

Calculate the share of blocks interrupted, the median recovery time, and the number of blocks that were abandoned. Report the distribution, not only the average. A small number of heavily interrupted days can carry most of the cost even when the overall average looks stable. The tail is the part the executive will recognize.

Compare the before and after periods using the same block definitions and the same executive cohort. If the policy changed the meeting cadence, report the change in the number of meetings beside the fragmentation result. A reduction in meetings that produces more messages is not necessarily a reduction in interruption.

Report the displaced work separately. If the protected block survived but the writing moved to the evening, the calendar looks better and the executive's day did not. The study should show where the work went, not only whether the block stayed on the calendar.

Report the number of blocks that were moved rather than interrupted, because a moved block can still lose its purpose. A block that is rescheduled to a low-energy part of the day may be technically intact and practically useless. The executive log can show whether the moved block was used. Keep moved and interrupted blocks in separate categories.

Analysis and reporting

Report the number of blocks, the share interrupted, the median and tail of recovery time, and the displaced-work categories. Break the results down by block type, day, and meeting load. Report the days that were excluded. A single fragmentation percentage can hide a serious problem in one block type.

Inspect the interruptions for patterns. A recurring approval meeting, a standing check-in, or an open-door norm may explain more than the formal meeting policy. The report should distinguish an interruption that the policy intended to remove from one that moved into another channel. That distinction determines the next change.

Keep the executive's interpretation separate from the measured result. The executive may experience a week as calmer even when the block count is unchanged. The report can include that view without treating it as proof of the policy's effect. The two kinds of evidence answer different questions.

Report the number of meeting-free days the policy intended and the number the executive actually had. A policy can look successful in the block data while the executive still attends informal calls. The report should compare the formal calendar with the observed work. That comparison is the honest test of the change.

Limits and next action

The study cannot prove that the policy caused the change, especially if the quarter included travel, a board cycle, or a reorganization. It also cannot measure the quality of the work that happened in the protected block. A block that stayed on the calendar may have been used for a different task. The executive log can show whether the protected time was actually used as planned.

The sample may miss interruptions that were handled without a calendar entry, such as a quick question in a hallway or a message answered between meetings. The executive log can capture some of these, but not all. The report should state the blind spot rather than imply that the calendar is the whole day.

Choose one change and assign an owner. The change might be a protected morning, a meeting-free day, or a required agenda for a recurring review. Set a repeat sample date and keep the definitions stable. A useful result is a calendar policy that the next quarter can test, not a one-time impression.

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

• Measuring the cost of context switching in an executive calendar
• Running a Weekly Executive Calendar Audit Without Becoming a Gatekeeper
• Auditing after-hours executive support requests against a response policy

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.