Skip to content

Why OTD

OTD started from a specific kind of frustration. Not "I need to be more productive." Something more concrete: I can't start anything.


The problem

The todo list was full. Too full. Thirty items across different projects, different contexts, different levels of urgency. Every morning began the same way: staring at the list, trying to figure out where to start, burning through willpower before doing anything at all.

The problem wasn't laziness. It was the list itself.

A flat list of thirty things forces you to make a judgment call every single time you move from one task to the next. Which one matters most right now? Which one will unblock something else? Which one has been sitting there too long? These aren't simple questions. They require real cognitive work. And by the time you've answered them for the third time in a morning, you're already tired.

GTD helped with some of this — capture everything, process it, get it out of your head. That part still works. But GTD was designed for a world where you work on one thing at a time. The "project" model is sequential at its core: finish this, then start that.

That's not how work actually happens.


What changed

Work happens in parallel. You send an email and wait for a reply. You hand something to a colleague and move on to something else. You ask an AI to draft something while you work on the structure. You're always running multiple threads simultaneously — some in your hands, some in others', some stuck in waiting.

GTD has "Waiting For" as a secondary list. That felt like an afterthought in a world where delegation and waiting had become first-class activities. If half your work on a given day is reviewing what others produced and sending new instructions, you need a system built for that — not one that treats it as a special case.

The other thing that changed: AI. Once you have access to AI that can actually execute tasks, the number of parallel threads explodes. You can delegate five things before breakfast. By noon you might have five results waiting for review, three new things to delegate, and two more you decided to handle yourself. The coordination work is real, and it needs structure.


What OTD is trying to solve

Three things, in priority order:

Overwhelm. When Today contains only what you can genuinely finish, the system tells you when you're done. Not "it's 6pm" — actually done. No backlog accumulating. No guilt carrying over. The feedback loop works.

Priority paralysis. Each stream of work surfaces one action at a time. You don't choose between thirty items every morning. You choose between five or six, and within each one, the order is already decided. The cognitive load of "what do I do next?" drops sharply.

Parallel work. Delegation is first-class. Await is first-class. Review is first-class. The system is built for a day where you're simultaneously waiting on three people, reviewing two AI outputs, and directly doing two more things. That's normal now. The framework should treat it as normal.


The open list problem

GTD recommends looking at your calendar and task list each morning to decide what to work on. That's reasonable. But the list you're looking at is open-ended — it always has more items than you can do today. After your morning "review," you're still working from an infinite list with no clear finish line.

This is a structural issue, not a habit issue. An open list never empties. So "done for the day" becomes a judgment call — based on energy, time, or guilt — rather than an objective signal.

OTD's Daily Review ends differently. Instead of browsing a list, you build a closed set called Today. Every item in Today is something you can genuinely complete today. When it's empty, you're done — not because you decided to stop, but because the set you built this morning is finished.

GTD asks: what should I do from this list right now? OTD asks: what am I committing to finish today?

The difference seems small. The effect isn't. A day that ends with an empty Today feels different from a day that ends with a shorter list. One is completion. The other is just less remaining.


OTD is not a replacement for discipline or judgment. You still decide what matters. You still design your own day. What the framework does is remove the structural friction that makes that judgment harder than it needs to be.

Released under the open source license.