Procrastination: Diagnosis and Prescription

2024/09/20

LIVEneurodivergence

I gave a speech about procrastination at Toastmasters. Three drafts. Each one got more honest than the last. The first version was a generic TED-talk-shaped thing about “overcoming procrastination.” By the third draft, I’d accidentally written a personal diagnostic manual.

Here’s what I actually learned — not the polished speech version, but the messy real version.

The premise

Procrastination isn’t about time management. I know that sounds like a bumper sticker, but stay with me.

It’s a psychological thing. Psychology, behavioral economics, neuroscience — they all converge on the same answer: you’re not procrastinating because you’re lazy or bad at calendars. You’re procrastinating because something about the task is triggering an avoidance response. Lack of confidence in success, aversion to discomfort, impulsivity pulling you toward easier dopamine, or the goal being so far away that your brain literally can’t connect present effort to future reward.

The problem is that “procrastination” is one word for at least four completely different problems. And if you treat the wrong one, nothing happens. Like taking ibuprofen for a broken leg — technically a pain response, technically the wrong intervention.

So I started sorting.

Type 1: Trivial tasks

Groceries. Taxes. That thing with the lease renewal. Replacing the air filter. Getting a new phone.

These aren’t hard. They’re not scary. They’re just… low-priority enough that they never win the competition for your attention. There’s always something more urgent, more interesting, more rewarding. So they pile up. And then the pile itself becomes stressful, which is ironic because each individual item takes maybe twenty minutes.

This is the easiest type to fix, which is probably why I procrastinated on fixing it the longest.

The solution is blunt: knock them out immediately when they appear, or make a conscious decision. Can I delegate this? Can I just… not do it? Is it actually reasonable to deprioritize this indefinitely? If yes — take it off the list entirely. Don’t let it sit there radiating guilt. Either do it now or decide it doesn’t matter. The middle ground — “I’ll get to it eventually” — is where the stress lives.

Type 2: Fear

This one’s sneakier. It doesn’t feel like procrastination. It feels like being busy with other things.

I used to put off sending out resumes. Not because I didn’t want a job — I desperately did. But every time I sat down to apply, my brain would generate seventeen reasons why I wasn’t ready yet. The resume needs one more pass. I should study more system design first. This company probably isn’t hiring anyway. All very reasonable-sounding. All just fear of rejection wearing a productivity costume.

A more recent one: I needed to ask my manager for meeting recordings. Simple request. Completely normal thing to ask. I put it off for weeks. Weeks. Because somewhere in my wiring, “send message to authority figure” triggers a threat response that is wildly disproportionate to the actual stakes.

The stoic approach works here, and I say that as someone who normally finds “just think about it differently” advice useless. But specifically: think about the worst case. Actually think about it. Not the vague dread — the concrete scenario. I send the email, my manager says no. That’s it. That’s the worst case. My brain was treating it like the worst case was public humiliation and career destruction, when actually it was a one-line Slack reply: “sorry, we don’t record those.”

Once you name the fear and compare it to reality, the gap is usually embarrassing. That’s the point.

Type 3: Dislike

Some tasks aren’t scary. They’re just awful.

My PhD research was this. I didn’t fear it — I’d already gotten into the program, I had a supervisor, the path was clear. I just hated doing it. The work was tedious, the feedback loops were long, and the dopamine-per-hour ratio was genuinely terrible compared to almost anything else I could be doing.

So I’d delay the research until the day before my one-on-one with my supervisor. Every time. Cram it all into one panicked evening, show up pretending I’d been working steadily all week. Classic. My supervisor probably knew. They always know.

What eventually helped — and this took me embarrassingly long to figure out — was the 25-minute timer trick. Not as a productivity hack. As a negotiation with my own brain. “You don’t have to do two hours of research. You have to do twenty-five minutes. That’s it. Then you can stop.”

And the thing is, once you start, it’s usually not as bad as the anticipation. The dread is almost always worse than the doing. Twenty-five minutes turns into forty, the flow state kicks in, and suddenly you’ve made actual progress. That progress itself becomes rewarding — a positive cycle that feeds the next session.

There’s a related insight I picked up somewhere that stuck with me: as soon as you identify the thing you’re avoiding and take the first concrete action — make the first phone call, send the first email, open the first file — even if it doesn’t solve anything, the mere fact that you’re addressing it dramatically reduces the stress. Because stress comes from ignoring things you shouldn’t be ignoring. Stop ignoring it, even a little bit, and the pressure valve opens.

Type 4: Perfectionism

This is the type that gets praised. “Oh, you’re just a perfectionist” — said like it’s a compliment. It’s not. It’s procrastination with better branding.

I’d prepare endlessly for presentations. Way beyond what was needed. Tweaking slides that nobody would notice, rehearsing sections that were already fine, researching edge cases that no one would ask about. The presentation was ready at 60% effort. The remaining 40% was me avoiding the moment of actually presenting — because presenting means being evaluated, and being evaluated means potentially being found inadequate.

Perfectionism is fear wearing a work-ethic costume. It looks like diligence. It feels like preparation. It’s avoidance.

The fix is pseudo-deadlines for minimum viable products. Ship the 60% version. Set a date. When the date arrives, what you have is what you present. This feels terrifying, and then you do it, and it’s fine, and you realize that the gap between your 60% and your 100% is mostly invisible to everyone except you.

The framework

Three drafts of this speech and the core insight boils down to two steps:

Diagnose, then prescribe.

Be honest about why you’re procrastinating. Not the surface reason — “I didn’t have time” — but the real one. Is it trivial and you just need to either do it or drop it? Is it fear and you need to name the worst case? Is it dislike and you need a 25-minute on-ramp? Is it perfectionism and you need to ship the MVP?

Different root cause, different solution. Applying the wrong fix is worse than no fix — it just adds one more thing you tried that didn’t work, which feeds the narrative that you’re fundamentally broken. You’re not. You’re just using the wrong tool.

Build your own system. When you find a solution that works for a type, write it down. Make it your standard operating procedure. Next time that type shows up, you don’t have to figure it out from scratch. You just run the playbook.

Diagnosis and prescription. That’s all it is.