The Anti-Backlog

The first time I wrote an anti-backlog, it was because I couldn’t sleep.

I was lying there doing the familiar midnight math: if I wake up early, and skip breakfast, and answer messages while walking… — bargaining with reality like it might accept store credit.

On my desk was a “to do” list that had stopped being a tool and become a character witness. Every unchecked item felt like evidence: lazy, scattered, unserious. The list wasn’t measuring work anymore. It was measuring worth.

So I did something that looked, at first, like giving up:

I wrote a list called Not Doing.

Not as a tantrum. Not as a cope. As a design decision.

It worked because it made one thing explicit that backlogs keep implicit:

Every “yes” is made of hidden “no.”

If you don’t name the “no,” you live inside it anyway — as guilt, as delay, as vague dread, as the sense that you’re always behind a version of yourself who is better at being alive.

This is the anti-backlog: a way to prune commitments without turning the pruning into a story about who you are.

What a backlog becomes when you’re tired

A backlog is supposed to help you remember what matters.

But when you have too many open loops, a backlog starts doing three quiet things:

1. It pretends the future is available.
   It acts like next week has infinite attention, energy, money, and clean mornings.

2. It turns desire into debt.
   Things you genuinely want become things you are failing to do.

3. It makes “later” into a hiding place.
   You don’t decide. You postpone deciding. The backlog becomes a parking lot for identity.

You can feel the shift when your list stops helping you do things and starts helping you avoid choosing.

The anti-backlog is for that moment.

The anti-backlog (definition)

An anti-backlog is a short document that answers three questions:

• What am I not doing right now?
• Why am I not doing it?
• What would make it true again? (re-entry conditions)

It’s a commitment prune that treats reality as a first-class input — and treats shame as noise.

The five-move method

You can do this in 30 minutes. You can also do it slowly over a week. The key is to write it down.

Move 1: Inventory the open loops (without solving them)

Make one list of everything that’s currently “floating”:

• projects
• side quests
• obligations you’ve half-agreed to
• habits you feel guilty about not maintaining
• messages you owe
• “I should” items that show up whenever you rest

Don’t triage yet. This is just making the invisible visible.

If you’re flooded, cap the list at 30 items. You can do another pass later.

Move 2: Label each item by its hook

Most stuck commitments aren’t stuck because they’re hard. They’re stuck because of what they mean.

Add a single label (just one) next to each item:

• Care (I genuinely care about the outcome)
• Fear (I’m avoiding consequences or disapproval)
• Identity (this is who I think I’m supposed to be)
• Fantasy (this is a “future me” project)
• Debt (I owe someone something concrete)

If you can’t label it, it’s probably a fantasy disguised as identity.

Move 3: Decide your “capacity truth” for the next 2–4 weeks

Pick a window. Two weeks is honest. Four weeks is sometimes realistic. Twelve weeks is usually a novel.

Write a sentence that names your capacity without arguing with it:

For the next 3 weeks, I have capacity for 2 deep projects, 1 maintenance stream, and 1 relationship repair.

Or:

For the next month, I’m in recovery mode; my only non-negotiables are sleep, money stability, and one meaningful connection.

This is the anchor point. Without it, you’ll try to prune using willpower, which is how you end up back in midnight bargaining.

Move 4: Write the anti-backlog as “not now” statements

Create a second list titled Not Doing (until further notice).

For each item you are dropping or pausing, write it in this format:

• Not doing: X
  Because: Y
  Re-entry: Z

Examples:

• Not doing: “Launch the new site redesign”
  Because: I can’t do it without rushing; rushing makes me resent my own work.
  Re-entry: I have 2 uninterrupted afternoons per week for 4 weeks and someone else owns support/admin.

• Not doing: “Weekly content cadence”
  Because: I’m using writing to perform stability instead of building it.
  Re-entry: I’m sleeping 6+ nights/week and writing feels like relief, not repayment.

• Not doing: “Catch up with everyone I’m behind with”
  Because: bulk repair turns people into tasks.
  Re-entry: I can do 2 reach-outs per week with full attention.

This is the heart of it: you’re not “failing.” You’re choosing.

Move 5: Do the two hard communications

The anti-backlog fails when it stays private.

There are two audiences you usually need to update:

1. Your future self (so you don’t re-add the item at 1 a.m.)
2. Other humans (so they aren’t living inside your silent delay)

Here are two scripts I use.

Script A: Dropping a commitment cleanly

Hey — I want to be honest about capacity. I’m not going to be able to take this on / follow through in the timeframe I implied.

I’m sorry for the drag. If it helps, I can either (1) hand off what I have so far, or (2) explicitly pause this until DATE and revisit then.

Which would be more useful?

Script B: Pausing without disappearing

Quick heads-up: I’m in a reduced-capacity season. I’m pausing a bunch of non-essentials for the next 2–4 weeks so I can stabilize.

I’m not ignoring you — I’m choosing fewer threads on purpose. If something becomes urgent, tell me directly and I’ll re-evaluate.

This is not about being perfectly liked. It’s about leaving fewer people (including you) stuck in ambiguity.

A note about “re-entry conditions”

Re-entry conditions are what stop your anti-backlog from becoming avoidance.

They should be:

• observable (time blocks, money, sleep, support)
• non-moral (not “when I’m a better person”)
• tight (one or two conditions, not a thesis)

This keeps you honest:

• If the conditions arrive, you can restart without drama.
• If they don’t, you can keep it dropped without guilt.

What this looks like in practice (a small scene)

A friend once showed me their task manager like someone showing a wound.

Thousands of items. Some from 2019. A recurring habit to “drink water” that had been skipped so many times it felt like an accusation.

They said, quietly: “If I delete it, it means I’m the kind of person who gives up.”

So we didn’t delete anything.

We wrote an anti-backlog on paper — ten items, just ten — and the first one was:

• Not doing: “Trying to become a person who keeps perfect lists”
  Because: the list has become a judge.
  Re-entry: when the list feels like a tool again, not a trial.

They laughed, and then they cried, and then their shoulders dropped like something unclenched. Not because they found the perfect system. Because they stopped trying to earn the right to exist by keeping their internal dashboard green.

That’s the point.

The anti-backlog isn’t productivity advice. It’s an agency practice.

It’s you saying: I will not let an overfull list decide my life by default.

One last rule

If you write an anti-backlog, you must also write one positive line underneath it:

This is what I am doing instead.

Otherwise “not doing” becomes a void, and the void gets filled with scrolling and shame.

Pick one or two things. Name them. Put dates on them if you can.

And then let the rest be truly not-now — not a secret debt you carry around like a second spine.