How to do deep work when your day is full of interruptions

Start without software. Keep a paper interruption log for three days, protect one 60 to 90 minute block a day, and run it on a kitchen timer. Write a one-line next step before you answer any interruption. Add Dayflow, a free Mac app, if you want an automatic record of where your screen time went. Use a separate blocker if you need distractions shut off.

You sit down at 9:40 with a clear plan: two hours on the proposal. At 9:52 a Slack message asks about yesterday’s numbers. At 10:05 a calendar reminder warns you about a call you forgot was at 10:30. At 10:50 someone leans over and asks if you have a sec. At 11:15 you look at the document. It has three new sentences, and you have rewritten one of them twice.

The worst part is not the lost time. It is the feeling at 6 p.m. that you were busy all day and did nothing that mattered. Each interruption was reasonable on its own. Together, they left no room for the work that needs a quiet head.

This guide covers three things. First, why interruptions cost more than their length suggests. Second, six things to try this week, most of which need nothing more than paper, a calendar and a timer. Third, where an automatic record of your day can help. That last part mentions Dayflow, a Mac app that we make, so weigh it with that in mind.

The short version

• Count before you fix. Keep a paper tally of every interruption for three days, with its source and whether it could have waited.
• Protect one block a day, 60 to 90 minutes at the same time. Give it a real name on your calendar.
• Leave a breadcrumb. Before you answer anything mid-task, write your next step on a sticky note. Coming back gets much easier.
• Give messages office hours. Tell people when you check and how to reach you if something is truly urgent.
• Use a physical timer. A kitchen timer on the desk makes the block real for you and visible to anyone nearby.
• Make restarting tiny. Decide the first five-minute action before the block begins.

Why does deep work keep falling apart?

Most people blame themselves: not disciplined enough, too easily distracted. Usually the shape of the day is doing most of the damage.

Interruptions cost more than their length. A two-minute question costs two minutes plus the time it takes to get back to where you were. For simple work, the second part is small. For work that lives in your head, like a tricky argument, a bug you are tracing or a plan with many moving parts, the context falls apart when you look away. You then have to rebuild it.

Expecting an interruption is its own interruption. If a ping could arrive any moment, part of your attention stays on guard. Many people notice they never fully settle into hard work on days when chat is open. They are not being interrupted constantly. They are waiting to be.

Small tasks are easier to finish. Answering a message gives a quick sense of completion. Hard work gives you nothing for a long while. When you are tired or stuck, the inbox wins, and it does not feel like avoidance at the time.

Meetings chop up the day. One call at 10:30 and another at 2:00 can turn a free day into four short gaps, none long enough to get going. The calendar looks mostly open. In practice, it is not.

Memory is a poor timekeeper. At the end of the day, you remember the meetings and the big moments. The dozens of small switches between them blur into “busy.” That makes it hard to see what is actually breaking your focus, so the fixes you try aim at the wrong target.

None of this is a character flaw. It is how attention behaves under pressure. The good news is that the shape of a day can be changed, often more than people expect.

Where do your interruptions actually come from?

Before you protect your time, find out what it needs protecting from. Guessing usually points you at the wrong culprit.

What to do: For three working days, keep a sheet of paper next to your keyboard. Every time something pulls you off what you meant to be doing, write one line: the time, the source (person, app, meeting, your own urge to check something), and a quick yes or no on whether it could have waited an hour. That’s all. Don’t try to change anything yet. If you’d like a structure, the daily work log template works for this with one extra column.

Illustration: Someone keeping this log might expect meetings to dominate. Then they find that most of their lines say “checked email, nothing new” or “opened news tab while thinking.” Those are self-interruptions, not other people. That calls for a different fix than declining meetings.

How to tell after a week: You should be able to name your top two sources of interruption without looking at the sheet. You should also be able to say roughly how many could have waited. If you can’t, keep the log a few more days. If the log itself feels like a burden, cut it down to just the source column.

How long should a deep work block be, and how do you protect it?

Trying to defend a whole day usually fails by mid-morning. Defending one block is realistic.

What to do: Pick one block of 60 to 90 minutes, at the same time each day if you can. Mornings work for many people because fewer things have caught fire yet, but choose whatever time your log showed was quietest. Put it on your calendar with the name of the actual task, such as “Draft pricing section,” rather than a generic “Focus time.” A named task looks like a commitment and is harder for others, and for you, to book over.

If meetings are what break up your day, see whether two or three could sit back to back to free up a longer stretch. The meeting cost calculator can help when you need to make the case to a team that a recurring meeting is expensive.

Illustration: A person with calls at 10:30 and 2:00 asks whether the 2:00 can move to 11:00. They now have 9:00 to 10:30 for a block and an open afternoon. Same number of meetings, very different day.

