275. That’s how many times a day the average worker gets pulled away from what they were doing, a meeting invite, an email, a ping. Not once an hour. Every two minutes

Microsoft’s Work Trend Index puts a number on the feeling: the average knowledge worker is interrupted roughly every two minutes during core hours, about 275 times a day, by a meeting invite, an email, or a chat ping. Communication itself, meetings, email, chat, now eats up 57 percent of the average workday. Building things gets whatever is left over.

And every interruption costs more than the interruption. Gloria Mark’s attention research at UC Irvine, one of the most cited studies in the field, found it takes about 23 minutes to fully return to a task after being pulled away from it. Do the math on 275 pings a day and you’ll understand why nobody on your team seems to finish anything in one sitting. It’s not that people are distractible. It’s that they’re working inside a system that scatters their attention on purpose, even if nobody designed it that way.

The usual advice stops at the symptom. Turn off Slack notifications. Set email hours. Block your calendar. Fine tactics, and they’ll buy someone an hour back here and there. But none of it touches the actual reason people keep interrupting each other: work doesn’t live anywhere.

A contract’s status sits in somebody’s inbox. A vendor’s onboarding stage is buried in a WhatsApp thread. A project update is wherever the last person happened to post it. When there’s no single place to look, people ask instead. And asking is what fills your calendar.

What This Actually Looks Like on a Procurement Team

Picture a procurement lead trying to find out whether a vendor contract has been signed. It’s not in the contract, so she checks her inbox. Not there either, so she messages the vendor manager. He’s in a meeting, so she pings legal instead. Twenty minutes later she has an answer, and everyone she interrupted has lost their thread on whatever they were doing before she reached out.

Multiply that by every contract, every approval, every onboarding step your team handles in a given week, and the picture gets clearer: most of the meetings and messages clogging your day aren’t about doing the work. They’re about locating it.

Turning Off Notifications Doesn’t Fix a Broken Workflow

Personal discipline can only absorb so much of a structural problem. If the contract itself doesn’t carry its own status, the procurement lead will keep asking three people where things stand no matter how well she manages her notifications. And each of those people will lose their 23 minutes anyway.

The companies that have actually solved this didn’t train employees to filter noise better. They took away the reason to ask.

37signals, the company behind Basecamp, has said that 98 percent of its internal communication happens inside one tool, no separate email habit, no side chat app, nothing to chase down. GitLab runs a version of the same idea at a much bigger scale: its internal handbook is the single source of truth for how the company works, written down instead of passed around in meetings. CEO Sid Sijbrandij has said the effect is that when someone has a question, the answer is usually already documented, no need to pull a colleague away from their work to get it.

Neither company got here by asking people to be more careful about pinging each other. They got here by giving the work a fixed address.

Give the Document Somewhere to Live, and the Pinging Stops

For a team running contracts, approvals, and vendor paperwork rather than software sprints, the equivalent fix looks like this: the document becomes the update. Nobody has to explain a status in a meeting or type it out in a message, because anyone can open the file and see it: drafted, under review, awaiting signature, approved.

That one shift removes most of the reason people interrupt each other in the first place. Nobody asks “where are we on this” because the document already says so. A new vendor doesn’t need three messages to figure out what needs signing and when. Approvals move because there’s nowhere for them to get stuck waiting on a status check.

This is the specific gap Flowmono Automate is built to close. It attaches status, routing, and approval history directly to the document, so the update travels with the work instead of living in a separate channel someone still has to babysit.

For teams juggling procurement, vendor onboarding, or any process with more than one approver in the chain, this isn’t a nice-to-have. It’s the difference between a calendar full of “just checking in” and a workflow where the answer is already sitting there, waiting to be opened.

None of this gets fixed with a stricter Slack policy or a better notification filter. It gets fixed when the thing being tracked can answer its own question, so people stop having to ask each other in the first place. If your team’s meetings are mostly people trying to find out where something stands, the problem was never how they communicate. It’s that the work never had anywhere to live.

See what that looks like against your own contracts and approval flows. Request a Flowmono demo and walk through it with your own paperwork.