Let’s start with a spreadsheet, one of the easiest ways to get real, good results from everything you set up in Parts 2 and 3. You describe your tasks once, and the sheet blends your priorities into a single, sorted answer for you. Open it, glance at the top, and there’s the short, deliberate set of tasks you should actually be working on right now.
A ready-made spreadsheet that scores and sorts your tasks for you.
That’s it. The top of that sorted list is your “hot list”, the tasks that you should be focusing on right now.
It works because a spreadsheet does the one thing your mind can’t: blend several judgments into one number, for hundreds of rows, instantly and identically every time. You don’t need to know the exact formula, the sheet runs it, but the logic is worth understanding, because the logic is the system.
Every task gets a score that answers “how much should this compete for my attention right now?” It’s built from the same two buckets you recorded in Part 3: how much the project matters, how much the task matters, and how much pressure is there to get it done soon.
Because the score blends your inputs rather than depending on any one of them, it forgives imperfect placement, which is the “close enough is good enough” promise from Parts 2 and 3. Drop a task under a roughly-right project and its score lands roughly right. But don’t mistake “forgiving” for “coarse.” The score isn’t just flagging the obvious extremes and shrugging at everything in the middle, it makes real distinctions across the whole list, so when two tasks are genuinely close, it still gives you a defensible order to work in. It helps most, in fact, exactly where your own judgment is weakest: the crowded middle ground, where everything feels equally urgent and you can’t see daylight between options.
The time-pressure part rides on top of the mattering part. A task with no due date contributes nothing here, it ranks purely on how much it matters, which is exactly right, an important but undated task should hold its place without a fake deadline propping it up. This is the cure for due date inflation from Part 1: you never again need to invent an early deadline to keep something visible, because importance keeps it visible on its own.
Real deadlines, though, assert themselves, and they do it with good timing. A task with a genuine due date starts to climb a few days out, gently at first. If nothing more important is in your way, it’ll surface early and you’ll get to it ahead of time. But if you’re busy, it keeps climbing, and by the day it’s actually due, it has risen to the top of your list. That’s the behavior you want: when a due task appears near the top, your reaction is “yes, that’s exactly what I should be working on,” not “can I snooze this another day?” This is also where Part 2’s promise finally pays off, the one about implementation intentions, where you supply the action and the system supplies the moment. You decided, back in Part 3, that a task matters and when it’s due. The score turns “when it’s due” into “here it is, now,” surfacing it at the right time without you having to remember to watch for it. And the moment something is genuinely due today or overdue, it rises above the merely-important work entirely, so a real deadline can’t get buried under things that just feel pressing.
The sheet also keeps what you can’t act on out of your way. A task that’s blocked, waiting on something unfinished, or not startable until a future date, stays down and out of sight until it’s actually ready. You’re never left wondering whether the thing at the top is something you can even start, if it’s there, it’s ready. That’s the dependency and start-date work from Part 3, doing its job so you don’t have to keep re-checking.
Here’s the truth about this spreadsheet: it’s genuinely good. I ran my own life on one for about a year while I was working the whole approach out, with over 200 tasks, and it really worked. The prioritization you get out of it is the real thing, not a proof of concept. If you build nothing else from this guide, a populated version of this sheet will put you ahead of almost everyone drowning in a flat to-do list. I want to be clear about that before I tell you where it falls short, because its shortcomings are not failures of logic, they’re just the ceiling of what a spreadsheet can be.
A spreadsheet is a brilliant grid for computing numbers, and we’ve bent it into a task manager, and it does that job well up to a point.
The one that finally wore me down was simple: it’s stuck on my computer. A spreadsheet doesn’t live in your pocket, at least not in a usable way. Out and about and want to see what tasks to work on now? You better have your computer open. For some that may not be an issue, but for me it was.
There are smaller limits too, and they’re all the same species: a spreadsheet can only bend so far. It generally caps you at two grouping levels, because deeper nesting turns the grid into a maintenance nightmare. It cleanly handles one tag per task, the moment a task needs two or three contexts at once, the columns get ugly.
And underneath all of it sits one limit that isn’t really the spreadsheet’s fault at all: it’s frozen between glances. It only knows what’s changed the moment you open it and let it recalculate. A deadline’s pressure genuinely rises as the day gets closer, but only when you’re looking, the sheet isn’t climbing in the background while you’re at lunch. Any system tells you the wrong thing if the truth changes and you don’t update it, that’s true of paper, of the sheet, of any app, and it’s on you to keep your data honest in all of them. But a spreadsheet takes this further than it needs to: even when your data is honest, the sheet still can’t act on it until you’re the one sitting in front of it. Those aren’t bugs to fix. They’re the edges of what a spreadsheet is.
Which is exactly why it’s worth having a version of this method that travels with you, one that doesn’t need a screen at all. That’s next.