Case Study: Recovering A Focus Day After Interruptions

What This Case Study Shows

This case study shows how to recover from interruptions without abandoning the whole day. The key is to protect the return path before you switch away.

The Interrupted Focus Block

Sofia planned to write a project brief. At 9:40, support needed help. At 10:30, a manager asked for numbers. At 11:15, a teammate needed a decision.

Previously, Sofia would keep switching until the day disappeared. This time she used a simple recovery pattern.

Each interruption was captured, triaged, and either handled or parked. Before leaving the brief, she wrote one resume note:

Continue from "customer problem" section. Need example from last support ticket.

When she returned, she did not start from zero.

This is a practical response to attention residue: switching is sometimes necessary, but you can reduce the cost of resuming.

The Recovery Pattern

Use four steps:

1. Capture the interruption.
2. Decide: now, today, later, or no.
3. Leave a resume note for the active task.
4. Restart with the smallest next action.

Examples

Interruption:

Can you check this invoice?

Decision:

Today at 15:00, not now.

Resume note:

Next: write two bullet points under proposal risks.

Practical Takeaway

The resume note should be concrete enough to restart in under a minute. Continue brief is weak. Add support-ticket example under customer problem is strong.

That small note prevents a temporary interruption from becoming a full restart.

Common Mistakes

Do not rely on memory to resume. Interruptions are expensive because they break context. A one-line note can save 20 minutes.

Use FocusToday

When interrupted, keep the original task visible in the Focus view. Add the interruption as a task if it is real work, then return to the active task when possible.

Sources And Influences

Influenced by Deep Work, Getting Things Done, and interruption-management research.