Reading your own log
Three days of entries produce a document you did not intend to write. Read it in a specific order, because reading it in the wrong order produces resolutions instead of findings.
First, count by source. Not by category. Name the two people or systems that appear most often. In most logs the top two account for a large share of the total, and in most cases at least one of them is a surprise.
Second, sum displacement by priority. Take the two or three things you would have named on Monday as your most important work. Add up the minutes displaced from each. This is the number that changes minds, and it is the only one you should consider showing to anyone else.
Third, look at the times. Interruption clusters. If yours is concentrated between 09:00 and 11:00, you have an arrival-pattern problem with a structural fix. If it is evenly distributed, you have a norms problem, which is harder and slower.
Fourth, read the self created column against the clock. People generate their own interruptions at predictable moments: at the start of hard tasks, after a difficult message, and in the twenty minutes before a meeting they are not looking forward to. If your self-created entries cluster before the same recurring meeting, you have learned something about the meeting.
Fifth, and last, decide one thing. Not five. One removal or one arrangement, tested for two weeks.
There is direct evidence for the most common version of that one thing. In a crossover experiment, 124 adults spent one week checking email freely and one week limited to three checks a day. Daily stress was 1.46 in the limited week against 1.55 in the unlimited week, d = .37, p = .04. Compliance was partial, which is the interesting part: participants managed 4.70 checks a day when limited against 12.54 when not, from a baseline of 15.48 (Kushlev & Dunn, 2015).
Note the size. This is a real, randomised, measurable effect and it is small. Nobody in that study was transformed. They were slightly less stressed, and they failed to hit the limit they had agreed to, and both of those are what your first two weeks will look like.
The log is interesting, and interesting is the problem. A log read as a document produces insight, a sense of having understood something, and no change. A log read as an instrument produces one arrangement you have to negotiate with a named person, which is uncomfortable, which is why the first reading is more popular.
There is a specific finding you should carry out of this lesson, and it is about the size of what you are attempting.
The email experiment produced d = .37 on self-reported stress. That is a genuine effect from a randomised crossover design, and by the standards of this literature it is respectable. It is also a shift of 0.09 points on a scale, from a group of people who could not keep to their own three-check rule and averaged 4.70.
Two conclusions follow. The first is that the intervention was worth doing. The second is that anyone promising you a transformation from an attention practice is selling something the evidence does not contain.
The reason to run the log is not that it will change your life. It is that you cannot negotiate about a cost you cannot name, and after three days you can name it in minutes displaced from a specific piece of work, to a specific person, on specific days. That is a different conversation from "I am finding it hard to focus", and it is the only version of the conversation that has ever worked.
Your log shows interruption spread evenly across every working hour, with no clustering. What does this indicate about the fix available to you?
After reading your log you identify five changes worth making. The lesson tells you to decide one. Why?
You want to ask your director to move the Monday 09:30 stand-up because it fragments the only long block in your week. Which framing does the log support?
Notes are kept with your account, alongside your progress and your gate claims. The lesson itself is readable without one.
This lesson has a tool
Open it and get your draft reviewed. Drag-and-drop tools need a wider screen; the review works anywhere.