Your Brain Wasn't Built for 47 Interruptions a Day

You’re deep in a bug. You’ve got the call stack in your head, three files open, and you’re about to pinpoint the issue. Then someone pings you about a different work item. You open it in Azure DevOps, check the status, leave a comment, and try to go back to what you were doing.

Except now you can’t remember which file you were in. Or which work item it was for.

This isn’t a discipline problem. It’s a brain problem — and there’s a solid body of research that explains exactly why.

The 23-minute tax

Gloria Mark, a researcher at UC Irvine, found that it takes an average of 23 minutes and 15 seconds to fully regain focus after an interruption.[1] Not to finish the interrupted task — just to get back into the same mental state.

For developers, that number is probably optimistic. When you’re holding a mental model of code — variables, state, control flow — the recovery time can stretch to 30–60 minutes. Sophie Leroy at the University of Washington calls this attention residue: even after you switch back, part of your brain is still stuck on the previous task.[2]

A study tracking 50 developers over two weeks found they averaged 47 interruptions per day. With 23 minutes of recovery each, the math is brutal. Those developers managed only 2.3 hours of actual deep work out of an 8-hour day.

Working memory has hard limits

Your working memory — the part of your brain that holds and manipulates information in real time — can juggle roughly 4 items at once. That’s it. Not 7 (that number was revised decades ago). Four.

Every context switch forces your working memory to dump its current contents and load new ones. Stanford researchers found that chronic multitaskers had inferior working memory performance and more difficulty filtering out irrelevant information.[3] The more you switch, the worse you get at it.

For developers, working memory is everything. You need it to hold the shape of a function, the state of a debugger, the relationship between three services. When you interrupt that to go find “which work item was I looking at earlier?” — you’re burning cognitive resources on recall instead of problem-solving.

The cortisol spiral

It’s not just about lost time. Research shows that frequent interruptions elevate cortisol levels — your body’s stress hormone. Over weeks and months, this chronic low-grade stress contributes to burnout, irritability, and reduced problem-solving depth.

A 2024 narrative review found that digital multitasking is associated with measurable changes in brain function, including reduced attention capacity and impaired executive function — the cognitive skills you need most for planning, debugging, and architectural decisions.[4]

This isn’t about being “bad at multitasking.” It’s physiology. Your brain literally wasn’t designed to hold 12 work items in rotation while fielding Slack messages and jumping between browser tabs.

What actually helps

The research points to a few clear strategies:

Reduce what you need to remember. Every piece of context you offload from your brain is working memory freed up for actual work.
Minimize voluntary context switches. Half of context switches are self-initiated — you interrupt yourself to check something, find a work item, or look up what you were working on yesterday.
Make resumption fast. If you can instantly see what you were last working on, recovery time drops dramatically.

This is the exact problem we built TicketHop to solve. It’s a Chrome extension that automatically tracks every Azure DevOps work item you visit — no clicks, no bookmarks, no manual logging. Just browse Azure DevOps as you normally do, and your history is there when you need it.

Open the popup with Ctrl+K (or Cmd+K on Mac) and you instantly see your recent work items. Press # to jump to any work item by ID. No searching through browser history, no trying to remember “was it bug 4523 or 4532?”

Less recall, more focus

The goal isn’t to track your time or measure your productivity. It’s simpler than that: stop wasting mental energy on remembering what you were doing.

Add private markdown notes to any work item — “left off at the failing test in UserService” — and your future self doesn’t need to spend 10 minutes reconstructing context. Organize items into custom lists when you’re juggling multiple streams of work.

If you work across devices, encrypted sync keeps everything available with zero-knowledge, end-to-end encryption. Your notes and lists stay private and accessible wherever you need them.

Your brain will thank you

The science is clear: context switching is expensive, working memory is limited, and the cumulative effect is real fatigue — not the kind you solve with coffee, but the kind that erodes your ability to do your best work over time.

You can’t eliminate interruptions. But you can eliminate the ones you inflict on yourself — the “where was I?” moments, the searching, the mental bookkeeping that burns cycles without producing anything.

TicketHop is free to install and works out of the box with no setup. If you spend your day in Azure DevOps, give your working memory a break.

References

[1] Mark, G., Gudith, D. & Klocke, U. (2008). “The Cost of Interrupted Work: More Speed and Stress.” Proceedings of CHI 2008, ACM. https://ics.uci.edu/~gmark/chi08-mark.pdf

[2] Leroy, S. (2009). “Why Is It So Hard to Do My Work? The Challenge of Attention Residue When Switching Between Work Tasks.” Organizational Behavior and Human Decision Processes, 109(2), 168–181. https://www.researchgate.net/publication/46489122

[3] Ophir, E., Nass, C. & Wagner, A. D. (2009). “Cognitive Control in Media Multitaskers.” Proceedings of the National Academy of Sciences, 106(37), 15583–15587. https://pubmed.ncbi.nlm.nih.gov/19706386/

[4] Almufarrij, I. & Bhutta, M. F. (2024). “Understanding the Influence of Digital Technology on Human Cognitive Functions: A Narrative Review.” Cureus, 16(11), e74568. https://pmc.ncbi.nlm.nih.gov/articles/PMC11609471/