What I Found When I Tracked Every Interruption for a Week

It started as a curiosity. I had read something about context switching and thought it might apply to me, but probably not that much. I was mostly disciplined. I worked from home. I had a quiet space.

So I ran an experiment. For one week, every time something pulled me away from the task I was tracking, I logged it as a separate entry. Client message. Slack ping. Quick question from a contractor. Phone call I told myself would take five minutes.

I was not prepared for what I found.

The Numbers

By Thursday I had 23 separate interruption entries and I still had Friday to go. Some were short. Some were not. But every single one had ended a work session before it was done.

The total time in those entries was around 4 hours and 20 minutes for the week. Not the time spent on the interruption itself, just the interruptions I logged. The actual work I had to redo or restart after each one wasn't counted at all.

I had thought I was losing maybe 30 minutes a day. I was losing closer to 90.

Where They Were Coming From

One client was responsible for about 40 percent of my interruptions. She was responsive, enthusiastic, and sent messages throughout the day as ideas occurred to her. She wasn't being difficult. She just operated that way.

The problem was that I had never set any expectation otherwise. I answered quickly because I wanted her to feel taken care of. And she had learned, reasonably, that I was available.

She wasn't doing anything wrong. I had just never defined what right looked like.

What the Timer Showed That I Would Have Missed

Without tracking the interruptions as separate entries, I would have just felt scattered at the end of each day and blamed my own focus.

That's what I had been doing for months, honestly. Thinking I needed to be more disciplined. Wondering why deep work felt so hard to hold.

But it wasn't a focus problem. It was a structure problem. And the time log showed me exactly where the structure had broken down and who was on the other side of it.

What I Changed

I started batching communication with that client to two windows per day. Morning and late afternoon. I told her I was doing this to make sure I gave her messages proper attention instead of quick replies. She thought that was reasonable.

I also started tagging client communication in my time tracker so I could see the total each week. Not because I was planning to bill for it, but because I wanted to see it as a real cost.

Once I could see it, I could price for it. Projects with high-communication clients started getting a line built into the estimate.

The Part That Surprised Me Most

The week I ran the experiment, I billed fewer hours than a typical week. Not because I worked less, but because I could suddenly see all the time that wasn't billable and had been hiding inside my workday.

I had been thinking of those hours as nothing. Background noise. Just the cost of doing business.

They weren't nothing. They were real time I wasn't recovering. And they were making every project take longer and feel harder than it should have.

Tracking them didn't fix everything immediately. But it made the problem visible. And visible problems are the only kind you can actually solve.

If you feel scattered but you can't explain why, track the interruptions for a week. Not to punish yourself, just to see them. The pattern will be there. It always is.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots