Skip to content
Theodora Velli

Starting tasks · 5 min read

ADHD task paralysis: make the first action smaller than the task

By Theodora Velli · 5 min read · Published

Six days, four lines

In the book, Leo has a four-line email to answer. A colleague wants to know which version of a dataset is final. Leo could reply in ninety seconds. He has not replied in six days, and the fact that it would take ninety seconds makes day six feel worse than day one.

At first it was just a task. Six days in, it carries weight: he owes an apology, an explanation, a little admission that he left something so simple undone. Opening the laptop makes his chest tight, a game waits one tab over, and the lid goes down again.

The reply itself is tiny. Starting it has grown huge.

Tasks hide their first steps

A task name sounds like one thing. It usually arrives as many demands. The book breaks down write the report into eight: find the latest document, identify the audience, locate the data, decide the structure, notice missing information, ask for it, tolerate not knowing whether the argument is good, and write a first sentence.

Leo's reply hides six: going back into the thread, facing the six days, judging how big the apology should be, checking which file is final, locating that file, and accepting that the colleague may be irritated.

So before you blame motivation, expose the hidden steps. The task you cannot start may be six smaller tasks wearing one name.

What a good first action looks like

A useful start has five features. It is physically visible. It takes less than two minutes. It does not require finishing the task. It reduces uncertainty about the next step. It leaves a marker if you stop.

Pair a verb with something you can physically touch or open. The book gives these contrasts.

Starts that stay vague: taxes. Presentation. Clean kitchen. Sort life out.

Starts you can see: gather every piece of tax mail into a single box. Open the presentation and type the decision it has to support. Make room in the sink to wash a single pan.

A start can be unimpressive. What it must do is change the state of things.

When the problem is not knowing rather than not wanting, use an uncertainty verb: ask, compare, inspect, choose, define, confirm, find or test. So work on website turns into deciding the single action the home page should lead a visitor to take.

Contact is not completion

People often avoid a task because opening it feels like signing up to complete it. The book rewrites that deal: ten minutes of contact, then I may stop.

In that time you can look at the current state, find the missing information, write the next question, finish one small section, or leave a note. Stopping after honest contact still produces something. It gives you information and lowers the cost of the next start.

How Leo did it

Leo stopped trying to reply. Going at the reply head-on had lost six days.

He put on an instrumental playlist, which is his opening ritual: when it starts, one document opens. His contact action: open the thread, type the opening line into a draft, save it, and then he had permission to stop. He wrote a holding line that said he was sorry for the slow reply, was confirming which version is final, and would send it across that day.

One line, saved as a draft. He did not have to find the file or answer the real question. The task had gone from silence to one sentence that included a date.

Then the rest shrank too. Locating the final file was now simply the next obvious step, not the sixth item in a heap of dread. He found it in under a minute, attached it and sent it.

A few weeks later a different reply stalled, and the saved first line was all he managed that day. He saved the draft, wrote the promised date in his INBOX note and closed the laptop. The book counts that as a completed Low Power session. The next morning the draft already had its first line, so the start cost almost nothing.

When tiny steps still do not work

The book names two usual reasons.

The tiny step was really the whole task. Just start the email held every one of Leo's six hidden demands. Make it smaller. Instead of reply, open the thread. Instead of opening the thread, start the playlist and leave the phone in another room. Go on cutting until the first action seems nearly pointless. That is exactly the size you want.

The tiny step came with a hidden promise to keep going. You said two minutes, you meant two hours, and some part of you knew. Leo did this for years, telling himself just five minutes and then feeling cheated when those minutes did not end in a finished task. What fixes it is a stop rule you actually keep. Trust builds when the deal is a real one.

Keep the setup small too

A landing strip is the least amount of preparation that lowers the cost of starting: the right file already open, the next question written at the top, the phone out of reach. Prepare just enough to clear the first obstacle. Once a landing strip turns into a project of its own, it has become a way of avoiding the work.

The next action

Choose one task you have avoided this week. Write its first visible verb and object, set a two-minute stop rule, and do the contact action before you close this page.