How to Stop Procrastinating at Work: Three Causes, Three Different Fixes
Procrastination at work is almost never a finishing problem. Once a task is twenty minutes in, it usually gets done. It is a starting problem, and the reason the standard advice fails is that there are three different reasons people do not start, and each needs a different fix. Treating an unclear task like a boring one, or an overloaded week like a personal failing, produces a lot of guilt and no progress. This guide separates the three causes, shows how each looks in a working day, and gives the fix for each.
Procrastination Is a Starting Problem
Watch what actually happens when someone procrastinates. They do not sit idle. They answer email, tidy a document, attend to something urgent but small. The avoided task is not ignored; it is circled. And once they finally begin, the task is frequently easier than the avoidance was.
This has a practical consequence: the whole problem is concentrated in the first few minutes of starting, and any fix that gets a person through those minutes solves most of it. It also has a diagnostic consequence. What a person does instead of starting tells you why they are not starting, and that is where the three causes separate.
Cause One: The Task Is Aversive
The work is boring, unpleasant or emotionally loaded: the expense report, the difficult email, the review of a colleague’s weak draft. The person knows exactly what to do and does not want to do it. The avoidance behaviour is pleasant busywork.
The fix is to shrink the start. Commit to ten minutes, not to finishing. Put the task first in the day, before the inbox has a chance to offer alternatives. Pair it with something mildly rewarding: the coffee, the better chair. Timeboxing methods such as the Pomodoro technique exist for exactly this cause, and they work because they make the commitment small enough to keep.
What does not work: waiting to feel like it. The feeling arrives after starting, not before.
Cause Two: The Task Is Unclear
The person does not know what “done” looks like, what the first step is, or who to ask. The avoidance behaviour is research: reading around the subject, opening the file and closing it, drafting a question and not sending it. This is the cause most often misdiagnosed as laziness, including by the person themselves.
The fix is to define the next physical action. Not “write the proposal” but “list the three sections the proposal needs”. Not “fix the integration” but “reproduce the failure once”. If the next action cannot be named, the task is not ready to be worked on, and the honest next action is to ask someone. Managers can prevent this cause almost entirely by handing over work with a clear definition of done; our guide on prioritising tasks at work covers breaking work down to the point where it can be started.
Cause Three: The Week Is Overloaded
There is more work than time, and starting anything means choosing what to fail at. The avoidance behaviour is doing whichever task is shouting loudest, which is rarely the one that matters. This cause looks like procrastination from the outside and feels like drowning from the inside, and no personal technique fixes it because the problem is not personal.
The fix is to make the trade-off explicit. List the commitments, estimate them honestly, compare with the hours available, and take the difference to whoever owns the priorities. That is uncomfortable, which is why people procrastinate instead, but it is the only fix that works. The Eisenhower matrix is the sorting tool; the harder skill is the boundary-setting our guide to time management skills describes.
Managers should assume this cause first when a previously reliable person starts slipping. Our guide on workload balancing covers how to see it before the person has to say it.
What Procrastination Looks Like in the Working Day
Each cause leaves a different trace, which matters because people are poor judges of their own avoidance.
Aversion shows as a task that is opened and closed repeatedly, with short sittings and long gaps, while other work proceeds normally. Unclear work shows as time in research and reading without output, and questions drafted but not sent. Overload shows as everything getting short, fragmented attention, hours rising, and the most important task getting the least time.
Two numbers make this visible without any judgement attached: sittings per task, meaning how many separate sessions a piece of work took, and the gap between a task being assigned and its first session. Both are available from productivity data and both are most useful when the person can see their own. A rising sittings-per-task figure on one project is a diagnostic; it is not a disciplinary matter, and it should never be treated as one.
Task Start Patterns, Last 2 Weeks
Same-day starts by week
Where avoided time went
▲ Time-to-first-session fell sharply after a 'define the next action' step was added to task handover in W2.
Illustrative eMonitor dashboard.
The Techniques, Matched to the Cause
Most procrastination advice is a list of techniques with no diagnosis, so people try the wrong one and conclude the technique failed. Matched properly:
Aversion: two-minute and ten-minute starts, Pomodoro, eat-the-frog (first thing, before the inbox), temptation bundling. Unclear: next-action lists, a written definition of done, a five-minute question to the owner, breaking the task into pieces that can be started today. Overload: weekly capacity review, explicit prioritisation with the manager, dropping or deferring commitments in writing, protecting one block a day for the most important thing.
Time blocking helps all three, because a task with a slot on the calendar has a start time, and the decision to begin has already been made. Our guide to time blocking covers the method.
See the Starting Problem, Not Just the Late Delivery
eMonitor shows sittings per task and time-to-first-session per person, with employee-facing dashboards, so the cause of a stalled task is visible before the deadline is missed.
What Managers Can Change
A team’s procrastination is mostly a product of how work arrives. Work that arrives without a definition of done produces cause two. Work that arrives faster than it leaves produces cause three. Work that is genuinely unpleasant and never rotated produces cause one in the same people every time.
Three changes address most of it. Hand over work with the next action named and the definition of done written. Review capacity weekly, and treat “more work than time” as the manager’s problem to resolve rather than the employee’s to absorb. And notice the pattern early: a task that has been open for a week with no session is a conversation, not a reprimand, and the conversation usually reveals which cause is at work within a minute.
Our guide to improving team productivity covers the structural side; the guide to burnout signs covers what happens when cause three is left alone.
Procrastination That Is Actually Judgement
Not all delay is procrastination. Waiting for information that is genuinely coming, letting a decision settle overnight, or declining to start work that should not be done at all are all sound. The distinction is whether the delay is chosen and explained or drifted into and disguised. A person who says “I am not starting this until Thursday because the data arrives Wednesday” is managing their time. A person who has not started and cannot say why is not.