Handling drop-by interruptions without losing your place
Someone is standing at your desk. They need “just a minute.” What do you owe them — and what do you owe the half-finished thought on your screen, the one that will take far longer than a minute to rebuild if it evaporates? Most advice answers with avoidance: close the door, wear the headphones, publish your deadline. Prevention helps, and the sections below use it. But the interruption in front of you has already happened. What it needs is a decision, made in about ten seconds, with words ready for whichever way the decision goes.
The cost, stated as a scenario — not a promise
Price the problem before fixing it, with the numbers labelled for what they are. Take a purely illustrative scenario: four drop-bys in a day, each one short, each one followed by the slower work of finding your place again — re-reading, reconstructing, remembering what the next step was. Even at a modest few minutes of re-entry per interruption, the day loses the equivalent of a solid work block to restarting, and the block it loses is usually the deepest one, because that is when people come looking for you. Your mileage will differ; count your own drop-bys for two days before changing anything, so the fix is aimed at a measured problem rather than a bad afternoon.
The opportunity here is narrow and real: most drop-bys are not emergencies. They are questions that arrived in person because in person was fastest for the asker. A triage that sorts them honestly — some handled now, most handled later at a named time, a few redirected — returns those re-entry minutes without turning you into the colleague nobody can approach.
The ten-second triage
Ask one question, silently: what happens if this waits until my next break in work? The answer sorts every drop-by into one of three classes.
| Class | The test | Your move |
|---|---|---|
| Now | Waiting causes real harm: someone is blocked, a deadline today breaks, a customer or system is waiting | Write the resume note (below), then switch fully — half-attention helps neither task |
| Later | It matters, but nothing breaks if it is handled at a named time today | Defer with the three-part sentence and a specific time — then keep that time |
| Redirect | You are not the owner, or the answer already exists in a document, ticket, or channel | Name the right owner or place, in the sentence, so the asker leaves with a direction rather than a refusal |
The triage is the decision framework underneath everything else here. Get the classification right and the words are easy. Get it wrong in either direction — treating later as now, or now as later — and no script will save the outcome.
The sentences, by class
For later, use the three-part structure that tactful deferrals are built from: acknowledge, state your situation, then state the action with an exact alternative time (s2). Assembled: “That sounds important. I'm mid-report and it's promised within the hour. Let's meet at 2 p.m. in your office and I'll give it proper attention.” The same shape works for repeated interruptions during focused work — name the focused work, offer a specific later time the same day, and, if pressed, ask for an outline to discuss then (s3).
Scripts are starting points, not formulas that control the other person's reaction (s3). Adapt the wording to your voice; keep the structure, because the structure is what makes the sentence work — the acknowledgment proves you heard them, the situation explains without apologising, and the exact time proves the deferral is real.
For now, the sentence is shorter: “Okay — give me twenty seconds to note where I am, and I'm yours.” For redirect: “That's Priya's call — she's in the channel this morning, and the spec is pinned there.” One line each, then act on it immediately.
The supervisor case deserves its own line, because rank changes the negotiation. When your manager interrupts, offer the choice explicitly: defer the current work to a stated time and meet now, or finish it and come right after — letting them see the situation and make the priority decision (s2). That is not pushback. It is the trade-off, priced, handed to the person who owns it.
Before you switch: the resume note
When the triage says now, buy back your place before you give the interruption your attention. Pause for about twenty seconds and jot a handful of key words — what you were doing, what the next step was, how the pieces connect — so the ideas survive the switch (s1). Twenty seconds is the published figure for brainstorming work, and it generalises: a note that makes sense only to you is enough, because you are the only one who has to resume from it.
Match the note to the work. For writing, the cheaper return is re-reading: when you come back, re-read the last few paragraphs and let them reload the thread, instead of expecting to resume mid-sentence (s1). For analysis or code, the note carries the state — the open question, the figure you were checking. And when refocusing genuinely will not happen, do not force it: stand up, walk, get a coffee, and return fresh rather than grinding at a cold task (s1).
The procedure, start to finish
- Publish your focus windows first. Before a major piece of work, tell the colleagues who need to know — boss, immediate teammates — that you are on a deadline and should be reached only with items that cannot wait (s1). Prevention is what makes the triage rare.
- Triage in ten seconds. Now, later, or redirect, by the test above — what breaks if it waits?
- Say the sentence for the class. Three parts for a deferral, twenty seconds for a switch, one line for a redirect. No improvised essays.
- Capture the deferred item where the asker can see it. Write it on the list or the board, in front of them. A visible capture is the difference between a deferral and a brush-off — the follow-up is visibly on your list (s1). A desk sign asking callers to leave a note, with a callback when you are free, does the same job when you cannot look up at all (s2).
- Write the resume note before any switch. Key words, next step, connections — twenty seconds, before the conversation starts, not after.
- Keep the later time. When 2 p.m. comes, go. A deferral you honour once teaches colleagues the system is real; one you blow teaches them to insist on now next time.
- Repeat a pushed limit without new reasons. If someone presses, restate the same limit calmly rather than adding justifications — each new excuse is a fresh target for debate (s3).
What success looks like: drop-bys get shorter and rarer within two weeks, nobody with a genuine emergency waits, and your return to interrupted work starts from a note instead of a blank stare at the screen.
When this is the wrong tool
Some roles are interruption-shaped by design — support, reception, on-call, a manager of a team in a live incident. Sorting those interruptions away is not focus; it is absence. The triage still helps there, but inverted: protect the response work as the job, and schedule the solo work into the quiet windows instead. And if one person's drop-bys survive every step above — published windows, named times, kept appointments — the problem has stopped being a workflow problem. Raise it as one, with two weeks of your counted log as the evidence.
Kill criterion: count drop-bys and re-entry time for two days before starting, and again after two weeks of the procedure. If the count has not fallen, the triage is not the bottleneck — the team's norms are — and the next move is a team-level agreement about interruption windows, not a better script for you alone.
General information only. Follow your employer's policies and your team's working agreements where they cover availability and response times.
— Sterling Cole, Money Writer — Earning Desk