Share or save this article

Share on X

AUDIO

Listen to this article

3:42

日本語

Checking your sign-in status…

An audio edition based on this article.

The meetings are over, the emails answered, the chat messages handled. Yet the important work planned for today remains unfinished. Is this simply a matter of individual concentration?

In 2025, Microsoft reported how workplace communication and meetings can fragment concentration. But reading this as “every employee actually lost focus every 2 minutes” would be a mistake. Examining how the figures were calculated reveals the central issue: whose priorities shape the day matters more than the number of notifications.

1. What did “every 2 minutes” measure?

Microsoft’s 2025 special report, “Breaking down the infinite workday,” combines anonymized, aggregated Microsoft 365 usage signals with a survey of 31,000 knowledge workers across 31 markets. The usage signals cover the period through February 15, 2025. Educational institutions and EU tenants are excluded.

The report’s “every 2 minutes” is an average interval calculated from signals for meeting invitations, emails, and chats received during 8 core working hours. The figure of “275 times a day” uses signals over 24 hours. Both cover users in the top 20% by incoming volume; neither is an average across all workers. Receiving a notification is also not the same as actually interrupting work.

MetricWhat Microsoft reportedWhat the figure does—and does not—mean
2 minutesAverage interval between signals over 8 hours for users in the top 20% by incoming volumeDoes not directly measure whether concentration broke each time
275 timesNumber of signals over 24 hours for users in the top 20% by incoming volumeNot the average across all employees
48%Employees who said their work felt chaotic and fragmentedSelf-reported; does not establish causation
52%Leaders who said the sameReflects differences in perception across roles

This distinction matters. Striking figures alone do not justify concluding that halving notifications would double productivity.

2. Why does more communication push core work aside?

Consider someone preparing a proposal who answers a customer’s questions, reports progress to a manager, and waits for confirmation from another department. Each exchange may be necessary. Still, repeatedly reshuffling tasks means spending time recalling the assumptions behind the proposal.

The distinction here is between “communication for collaboration” and “communication for its own sake.” The former speeds up decisions and reduces rework. The latter piles on reports while leaving unclear what needs to be decided.

Interruptions do not always slow work down, however. In a 2008 experiment, participants interrupted by other tasks actually completed the target task faster, with no observed difference in quality. Yet they experienced greater stress and time pressure. These results came from a limited set of experimental tasks and do not measure productivity across an entire company. Even so, they show that finishing faster does not necessarily mean a lighter burden.

Workflow (conceptual diagram)

A request arrives → Priorities are assessed → Work begins → Another request arrives → Priorities are assessed again

This sequence does not mean that every interruption is harmful. When responding to an outage or an urgent customer inquiry, changing plans is the right decision. The problem lies in a system that delivers requests of differing urgency through the same channel with equal prominence.

3. Cutting meetings alone will not solve the problem

Microsoft also reports frequent unscheduled meetings and a tendency for document editing to cluster just before meetings. This suggests that coordination may be growing more complex. But eliminating meetings will not necessarily improve results.

An organization could cut meetings and leave decision-making authority unclear, with the same questions repeated across multiple chats. Using meeting time as the sole measure risks increasing unseen work to check and clarify details.

The measures should be “How many days did a necessary decision take?” and “How many instances of rework followed that decision?” rather than “How many minutes of meetings were cut?” This is the article’s proposal, not an effect Microsoft has demonstrated experimentally.

4. Improve decision-making, rather than simply cutting communication

First, separate the channels through which requests arrive. An incident that must be stopped immediately, a check needed today, and a discussion that can wait until later in the week should not trigger the same notification. Assign responsibility and define decision criteria for urgent communications.

Second, write down what needs to be decided before a meeting. A document may suffice if the purpose is simply to share information. Keep meetings that resolve disagreements, but limit attendance. Measure the quality of decisions rather than the number of meetings.

Third, avoid imposing the same focus time on everyone. Customer-facing roles have different work rhythms from design and writing roles. Test arrangements for each role, checking both response times to customers and the quality of work produced.

