ADHD paralysis: getting unstuck when you know what to do

ADHD paralysis is the freeze you hit when you know what to do and still cannot start. It is an informal name, and doctors tie it to weak executive function, the brain skills that start, plan and finish tasks. I get moving by writing the next step down outside my head and making it small enough to check in minutes.

Do this now if you are stuck

1. Write the one next step on paper or on your screen.
2. Shrink it until it takes under 10 minutes.
3. Write one line that says how you will know it worked.
4. Start that step. Leave the rest of the task alone for now.

If you use Claude or ChatGPT, paste the template below at the start of a stuck session.

TEMPLATE (a starting point, not my personal prompt)
I am stuck starting this task: <task>.
Here is where I left off: <paste your last note, commit or handoff>.
Give me one next step that takes under 10 minutes.
Tell me how I will know that step worked.
Do not give me a plan for the whole task.

This template follows the same idea as the resume card further down. It is a template, and I label it that way because it is not the exact prompt I type. The last line matters most, because a full plan is one more thing to hold. For more prompts in this style, see my ADHD prompts for Claude.

This post is about my own setup as a developer with ADHD. It is not medical advice. If the freeze is frequent or heavy, raise it with a clinician who knows ADHD.

Why can I know the task and still not start?

You can know the task and still not start, because knowing what matters and doing it are two different jobs. I code with Claude Code, Anthropic’s AI coding tool, and my setup keeps a log of every tool that it runs. That log showed me this on 06/04/2026.

I also run citability.dev, a tool that checks how AI search sees a website. The task I had picked as most important for it was finding the best next move to win its first self-serve customer. It sat open for days.

Over two weeks, about 90% of the tool runs in my log went into my setup itself. Those runs went to tools that sort, tidy and review my setup. I knew which task mattered. I built more tools instead.

I was busy the whole time, just on the wrong thing, and I think that pattern is worth watching for in yourself. If you stay busy around one task, the next step is probably too big or too vague to start.

What is ADHD paralysis, and what does research say?

ADHD paralysis is a name people use for freezing in front of a task, even one they want to do. The Child Mind Institute says it is not an official symptom of ADHD, though many people with ADHD have felt it [1]. Cleveland Clinic also says plainly that it is not a medical diagnosis [2].

Child Mind draws a line I find useful. Executive dysfunction can mean trouble planning the work or picking what comes first. Paralysis is the freeze that happens even when you know what to do [1]. CHADD (a national ADHD group) says problems with executive function affect whether a person can start a task and see it through [4].

Health sites often split it into mental, choice and task paralysis, but these labels come from the press [1][3]. So I treat them as handy words. Task paralysis is the freeze on a task, and Healthline says new tasks and tasks with many steps can set it off [3].

Working memory, the brain’s short-term scratch pad, is part of why I freeze. A 2005 meta-analysis by Martinussen and colleagues pooled many studies and found working memory problems in children with ADHD [6]. I am an adult, so I hold that study loosely. But it matches how my days feel.

I close the laptop and sleep. By morning my picture of the project is gone. I keep short written rules for coming back to a project after time away, and they say it bluntly. An ADHD brain 12 hours later is a different brain.

How do you get out of ADHD paralysis?

You get out by shrinking the next step until it is small and visible, then checking it before you stack anything on top. That lines up with Russell Barkley’s book Taking Charge of Adult ADHD [5]. His Rule 4 tells you to write key information down outside your head. He calls Rule 6 “Break It Down…and Make It Matter” [5].

Cleveland Clinic lists taking the smallest next step and writing things down among its strategies [2]. None of that is new. I knew it too.

The hard part is that the frozen brain is the one that has to do it. So I stopped asking my brain. I built the habit into my setup instead, which is the hooks, skills and notes I use with Claude Code.

For months I had held the plan for every project in my head, and I held it for Claude Code too. On top of my own ADHD, that was too much. So I told Claude Code to take over the planning and tracking for both of us. I asked it to plan as if it had ADHD as well, so it would expect to lose track and write every open task down.

Put the next step on the screen before I need it