How to tell after a week: Count how many blocks survived mostly intact. If fewer than three out of five did, the block is in the wrong spot or too long. Move it or shorten it to 45 minutes before you decide the idea doesn’t work. A short block that holds beats a long one that never happens.

How do you get back on track after an interruption?

Some interruptions can’t be avoided. A manager needs an answer, a customer calls, a child comes into the room. The goal then is to make coming back cheaper.

What to do: Before you turn to the interruption, take ten to twenty seconds to write your very next step on a sticky note or in the margin. Not a summary, just the next physical action. “Check whether the March numbers include refunds.” “Rewrite paragraph 3 to lead with the cost.” Then deal with the interruption. When you come back, read the note and do exactly that.

Illustration: A developer tracing a bug is called into a quick huddle. Before standing up, they write “log the user ID right before the second API call.” Twenty minutes later they sit down, read the line, and are back inside the problem within a minute. Without the note, they would have spent the first ten minutes scrolling and wondering where they were.

How to tell after a week: Notice how restarts feel. They should feel less like starting over. A small pile of used sticky notes is a good sign. If you keep forgetting to write the note, put a pad directly on top of your keyboard during blocks so you have to move it to do anything else.

How do you stop messages from eating the day?

Chat and email feel urgent because they are always there. Most of them are not urgent at all.

What to do: Choose set times to check messages. Three times a day works for many people, such as late morning, after lunch and mid-afternoon. Close the apps between those times, or at least during your protected block. Then tell the people who need to know, in plain words: “I check messages at 11, 2 and 4. If something is truly urgent, call me.” That gives real emergencies a clear route and makes everything else predictable.

It also helps to make a simple agreement with one teammate. You cover each other’s urgent questions during focus blocks, or you agree on what counts as urgent.

Illustration: A designer posts their check times in the team channel and sets a status for the morning block. Over the first week, one person calls with something urgent. Everything else waits a couple of hours, and nobody mentions it.

How to tell after a week: Ask one honest question: did anything actually break? If nothing did, you have good evidence to keep going. If something did, change the rule for that one kind of message rather than dropping the whole approach.

Does a kitchen timer really help with focus?

It sounds too simple to matter. For many people, it is the piece that makes the rest stick.

What to do: Use a physical timer, not your phone. Picking up the phone to start a timer is an invitation to check something else. Set it for the length of your block, start it, and put it where you can see it. The ticking or the visible dial tells you the block has started, and it tells people nearby that you are mid-task. Headphones, a closed door or a small sign can do the same for people who share your space.

If you often lose track of how long you have been working, the time estimation test is a quick exercise that compares your sense of time with a clock. It is not a diagnostic, just a way to see how far your guesses drift.

Illustration: Someone working at a kitchen table sets a 60-minute timer and puts it beside the laptop. Their partner learns that a running timer means “unless it’s important, wait until it rings.” The deal costs nothing and removes several small interruptions a day.

How to tell after a week: Check whether you actually started the timer most days. If you did, compare those blocks with the ones where you didn’t. If you keep forgetting it, put it on the laptop lid at the end of each day so it is the first thing you touch.

How do you start hard work when you only have a short window?

After an interruption, or on a fragmented day, the hardest part of deep work is the first few minutes. Hard tasks tend to look like a wall: “write the proposal,” “fix the architecture.”

What to do: At the end of each block, or the night before, write down the first five-minute action for the next block. Make it small and concrete enough that you could start it while still a bit distracted. “Open the doc and list three headings.” “Run the failing test and read the error.” When the block begins, do only that. Momentum usually carries you past it.

Illustration: A writer with a 40-minute gap between calls doesn’t try to “work on chapter 4.” They open the file and fix the one paragraph they flagged yesterday. By the time it’s done, they are warmed up and write a page.

How to tell after a week: Notice how long it takes from sitting down to doing real work. If that gap is shrinking, keep going. If you still stall, the first step isn’t small enough yet. Cut it in half.

Where seeing your actual day helps

Most of the steps above depend on knowing where your time went, and memory is unreliable for that. The paper log works, but only while you remember to write in it, and the moments you forget are often the ones that matter. Some people want a record that keeps itself, so they don’t have to start a timer or rebuild the day from memory. The where did my day go page covers this question in more depth.

Dayflow is one option for this on a Mac. It records your screen at one frame every 10 seconds, and AI writes the day into a readable timeline. Full recordings and the timeline are stored on your Mac. You can keep screenshot analysis on-device with a local model through Ollama or LM Studio. You can also send selected screenshots to a cloud provider you configure, or to Dayflow Pro. The details are on local and cloud processing. You can export a date range as Markdown from Settings, which is handy for a weekly look at when your blocks held and when they didn’t. The AI summaries can miss or misread work, so treat them as a draft.

