Your to-do list is lying to you. Not about what needs to happen — but about what you're actually capable of holding.
Most founders I work with have a to-do list.
Many have several. A master list, a weekly list, a someday-maybe list, a Notion database with seventeen views, a voice memo from last Tuesday that starts with "okay so this is important—"
Here's the thing about to-do lists: adding to them is nearly frictionless. Removing from them requires a decision — and decisions have a cost that ADHD brains can't always afford.
The Stop/Kill List inverts the whole system. Instead of managing what you're going to do, you make a deliberate, explicit list of what you are actively stopping doing.
It sounds obvious. It is surprisingly difficult. And it may be the single highest-leverage productivity intervention available to a neurodivergent founder.
The Cognitive Load Problem
Working memory deficits are one of the most robustly documented features of ADHD — meta-analytic effect sizes of d=0.7–1.0 versus neurotypical controls (Martinussen et al., 2005). In practical terms: your brain is holding fewer things reliably than you think it is.
Every item on a to-do list is a low-grade background process. Even when you're not actively working on it, the brain knows it's there. It checks on it. It generates anxiety about it at 2am. It creates decision overhead every time you open the list and have to re-triage.
A list of 47 items is not a productivity system. It's a cognitive load tax that runs continuously, whether you're working from it or not.
The neurotypical productivity literature largely ignores this because working memory deficits aren't the norm for the audience it was written for. For ADHD founders, it's the central constraint.
Why Adding Is Instinctive and Subtracting Is Hard
Two forces make subtraction difficult for the neurodivergent founder specifically.
The first is the ADHD novelty drive. New ideas carry dopamine in a way that old commitments don't. Adding a new project to the list produces an immediate reward. Removing an old one requires confronting the loss — the project you won't finish, the idea you're releasing, the version of yourself that was going to do that thing.
The second is people-pleasing as a protective pattern. Many of the items on a founder's list were never really their priorities — they were absorbed from clients, co-founders, advisors, podcast episodes. Removing them feels like disappointing someone, even when that someone isn't watching.
If a part of you already feels resistance to this idea — the part that says "but what if that item is actually important?" — notice that. That's probably a Manager doing its job. The question isn't whether the items are important. It's whether carrying all of them is.
What a Stop/Kill List Actually Is
It is not a someday/maybe list. That's just a to-do list with a more honest name.
It is not a "parking lot." Items in parking lots never leave parking lots.
A Stop/Kill List is an active decision, documented: I am no longer doing this thing. Full stop.
Categories it captures:
- Projects you have started and will not finish (GitHub repos, course drafts, product features that haven't moved in 90 days)
- Commitments you said yes to and should not have
- Systems you built that you don't use
- Meetings that recur without producing decisions
- Aspirational habits that have never actually become habits
- SaaS tools you're paying for that serve a version of your workflow that no longer exists
Each item on this list is not a failure. It's a freed cognitive resource.
The Reducer Principle
This approach draws on what I call the Reducer Principle — inspired by Rick Rubin's creative methodology, not clinical research, and worth being transparent about that distinction.
Rubin's default in record production is subtraction: what can be removed and still have the essential thing remain? Every element that stays has to earn its place. The record that results is not the one with the most tracks — it's the one where nothing is wasted.
Applied to founder operations, the principle is: the default action is removal, not addition. Before any new commitment enters the system, something else must leave. Not as a trade — as a rule.
This isn't Rubin's idea dressed up as clinical advice. It's a practical heuristic with strong face validity for ADHD: fewer decisions, fewer context switches, lower background cognitive load. The mechanism aligns with what we know about executive function and inhibition deficits. It doesn't have its own RCT. It doesn't need one to be useful.
How to Build One in 15 Minutes
Open a blank document. Set a timer for 15 minutes — not Pomodoro-style, just a boundary.
- Write every project, commitment, and recurring task you're currently "holding" — including the ones you've been avoiding.
- Mark anything that hasn't moved in 60 days.
- Mark anything that was someone else's priority absorbed into yours.
- Mark anything that would require more capacity than you currently have to complete at acceptable quality.
- Move everything marked to the Stop/Kill List. Don't archive it. Kill it. Close the loop — cancel the tool, send the email, delete the repo.
What remains is your actual list.
It will be shorter than you expect. It will probably also feel lighter than you expect — and then slightly terrifying, because a short list removes the busyness buffer that was protecting you from the question: am I working on the right thing?
That question is worth sitting with.
The Rule Going Forward
Every new commitment requires removing an existing one.
Not a suggestion. A rule. The new opportunity goes in only when something comes out.
This feels constraining until you realize what it actually does: it forces a real prioritization decision at the moment of intake, rather than deferring it indefinitely to a future self who will also be overloaded.
The ADHD founder brain is particularly susceptible to Shiny Object Syndrome — 12 side projects, 0 shipped in the last six months. The Stop/Kill List is the structural intervention that addresses it directly. Not by suppressing curiosity, but by making the cost of new commitments visible in real time.
The Most Productive Thing You Did This Week
Might be what you stopped doing.
Not metaphorically. Literally. The SaaS tool you cancelled. The project you officially closed. The meeting you removed from the recurring calendar. The feature you killed before spending two more sprints on it.
Subtraction is not giving up. It's accurate triage.
In a system running on limited working memory, high task-switching costs, and a novelty drive that makes everything feel urgent — the most skilled operational move is often the one that takes things off the board.
What's on your list right now that you already know isn't going to happen?
Start there. Not with a plan to eventually get to it. With a decision to stop carrying it.
High Signal LLC | Educational content — not a substitute for therapy, psychiatric care, or formal clinical evaluation. Evidence references: Martinussen et al. (2005, Tier 1) · Barkley (2015, Tier 1) · Reducer Principle: creative methodology heuristic, not clinical research