The reading room · Digna Legi
The Math of Why You Can't Focus at Work
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps and the model’s empirical validity cannot be independently checked from the supplied text alone.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
Focus failure can be structural: interruptions, recovery lag, and minimum useful block size determine whether deep work is possible.
AI brief · Checked against source text
The main idea
The piece argues that bad focus days are often structural rather than personal: interruptions, recovery lag, and minimum useful work-block size jointly determine whether deep work is possible. Its useful move is treating total work time as less important than block shape; five short fragments may have far less capacity than one long stretch because meaningful work needs uninterrupted chunks.
Some background helpful. Comfort with basic probability notation and simple formulas helps.
Go a little deeper
Fragmentation beats raw hours
The strongest distinction is between focus time and usable capacity. A day can contain plenty of nominal focus minutes yet still produce little deep work if those minutes are chopped below the task’s threshold. The floor-function example makes this concrete: the same 155 minutes can yield four, three, or one units of work depending on whether the meaningful block size is 30, 45, or 60 minutes.
Small parameter changes have nonlinear effects
The model’s advice is sharper than generic focus advice because it shows why modest environmental changes can matter disproportionately. One extra interruption per hour is not just one extra pause; it can trigger recovery overlap, destroy future blocks, and lower the odds of assembling multiple long stretches. That is why reducing access can be more powerful than trying to be more disciplined inside a noisy system.
Theta is a design choice when conditions are fixed
The piece does not simply say to do smaller tasks. It distinguishes changing the environment from changing the question you ask of the environment. If interruption rates are high, a 90-minute task may be unrealistic, but decomposing it into independent 20- or 30-minute units can make progress feasible without pretending the workplace has become calmer.
Recovery time is operational, not mystical
Delta is presented as the lingering cost after an interruption ends, so the remedy is not willpower but re-entry design. Breadcrumbs, similar-context interruptions, and small restart rituals reduce the time needed to reload a mental model. The practical point is that recovery savings compound because they apply after every interruption, not only once per day.
A case from the article
One more interruption per hour
The source compares the chance of finding three 60-minute blocks under the same setup while increasing interruption rate from one to two per hour. At one interruption per hour, 70 of 100 simulated days satisfy the condition; at two, only 14 do. The example illustrates the model’s central warning: a seemingly small rise in availability demands can collapse deep-work capacity.
How the case is made
The case is made through a simple mathematical model, simulated workdays, heatmaps, and cited interruption/recovery studies.
Where the idea has limits
The model intentionally simplifies interruption patterns; the author notes real interruptions cluster rather than arriving uniformly, which can create occasional clean gaps or compound recovery damage.
A question to take away · from Digna Legi
Which work in your week truly needs long blocks, and which merely feels large because it has not been decomposed?
What the original adds
The original includes simulated timelines, 100-day grids, heatmaps across interruption and recovery values, and an interactive-style threshold comparison for 30-, 45-, and 60-minute work.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.