When to Set a Focus Horizon
Five situations where marking the decay curve changes what you ship.
Focus Horizon fires at session-start — not mid-session, where it has no leverage.
The horizon is useless if you check it once you are already in the decay tail. It pays off when set at the start of a session and respected as the break marker. Five moments in particular benefit most from explicit horizon-setting.
Quick answer
Focus Horizon fires at session-start — not mid-session, where it has no leverage.
Key points
- ▸ Start of any deep-work session. Set the horizon to 90-120 minutes with a break at the marker. Pre-committing prevents the "just 10 more minutes" trap.
- ▸ Hard problem-solving. The hardest part of any problem should happen in the first 45 minutes when quality is above 63%. If it is still unsolved at 120 minutes, break — the solution is not hiding in the decay tail.
- ▸ Creative work. Writing, design, coding creative features — quality drops hard below 40%. Better to write 40 sharp minutes and stop than grind 3 dull hours.
- ▸ After an interruption. Reset the timer. The decay is from continuous focus; interruptions usually require a re-ramp period that restarts the curve.
- ▸ End-of-day decisions about what to work on. If the horizon already shows < 30% at 4pm, do not start a hard task — pick a decaying-friendly one (cleanup, admin, documentation).
Examples
- Morning deep-workStart 9am, horizon 120 min, break at 11am. Do the hardest task first; routine work after the break.
- Stuck-problem break75 minutes into a debugging session, quality 47%. Walk for 20 min; return at near-peak. Solution usually appears in the first 15 minutes after the break.
- 4pm reality checkHorizon readout: 25% quality, rapidly decaying. Do not start the hard proposal. Batch admin, prep for tomorrow, stop.
When to use which tool
- Deep Work Capacity · Focus HorizonAt session start. Mid-session use is diagnostic only; the leverage point is the pre-commitment.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 OverheadEvery context switch restarts the decay curve — high task-switching guarantees low horizon.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 BatteryFocus horizon and willpower battery overlap heavily; low on either means stop deep work.Model remaining willpower across the day. Every decision draws from the same finite reserve — trivial × 1, moderate × 5, heavy × 10.
- Signal-to-Noise · Content ThroughputContent consumption in the decay tail produces very low signal-to-noise — schedule research when horizon is still above 60%.Measure how much of your daily information intake converts into actionable decisions. Throughput-pipe visual with clogged / flowing state.
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.
- Signal-to-Noise · Content ThroughputMeasure how much of your daily information intake converts into actionable decisions. Throughput-pipe visual with clogged / flowing state.
- What Focus Horizon CalculatesQuality = 100 × e^(−0.01 × min). Half-life ~69 minutes. The tail is where the bugs live.
- Five Focus-Horizon MistakesThe errors that spend peak focus on the wrong things.
- When to Check WillpowerFive moments when knowing your battery level changes the next move.
Frequently asked questions
› How long should a deep-work block be? How-to
For most people, 90-120 minutes peaks out productive output per session. Longer sessions produce more hours but less usable work. Two 90-minute blocks with a real break between usually beat one 180-minute grind.
› Do short focus sprints help?
For routine or maintenance work, yes. For hard problems, no — the ramp-up cost eats most of a 25-minute Pomodoro. Hard problems want longer unbroken windows.
› 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.