Most AI productivity advice assumes a quiet morning and one big project. This is for the days when other people's questions decide your schedule.
Write down what interrupts you for a week and sort it into catch up, re-answer and re-shape. Save a ready-to-paste prompt for the most common type, use the 30-second handoff test before each use, and read every output against its source before it goes anywhere. Judgment calls and anything personal stay with you.
Most advice about AI and productivity is written for a day you may not have. It assumes a clear morning, a protected block for focused work and one big project waiting for a smarter approach. Plenty of jobs don’t look like that. An operations coordinator, an executive assistant or an HR generalist spends most of the day answering whoever is in front of them, and the project they meant to use AI for gets the last tired hour, if it gets anything.
That’s why AI can feel like it should help and somehow doesn’t. Opening a chat window, explaining the situation and checking the answer takes a few minutes of attention, and on a reactive day nobody has a few minutes in one piece.
A coordinator gets halfway through drafting a supplier summary when a director asks where a delivery is. Then a new starter asks how expenses work. Then a thread she was copied into an hour ago turns out to need her answer. By late afternoon the summary is still half-written, and the AI tool has been open in a tab all day without doing much.
The interruptions are the part worth handing over, because most of them are the same few requests in different clothes.
How common is this? Microsoft’s anonymised Microsoft 365 data from early 2025 suggests that for the most heavily pinged fifth of users, a meeting, email or chat arrives about every two minutes during core hours.[1] That’s the busiest fifth, not everyone, but if your role is the one other people route their questions through, it probably sounds familiar.
This guide is about everyday productivity with AI for that kind of day: which interruptions to hand over, how to have the prompt ready, when it isn’t worth it, and what stays yours. If your problem is planning the week rather than surviving it, our guide to using AI for time management covers that side.
Write down what interrupts you for a few days and the list tends to shrink to a handful of shapes. Three of them make up much of a reactive day, and AI handles them well because the source material already exists. You’re asking it to read, match or convert rather than decide.
A Future Factors working model for reactive days, based on our own judgment about where AI’s strengths meet everyday requests. It is not a research-validated typology.
An HR generalist gets a message from a new starter asking whether unused leave carries over. She’s answered versions of it before, each from a different person with a different detail attached. The policy page has the answer. What takes time is reading it again, finding the clause and writing it kindly for someone who has just joined. That’s a re-answer, and it’s an AI job: paste the clause and the question, get a draft that answers this person’s version, check it against the clause and send.
Catch-up requests are the ones people underrate. Joining a long thread halfway through costs more than it looks, because you rebuild the context before you can do the small thing being asked. A summary of what changed and what’s addressed to you gets you back in faster. Our inbox triage workflow applies the same idea to a full inbox.
Some interruptions fit none of the three, and those stay with you:
There’s an argument for handing over the repeatable ones even if each only takes a minute. In a small 2008 lab experiment by Gloria Mark and colleagues, people who were interrupted finished their tasks faster with no loss of quality, but reported more stress, frustration, time pressure and effort.[2] With 48 participants in a lab, hold it loosely, but the pattern rings true: you keep up by speeding up, and the cost lands on you rather than the work.
The reason AI doesn’t get used on a busy day is usually set-up time, not capability. When the director is waiting for an answer, nobody stops to write a careful prompt. So the prompt has to exist before the interruption does.
Set AI up for an interruption before it arrives, not while someone is waiting for your answer.
In practice that means three saved prompts, one per interruption type, written once and reused. These work in any general-purpose assistant your organisation has approved.
| Interruption | Prompt to save | What you check before using it |
|---|---|---|
| Catch up | I’ve been away from this thread or document. Here it is: [paste]. In five bullets or fewer, tell me what changed, what’s been decided, what’s still open, and anything addressed to me or waiting on my reply. Quote the exact line for anything addressed to me. If something is unclear, say so instead of guessing. | Open the quoted lines in the original and confirm they say what the summary claims. |
| Re-answer | Here is how this has been answered before: [paste the policy text, tracker notes or your earlier reply]. A [role] has asked: [paste question]. Draft a reply in under 120 words that answers their version of the question using only the source above. Flag anything in their question the source doesn’t cover, and don’t fill that gap. | Read the source clause next to the draft, and answer any flagged gap yourself. |
| Re-shape | Turn the text below into [a three-bullet update for my manager / a short email to a client / a quick chat message]. Keep every name, number and date exactly as written. Don’t add claims or promises. Then list anything you left out. [paste] | Compare names, numbers and dates against the original, and read the left-out list. |
Each prompt asks the tool to show its working: quoted lines, flagged gaps or a left-out list. That’s what makes the check fast.
Where you keep them matters more than people expect. A prompt buried in a document won’t get used on the day you need it most. Places that tend to work:
The re-answer prompt does better with a standing source. An executive assistant who keeps a short “how things work here” note, covering travel rules and who approves what, can paste it in all week, and the next person in the role inherits it.
Not every interruption is worth handing over, even when it fits one of the three types. A one-line question from a colleague is faster to answer yourself than to paste anywhere. So the useful question is whether the round trip of briefing, waiting and checking costs less than doing it, rather than whether AI can do it at all.
An account manager gets a client email asking to move a review meeting and confirm a couple of figures from last quarter. Drafting a reply with AI would take longer than typing three sentences, and the figures need checking against the source either way. She types it herself. Later that morning the same client sends a long email chain from their side, asking for a view by tomorrow. That one goes into the catch-up prompt straight away.
Here’s the quick test we’d use, based on our own working judgment rather than a measured threshold.
| Request | Can you brief it in about 30 seconds? | Can you check it faster than you’d write it? | Verdict |
|---|---|---|---|
| Summarise a long thread you were added to | Yes, paste and one line | Yes, check the quoted lines | Hand it over |
| Answer a new starter’s policy question from the policy page | Yes, with the clause pasted | Yes, compare to the clause | Hand it over |
| Turn meeting notes into actions with owners | Yes | Mostly, if names and dates are kept | Hand it over, check names |
| Reply to a one-line question from a colleague | Briefing takes longer than answering | Not relevant | Do it yourself |
| Reply to an upset customer | Yes | No. Tone needs your judgment, not a fact check | Draft it yourself, maybe ask AI to check tone |
| Decide which of two urgent requests goes first | No. The context lives in your head | No | Yours |
Ask two more questions before any hand-over: is a small mistake cheap and easy to spot, and is this content allowed in the tool you’re using? A no to either means it stays with you, whatever the first two columns say.
Hand it over only if you can check the answer faster than you could write it yourself.
The checking column matters because AI output tends to sound just as confident when it’s wrong as when it’s right. In a 2023 field experiment with Boston Consulting Group consultants, people using AI on tasks it handled well did better and faster work. On a task picked to sit just outside what the AI could do, they were 19 percentage points less likely to reach the correct answer than colleagues without it.[3] On a busy day, that points to handing over work you can verify quickly, because nothing about a polished answer tells you which side of that line you’re on. Our guide to fact-checking ChatGPT has a reusable routine for the numbers.
The test also explains why some days AI saves nothing: if most of what arrived was one-liners and judgment calls, there wasn’t much to hand over. For a closer look at where time savings show up and where the bottleneck just moves, see AI as a workflow accelerator.
Where AI does real work in a reactive day, be exact about who owns what. Someone wanted your answer, and that doesn’t change because a tool drafted it.
| What AI does | What you still own | How it gets checked |
|---|---|---|
| Summarises a thread or document you’ve been away from | Deciding what needs your reply and what can wait | You open the quoted lines in the original before acting on them |
| Drafts an answer to a repeat question from a source you paste | Whether the source is current and right for this person | Draft and source side by side, and you answer any flagged gap |
| Converts notes or emails into a different format | What the reader needs to know and what can be left out | Names, numbers and dates compared, and the left-out list read |
| Suggests wording for a delicate message | The relationship, the tone and the decision to send | You read it aloud as if you were the person receiving it |
| Nothing. This part is yours. | Which request goes first, and anything involving a colleague’s personal situation | Your own judgment, and your manager’s when it’s a close call |
A human-ownership split for everyday AI use. The checks are Future Factors working practice, not a formal standard.
Nothing leaves your hands that you haven’t read as if you wrote it.
The mix of interruptions changes with the role, so the check that matters most changes too:
In every role, data rules come first: use the tools your organisation has approved and keep confidential details out of anything else. Our guide to using AI safely at work covers the questions to ask if nobody has told you.
Writing the prompts is the quick part. What tends to happen is that people use them enthusiastically for a week, a busy patch arrives, and they slide back to doing everything by hand because that feels faster under pressure.
For one person, keep the prompts one click away and use them on the next interruption that fits, even when doing it by hand feels quicker. On Friday, notice which prompt you forgot existed.
For a team, the four stages are worth keeping distinct. Training builds the capability to brief a tool and check what comes back. Workflow design gives it somewhere to land, such as a shared catch-up prompt and a source note behind each common question. Reinforcement turns it into behaviour, usually a manager who asks “did you run the catch-up first?” until nobody needs asking. Adoption is what you see when it sticks. This is the Workflows and Behavior side of the Tool x Workflows x Behavior framework, applied to a day with no quiet hours in it.
A team can start on its own with the three prompts and the handoff test. Structured training shortens the learning curve, because people practise on their own threads, agree a shared checking standard, and leave with prompts the whole team uses rather than one enthusiast’s shortcuts.
To tell whether it’s working, look past whether people used the prompts once:
If you want to put numbers on it properly, our guide to tracking your time savings from AI shows how to measure a task rather than a tool. Watch the checking time too. If review starts eating the time the drafts saved, that’s the pattern described in our piece on botsitting, and it usually means a prompt needs a better source or a narrower job.
A good starting point is a week of noticing, before you set anything up. Keep a short log of what interrupts you and which of the three types it is. By Friday you’ll know which prompt to write first.
| What came in | Type | How often | Handed to AI? | What to prepare |
|---|---|---|---|---|
| “Where are we with the supplier onboarding?” from different people | Re-answer | Most days | Yes, from the tracker notes | Re-answer prompt, with the tracker pasted in each morning |
| Added to a long email chain halfway through | Catch up | A few times | Yes | Catch-up prompt, pinned in the tool |
| Manager wants the update as three bullets, not the full email | Re-shape | Twice | Yes | Re-shape prompt with the keep-every-number line |
| New starter asking how expenses are approved | Re-answer | A few times | Yes, from the policy page | A standing source note on expenses |
| A director’s urgent booking change that clashes with another | None of the three | Once | No, a judgment call | Nothing. This one stays yours |
An example of a completed log. The frequencies are illustrative, not measured. Your own log after a week is what decides which prompt to write first.
Then run the week after it like this:
If it goes well, the change is small and noticeable. The repeat questions stop costing you a whole context switch, and the half-written thing from Monday gets finished on Wednesday.
That’s everyday productivity with AI in a reactive job: a little attention handed back, several times a day.
Whichever general-purpose assistant your organisation has approved. The prompts rely on pasting your own source material rather than a particular feature. If you have a choice, pick the one already open where your email lives, because a tool you have to switch to won’t get used mid-interruption.
Sometimes, and that’s what the handoff test is for. The prompts are written so checking is fast: the catch-up prompt quotes lines you can confirm, the re-answer prompt flags gaps, and the re-shape prompt lists what it left out. If a check keeps taking longer than writing the thing, take that task off your list.
Only into tools your organisation has approved for that kind of content. Published policies are usually fine there. Personal details about colleagues, client contracts and anything confidential need a clear yes from your policy first; when in doubt, describe the situation without the names.
Then they may be judgment calls, which stay yours, or a sign that a source doesn’t exist yet. If the same new question keeps arriving, write the answer down once. It becomes a re-answer next week, and the note helps whoever covers for you.
In our judgment, the first prompt can pay for itself within the week you write it, if your log showed that type coming up most days. The bigger change takes longer: a month in, check whether you still reach for the prompts on your busiest days. If you do, the habit has stuck.
The interruption figure comes from Microsoft WorkLab’s June 2025 analysis of anonymised Microsoft 365 signals and applies to the most heavily pinged fifth of users, not everyone. The interruption experiment is Gloria Mark and colleagues’ 2008 CHI paper, a lab study with 48 participants, and the AI performance finding is from Dell’Acqua and colleagues’ 2023 field experiment with Boston Consulting Group consultants. All three were read on October 7, 2026. We left out the widely repeated claim that it takes 23 minutes to refocus after an interruption, because it isn’t in the paper we read. The three interruption types, the handoff test, the rules and the ownership table are Future Factors working methods based on our own judgment, not research-validated scales, and the scenes are illustrations, not client stories.
Weekly tips. Real examples. Practical help for busy professionals.
We care about your data, check out our privacy policy.