The Interruption Log: Find Out What Only You Can Decide

You cannot find out what only you can do in your business by thinking about it. You find it by logging one real day: every interruption, in the order it arrived, with the reason the person came to you written next to it. Then you sort the list by reason instead of by task. What survives that sort is the short list of things that actually require you, and it is always shorter than you expect.

How to find out what only you can do in your business

Log a day you actually lived, not a week you can describe. When we send an operator the prompt "walk me through your normal week" ahead of a session, the answer that comes back is a tidy version of the job description: bids in the morning, meetings midday, paperwork at night.

One senior estimator at an electrical contractor decided that was dishonest. Instead of describing a typical week, he wrote down everything that interrupted him on one ordinary morning, from the time he sat down at 6:30 until his 11 o'clock meeting. He walked into the session with the list.

Generic questions get generic answers. A real morning gets you eleven interruptions with names, dollar values, and root causes attached to each one.

A day you actually lived is evidence, and a typical week is a story you tell about yourself.

What does a finished interruption log look like?

It looks like a mess, and the mess is the point. In four and a half hours, before his first scheduled meeting, that estimator chased charger submittals with a colleague, redirected another estimator on a bid where somebody had a favorable back-channel conversation, handled a lighting warranty, ordered fixtures for a school, ran a set of bid documents through a summarizer to prep the next day's walkthrough, coordinated a pole installation over email, sent a general contractor the sub scope verbatim to calm him down, took a forty minute call on an eleven million dollar opportunity, priced a small government job, and had a colleague walk into his office with an item that belonged in Monday's meeting.

Eleven items. Zero of them were estimating, which is the job he is paid for and the only thing on his official calendar.

Write yours the same way: one line per interruption, who brought it, and what it was about. Do not batch three small ones into a tidy entry. A summarized log is just the typical week again with a timestamp on it.

Sort by why they came to you, not by task

The instinct is to group the list by subject: warranties here, submittals there, bids in a third pile. That grouping tells you nothing you did not already know. The useful sort is by cause, and you get it by asking one blunt question about the whole list: if fifty questions came at you this week, what percentage traces back to one part of the business?

That estimator resisted the premise at first. He would not say his people were incapable, and he was right not to, because that was not the answer. Pressed, he produced the real one: "I'm quicker to pick up the phone." Then, separately, the harder half: "I'll make a decision for them. I think that's lacking elsewhere. A lot of people just won't make a decision."

Neither of those is a capability problem. That matters, because capability is the reason most owners assume when they look at their own calendar, and it is the one that leads to hiring instead of fixing.

The three reasons, and what each one means

Every line on your log traces to one of three causes. Read each interruption and mark it before you do anything else with the list.

Notice which column the fixes live in. Speed items get fixed by changing who the phone rings for, not by writing anything down. Authority items get fixed by naming the dollar threshold, the discount, or the scope call somebody else is now allowed to make without you. Only the knowledge column earns a written procedure, and it is usually the smallest of the three.

Marking that column honestly is the same work as a knowledge risk assessment to find your single points of failure, run on one day instead of across the whole org chart.

This is also why handing work off feels impossible when you are the fastest person in the building. You are not protecting quality, you are protecting four minutes, which is exactly the trap described in how to hand off work when you have no time to train.

If you disappeared for two weeks, what pauses?

Ask it exactly that way, out loud, and answer it before you look at your log again. It is the fastest single question we know for locating a bottleneck. In that same session, twenty minutes of careful process questions had turned up nothing alarming. One disappearance question got an instant, unhedged answer: "Things will pause. I got to be the one to keep my foot on the gas."

Pressed for a fix, he did not have one. He had already tried the workaround most people try, which was to declare himself out of office and then quietly stay at his desk so nobody would come to him. He never got to run it. In his words, he did not do it because he got too busy with other stuff.

That is the whole diagnosis in one sentence. A bottleneck cannot schedule its own escape, because the interruptions arrive faster than the plan does. If the two-week answer makes you wince, the longer version of the same exercise is the vacation test.

The version that scores every function instead of one week is an owner dependency audit, and it turns a wince into a number you can watch move.

Ask what pulls you backwards

Do not ask yourself what your biggest problem is. That question gets you the impressive answer: margin, hiring, the pipeline. Ask instead what pulls you backwards when you take a couple of steps forward, and you get the real one.

For that estimator, it was closeouts and equipment submittals, administrative work he had never touched in twenty years at a prior employer and considered beneath discussion. He almost did not raise it. "I used to joke around that this is a waste of my talent. But it's not. It's all part of it. It slows me down."

That is a drag item, and drag items never show up on an interruption log because nobody interrupts you to do them. Add a second short list next to the first: the things that eat your afternoon without anyone asking.

The bottleneck is rarely the work only you can do, it is the work nobody else is permitted to finish.

Turn the log into a documentation order

You now have a ranked list without having ranked anything, because frequency did the ranking for you. Work it in this order.

1. Cut the routing first. Every speed item goes to whoever should have taken the call, with their name and number sent to the people who currently dial you. This costs nothing and clears the most lines.
2. Publish the decision rules. For every authority item, write the threshold and the right call in two sentences, and say out loud who owns it now. These are the decision points a procedure exists to carry.
3. Document only what is left. The knowledge items are the genuine single points of failure. Record yourself doing the work rather than writing it from memory, using the approach in documenting your own job before you hand any of it over.
4. Re-log in ninety days. Same exercise, one ordinary day. The list should be shorter, and the items that came back tell you which fix did not hold.

When we run capture sessions at The Systems Effect, the interruption log is the first artifact we ask for, because it is the only one nobody can produce from memory. The rest of the sequence, once the list exists, is covered in the step-by-step plan for getting out of day-to-day operations.

Do not schedule this. Tomorrow, keep a notepad open and write one line every time somebody pulls you off what you were doing. Stop at lunch. You will have your answer by then.

Frequently Asked Questions

How do you find out what only you can do in your business?

Log one real day of interruptions and sort them by why the person came to you rather than by what they asked about. Three reasons cover almost everything: you are faster, you are the only one allowed to decide, or you are the only one who knows. Only the third reason is genuinely yours, and on most logs it accounts for a minority of the lines.

What is an interruption log?

An interruption log is a plain running list of every time somebody or something pulls you off the task you sat down to do, written in real time on a single ordinary day. Each line records who came to you, what it was about, and why they came to you specifically. It is not a time-tracking spreadsheet and it does not need categories or durations. One estimator produced eleven lines in the four and a half hours before his first meeting, and none of them were the job he is paid to do.

How long should you keep a time log?

One real day beats a described week, and a second day a quarter later beats a month of diligent logging. The point is not statistical coverage, it is honesty: a day you lived contains interruptions you would never have predicted. If one day feels thin, log a second on a different weekday, then stop and act on what you have.

What do you do with the log once you have it?

Sort it into speed, authority, and knowledge, then fix them in that order. Speed items are a routing change, authority items are a written decision rule and a named owner, and knowledge items are the only ones that need to be documented properly. Re-run the log in ninety days to see which fixes held and which interruptions found their way back to your desk.