Dana runs projects for a fourteen-person design studio, and her Tuesday looks like this: a client asks over email whether the homepage mockup is approved. She checks her inbox, doesn't see it, checks the shared drive, finds three files named "final," pings the designer on Slack to ask which one is real, waits four minutes for a reply, then opens the project spreadsheet to update the status column so it matches what Slack just told her. Eleven minutes, one fact.
The tax nobody puts on the timesheet
None of that shows up as a line item anywhere. It's not a meeting, it's not a task, it's not billable. It's the unlogged tax of finding out what's true before you can do the thing you actually opened your laptop to do. Multiply Dana's eleven minutes by however many "wait, where is that" moments happen in a day, across a team, across a year, and the tax stops being trivial.
Why the interruption costs more than the interruption
The well-documented finding from research on task switching isn't that switching itself takes long, it's that getting back to where you were takes longer than the switch does. You don't just lose the thirty seconds it takes to open Slack, you lose the run-up you'd built toward the thing you were doing before Slack pulled you away. Do that six times an hour and you never actually reach deep, uninterrupted work at all, you just live in the recovery period between interruptions.
Where the minutes actually go
On most teams the same handful of hunts repeat every day:
- Checking a spreadsheet because the task tracker doesn't have current status
- Searching Slack for a decision that was made three weeks ago and never written down anywhere durable
- Emailing someone to ask for a file that's sitting in a drive folder nobody remembers the name of
- Opening a separate wiki tool to find a spec that has since drifted out of sync with the actual task
Each one is small. None of them shows up on a status report. All of them are avoidable, because none of them are actually hard problems, they're just information kept in the wrong place.
One place beats five tools
The fix isn't a faster Slack search or a better-organized spreadsheet, it's not needing either one for most questions. That's the whole premise behind organizing work into spaces, folders and lists instead of a flat pile of channels and files: the mockup lives on the task about the mockup, the client's approval is a comment on that same task, and the brief that explains why the design looks the way it does is a doc nested one click away, not a separate tool with its own login and its own search box.
What Tuesday looks like afterward
Run the same scenario with the work in one place. The client's question arrives, Dana opens the task, the comment thread already has the designer's "here's the final version, approved by the client Monday" note attached to the actual file, and the status column already reflects it because updating the status was the same click as leaving the comment. Eleven minutes becomes forty seconds. That difference, repeated across a team every day of the week, is the actual argument for structure: not that it looks tidy, but that it gives back the minutes context switching quietly takes.