Blog · Productivity

Why Do We Procrastinate on Projects?

We often hear it's just a matter of "more willpower." Psychology and neuroscience tell a different story. · September 20, 2026 · 7 min read

An equation for procrastination

Behavioral procrastination is defined as the voluntary, irrational delay of a planned action, despite knowing the negative consequences that will follow. In a project, it typically shows up as two patterns: Parkinson's Law, where work expands to fill the time available, and the Student Syndrome, where real work on a task only starts once the deadline becomes critical.

The Temporal Motivation Theory (Steel & König, 2006) models this with a simple formula:

Utility = (Expectancy × Value) / (1 + Impulsiveness × Delay)

In plain terms: the further away a deadline is, the closer today's perceived utility of working on it drops to zero - compared to tasks with instant gratification, like answering an email. A project spanning several months with no intermediate milestones is, mathematically, fertile ground for procrastination.

Two colleagues discussing their views on a project
Two colleagues discussing their views on a project

What's actually happening in the brain

Brain imaging shows that procrastination isn't a logistics or organization failure - it's difficulty regulating the negative emotions a task triggers: anxiety, fear of failure, boredom. The prefrontal cortex tries to enforce a long-term view, while the amygdala and limbic system chase immediate relief instead.

When a project is vague or poorly structured, that ambiguity is perceived as a threat: the limbic system takes over, and we retreat into a more comfortable task to ease the emotional tension (Sirois & Pychyl, 2013).

Three organizational flaws that make it worse

What the research says actually works

Evidence-based protocols converge on three concrete levers: break work into chunks under 90 minutes to maximize your sense of "I can do this," artificially shrink the delay with short sprints (1–2 weeks in Agile/Scrum), and make dependencies explicit with a Gantt chart and critical milestones.

That's exactly what a tool combining Kanban, Scrum and Gantt in one place enables: visually breaking a project into short tasks, pacing the work in sprints, and making milestones tangible so deadlines stay psychologically close.

Sources

← BackAll articles Next article →Why Breaking Down Tasks Boosts Productivity