Dana is building a quote for a long-standing client, pricing sheet open, three tabs of specs lined up in order. She's four line items in when a coworker leans over her desk.

"Hey, is the Miller order shipping today?" Dana checks, answers, turns back to her screen. Twenty seconds, start to finish.

But she doesn't land back where she left off. She retypes a line item that was already there. She skips a discount field she'd filled in twice before catching the gap. Nobody logs any of it, because nothing about it looked like a delay.

This is attention residue. When Dana switches from the quote to the question, her mind doesn't fully switch with her. Part of it stays attached to the pricing sheet, the specs, the place she'd stopped, even as she answers something unrelated. Then when she returns, that residue is still there, competing for the same mental space she needs for the task in front of her.

Research on workplace interruptions backs this up: knowledge workers get interrupted roughly every six to twelve minutes, according to research summarized by Harvard Business Review, and performance on the task right after an interruption drops by 30 to 40 percent, according to research summarized by Calendar.com. The interruption costs thirty seconds. The recovery costs ten times that, and nobody counts it. It never shows up as a missed deadline or a visible gap in the day. It shows up as a mistyped line item, a skipped field, a slightly slower quote, five or six times over, spread across everyone who got asked something quick.

The fix isn't asking Dana to concentrate harder or ignore her coworkers. It's keeping the quick question from reaching her while she's mid-quote: a vendor call comes in → the question is classified as a routine status check → it's routed to an automated lookup → it's resolved before it reaches Dana. She never picks it up. She never has to switch back.

The same routing works for the questions that used to travel through her all day: availability checks, simple pricing lookups, "did this ship yet." Each one used to cost thirty seconds of her time and several minutes of her focus. Multiply that by five or six interruptions a day, across everyone on the floor who fields quick questions, and the hours add up fast, not in a line on the schedule but in the slower, sloppier version of every task that follows an interruption. Removing the interruption removes the residue with it.

Webspenser · Reply to this email with the moment you'd like covered next.

Two things from the blog worth your time this fortnight. Plus one extra.

Unchecked AI agents for business risk fast, costly errors. Map your automation boundaries and put technical kill switches in place before systems fail.

Stop sending robotic text replies to missed calls. Use our prompt frameworks and edit rules to build a human AI receptionist for small business.

Harvard Business Review · The original research behind the six-to-twelve-minute interruption interval, with practical steps for reducing it.

Why people in your business behave the way they do, and what technology can do about it. Bi-weekly, three minutes.