← All posts

The 2-minute door opener: why the 'first step' field is the only one that matters

The 2-minute door opener: why the “first step” field is the only one that matters

The dishwasher has been full for three days. I know this. I look at it every time I walk into the kitchen. The task “clean the kitchen” has been on my list since Sunday and it’s now Wednesday.

The kitchen is not actually that dirty. The blocker isn’t the kitchen. It’s the size of the task in my head.

If I could just open the dishwasher for five seconds, the rest happens. I know this from years of evidence. The first physical action is the entire problem. Once my hands are touching dish-related objects, the next minute is on rails.

So why does my todo app keep saying “clean the kitchen” instead of “open the dishwasher”?

The ADHD task-initiation problem in one paragraph

Task paralysis isn’t laziness or poor prioritization. It’s the gap between recognizing a task and starting it, which for ADHD brains is wider than for neurotypical ones. There’s robust clinical literature on this. The shortcut version: dopamine pathways that handle task initiation are dysregulated, so the small reward that normally fires when you decide to start something either doesn’t fire or fires weakly. The decision-to-action loop never closes.

Productivity advice tells you to break tasks into sub-tasks. This is correct in spirit and almost useless in practice, because most apps make sub-tasks optional and most users don’t write them.

The 2-minute door opener: what it is, what it isn’t

A door opener is the smallest physical action that puts you inside the task. It is not a sub-task in the project-planning sense. It’s not “step 1 of 12.” It’s the action that takes less than two minutes and that, once performed, makes refusing to do the rest harder than just doing it.

Examples:

Vague taskDoor opener
Clean the kitchenOpen the dishwasher
Reply to Sarah’s emailOpen the email and re-read it
Write the project proposalOpen a new doc and type the title
Call the dentistFind the number in contacts
Go for a runPut on running shoes
Do my taxesLog into the tax app

Notice the pattern. None of these “do” the task. All of them put you in physical proximity to the task with the next step obvious.

That’s the entire trick. The door opener is bait for momentum.

Why this has to be required

Most apps will let you write a sub-task. They don’t make you. That is the failure.

If the first-step field is optional, the post-it-note version of the user (the one writing the task in a moment of clarity) skips it because they’re confident they’ll figure out the first step later. The depleted version of the user (the one reading the task at the moment of action) cannot find the first step. The decision-to-action loop never closes. The task rots.

If the first-step field is required, both versions of the user are forced to do the same job at the right time: the clarity-moment user writes a concrete first step; the depleted-moment user reads it and acts.

This is one design decision. Required vs optional. It changes the entire success rate of the system.

In Ikoi, you cannot create a task without a first step. The placeholder text is “What’s the first 2-minute action?” The field is half the form.

What about real sub-tasks?

Real sub-tasks (the project-management kind) are useful for genuinely multi-step projects with parallel work. They’re a different feature with a different purpose. Most “tasks” people put in their todo app are not projects. They’re single intentions stalled on initiation. For those, exactly one sub-task matters: the first one.

Apps that conflate these end up with a sub-task system that’s powerful for project managers and unusable for the people whose problem is starting at all.

So

If you remember nothing else about ADHD-friendly task design: make the first physical step a required field, label it in plain language, and put it directly underneath the task title.

Most apps put it in a sub-menu or call it “notes.” That’s where it goes to die.

Related: ‘Not today’ is a feature, not a failure covers the deferral side of the same problem.