The app is $0 and MIT licensed, with an optional Pro plan at $20 a month, and needs macOS 14 or later. If you want to compare it with other approaches, there is a roundup of Mac time trackers.

Dayflow publishes this article. The Dayflow details above come from its published documentation as of September 6, 2026 (version 2.2.0).

Where Dayflow is the wrong pick

Be clear on what it is not.

• It does not block anything. Dayflow has no website blocking. If your log shows that most interruptions are you opening news or social sites mid-block, a dedicated website or app blocker will do more, because it stops the visit as it happens. Dayflow only shows it to you afterward.
• It sees only your Mac’s screen. People at your desk, phone calls, your phone itself and work on paper are invisible to it. If your interruptions mostly happen away from the computer, the paper interruption log wins.
• It is Mac only. No Windows, Linux or iPhone version.
• It is a record, not a coach. It won’t tell you when to focus, nudge you back on task, or negotiate with your team. The kitchen timer and the message agreement do that work.
• You may not need it at all. If three days of paper logging already shows you the pattern, that is enough. Many people never need more than paper and a timer.
• It records your screen. If having a recording of your screen on your machine bothers you, even stored locally, skip it. A pen and paper raise no such questions.

The bottom line

Deep work on an interrupted day is less about willpower and more about the shape of the day. Find out where your interruptions come from. Protect one block. Leave yourself a note before you look away, give messages set times, and make the first step of hard work small enough to start while distracted. Each one costs little and can be tested within a week.

Start with the paper log tomorrow morning. In three days you will know which of the other five steps matters most for you. When you want to look back over a longer stretch, a short weekly deep work review helps you keep what works and drop what doesn’t.

Frequently asked questions

How long does it take to get back into focus after an interruption?

It varies a lot by person and task. Something you know well can pick back up in a minute. A tangled problem that lived only in your head can take much longer, because you have to rebuild it. The most reliable way to shorten the restart is to write the next concrete step on paper before you turn to the interruption. That way you do not have to rebuild the thread from nothing.

How long should a deep work session be?

Many people find 60 to 90 minutes a workable starting length. It is long enough to get past the warm-up and short enough to defend on a busy day. If your blocks keep getting broken, shorten them to 45 minutes and protect them better instead of aiming longer. Once you can hold several blocks a week, try stretching one of them.

How do I do deep work when my calendar is full of meetings?

Look for the gaps between meetings, then ask whether two or three meetings could move next to each other to make one longer gap. A clustered afternoon of calls often leaves a clean morning. Book the gap you create as a named calendar event, such as "Draft Q4 proposal," so it looks taken. A generic "Focus" block tends to get booked over.

How do I tell coworkers I need focus time without seeming rude?

Tell them what you will do, not what you won't. For example: "I check messages at 11, 2 and 4. If something is truly urgent, call me." That gives people a clear route for real emergencies and a predictable answer time for everything else. Most people mind a slow reply far less when they know when the reply is coming.

Is it okay to check messages during a deep work block?

It is your call, but each check pulls you partly out of the work, even when nothing needs a reply. A middle path is to close the chat app during the block and keep one route open for true emergencies, such as a phone call. Then check everything at the end of the block. After a week, see whether anything actually suffered from the delay.

Can Dayflow block distracting websites during deep work?

No. Dayflow does not provide website blocking. It records what was on your screen and turns it into a timeline afterward. If your main problem is reaching for distracting sites mid-block, a dedicated website or app blocker beats Dayflow, because it stops the visit in the moment. Some people use a blocker during focus blocks and a record like Dayflow to review the week.

Does Dayflow work on Windows, Linux or iPhone?

No. Dayflow is Mac only and needs macOS 14 or later. It sees only what is on your Mac's screen, so time on your phone, in conversations or on paper does not show up. If most of your interruptions happen away from the Mac, a paper interruption log will tell you more than any Mac app can.

Is Dayflow free?

Yes. The app is $0 and open source under the MIT license. There is an optional Dayflow Pro plan at $20 a month, in which Dayflow manages cloud analysis of screenshots. On the free app you can run analysis on your Mac with a local model through Ollama or LM Studio, or connect your own cloud provider, whose own charges and terms apply.

Does Dayflow send my screenshots to the cloud?

Only if you choose a cloud option. With Local AI, screenshot analysis stays on your Mac. If you connect your own provider, selected screenshots go to that provider under its terms. With Dayflow Pro, Dayflow processes selected screenshots off-device and, under its privacy policy, deletes them after processing and may keep Activity Data for sync. Full recordings and the timeline are stored on your Mac.