Research question

How strong is the evidence that coordination overhead consumes meaningful capacity in small-business operations?

This article examines published workforce and project evidence through the narrow lens of small-business operations coordination. It does not assume that a vendor survey describes every organization, and it does not treat correlation as causation.

What the evidence shows

Microsoft’s 2023 Work Trend Index reported that employees in its Microsoft 365 telemetry spent 57% of their time communicating and 43% creating; 68% of surveyed workers said they lacked uninterrupted focus time. Asana’s 2023 Anatomy of Work study, based on 9,615 knowledge workers, reported 3.6 hours lost weekly to unnecessary meetings and 62% of the workday lost to repetitive, mundane tasks.

Operations-specific analysis

The two studies define activity differently, so their percentages should not be added or treated as a universal small-business benchmark. They do converge on a narrower conclusion: communication, search, meetings, and routine coordination occupy a material share of knowledge work. In a small company, that load is concentrated because the same owner or specialist often receives requests, schedules work, chases inputs, and reconciles status. The operational problem is therefore less “too much communication” than communication without a durable record, owner, or next action.

The appropriate boundary is consistent: a support professional may maintain records, assemble source evidence, coordinate agreed follow-ups, and flag exceptions. Leaders and subject-matter owners retain policy, priority, personnel, and substantive project decisions.

Practical conclusion

A defensible response is to measure coordination load locally for two weeks: meeting hours, request intake, status-chasing touches, missing-information loops, and time spent locating records. Delegate the repeatable recording and follow-up layer only after those categories are visible. The research supports treating coordination overhead as a capacity issue, but the company’s own activity log should determine which routines merit redesign.

Sources and interpretation limits

These sources use different populations, definitions, and methods. Their figures are not directly additive, and associations should not be read as proof of causation. The analysis above uses them to test a bounded operations question and states where local measurement is still required.