“Not today” is a feature, not a failure

I changed three words in Ikoi last month and the emotional weight of opening the app dropped by half. The button used to say “Snooze.” Now it says “Not today.”

That’s the whole change. Same behaviour underneath: the task moves out of today’s view and reappears tomorrow. But every user who’s mentioned it has used a version of the same word: relief.

Naming matters more than designers admit, and it matters specifically more for ADHD users than for anyone else.

The default language of todo apps is the language of failure

Open most apps. Look at the verbs: snooze, defer, postpone, push, reschedule. Look at the visual states: overdue (red), missed (strikethrough), late (timestamp). Look at the streaks: broken, restarted, abandoned. (Streak pressure is one of the productivity strategies that doesn’t survive an ADHD brain for exactly this reason.)

Every one of these words frames the user as the one who didn’t do enough. The task didn’t get done. The system didn’t fail to schedule the task; you failed to act.

For someone whose working memory and executive-function track record broadly match what generic productivity assumes, this is fine. The red tag is information: catch up. For an ADHD brain that already carries baseline guilt about every unfinished task, the red tag is fuel for avoidance.

It is, structurally, a punishment signal handed to a brain that is already over-punishing itself.

Deferring is a real decision

When I move a task out of today, there are usually three reasons:

1. The day got smaller than I expected. Three meetings I didn’t see coming. The dishwasher broke. My brain went sideways at 2pm and didn’t come back.
2. I was wrong about the priority. Past-me thought this had to happen today. Present-me, with new information, doesn’t.
3. I don’t have the energy. Some days I have spoons for hard things. Some days I don’t. Forcing it doesn’t make spoons appear.

In every one of those cases, deferring is the right move. It is not a failure of will. It is a choice between two real options: do this now while depleted (badly), or do this later while functional (well).

The app’s job is to let me make that choice cleanly. Not to make me feel like I lost.

What changes when language changes

Renaming “Snooze” to “Not today” sounds cosmetic. It isn’t. Three things actually shift:

• The action becomes a sentence. “Snooze” describes what happens to the task. “Not today” describes what I decided about the task. The agency moves from the system to me.
• The grammar implies a future. “Not today” presupposes “but maybe tomorrow.” The task isn’t gone, isn’t failed, isn’t shelved indefinitely. It’s marked.
• The word is one I’d say aloud. “I’m going to snooze that one” is software-speak. “Not today” is a real human sentence. The closer the UI gets to the way users actually talk to themselves, the less friction there is.

That last point matters most. Software using words I’d never say in conversation forces a translation step every time I use it. Translation is decision overhead. Decision overhead is where ADHD use-cases collapse.

What this is not

This is not a case for removing accountability. The post is about deferral, not erasure. Tasks that get deferred too many times still need a moment of reckoning: do I still want to do this, or am I lying to myself? In Ikoi, that moment shows up as task decay (untouched tasks fade after a configurable number of days), not as a red overdue tag.

The point is to separate two questions that most apps fuse:

1. Did you do it today? (No.)
2. Did you fail? (Almost never the right second question.)

Most apps treat the answer to question 1 as the answer to question 2. They shouldn’t.

What to take from this

If you’re building software for ADHD users (or really, for any user who’s already hard on themselves), audit the verbs. Walk through every action label, every status, every empty state. Ask of each one: does this language assume the user did something wrong?

If yes, change it.

The easiest changes look like nothing. They are not.