Change to testIntended mechanismSide effect to monitor
Communication channels organized by urgencyReduce how often priorities must be assessedImportant messages being missed
Meeting invitations specifying decisions to be madeBring discussions to a conclusionInsufficient information for those not attending
Focus time tailored to each roleSecure uninterrupted time for workDelays in responding to customers

To assess the effects, compare the same measures over several weeks before and after implementation. Busy periods and staffing changes can also shift the numbers, however. Where possible, compare teams doing similar work and assess causation cautiously.

5. Counter-evidence: Is frequent team communication really a bad thing?

Not necessarily. In busy sales teams or incident-response teams, frequent communication can itself create value. Microsoft’s usage signals do not directly measure work outcomes or whether individual communications are necessary. Nor does the study population represent every occupation worldwide.

The report also includes usage data from workplace tools provided by Microsoft itself. It is an important primary source, but readers need to account for two factors. Its analysis is skewed toward Microsoft’s product suite, and its recommendations reflect the company’s strategic interest in AI adoption.

This is why the article rejects a blanket prescription to reduce communication. The target should be unclear requests that force people to revisit decisions repeatedly, while preserving valuable communication.

6. Conclusion: A workplace where decisions are clear matters more than a quiet one

If unfinished work is attributed solely to individuals’ lack of concentration, organizational systems will remain unchanged. Sending a message may impose little burden on the sender, yet leave the recipient facing competing priorities.

This article’s distinctive framing is to manage the “cost of reassessing priorities” rather than notification volume. Notification counts, meeting time, and response speed are easy to observe. But those measures alone cannot show whether work of real value has advanced. Only by also examining time to decision, rework, and the quality of work produced can an organization move closer to improvement.

To try this tomorrow, divide the team’s requests into “urgent,” “today,” and “this week,” and assign a decision-maker to each category. After 1 week, check whether any urgent matters were missed and whether important work moved forward. Reducing communication is not the goal. The goal is to advance important work while preserving necessary communication.

SOURCE

Sources

These are the primary sources we used to check the facts. The article identifies our own analysis.

  1. Sourcehttps://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday
  2. Sourcehttps://doi.org/10.1145/1357054.1357072
  3. Sourcehttps://www.microsoft.com/en-us/worklab/work-trend-index/2025-the-year-the-frontier-firm-is-born
  4. Sourcehttps://blogs.microsoft.com/blog/2025/04/23/the-2025-annual-work-trend-index-the-frontier-firm-is-born/
NEXT BASIS
More in Business →
Business2026.11.14About 7.6 min read READ

Revenue Down 12%, Operating Profit Up 49%: Why Console Unit Sales Alone Cannot Explain Nintendo’s Business

Nintendo’s interim financial results on November 5, 2026, showed that profit rose even as console unit sales fell. However, software’s share of sales was not the only factor. Understanding the profit increase requires distinguishing its drivers, including a one-time factor: US tariff refunds.

Business2026.11.14About 5.3 min read READ

Does Costco’s 10% Revenue Growth Mean Customers Bought 10% More? Separating Gasoline, Exchange Rates, and Gross Profit

In fiscal 2026, Costco increased net sales from merchandise and other sales by about 10% from the previous year. That looks like solid performance for a membership warehouse retailer. But revenue reflects more than the volume customers bought. It also reflects gasoline prices, exchange rates used to convert overseas revenue into dollars, and the impact of adding stores. When revenue grows, what should we conclude has increased? We break down the company’s official US financial results.[1][2]

Business2026.11.13About 5.0 min read READ

Subscriptions Generate 96% of Adobe’s Revenue. That Does Not Necessarily Mean a Stable Business—Read Three Earnings Metrics Separately

In Adobe’s fiscal 2025 financial results, subscription revenue was approximately $22.904 billion out of total revenue of approximately $23.769 billion—about 96%. But a high share of recurring revenue is not the same as retaining customers. Assessing the business’s strength requires reading revenue, ARR, and contracted future revenue separately.