I wired two hooks into Claude Code. These are small scripts it runs when a session ends and when the next one starts. The first hook records what that session shipped. It writes nothing for an empty session, so it never invents a win for me.

The second hook reads that record and prints a three-line card when I sit back down. The middle line shows my open loop, a task I started and did not finish.

↩ were: <what I was doing>
→ next: <the open loop>
✓ last session shipped: <receipts>

That card is most of the trick. It is boring, so it works. I do not have to remember where I was, what I touched last or which loop I left open. The card tells me before I type a single word.

If you do not use Claude Code, keep the same three lines in a plain text file. Update it when you stop. Read it first when you sit back down. I go deeper on my version in Claude’s executive function mode for ADHD.

If your Claude Code sessions keep starting from zero, copy the free ADHD CLAUDE.md config. CLAUDE.md is the notes file that Claude Code reads at the start of every session. This one gives you ADHD-friendly working rules and a checkpoint block that carries context from one session to the next, with no email required.

Make the first step tiny and check it

I hate going ten steps in one direction and then learning that step two was wrong. So I gave my setup a rule for it. If more than two later steps rely on an idea, it checks that idea before it builds anything. It also tells me at the start what result would mean we should drop the whole plan.

This matters more than it sounds. I can start a tiny step I can check in minutes, but I avoid a shaky step with nine more on top. I think the avoidance is my brain doing a cost estimate it never shows me.

Give every task a finish line

The same instruction gave my setup a check I like a lot. Every task needs a finish line, one line that says what finished looks like. My setup hands out no work without one, and it counts nothing as done without evidence.

A task with a finish line is easier to start, I think, because my brain can see where it ends. An open-ended task feels like an endless hallway with no door at the far end. So I circle it.

What does my get-unstuck sequence look like?

My sequence is a short ritual I wrote for coming back to a project after more than two hours away. The hooks run part of it for me.

1. Read the resume card that a hook prints when the session starts.
2. Read the top of the project’s status doc, the one file that says where it stands.
3. Run git log for the last five commits to see what I actually did.
4. Run the project’s smoke test before touching new work.
5. Write the finish line for the next step.
6. Before I stop, write down what was done, what comes next and what is blocking.

Step four is the tiny tested first step, because a smoke test gives me a clear pass or fail within a few minutes. If it fails, my rule says fix that first, so the rule picks my next step for me.

My rules call skipping this ritual the costliest ADHD failure mode I have. Rebuilding context from memory means making up facts that a file already holds. The same rules cap me at two active projects at once, so a third can wait in the background but cannot hold my attention.

I keep the rest of my tools in my ADHD developer tool stack.

Sources

1. Child Mind Institute, “What Is ADHD Paralysis?” https://childmind.org/article/what-is-adhd-paralysis/ (checked 10/10/2026)
2. Cleveland Clinic, “ADHD Paralysis,” published 10/09/2023. https://health.clevelandclinic.org/adhd-paralysis (checked 10/10/2026)
3. Healthline, “What Is ADHD Paralysis?” medically reviewed 07/11/2025. https://www.healthline.com/health/adhd/what-is-adhd-paralysis (checked 10/10/2026)
4. CHADD, “Executive Function Skills.” https://chadd.org/about-adhd/executive-function-skills/ (checked 10/10/2026)
5. Russell A. Barkley, Taking Charge of Adult ADHD, second edition, Guilford Press, table of contents. https://www.guilford.com/books/Taking-Charge-of-Adult-ADHD/Russell-Barkley/9781462546855/contents (checked 10/10/2026)
6. Martinussen, Hayden, Hogg-Johnson and Tannock, “A meta-analysis of working memory impairments in children with attention-deficit/hyperactivity disorder,” Journal of the American Academy of Child and Adolescent Psychiatry 44(4), 377 to 384, 2005. https://pubmed.ncbi.nlm.nih.gov/15782085/ (checked 10/10/2026)

I write about the neurodivergent systems I build for myself. Join the neurodivergent systems list to get the next one first.

Keep reading

• Claude’s executive function mode for ADHD
• My ADHD engineer productivity system
• Claude Code skills for ADHD developers
• ADHD prompts for Claude
• The free ADHD developer scorecard