openskills.info

Focus and Deep Work

Protecting long enough stretches of attention to do the work that actually requires thinking.

Some work is genuinely improved by being done in one uninterrupted stretch — anything where you have to hold a lot in your head at once, which is most design, most writing, most debugging of hard problems. That kind of work has a warm-up cost, and every interruption charges it again. Research on attention residue shows the cost isn't just the three minutes of the interruption; part of your attention stays with the previous task, so the recovery is slower than it feels. The practical implication isn't heroic isolation. It's that a few protected blocks per week produce more of this kind of work than a permanently available forty hours, and that protecting them is a scheduling decision rather than a matter of willpower.

Mostly Harmless

The Notification Permeable

Reachable on six channels with alerts enabled on all of them, and proud of a median response time measured in seconds. Has not had an uninterrupted stretch longer than eleven minutes since a power cut in 2023. Experiences the day as extremely busy and productive, which is accurate about the first half, and finds that the one genuinely difficult task on the list has been carried forward, untouched, for nine consecutive days. Has begun to suspect the task is unusually hard rather than unusually unprotected.

The Multitask Believer

Accepts that most people can't work on two things at once and considers themselves, on the available evidence, an exception. Attends the call while reviewing the pull request, contributing usefully to neither and catching roughly the gist of both. The review misses the thing it was for and the call requires a follow-up, both of which are attributed to the review being complicated and the call being poorly run, rather than to the only variable common to both.

The Deep Work Ritualist

Requires conditions: four clear hours, the correct café, the headphones, the specific playlist, and a morning with nothing before it. Has assembled a set of preconditions so demanding that it is satisfied roughly twice a quarter, and treats each failure to assemble them as an external obstacle. Would in fact do excellent work in ninety ordinary minutes, an experiment that has not been run because the conditions weren't right.

The Interruption Broker

Unblocks themselves efficiently by tapping the nearest person who knows, prefaced with "quick question" — accurate about the question, silent about the twenty minutes it costs the person answering. Runs a personally optimal strategy, saving fifteen minutes of searching at a cost of considerably more elsewhere, and has never had cause to compute the exchange rate because it is settled entirely in other people's currency. Is, by every measure available to them, highly efficient.

Scenarios

The one hard task on your list has been carried forward for over a week while everything else gets done. What would you do — try harder to get to it, or block two hours tomorrow and turn off notifications for them?

You're on a call that only needs half your attention. What would you do — use the time for a code review, or decide whether you need to be on the call at all?

You need an answer a colleague has and could either search for it or ask them. What would you do — ask, since it's faster for you, or spend ten minutes searching first and batch anything left for one conversation?

Takeaway

  • Schedule protected blocks rather than hoping for them. Focus is a calendar problem before it's a discipline problem.
  • Turn notifications off for the block. Available-with-good-intentions is the same as interrupted.
  • Don't pair demanding work with anything. You will do both at about sixty percent and attribute the result to the tasks.
  • Start with the ninety minutes you have instead of the four hours you don't. The perfect conditions are a way of not beginning.
  • Batch your questions for other people. "Quick question" is quick for exactly one of the two participants.

Go deeper

Awesome Links