Nobody pops into a sterile production suite. I stood in one recently, at a pharmaceutical production site, and getting in took me twenty minutes: the airlocks, the stepwise gowning, gown and re-gown, gloves over gloves, because on the other side of that door medicines were being filled that would end up in patients’ bloodstreams, and contamination in that room has two properties that make it uniquely vicious. It is invisible at the moment it happens, and its damage appears later: the batch looks perfect when it leaves the line, and the sterility test that catches the failure reads out days afterwards. So the discipline is absolute, not because anyone in there enjoys ritual, but because nobody can see a microbe, and the whole industry has learned to respect what it cannot see. The door is the whole game. Keep it closed, and the room does what only that room can do. Prop it open for one quick question, and you have not lost a minute. You have contaminated a batch, and you will find out next week.
Your best thinking happens in a cleanroom, and most researchers run it with the door propped open. The contaminant has a name in the research literature, attention residue, and it behaves just like the microbes: invisible when it enters, billed later, in work that looked fine while you did it. This article is about the mechanism, why research work is more vulnerable to it than almost any other profession’s, and the entry protocol that protects the room, the discipline the term deep work, coined by Cal Newport, has made famous [1], translated for the realities of a research week.
Table Of Contents:
- Peter answers one Slack message during the analysis
- Attention residue: the contamination, measured
- “Protecting deep work time”: the discipline, named from inside
- The entry protocol: five rules for the door
- What Peter’s blocks produce now
- A few thoughts for the researcher whose work lives at the bench
- FAQ
- References
Peter answers one Slack message during the analysis
Peter, whose timer habits I wrote about in my post on the Pomodoro technique for researchers, has since learned to dose his focus blocks properly, and believes, reasonably, that his attention problem is solved. Watch one of his 90-minute analysis blocks from the inside, though. Twenty minutes in, deeply into the model, a Slack notification: a labmate’s quick question about a reagent. Peter answers it, forty seconds, barely an interruption, and returns to the analysis. Here is what Peter cannot see, and what makes this the cleanroom problem in miniature: he did not return. A measurable part of his mind stayed with the reagent thread, and for the next stretch of the block he worked on his hardest problem with partial cognition, producing analysis that felt normal and was quietly shallower, the defect that shows up later, as the argument in section four that a reviewer will call underdeveloped. The door was open for forty seconds. The batch took the particles for half an hour.
Attention residue: the contamination, measured
The contaminant got its name in 2009, when the psychologist Sophie Leroy ran a series of experiments on task switching and found something with an unnerving property [2]: when you switch from task A to task B, part of your attention simply stays behind with A. She called it attention residue, and while it lingers, your performance on B is measurably worse. And here is the unnerving part: you cannot feel it. You are thinking with less than a full mind and experiencing it as a full one. Two of her findings matter enormously for how researchers actually work. The first: residue is worst when the interrupted task is unfinished, because open loops cling, and Peter’s forty-second reagent answer left his analysis loop hanging wide open behind it. The second, and less intuitive: even finishing a task does not fully clear it if you finished under time pressure, which is why the morning after a submission deadline is so strangely useless; the manuscript is gone, and the mind is still processing it. Multitasking, in this light, is not doing two things at once, which the brain cannot do with demanding tasks anyway. It is rapid switching with a residue charge on every switch, a workday spent walking in and out of the cleanroom and wondering why the batches keep failing.
Now look at what a doctorate is made of, and the reason this mechanism should worry researchers more than almost anyone becomes an argument you can state in one sentence: research tasks are structurally open. A manuscript is never finished, only paused; an analysis always has a next question; the experiment’s result is pending by design. Other professions close their loops at the end of a task; research work is loops that cannot close for months, which means the residue-generating condition, unfinished business, is not an occasional state of your tasks. It is their nature. A researcher who switches freely between three open projects and an inbox is running the highest-residue workload the mechanism allows, and then blaming their focus.
“Protecting deep work time”: the discipline, named from inside
Participants who build the alternative choose their words in a way worth noticing. Here is one, summarising what a training’s worth of practice taught them:
“I learned that focusing on the most important task each day leads to real progress. Planning realistically, protecting deep work time, and reviewing weekly goals keep me accountable and reduce stress.”
Look at the verb this researcher chose: protecting. Not finding deep work time, not trying to focus, protecting, which is an engineering word, the cleanroom’s word, and they arrived at it from practice rather than from touring a sterile production line. That is the entire reframe this article asks for: focus is not a virtue you summon, it is an asset you protect, with structure, from a contaminant you cannot feel entering. And notice what the protection bought, in their accounting: real progress and reduced stress in the same sentence, because a protected block does not just produce better work, it ends the low-grade all-day scatter of a mind carrying residue from everything into everything.
The entry protocol: five rules for the door
The cleanroom’s insight is that purity is a property of the entry protocol, not of the person inside. Five rules, all of them installable this week, and all of them doing the same job: keeping the door closed.
Gown up: a fixed start ritual. Ninety seconds that tell your brain the room has changed: same desk state, notifications off, phone physically elsewhere, one line written stating the block’s single task. The ritual is not decoration; it is the airlock, and its sameness is what makes it work. I learned this rule in its physical form during my own PhD, in the isotope lab. Getting in meant gowning up; getting out meant checking out; so every entry carried a real time cost, and nobody just popped out for a quick something. And once inside, you had at hand only what the task in front of you needed, because anything extra you brought in risked contamination and a decontamination bill. Entry cost, one task, nothing spare in the room: the isotope lab was running the deep work protocol before I had a name for it.
One batch at a time: a single named task per block. “Work on the paper” admits fifteen sub-tasks and therefore fifteen internal switches. “Draft the methods section” is one batch. The block’s task should be named before entry, in writing, which is also what makes the residue check at the end possible.
The capture pad: where intrusions go instead of in. Thoughts, remembered emails and labmates’ reagent questions will arrive mid-block; the rule, the same deferral rule as in that Pomodoro post, is that they get written on a pad and answered after. The pad is what makes the closed door sustainable rather than heroic: nothing is lost, everything is queued, and the forty-second Slack answer waits twenty minutes and costs nothing.
Close the loop on exit: a written next action. Leroy’s open-loop finding gives the shutdown its scientific job: a block that ends with “next: rerun model with the corrected variable” written down is a loop your mind can release, which protects not just this block but the next one, and your evening. This is the same boundary as the daily shutdown in my article on PhD burnout, doing residue control instead of recovery, same tool, second job.
Place the room where your best hours are. A protected block at the wrong time protects mediocre cognition; the scheduling half of this discipline, chronotypes and peak windows, is the subject of my article on how many hours a PhD student should work, and the two pages are designed to be read together: that one decides where the room goes, this one keeps its door closed.
What Peter’s blocks produce now
Peter added two things to his existing 90-20 rhythm: the phone left in his bag across the lab, and the capture pad, on which the reagent question now waits its twenty minutes. What Peter actually reports after a month is not that his focus feels different; residue was never feelable, which is the whole problem. It is that the output changed texture. The analysis sections that used to come back from his supervisor marked underdeveloped stopped coming back, and one participant’s account of the same practice names where the gains concentrate: “Dedicated time blocked deep work sessions have helped me especially for brain-stroming ideas/experiments and writing.” Ideas, experiments, writing: the three most residue-sensitive things a researcher does, which is to say the three that were being quietly taxed all along. The tax was invisible. The refund is not.
A few thoughts for the researcher whose work lives at the bench
And if you have been reading this thinking it describes theorists, your day is pipettes and incubation timers and a shared machine, not four-hour writing blocks: mine was too. The cleanroom translates, because you already work in one. Bench work has natural pockets, the 40-minute incubation, the run on the instrument, and the fragmented researcher spends them on email, converting every pocket into a residue generator aimed at the afternoon’s writing. Now, some nesting does work at the bench, and it is worth being clear about why. Those gaps between steps, five minutes, fifteen, twenty-five, invite you to slot tasks into them, and when the nested task is mechanical, labelling tubes, preparing the next buffer, walking through an established protocol step by step, the cost is small, because residue degrades demanding thought, and a protocol you could run half-asleep asks nothing of the part of the mind that carries residue. That is why it feels free. It is not quite free: every switch still pays a small toll, and a day of fully nested pockets ends with the gaps all spent and the thinking work still waiting, now facing an evening mind. So the bench adaptation is modest and concrete: protect two or three of the week’s largest pockets in advance as named deep blocks matched to real gaps; nest only the mechanical work into the small ones; run the capture pad at the bench, because the deferral rule works in a lab coat; and accept the zoning truth I map from the other side in my post on protecting research time as a PI, that some days are legitimately interrupt-driven and the win is making the protected pockets structural rather than hoping for a monastery. The skills underneath all of it, the planning that creates the pockets and the discipline that defends them, are what Fast Forward trains across seven weeks, with over 1,500 individuals trained at more than 30 institutions. Nobody ever built a sterile production line and left the door propped open because the operators were busy people. Your best thinking is the most expensive room you own. Put a door on it.
FAQ
What is deep work and why does it matter for researchers?
Deep work, the term is Cal Newport’s, is cognitively demanding work done in sustained, distraction-free blocks, and it matters for researchers more than for most professions because of attention residue: every task switch leaves part of your mind on the previous task, degrading the next one invisibly, a mechanism the psychologist Sophie Leroy identified in 2009. Research tasks are structurally open, manuscripts pause, results are pending, so researchers carry the highest residue loads of any profession, mostly without knowing it.
Why is multitasking bad for research?
Because multitasking on demanding work is really rapid switching, and every switch is billed: residue from the interrupted task degrades performance on the next, worst when the interrupted task is unfinished, which research tasks always are. The damage is invisible while you work and appears later, as the analysis a reviewer calls underdeveloped. A forty-second message answered mid-block costs half an hour of full cognition.
How do I do deep work during a PhD?
Run an entry protocol, not a willpower test: a fixed 90-second start ritual with the phone physically elsewhere; one named task per block; a capture pad where mid-block intrusions get written instead of followed; a written next action on exit, which releases the open loop; and blocks placed in your chronotype’s peak hours. Two to three protected blocks a week, defended like meetings, beat a fragmented forty hours.
Can lab scientists do deep work?
Yes, inside the bench day’s natural pockets: incubations, instrument runs, and the gaps between physical tasks. Protect the week’s largest pockets in advance as named blocks instead of spending them on email, nest only mechanical, protocol-driven tasks into the small gaps, since those ask little of the mind that carries residue, run the capture pad at the bench, and accept that some days are legitimately interrupt-driven, the goal is structural pockets, not a monastery. Fragmented pockets are where a bench scientist’s writing quality quietly leaks away.
References
[1] Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing.
[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.
Dr Nadine Sinclair
Dr. Nadine Sinclair is a molecular biologist, strategy consultant and co-founder of Mind Matters. A scientist by training and at heart, she conducted her doctoral research at the Max Planck Institute for Biophysical Chemistry. She has 30,000+ hours of hands-on project management experience, built across 18 years as a strategy consultant at McKinsey and as an independent consultant, working with research institutions, foundations, pharmaceutical and biotech companies and governments. She is the co-creator of the Personal Resilience Indicator and the author of On Track. Since 2018, over 1,500 researchers from more than 30 institutions have trained with Mind Matters.