How to Focus at Work

What does focus at work depend on?

Focus at work depends on the conditions around a task far more than on how hard you try to concentrate. Three of them do most of the work: whether you have a block of time nobody else can claim, whether the task was chosen before the block started, and whether an interruption can reach you inside it. Get those right and attention tends to arrive on its own; get them wrong and no amount of resolve holds the line for an afternoon.

The first condition is usually decided by a calendar rather than by you. A day with three meetings scattered through it can still show several free hours between them and be useless for demanding work, because the free time arrives in pieces. The Deep Work page on this site asks for blocks of 90 to 180 minutes, and that number is a useful test: a day chopped into short gaps between calls cannot supply one, however willing you are. The fix for a fragmented day is a scheduling move rather than an effort move.

The second condition is settled in the minutes before you begin. A block with no named task in it gets filled by whatever is loudest, and at work the loudest thing is usually somebody else's request. Choosing what the block is for while the block is already running is the most expensive place to choose, because the clock is moving and every open tab is arguing its case. Naming it in advance takes a minute and settles the question while nothing is at stake.

The third condition is the interruption itself, and its price is routinely underestimated. Moving between unrelated tasks costs a little time in the moment and a little more afterwards, while your attention finds its way back. Answer a chat message in ten seconds and the ten seconds is not the bill; the bill is the stretch afterwards spent hunting for your place in the work. Do that often enough and a day of real work quietly becomes a day of returning to work.

Most of those interruptions are invited by default settings rather than by emergencies. A chat client installed with every alert enabled, a mail client that pops a preview over whatever you are reading, a phone lying face up beside the keyboard: none was chosen deliberately, and each is a decision about your attention that somebody else made. An open-plan office adds the same problem in physical form, where being visible means being available. Remote work does not remove that; it moves it into a status dot that says you are online.

None of this makes focus at work a question of character. It makes it a design problem, and design problems can still be worked on when effort has run out. Each of the five methods below removes a class of decision or interruption before the work starts rather than during it: one names the task, one shortens the commitment, one groups the small jobs out of the way, one walls off a long stretch, and one stops trivial work from piling into a queue. If your real friction is deciding what to work on rather than staying with it, the other families on the hub take that end of the problem.

How do you choose a focus method?

Which method fits depends on the shape of your day rather than on which one has the best reputation. All five protect a block of attention, but each is built against a different threat, so the question worth answering first is which threat takes your day apart most weeks. Working style matters, and it matters second.

If the hard part is starting, begin with the Pomodoro Technique. Francesco Cirillo's method asks for 25 minutes on one task, then a five-minute break, with a longer break after four rounds. The length is the trick: short enough that agreeing costs you nothing, long enough for real work to happen inside it. It also puts a visible price on interruption, which no longer costs a moment but costs the sprint. It suits Sprinters, who work best in bursts, and anyone whose difficulty is the first ten minutes rather than the next two hours.

If the hard part is that the day never holds still, Task Batching is the better first move. It gathers similar small work - mail, admin, calls - into scheduled blocks, so each kind gets handled once instead of interrupting you all day. Nothing is dropped: the same messages are answered and the same calls are made, but at a time you picked rather than the time they arrived. It suits interrupt-driven roles, and in this site's mapping it lands with the Improviser, whose weeks rarely look the same twice, and the Architect, who likes a week in containers.

If the hard part is that your most valuable work needs more room than the day gives it, Deep Work is built for exactly that. The method is the least clever thing on this page and the hardest to arrange: one long block, every interruption taken out of it beforehand, one task inside it. Difficult problems charge a warm-up fee, the stretch spent loading the problem back into your head, and a protected block pays it once instead of every twenty minutes. It suits Architects, and it carries the highest entry cost here, because it asks something of the calendar before it asks anything of you.

If the hard part is work that sprawls - the review that could always take another pass, the document never quite finished - use Timeboxing. You commit to a length before you start and stop at the end of it, which turns an open-ended job into one with a finish line. It leans on Parkinson's Law, the idea that work expands to fill the time available for it, and this site names that as a heuristic rather than a measured effect. It suits Sprinters, who respond to a deadline, and Architects who want their estimates tested.

If the hard part is small-task noise - the one-line replies and quick approvals that pile up until the pile is itself the distraction - the Two-Minute Rule clears it. The rule comes from Getting Things Done: when a task takes less than two minutes, do it on contact instead of writing it down, because tracking it costs more than finishing it. It suits Improvisers and Sprinters, with one strict boundary: it belongs to administrative time, never inside a protected block.

Two of these will often look equally plausible for the same difficulty, and that is where working style breaks the tie. The four profiles on the home page describe how somebody already operates when nobody is supervising, and the working-style self-check turns those profiles into a shortlist without asking you to read all four. Pairing is normal here too: batching clears shallow work out of the way of a long block, and a short sprint is a reasonable way to open a block you have been dreading. Whatever you land on, give it two honest weeks before you decide, and judge it on how the days went rather than on how the method reads.

How do you avoid distractions at work?

Avoiding distractions at work is mostly a matter of changing defaults rather than resisting temptation. A default is whatever happens when nobody decides anything: alerts on, chat open, door open, phone within reach. Each was set by an installer or an office layout rather than by you, and each can be reset once and then left alone. A setting is the better tool, because it is decided a single time while resolve has to be spent again every morning.

Start with the device, because it is the cheapest thing to change and the change lasts. Turn off banners and sounds for everything that is not a genuine emergency channel, then check the remaining channels on a schedule instead. Put the phone somewhere that requires standing up. Close the tabs open out of habit rather than for the task in front of you; a browser holding a dozen of them is a list of a dozen invitations. An app that promises to block distraction for you is often one more thing to configure.

Then handle the part other people control, which is where the durable gains are. If colleagues expect a reply within minutes, a quiet morning gets interrupted for you whatever your settings say, so the arrangement has to be said out loud: name when you check messages, name how somebody reaches you when something genuinely cannot wait, then answer reliably at those times. People accept a delayed reply from someone who always replies, and they escalate around someone who sometimes disappears.

That agreement is what makes Task Batching survive contact with a real week. Two or three scheduled passes through mail and chat, announced rather than assumed, cover almost everything a normal day delivers, and the agreed exception lane covers the rest. Deciding in advance what counts as a real exception matters: without that line, the first genuine emergency becomes the argument for reopening every interruption permanently.

Distraction also arrives from your own side of the desk, and that is easier to admit with a container already in place. The reflexive inbox check tends to happen at the exact moment the work turns difficult, which is where the Pomodoro Technique does its quietest work: the sprint is short enough that waiting for the bell is a small ask, and anything surfacing mid-sprint gets written down instead of chased. If the same thought keeps coming back, a note beside the keyboard removes the reason to switch.

In shared spaces, visible signals do the negotiating you would rather not repeat all day: headphones on for the length of a block, a booked room where one exists, a status that says when you are back rather than merely that you are busy. Working from home, the equivalent is the same block written on the calendar where colleagues can see it, which turns a private intention into a public fact. Then keep the arrangement small. One reliably undisturbed block a day beats an ambitious rule that collapses on the first busy Tuesday.

The five focus methods

Frequently asked questions