Focus and Deep Work in the Age of AI Distractions
The ability to hold attention on one hard task is getting rarer, not more common, at exactly the moment AI tools made switching attention easier than ever. Here's what deep work actually is at the level of attention mechanics, where AI fits into it, and how to train focus as a skill instead of relying on a one-off act of willpower.
Why focus became a scarce resource right now
The ability to hold attention on one hard task for a straight hour hasn't disappeared from human nature over the past few years, but it's become noticeably rarer in practice, and it's not because the brain changed. The environment around it changed. AI tools, for all their usefulness, have lowered the barrier to switching attention to almost nothing: you can ask an assistant anything in a second without physically leaving your work context, and that ease is exactly what makes switching so tempting, regardless of whether it's actually needed in a given moment.
The paradox is that each individual AI-powered convenience is genuinely useful on its own, and it's hard to fault any specific action, like a quick clarifying question to an assistant. The problem lives at the level of cumulative effect, not any single instance: dozens of small, individually justified switches over a day add up to a work rhythm where the brain almost never stays alone with a task for more than a few minutes at a stretch. The ability to sustain a longer stretch without switching atrophies quietly, until it's needed for a genuinely hard task, where short bursts of concentration are already physically not enough.
Cal Newport defines deep work as activity carried out in a state of distraction-free concentration that pushes cognitive abilities to their limit. The opposite, shallow work, is also necessary and unavoidable: emails, short calls, administrative odds and ends. The problem isn't that shallow work exists, it's that the modern work environment erodes the boundary between these two modes, letting shallow tasks leak straight into blocks originally set aside for deep work.
Newport frames this as a hypothesis about the value of deep work: the ability to quickly master hard things and produce output at the edge of your capability is becoming a rare, and therefore especially valuable, skill precisely because the surrounding environment is systematically training most people out of it. It's not that the capacity for deep concentration became more valuable on its own, it's that fewer and fewer people keep training it under conditions of constant, readily available distraction, and that makes the people who've held onto it objectively rarer and more in demand.
What follows: the mechanics of attention, specific techniques for entering a state of deep concentration, AI's role as both a helper and a new source of distraction, and why the ability to focus is worth training as a skill rather than relying on a one-off act of willpower every time.
Newport's rules for deep work: what's actually applicable
Newport proposes several specific strategies for scheduling deep work, and in practice not all of them apply equally well to every profession. The "monastic" strategy means full isolation from shallow obligations for an extended stretch. It's realistic for a writer or researcher with an autonomous schedule and almost unrealistic for most people with team obligations. The "bimodal" strategy alternates extended periods of deep work, days or even weeks, with periods of normal availability. It requires a level of calendar control most people simply don't have.
A third strategy, "journalistic," means switching into deep-work mode in short bursts whenever a free window opens up during the day, with no fixed schedule. The name refers to journalists who can sit down and write the moment free time appears, not just during a specially set-aside hour. This is the most demanding strategy of all in terms of an already-trained skill: without a developed ability to enter concentration quickly, short random windows go almost entirely to spinning up rather than to the work itself.
The "rhythmic" strategy is more practical for most people: a fixed daily block of deep work, the same length, at the same time, which over time turns into a habit and requires less and less conscious effort to enter. Rhythm works because the brain gets used to associating a specific time of day and a specific setting with concentration mode, and that lowers the cost of shifting into that state with every repetition.
Practical advice for choosing between strategies: start with the rhythmic one, even if your personality seems better suited to the monastic or journalistic approach. The rhythmic strategy needs the fewest external conditions to get started, no extended isolation and no already-trained ability to snap into focus instantly, and the habit of daily repetition itself eventually builds a foundation you can layer more demanding strategies on top of, if that ever becomes necessary.
An important detail Newport emphasizes, and one that's easy to miss: deep work is defined by the complete absence of switching within a block, not by its length. An hour with zero distractions is more productive than three hours with frequent phone checks, because every switch resets your state of concentration back to nearly zero, from which it has to be rebuilt.
That leads to a counterintuitive practical conclusion: a short but genuinely protected forty-minute block is often more productive than a formally long three-hour window, if that window is actually riddled with small checks of email and messaging apps. People often overrate the productivity of long but leaky blocks precisely because the total duration looks impressive on paper, even though the actual time spent in continuous concentration inside it can be a fraction of that.
A practical metric that reflects reality more honestly than a window's total length on the calendar: count not the hours set aside for a task, but the number of continuous stretches inside it longer than twenty minutes. Three hours made up of six uninterrupted half-hour stretches is closer to the ideal of deep work than a formally equal three hours chopped into fifteen short pieces between phone checks. Tracking this metric specifically, rather than total hours, gives a more honest picture of how much real deep work actually happens in a week.
How AI tools both help and hurt focus
AI delivers a genuine win for deep work exactly where shallow tasks used to force their way in: a draft of a routine email, a first pass through documentation, looking up reference information that would otherwise mean stepping away from the main task. Delegating that to an AI tool the moment the main task is already finished genuinely reduces the volume of shallow work that used to eat into part of the day.
The key phrase here is exactly "the moment the main task is already finished." That's what separates healthy delegation from the type of AI use covered next in this piece: a useful property of the tool and a harmful habit of using it look almost identical from the outside, differing only in whether the interaction happens before or after a deep-work block wraps up.
The problem starts when AI gets consulted not after a deep-work block ends, but inside it, at the very first snag. Phrasing a question for an assistant, waiting for the answer, reading and evaluating the result, that's the same type of context switch as any other distraction, it just looks productive because it's formally tied to the current task. A developer who opens a chat with an assistant at the first hiccup in their logic, instead of first thinking it through themselves for a minute or two, gradually loses their own ability to hold a complex problem in mind long enough to solve it unassisted.
A practical rule worth adopting deliberately here: a short pause before turning to an AI tool inside a deep-work block, a minute or two of trying to work it out yourself before phrasing the question. Not because AI gives bad answers, but because the habit of reaching for it instantly at every snag erodes the muscle memory of holding a complex thought on your own, which is the whole substance of deep work.
A practical test that helps you notice where this line sits for you personally: try explicitly writing down every moment the impulse to reach for an AI tool comes up in the middle of a hard task, without necessarily acting on it right away. After a few days of tracking this, it usually becomes clear how many of those impulses were a genuine necessity, and how many were just a reflexive reaction to the discomfort of a snag that could easily have been worked through with a minute of thought.
Does Pomodoro work with AI assistants
The Pomodoro technique, twenty-five minutes of work followed by a five-minute break in short cycles, was born in the nineties to fight procrastination, and it's far from a fit for every task. The format works well for routine, clearly defined tasks where the main difficulty is getting started at all, not the depth of the dive. For genuine deep work on a hard problem, a rigid twenty-five minutes often cuts off right as concentration is starting to build depth, and the mandatory break at that point resets the hard-won momentum instead of restoring it.
The arrival of AI assistants added a new practical question: what to do with a Pomodoro cycle if part of the work inside it, waiting on a response from an AI agent on a long task, for example, happens asynchronously, with no active involvement from you. This isn't the scenario Pomodoro was originally designed for: the technique assumed that for the entire cycle, you're either working yourself or resting, not waiting on the result of someone else's, even automated, process. It makes more sense here not to force asynchronous waiting into a rigid five-minute break, but to use that waiting time as a natural micro-break, covered in detail in the piece on preventing burnout: a short walk, a glance out the window, not checking social media while the agent works in the background.
The practical takeaway: a rigid version of Pomodoro with a fixed twenty-five minutes fits shallow, routine tasks well and genuine deep work poorly, where it makes more sense to fit the length of a block to the natural rhythm of getting immersed in a specific task, rather than to a universal timer.
Single-tasking vs. multitasking: what the science says
Multitasking in the strict sense, simultaneously processing two cognitively demanding tasks, is physiologically impossible for the human brain, no matter how it subjectively feels. What people call multitasking is, in reality, fast switching between tasks, and every one of those switches costs time and quality, even when it subjectively feels seamless.
Research on context switching consistently shows an effect called attention residue: part of your cognitive resources stays attached to the previous task for a while after you switch to a new one, lowering the quality of work on the new task until that residue clears.
The effect is stronger if the previous task got interrupted mid-stream rather than brought to a natural stopping point. Switching right after closing out a specific stage of work leaves noticeably less residue than switching mid-thought or mid-unfinished-piece-of-code. That's why experienced developers often try to finish at least one complete thought or close out one specific test before switching to a meeting, even when it's formally already time to go: the difference in residue afterward will be noticeable. This is separate from the plain cost of switching time, which I covered in the piece on productivity systems: it's not just about the minutes lost, it's that the quality of thinking on the new task is degraded while your head is still partly occupied with the previous one.
The practical takeaway: the subjective feeling of "I work well across several windows at once" is almost always misleading. A simple test for this: compare the quality of a result produced by single-tasking on a hard problem against a result produced while frequently switching between several. The difference usually isn't visible in the speed of individual actions, it's visible in the quality of the final solution, the depth of the analysis, the number of missed details.
There's an important caveat that often gets lost in a retelling of this idea, and it's worth stating separately, because otherwise the advice easily gets pushed to an absurd extreme: single-tasking applies specifically to cognitively demanding tasks, not to any pair of actions at all. Listening to instrumental music during routine physical work doesn't create multitasking in the problematic sense, because the two activities aren't competing for the same cognitive resources. The problem starts where both tasks demand verbal or analytical attention at once, like trying to write substantive text while carrying on a meaningful conversation in a chat at the same time, because that specific combination draws on the same limited brain resources and creates genuine competition, not imagined competition.
Rituals for entering a state of flow
Flow, complete immersion in a task with a lost sense of time, doesn't switch on by command, but you can build a predictable path into it through a ritual. A pre-deep-work ritual serves the same function as the morning ritual I covered in the piece on productivity: it removes the need to make decisions at the moment decisions are hardest, and replaces them with a pre-built sequence of actions.
A working ritual for entering deep work usually involves a few simple, repeatable steps: closing every unnecessary tab and app, setting a specific timer for the work block, sometimes playing certain music or seeking silence specifically associated with this mode. How repeatable these actions are matters more than their specific content: the longer you use the same ritual, the faster the brain links it to a shift into concentration, and the shorter the warm-up time becomes before you're actually immersed in the task.
Changing your ritual too often, chasing a more "efficient" version read about in yet another article, undermines the whole mechanism's main advantage. A ritual works through accumulated association, not through the optimality of its individual steps, and constantly experimenting with a new sequence every week keeps that association from ever locking in, leaving you back at square one for warm-up every time.
A detail that often gets overlooked: a block-closing ritual matters just as much as an entry ritual. Without an explicit closing action, a short note on where you left off and what to pick up next time, the brain keeps partially holding onto the unfinished task in the background, which interferes both with resting after the block and with concentrating on the next task.
This is a direct application of the Zeigarnik effect, which I covered in the piece on preventing burnout: an unfinished task keeps occupying background attention more than a finished one does, and a short written note on your current state works as a temporary close on that loop, releasing that background tension even if the task is objectively still far from actually done. The difference between "just stopped typing" and "wrote one sentence noting where I stopped and what to do next" feels minor in the moment and noticeably affects how easily you pick the task back up next time.
A workspace built for deep work
Physical surroundings affect the ability to concentrate more than people tend to think. Visual noise, a lot of objects in your field of view, works as a constant source of small distractions even with zero sound or notifications, simply because every object in view competes for attention through peripheral vision. A minimal desk free of clutter isn't an aesthetic preference, it's a working tool that reduces the number of competing visual stimuli.
A second monitor, or several open windows at once on one screen, deserves its own note. It's technically convenient to see documentation and code side by side, but the same setup makes it easier to accidentally slip into email or a messaging app sitting in view on an adjacent part of the screen in the background. A sensible compromise: keep only the windows directly needed for the current task visible, and close the rest entirely rather than just minimizing them, because even an inactive window's strip in the corner of the screen creates a weak but constant visual anchor for attention.
The sound environment works differently for different people, and there's no universal recipe here. Total silence helps some people concentrate, a steady background hum with no sharp peaks works better for others, because it masks random sounds that would otherwise yank attention away. A useful practice: test a few options on the same task across different days and honestly compare the result, rather than relying on generic advice about what "correctly" supports concentration.
Open office spaces are a separate problem, designed for ease of communication but poorly suited specifically for deep work. Constant background conversation, people moving through your field of view, coworkers dropping by with a quick question, all of it creates an environment where deep concentration takes noticeably more conscious effort than in an isolated space, even when nothing formally extraordinary is happening.
Practical compromises in an environment like that: headphones as an explicit, culturally understood "do not disturb" signal, even with no music playing, booking a conference room for a specific block of tasks if that's an option. Another working option: a direct agreement with the team about specific hours when interruptions are kept to a minimum, not formally announced through a calendar, just an accepted rule for that specific team. This only works where the team is small and the rule is genuinely respected by everyone, rather than turning into a one-sided expectation of silence from coworkers with no reciprocity.
Digital hygiene for focus
Technical settings solve the distraction problem more reliably than willpower not to give in to the temptation of checking your phone. Removing apps with an infinite scroll from your work device, a separate browser profile with no personal tabs for work tasks, physically disabling notifications for the duration of a block, rather than relying on your own discipline to ignore them in the moment.
Worth a separate note on the physical phone, not just its settings. Research shows that even a powered-off phone, if it's simply sitting within view on a desk, slightly reduces available cognitive capacity compared to a situation where the phone is put away in another room, because part of attention keeps going toward suppressing the impulse to check it. The simple act of moving your phone to another room for the duration of a deep-work block, rather than just flipping it face-down nearby, produces a measurable difference in the quality of concentration, even though it subjectively feels like too small a detail to mention.
A useful, if less obvious, technique: make the barrier before a distracting action slightly less convenient technically, rather than banning it outright. Removing a social app's icon from your phone's home screen, leaving access only through search, adds a few extra seconds before the action, and that's often enough for the impulse to reach for the phone to fade before the action happens automatically. An outright ban sometimes works worse than a partial barrier, because a ban reads as deprivation and provokes workarounds, while a small delay before the action just lowers the frequency of impulsive reaches without creating a sense of being denied something.
The same principle works in reverse too: the fewer extra steps it takes to start a desired action, the more likely you are to actually start it. If a book or notes for an important project sit open on your desk rather than closed away in a drawer, you're noticeably more likely to come back to them in a spare moment than if doing so requires several extra steps. Designing your physical and digital environment works equally well in both directions: making the path to distractions harder and the path to what you actually want to be doing easier.
Planning your day around concentration peaks
I covered in detail how to track your own energy peaks across the day in the piece on energy management. Applied specifically to deep work, one practical takeaway from that matters here: a deep-work block should go exactly on your concentration peak, not on the first free window in the calendar, even if both options are formally equally open. A free hour at the end of the day and a free hour during your morning peak are two different resources with a different capacity to sustain a hard task, even at the same formal length.
A common practical mistake: reserving peak hours for meetings simply because that's when everyone involved formally has no other commitments, and leaving deep work for whatever's left over after the peak. Scheduling meetings by "whenever everyone's free" quietly turns the most productive hours of the day into the busiest ones, if no one specifically protects them for hard individual work.
If the real priority is a hard task, peak hours should be protected for it first, not handed over to a meeting by default. In practice, that means negotiating to move non-essential meetings to hours that are less productive for focus anyway, and explicitly telling the team that certain hours of the day are reserved for individual work, rather than just formally marking them on a calendar with no explanation of why.
AI as a filter for distraction, not just a source of it
Set up correctly, AI tools can filter the flow of information down to something that needs fewer attention switches, instead of adding to the distraction. Automatically sorting incoming messages by urgency, summarizing a long thread before deciding whether it's even worth diving into, a draft reply to a routine request with no need to phrase it from scratch yourself, all of it reduces the number of small attention switches across the day rather than adding to them.
The difference between AI as a help to focus and AI as a source of distraction almost always comes down to who initiates the interaction, not to the mere fact of using the tool. A notification from an AI tool that pops up on its own and demands an immediate reaction works like any other distraction, regardless of how useful its content is. The same tool, invoked on your own initiative during time set aside for exactly that, removes part of the load instead of adding a new one, and that's exactly the difference between a filter and one more source of noise.
A practical example from my own work: this entire site was written alongside Claude Code, and one of the first settings I configured for working with the assistant was an explicit ban on proactive notifications outside the moment I reach out to it myself with a request. The agent doesn't write to me on its own, doesn't suggest continuing a conversation after a pause, doesn't pop up with ideas while I'm working on something else. All the initiative in the interaction stays with me, and that's the only reason a tool that's theoretically available around the clock hasn't turned into a source of constant small distractions throughout the day.
A direct connection to the topic of focus when working with an AI agent: while an agent runs a long task in the background, refactoring a big chunk of code, say, I have a choice between switching to something else in parallel and splitting my own attention, or using that time as an honest micro-break and coming back to the next task with a clear head. Tasks for the agent that stretch over several minutes of execution come up constantly in my work, and what I do with those minutes has a noticeably bigger cumulative effect on the overall quality of my attention across the day than it seems like it should for any single instance of waiting. A lot of developers intuitively pick the first option, trying not to waste time, even though in practice the second option more often preserves the quality of subsequent work, because it doesn't add a new parallel stream of attention on top of an already-running background process. The instinct to "never lose a minute" works against you here: a minute spent on an honest micro-break almost always pays for itself with better attention on the next task, while a minute spent opening one more thing in parallel just adds one more source of residual attention on top of what's already there.
Deep work as a trainable skill
The ability to hold attention on a hard task behaves like a muscle, not a fixed personality trait: it weakens with constant practice of shallow, quickly switched attention and strengthens with regular practice of sustained concentration. Someone who's spent years working in a mode of constant rapid switching between chats, emails, and short tasks objectively loses the ability to sit with one hard problem for an hour, even if they could once do it easily.
The comparison to physical training holds almost literally here. Someone who hasn't run in years can't just go run six miles, even if they used to do it comfortably long ago, and trying to force the result usually ends in injury or disappointment rather than progress. The ability to concentrate rebuilds by the same logic of gradual but regular load, not a single heroic effort, and expecting an immediate result from one attempt at deep work after months of constant switching is just as unrealistic as expecting marathon fitness after one jog.
The good news is that training works in reverse too. Start not with an ambitious four-hour block, but with a short, genuinely achievable interval, even twenty minutes with zero switching, and gradually extend it once the current length stops requiring noticeable effort. Trying to jump straight to long blocks while your current capacity for concentration has already dropped sharply usually ends in disappointment and abandoning the whole idea, rather than real progress.
A practical benchmark for scaling up: extend a block's length only once the current length has stopped feeling like effort for at least a week straight, rather than following a pre-set schedule of "plus five minutes every day." Progress here is inherently uneven: several days in a row can feel easy, and then one hard day resets the subjective feeling backward, even though the actual skill hasn't gone anywhere. Aiming for sustained rather than one-off improvement matters more than sticking to a rigid ramp-up schedule built with no regard for how you actually feel on a given day.
Worth knowing in advance: a side effect of this kind of training is that the first attempts at extended concentration after a long stretch of constant switching feel subjectively unpleasant, something like withdrawal, a restless urge to check your phone or switch to something else for no clear reason. That's a normal, temporary part of rebuilding your capacity for concentration, not a signal the method isn't working.
I noticed this atrophy in myself through a concrete example, not an abstract one: while working on this exact piece, I caught myself opening my email tab nine times in one hour of writing, with not a single real reason to, not one urgent email, not one expected reply. I specifically counted that number because I suspected a problem, and it came out higher than I was ready to guess in advance. Consciously registering that specific number worked harder than any vague intention to "get distracted less": I closed the email tab physically, rather than just minimizing it, and finished the rest of the piece with zero switches. The difference in speed and coherence between the first hour and the second was noticeable even to me on a reread.
Where to go from here
Focus, task organization, and recovery from depletion are three distinct, though connected, dimensions of productive work. If the main problem is that tasks are poorly organized and constantly get lost, productivity systems covers how to build a workflow around that. If the problem is chronic depletion that doesn't go away even with a perfectly organized day, preventing burnout covers what to do about that.
It's worth honestly identifying which of these three dimensions is actually the weak point right now, before picking up specific techniques from this piece. A perfectly organized task system doesn't help if your capacity to hold attention is already depleted to the limit. Training concentration does little good if you're chronically sleep-deprived and living under constant stress, because a physiological energy deficit outweighs any technique for entering a state of flow.
The capacity for deep concentration doesn't show up from one good technique read in an article, and it doesn't vanish from one bad day. It builds up over years of practice in one direction or the other, and the sensible strategy here isn't hunting for the perfect method, it's starting with one small, sustainable change and giving it time to take hold before adding the next one.
Comments
No comments yet. Be the first.