Five Focus-Horizon Mistakes
The errors that spend peak focus on the wrong things.
Focus-horizon errors are not about the formula — they are about what you schedule into the peak.
The tool tells you when focus degrades. The mistakes are in how you schedule against the curve. Five patterns consistently leak peak focus — once identified they are easy to eliminate and usually double the hardest-work output per day.
Quick answer
Focus-horizon errors are not about the formula — they are about what you schedule into the peak.
Key points
- ▸ Spending peak on email and admin. If your first 90 minutes of the day go to inbox triage, the hard work happens at 50% quality or worse. Admin is a decaying-horizon task; hard work is a peak-horizon task.
- ▸ Ignoring interruptions as resets. A 30-second question from a colleague does not "not count" — it partially resets the curve and burns reramp time. Protect the session or expect the decay to jump.
- ▸ Pushing past the break marker. "Just 10 more minutes" past the horizon produces output you rewrite tomorrow. Breaking at 70% quality ships more than grinding to 20%.
- ▸ Assuming coffee extends the horizon. Caffeine elevates alertness, not cognitive quality. The decay curve is the same; you just feel awake through the tail. Output still drops.
- ▸ Using short sprints for hard work. 25-minute Pomodoros work for routine tasks but strangle hard problems — most of the sprint is ramp-up. Hard work wants 60-90 minute blocks.
Examples
- Peak wasted on emailFirst 90 minutes of the day in inbox. Quality was 95% → 70% for email that needed 40% quality. Saved the 40%-quality tail for the hard proposal. Proposal suffers predictably.
- Interruption underweightedThree "quick" questions during a 90-minute session. Actual continuous-focus time: ~35 minutes across the session. Shipped output matches 35 minutes, not 90.
- Pomodoro misuse25-min sprints on a hard algorithmic problem. Each sprint: 8 min ramp + 17 min work + stop just as flow emerges. 4 sprints = 68 min of actual work, worse than one 90-min block.
When to use which tool
- Deep Work Capacity · Focus HorizonSchedule peak against the curve. Hard work first, routine second.Exponential decay model of focus quality. e^(−0.01×min) half-life ≈ 69 minutes — the horizon shows how long until quality drops below usable.
- Task Switching Tax · Context OverheadInterruptions are micro-switches that restart the horizon. Budget them separately.Calculate the hours per day you lose to juggling concurrent projects. Each additional context costs 20% of remaining capacity — CPU-usage view.
- Decision Fatigue · Willpower BatteryPeak focus with a drained willpower battery still produces subpar heavy decisions — need both full for hard calls.Model remaining willpower across the day. Every decision draws from the same finite reserve — trivial × 1, moderate × 5, heavy × 10.
Related
- Deep Work Capacity · Focus HorizonExponential decay model of focus quality. e^(−0.01×min) half-life ≈ 69 minutes — the horizon shows how long until quality drops below usable.
- Task Switching Tax · Context OverheadCalculate the hours per day you lose to juggling concurrent projects. Each additional context costs 20% of remaining capacity — CPU-usage view.
- Decision Fatigue · Willpower BatteryModel remaining willpower across the day. Every decision draws from the same finite reserve — trivial × 1, moderate × 5, heavy × 10.
- What Focus Horizon CalculatesQuality = 100 × e^(−0.01 × min). Half-life ~69 minutes. The tail is where the bugs live.
- When to Set a Focus HorizonFive situations where marking the decay curve changes what you ship.
- Five Task-Switching MistakesThe input errors that make the overhead look smaller than it is.
Frequently asked questions
› How do I protect peak focus from meetings? How-to
Block calendar time explicitly. If your peak is 9-11am, mark it unavailable; schedule meetings in the 1-3pm decay tail where they do less damage. Defending the peak is a one-time political cost that pays back weekly.
› What if my job requires constant availability?
Most jobs that claim this actually don't — they have ~2 hours of true-emergency response and ~6 hours of perceived-urgency noise. Audit a week, find the real emergency rate, negotiate protected peak blocks around it.
› How should I use a decision framework in real life? How-to
Use a decision framework to expose the tradeoff, not to outsource the decision. Write down the inputs, compare the output with your constraints, then ask what would change the answer. The strongest use is scenario testing: base case, conservative case, and failure case.
› Is this financial, legal, or tax advice? Trust & accuracy
No, this is not legal, financial, tax, medical, or professional advice unless the page explicitly says that use case is supported. It organizes assumptions so you can inspect them. Verify high-stakes choices with qualified people who can review facts, contracts, regulations, and downside risk.
› What assumption matters most in a decision model? Edge case
The most important assumption is usually the one you are least certain about and most emotionally attached to. Change that input first. If the recommendation flips after a small change, the decision is fragile and needs more evidence before you treat the model as useful.