How to run your week from a single plain-text file

Every few years someone rediscovers that a single text file outperforms an elaborate productivity system. It is not nostalgia. A plain file has properties no app can match: it opens instantly, it never syncs badly, it has no opinions about how you work, and it will still be readable long after the app you nearly chose has shut down.

The structure

One file. Four sections, in this order, because the order is what makes it work.

• This week — the handful of things that must actually happen. Five items, not fifteen. If everything is on the list, the list is a wish.
• Today — three items pulled up from the week each morning. This is the only section you look at while working.
• Waiting on — anything blocked on somebody else, with the date you asked. This section is the entire reason the file beats a task app for most people.
• Someday — the graveyard. Ideas go here to stop them cluttering the top of the file, and you read it once a month.

Why the plain file wins

The advantages are mostly about friction. Capture is instant — no app launch, no project field, no priority dropdown, just a new line. Editing is unrestricted, so you can restructure the whole week in five seconds by moving lines around, which is impossible in software that enforces a hierarchy.

And it is honest about volume. A task app hides three hundred overdue items behind a filter and shows you a tidy screen. A text file shows you the whole mess, which is uncomfortable and correct. That discomfort is what makes you delete things.

The daily and weekly loop

Each morning takes two minutes: read "This week", pull three things into "Today", clear yesterday's leftovers. Each Friday takes ten: move everything unfinished either forward or to Someday, chase anything in "Waiting on" older than a week, and write next week's five items.

The Friday pass is the part people skip, and it is the part that does the work. Without it the file accumulates and you stop trusting it, which is the same failure mode as every abandoned task app.

Practical setup

Keep it in a synced folder so it is on your phone, and use a plain .txt or .md extension so any editor on any device can open it. Date-stamp completed items at the bottom rather than deleting them — a running log of what actually got done is surprisingly useful at review time and costs nothing to maintain.

Where this approach genuinely fails is shared work. Assignment, due-date notifications and dependency tracking across a team need a real tool, and a text file will not fake them. But for one person's week, the file is faster than anything you would pay for, and it never asks you to upgrade.

When to graduate from it

Two signals mean the file has done its job and should hand over. If you are tracking work that other people are waiting on and they cannot see it, the file has become a bottleneck rather than a system. And if the same item has moved forward four weeks running, the file is telling you something a tool would hide — that the task is not actually going to happen, and it belongs in Someday or in the bin.