Why Your Task List Is Lying to Your Face

The Part Where I Admit My To-Do List Was a Scam

Let me describe a thing I used to do. Every Sunday night I'd open a notes app — sometimes a physical notebook, sometimes a whiteboard, once a very optimistic spreadsheet — and I'd write down everything I needed to do that week. Development tickets. DoorDash schedule. Roblox asset updates. Dad stuff. Grocery run. That one email I'd been avoiding for eleven days. I'd look at the list, feel briefly in control of my life, and then go to bed.

Monday morning: I'd open the list, stare at it, and then do the three easiest things on it. Then I'd add two more things I'd already done just so I could cross them off. Then I'd feel tired and get another coffee. By Wednesday the list was basically a monument to my own avoidance. By Friday it was just a record of what didn't happen.

Here's what I had wrong: I thought a task list was a system. It is not. A task list is an inventory. An inventory tells you what's in the warehouse. It does not tell you in what order to pull things, in what quantities, or which loading dock to use. Treating a list like a system is like printing out a map of the city and calling it a route. You've got the information. You've done nothing with it.

The thing that actually works — and I mean actually, as in it survived contact with a full-time remote engineering job, two active side hustles, a kid, and a general resistance to being told what to do — is task batching. Not the inspirational poster version. The actual mechanism. Which is different, and kind of ugly, and that's exactly why it works.

How Task Batching Actually Works, Step by Step

Task batching is the practice of grouping tasks by the mental mode they require — not by project, not by urgency, not by the order you thought of them — and then doing all the tasks in one mode before switching to another mode. That's the whole thing. The reason it works is cognitive, not motivational.

Your brain doesn't switch contexts for free. Every time you go from writing code to answering a Slack message to updating a spreadsheet to recording a voice note, there's a switching cost — researchers call it an "attention residue," which is a fancy way of saying your brain is still half-thinking about the last thing while you're trying to start the next one. You're never fully in any task. You're buffering between all of them. I'm not tired. I'm buffering. I said it as a joke for two years before I realized it was literally true.

Batching works by eliminating that switching cost inside a block of time. Here's how it actually runs:

Step one: Audit your task list and tag every item with a mode, not a category. Modes are things like: Deep Focus (writing code, building something, creating), Admin (emails, invoices, scheduling), Low-Lift (order groceries, pay a bill, respond to a quick text), and Physical (the DoorDash shift, the errand run, anything that gets you out of the chair). Four modes. That's it. Don't invent more.

Step two: Block time on your calendar for each mode. Not for individual tasks — for the mode. A two-hour Deep Focus block. A 30-minute Admin block. You're scheduling the mental state, not the item.

Step three: When a block opens, you pull every task tagged to that mode and you work through them consecutively without switching. The list becomes a queue, not a menu.

Step four: Anything that arrives mid-block gets tagged and dropped into the next appropriate block. It does not jump the queue. This is the step people skip, and it's the whole game.

One Week, Real Numbers, No Flattering Edits

Here's what an actual week looked like after I ran this for real. I had three active tracks: a sprint at my day job (two features in progress), a DoorDash schedule I was trying to optimize around peak pay windows, and a Roblox project where I was behind on scripting a new game mechanic a kid in a Discord server had been asking about for a month. Plus the usual domestic chaos.

Old method, the week before: I logged roughly 52 hours of "working" across all of it. I shipped one of the two features, missed two peak DoorDash windows because I was mid-code when they opened, and didn't touch the Roblox script at all. I crossed 14 things off a list that had 31 items on it. The 17 undone items rolled forward and became the psychological weight I carried into the next week.

Batching method, the following week: I tagged everything. Deep Focus got 9 items — both features, the Roblox mechanic, a side project doc I'd been avoiding. Admin got 11 items. Low-Lift got 8. Physical got 5 (DoorDash blocks, specifically the Friday and Saturday evening windows I'd calculated were highest yield per hour in my zone).

I blocked two Deep Focus slots per day, 90 minutes each, mornings. One 30-minute Admin block mid-afternoon. Low-Lift lived in the gaps. Physical was pre-scheduled and locked.

Total logged hours that week: 49. Three hours less. I shipped both features. Hit both peak DoorDash windows — $118 combined, up from $61 the prior week on more hours. Finished the Roblox mechanic. Cleared 26 of 28 tagged tasks. The two that didn't get done were correctly deprioritized, not dropped by accident.

It's not pretty. The blocks don't always go clean. But the number doesn't lie: same life, three fewer hours, more output. That's the mechanism doing its job.

Where This Falls Apart and Who Gets Caught

I want to be straight with you here, because Post the Ls too is not just a catchphrase I put on a mug. Batching breaks in specific ways and I've hit most of them personally.

It breaks when your modes are wrong. I spent three weeks wondering why my Admin blocks felt as draining as Deep Focus blocks. Turned out I'd been tagging "write a project proposal" as Admin because it involved email. It's not Admin. It's Deep Focus with a Send button at the end. If you tag wrong, you batch wrong, and you end up stacking cognitively heavy tasks into a block that was supposed to be low-resistance. You just rebuilt the problem with extra steps.

It breaks for people with reactive jobs. If your work genuinely requires you to be on-call — customer support, anything with a live production system, parenting a toddler — the "don't interrupt the block" rule is a fantasy. I have a kid. Some mornings the block lasts eleven minutes. You have to build a shorter, more realistic version: 45-minute blocks instead of 90, with explicit interrupt windows between them. Smaller batches still beat no batches. But pretending you have the kind of schedule that allows unbroken 90-minute focus when you don't will just make you feel like you're failing at the system instead of recognizing the system needs to fit your actual life.

It breaks when you use it to avoid the hard thing. Deep Focus blocks have a magnetic pull toward the second-hardest task on the list. The hardest one is right there, tagged correctly, in the queue — and somehow you find a reason to do the one below it first. Batching removes the switching cost. It does not remove the instinct to avoid. That part's still on you.

How to Actually Use This Starting Tomorrow

I'm not going to hand you a template. You'll tweak it once, feel clever, and never open it again. Instead, here's the minimum viable version that works before you've had your second coffee.

Tonight — not this weekend, tonight — open whatever list you're currently ignoring and tag every item with one of the four modes: Deep Focus, Admin, Low-Lift, Physical. Don't overthink it. If you're unsure between two modes, pick the one that requires more mental energy. You can recalibrate after a week.

Tomorrow morning, before you open email or Slack or anything with a notification badge, block two 90-minute slots on your calendar. Label them Deep Focus. These are not meetings. They are not flexible. They are the most important infrastructure your day has. If 90 minutes feels impossible, do 60. If 60 feels impossible, do 45 and be honest with yourself about why.

Build one Admin block in the afternoon. 30 minutes. Pull every Admin-tagged item and run through them in sequence. Do not check email outside this block if you can help it. I know that sounds unhinged. Try it for three days before you decide it doesn't work.

The one insight I want you to walk away with — the thing that actually changed how I work — is this: urgency and cognitive weight are not the same thing, and your task list cannot tell the difference between them. A mode-based batch system is the mechanism that separates them. Once you can see your week as a sequence of mental states instead of a pile of items, the pile stops feeling like it's winning.

One more coffee and I'll pretend I've got this. You probably will too.