23 minutes, every time
The research is consistent and brutal: after an interruption, it takes about 23 minutes to fully refocus on the original task. Not to glance back at it — to actually reload the mental context and get productive again.
The problem is that knowledge work is nothing but interruptions. A Slack ping, a ticket, a quick question, a context switch to check the CRM. Each one looks free. None of them are.
Doing the math
Say an engineer is interrupted six times a day. At 23 minutes of refocus each, that is more than two hours of prime cognitive time evaporated before lunch — not spent on the interruption itself, just on recovering from it.
Multiply that across a team and a quarter, and context switching is quietly one of the largest line items in your engineering budget. It just never shows up on an invoice.
Where the hours actually go
The insidious part is that most of these switches are not even real work. They are lookups. Checking whether that error is known, finding which ticket relates to a report, confirming the status of a deal. Low-value queries that shatter high-value focus.
That is precisely the category an agent absorbs. It already has the context, so the human never has to leave theirs.
Buying back focus
When agents handle the watching, the correlating, and the status-checking, interruptions stop reaching your team as raw noise. They arrive pre-answered, or they don't arrive at all.
The return is not measured in features. It is measured in uninterrupted hours — the scarcest and most valuable resource your team has.