How to Stop Procrastinating at Work

What does procrastination at work look like?

Procrastination at work rarely looks like doing nothing. It looks like doing something else, and usually something defensible: rereading an inbox processed an hour ago, tidying a tracker nobody asked about, collecting background reading for a task you have not opened. The hours get spent, the day reads as busy, and the work that mattered sits where it sat at nine o'clock. Substitution is the shape it takes inside a workday, which is why it runs for weeks unnamed.

Not everything postponed is procrastination. A task pushed to Thursday because two others genuinely outranked it was decided on, and producing that kind of ranking is what the prioritization methods are for. Stalling is the other case: the task is at the top, nothing has outranked it, and it still does not begin. The test is whether a decision exists: if you can name what the task lost to, it was ranked; if it simply failed to happen, it stalled.

Three signatures make stalling visible in your own week. The first is the copied-forward line, moved from Monday's list to Tuesday's to Wednesday's, occasionally reworded, never started. The second is the swerve into small work: a request that would have waited an hour any other day gets answered in four minutes, because answering is easy and the other thing is not. The third is the manufactured dependency - a confirmation you do not need, or a meeting booked about a task that could have been begun instead.

One kind of task attracts all three: the big one with no edges. Write the strategy. Fix the reporting. Sort out the handover. Each is a heading rather than a task, and a heading offers nothing to open, nothing to do for twenty minutes, no way to tell at four o'clock whether the day moved it.

The bill rarely arrives as work left undone. It arrives as work done in a single pass at the last possible moment. A report begun the evening before it is due gets written once, with no room for a second read and none for anyone else to look at it. A decision deferred until the meeting that forces it gets made on whatever is in the room. What stalling costs at work is seldom output; it is timing, and the quality that timing permits.

The eight methods here are not a category of their own. They are borrowed from three of the site's other categories - two from prioritization, three from focus, three from habits - and the hub still files each where it belongs. No planning system carries the tag, which is worth a moment: planning decides when work happens, and a stalled task is one the plan already placed. What the eight share is a mechanism, not a family: each removes one condition a stall needs to continue.

How do you choose an anti-procrastination method?

Stalling happens at four identifiable points in a task's life, and these eight methods divide two to a point. What to settle before choosing, then, is where your own tasks stop: at the start line, at their size, at the deadline, or on the second pass. Take the pair matching the case you recognize below; the other six are aimed at a stall you do not have.

Stalls at the start line are the plainest: the task is clear, the time is there, and the file still does not get opened. Both answers shrink what you agree to. The Two-Minute Rule works on size - a job you could finish inside two minutes never joins a list at all, because Getting Things Done treats the bookkeeping as dearer than the task. The Pomodoro Technique works on duration: Francesco Cirillo's sprint runs 25 minutes, small enough that turning it down takes more argument than beginning.

Stalls about size look different: one oversized task gets passed over while a dozen smaller ones are finished around it. Position fixes this, not reduction. Eat That Frog moves the postponed task to the front of the workday, ahead of mail and other people's requests; Brian Tracy's book supplies the name. The Ivy Lee Method gets there through order: six tasks written the evening before, ranked one to six, worked in sequence, with no permission to reach the second before the first is finished. Dropping that clause is the pitfall its page warns about.

Stalls at the deadline are the ones no ranking will fix. Work due in three weeks exerts nothing on a Tuesday, and a ranking that leaves it alone is honest: nothing happens today if it waits. So move the date. Parkinson's Law supplies the reasoning - give a task a week and it will find a way to need the week - and its page suggests cutting an honest estimate by a quarter to a half. Timeboxing applies that per sitting: fix the length before you begin, run a timer, stop when it ends. This site names Parkinson's Law a heuristic, never a measured effect, so what you borrow is the container.

Stalls on the second pass appear only after the first worked: three days go well and the fourth does not. Both answers come from the habits family. The Seinfeld Strategy puts the record on a wall rather than in memory, one mark per day the work happened, so the daily question shrinks to whether you will end a run you can see. The Two-Minute Rule for habits works the same gap from the other end, capping the recurring commitment at two minutes and leaving it capped. Its page names the failure mode: enlarging too early.

Working style comes in afterwards, and this page leans one way more than its neighbors do. The comparison table on the home page hands each of the four styles three methods to try first, and all three of the Sprinter's - the Pomodoro Technique, Timeboxing and Eat That Frog - sit on this page. The Improviser's row names the Two-Minute Rule, here twice, for tasks and for habits. Nothing the table offers the Architect or the Visionary appears here at all. That matching is the site's own editorial judgment, and it hardly means only Sprinters stall; but recognizing yourself in the Sprinter or Improviser profile among the four working styles shortens this page.

One warning belongs with this list: every method on it can be turned into the stall it was meant to remove. An hour clearing two-minute jobs is procrastination with a system attached, which is why that rule's page confines it to administrative time and bars it from a protected block. A timebox spent on the wrong task is a well-run stall. Six ranked Ivy Lee tasks with the difficult one at number four is a plan for not doing it. Identify the task you keep getting round, then ask whether the method you started moves that task today.

Why structure beats willpower

Underneath those stall points sit four causes, each a property of the task, not of the person holding it: scope nobody has pinned down, no physical first move written anywhere, a date too far off to implicate this week, an opening step sized for a clear afternoon you do not get. A property of a task can be edited in a minute at a desk. Willpower is not the variable this page works on, because none of the four shrinks when you want the work done more.

Vague scope is the commonest and the easiest to miss, because the heading on the list still reads like a task. Timeboxing removes it by force: a box ending at a fixed time cannot be entered without a definition of enough, and its page asks for that definition before the timer starts. Eat That Frog demands the same in its own vocabulary, telling you to define done for the frog first, because work with no finish line can absorb a morning and still be open.

The second cause is the missing physical move. A line reading prepare for the review names an outcome; open last quarter's deck and list the three numbers that changed names something your hands can do in four minutes. Making that translation is planning work, and Getting Things Done gives it a step to itself. Here it comes free with size: the Two-Minute Rule for habits demands a version of the work fitting inside two minutes, and no such version can be written vaguely.

The third cause is a date that does not reach into the current week. Parkinson's Law removes it by supplying a nearer one deliberately and then making that date behave like a real one; its page is specific about how, which is to promise delivery to somebody or book the next thing immediately afterwards. That second half is the part that gets dropped, and a deadline only you know about is one you are free to move.

The fourth cause is an opening step sized for conditions you do not have. A step needing two clear hours is unavailable on a day holding a stand-up at ten and a call at eleven, so the task waits for a better day, and better days are scarce at work. The Pomodoro Technique cuts the entry price to one sprint, which fits between two meetings; Eat That Frog allows for it too, making the frog the first 30 to 60 minutes when the task is genuinely too large.

There is a limit, worth naming rather than engineering around. Sometimes a task stalls because it does not belong on the list: the report nobody reads, or the process step that outlived the project it served. Tightening its scope and pulling in its date will get it done, which is the wrong outcome reached efficiently. Before applying any of this to a task that has resisted for a month, check that it still deserves the slot - a ranking question the prioritization methods answer. Structure is good at making work start. It says nothing about whether the work was worth starting.

Eight methods that counter procrastination

Frequently asked questions