Due by five? Do by Five.
A way of keeping a to-do list. Five headings. Three line types. Start at the top; position is priority.
Only these five headings, and always in this order:
Under the headings are the lines. Each is one of three, and whether a line is about now or about later makes no difference to its type:
A Do by Five list describes getting from now to done.
Practice two habits with this method: capture your project ideas as small lines, and position each one according to priority.
In practice the list is a text file written in
Markdown, a
todo.md kept with the project; in a repository, at the root and committed to source control. Markdown already has headings, bullets, and checkboxes; Do by Five adds meaning: which heading a line sits under, and what its first characters say it is. The precise details are spelled out below. The name
todo.md is convention, not a rule;
tasks.md or
next.md works as well. The five headings are what matters.
Each heading is a level-two Markdown heading:
## Blockers, ## Critical, ## Normal,
## Backlog,
## Notes, in that order. Above them goes the “Done when” statement: one sentence saying what done means for the current
effort period, the end of the period included. A
# with the project’s title may sit above it; the title is optional. Any other context about the project is a statement under Notes. Under each heading, the lines are written as:
| Line | Form |
|---|---|
| Question | * ? {question} |
| Statement | * {statement} |
| Action |
- [ ] {action}- {action}
|
The opening characters are the whole form:
* ? for a question, * for a statement,
- for an action. Questions and statements start with
*, so one glance tells information from work.
A question needn’t end in a
? according to this format.
An action takes a box,
- [ ], or goes without one; both parse as actions to Do by Five. Once an action is completed, delete it or mark it
- [x] {action}.
In most Markdown previews a
* and a bare
- both appear as plain bullets, while
- [ ] draws a checkbox. Do by Five allows
- as action shorthand because it is quick to type. So if the list is mostly read as a preview rather than as source, use
- [ ] for actions.
Anything else under a heading–a sentence of context, a table, a code block, a quote–is fine, but it isn’t a line. It is the owned block of the line above it: everything from the end of that line to the start of the next line or heading, blank lines included, belongs to that line and should move, copy and delete with it. Indentation makes no difference; Markdown attaches content to a list item by indenting it, Do by Five by position alone.
Of course, the idea of five headings and three line types works just about anywhere: a note on a phone, a Google Doc, a paper notebook. So you’re not limited to Markdown to exercise these structured habits. For this reason there are templates for popular apps, pages for writing by hand, and snippets that type the headings.
Five fits on one hand: the thumb, the strongest finger, is Blockers, and the pinky, the weakest, is Notes. Hold up a hand and there is the whole list. Five headings, no more and no fewer. Every line goes under one of them, and its priority decides which. Never invent a sixth; a line that fits nowhere else goes under Notes.
An example project, in one effort period: now to launch day. Position is priority; start at the top.
# Northwind Coffee rebrand Done when the new logo is live on the website and in the press kit on launch day, Oct 10. ## Blockers - [ ] Hear back from Northwind on logo B or C Sent both on Oct 1. They said end of the week. ## Critical - [ ] Swap the logo in the site header - [ ] Replace the logo download on the press-kit page ## Normal - [ ] Update the email signature - [x] Make the new browser-tab icon - [ ] Dana: update the LinkedIn page ## Backlog - [ ] Add an animated logo for the loading screen * ? Is the tagline changing too, or just the mark ## Notes * Dana owns print and social; I own web and email * Northwind prefers the warm palette (Sep 29 call) | Use | Color | |------|---------| | Logo | #B5451B | | Type | #2B2620 |
When do items move?
Every time the list is opened. Up when something got more urgent, down when it didn’t. Backlog to Normal once it is meant for the current effort period. Normal to Critical once success can’t be claimed without it. Anything to Blockers the moment it blocks progress. And back down the moment that stops being true. When an effort period ends, done is stated again for the next one, and every line is placed by the new definition.
Blockers or Critical?
Critical is what must be addressed in the current effort period before success can be claimed. A blocker is whatever must be addressed before any line under the other four headings, a question, a statement or an action, and it sits under Blockers only while that is true. A question the work can go on without belongs under whatever heading its priority gives it; the moment it holds everything up, it moves to Blockers. While Blockers has a line, nothing under the other headings moves, so a line goes there only if it deserves all of the focus first. Use Blockers sparingly and wisely. Blockers don’t block each other; chase them in any order, or help clear them. When it clears, delete the line and write the work it made under the heading it deserves: “Hear back from Northwind on logo B or C” becomes “Swap logo C into the site header” under Critical.
Everything feels Critical.
Usually the lines are too big. “Open the second location” is critical, and it’s also fifty actions. Split it, and most of the pieces turn out to be Normal. Then ask of each Critical line: if this were left when the effort period ends, could success still be claimed? If so, demote it.
The project is in Git.
todo.md lives at the root beside the README and gets committed like any other file. Git and Markdown are already in the daily workflow, so there is no new tool to learn. And because the list is in the repository, it flows with the project to every team member; it communicates itself. Tick a line in the same commit as the work it names, so the history tells one story, and
git log -p todo.md becomes a record of what mattered when. A list of single lines rarely conflicts on merge; when two people reorder the same heading, keep both sets of lines and put them back in order.
Does it work for a team?
One list per project. It belongs to the project, not a person, and lives where the team works: the repo, the project doc, the pinned ticket. Do by Five defines basic list rules, so anyone can read the priority without asking, because position says it. The details of managing a shared list are for the team to work out.
I already use Jira, Asana, Trello, or GitHub Issues.
Keep it. The tickets stay there. The list sits beside it, in the project doc or a pinned issue, and answers the one question a board of forty cards doesn’t: what’s next. A tool with sections can hold the five headings inside it.
Normal has forty lines.
Then it’s a pile again. Normal is for work meant for the current effort period; the rest drops to Backlog, which can be as long as it likes. It’s the heading read least and pruned rarely.
I have six projects.
Six lists, one per project. The morning starts with the top of each one, and the top is short on purpose: Blockers and Critical, rarely more than a screen. Work that belongs to no client, invoices, renewals, leads, gets a list of its own. Then read the six tops side by side and decide which line comes first across all of them.
Is this that different?
Do by Five describes in one specific way how to implement common-sense strategies that people are already familiar with and using on a daily basis. Because systems of organization are highly personalized, it may not stick for you. If it does, though, that’s great!
Aaron Klump builds web applications at In the Loft Studios, specializing in Drupal. Do by Five is how he keeps his own projects straight. Write to him at aaron@intheloftstudios.com.
The five headings, blank, in whatever format the work lives in.
Google Tasks, Apple Reminders, any plain list. An emoji marks each heading.
Word, Pages, Google Docs.
Excel (2021 or later) and Numbers. A zip: the spreadsheet and a README.
Fillable, or print it blank.
For a pen, on a tablet or on paper. Rows can’t move there, so a number beside a line sets its priority. Each zip holds the pages, a filled-in example and a README.
Pages sized for the reMarkable 2, the Paper Pro and the Paper Pro Move. Import the PDF as a document.
US Letter, US Legal, A4, A5 and B5, with a margin for the hole punch. Print at actual size.
For the editor or text expander already at hand:
Alfred,
Raycast,
Espanso,
VS Code, or a
JetBrains IDE. Type
;;todo and “Done when” and the five headings appear;
;;do starts an action line. Change the keywords to taste.
Double-click to import. Snippets need the Powerpack.
Run Import Snippets and choose the file.
Drop it in the match folder. Mac, Windows, Linux.
Drop it in the user snippets folder. Type
todo, then Ctrl+Space.
PhpStorm,
IntelliJ,
WebStorm. File › Manage IDE Settings › Import Settings. Type
todo, then Tab.
For a Markdown previewer. Draws a
todo.md as Do by Five structures it: five sections, a checkbox per action, a highlight on an open question.
A Custom Processor and style for Brett Terpstra’s Markdown previewer. Unzip and see the included README; setup differs between Marked 2 and 3.
For working several lists at once.
In active development. It will be a paid app. Reads several existing
todo.md files and shows them as one Do by Five list; reorder, check off, add, edit, or delete a line, and the change is written to the file it came from. Each file stays where it is, in its own repository, and remains the source of truth: the app never moves or copies it, and any text editor still edits it.
Ask for a note at launch.