The relapse nobody warns you about
You clear the pile. It feels like a genuine win, because it is one: an hour of sorting, a bag for the bin, a folder for the paperwork, a surface you can see again. Then, within days, a new pile starts in the same spot. Not the same items. A new pile, made of new things, growing at roughly the same rate as the old one did.
This is treated as a personal failing, evidence that the clearing 'didn't take.' It isn't that. It's evidence that clearing a pile and preventing one are two different skills, and most advice only teaches the first. Sorting technique gets all the attention. What gets almost none is the question of why a surface accumulates in the first place, which has nothing to do with sorting and everything to do with what happens the moment before an item gets put down.
What a surface is actually doing
A pile-prone surface isn't neutral. It's doing a job, even though nobody assigned it one. It's absorbing every item that arrives without an immediate decision attached — the letter you haven't opened, the receipt you might need, the thing you're mid-way through using. Each item lands there because putting it down was faster than deciding what it was or where it belonged. That's not laziness. Deciding takes working memory, and working memory is exactly the resource that's already stretched thin by the rest of the day. Executive-function difficulties, including trouble holding several open decisions at once, are common in ADHD, and a flat surface asks for none of that. It just takes the thing.
So the surface becomes a decision deferred, repeated hundreds of times. That's why clearing it once changes nothing about tomorrow: the deferral mechanism is still fully intact and waiting for the next item that arrives without a clear home.
Piles are a symptom of missing addresses
Every item that lands on a surface instead of somewhere specific is an item without an address. Not a category — an address. Categories tell you what kind of thing something is. An address tells you exactly where it lives when it's not in use, and exactly where your hand goes to put it there without thinking. Most households have plenty of categories and almost no addresses, which is why sorting works for an afternoon and then stops working the moment life speeds back up.
The fix isn't more categories. It's picking, in advance, one specific spot for the handful of item types that land on that surface most often — post, keys, the thing you're using this week — so that putting something down correctly takes exactly as little effort as putting it down carelessly. If the correct action and the lazy action require the same amount of thought, the correct one usually wins by default, because the surface never gets a chance to become a container for indecision.
The next action has to survive being put down
There's a second failure point that has nothing to do with where things go: the moment something is genuinely unfinished. A form partly filled in, a task interrupted, a project waiting on one more piece of information. These items get put down mid-task, and the pile grows around them because putting something down loses the thread of what happens next. By the time you return to it, the next action isn't visible anymore. You have to reconstruct it, and reconstruction is expensive enough that the item often gets put down again, unresolved, for longer.
An item that's mid-task needs its next action written on it, or beside it, in a form visible without having to reopen the whole thing. Not a full plan — one line. What has to happen next, and roughly when. This does more to prevent a pile than any sorting method, because it removes the reconstruction cost that makes revisiting the item feel worse than avoiding it.
Where unfinished things are allowed to wait
Some items genuinely aren't finished and can't be dealt with today. Pretending every item can be resolved on contact is unrealistic and sets the whole system up to fail by its own standard. What actually helps is deciding, once, where unfinished items are allowed to wait — a single named spot, visible, with a rough limit on how much it can hold before it gets reviewed. This is different from a pile because a pile has no boundary and no review point. A holding spot has both.
The difference matters because a boundary turns an invisible habit into a visible one. When the holding spot is full, that's information, not failure. It tells you the review is overdue, which is a concrete, small task, rather than a vague sense that things have got away from you again.
What actually changes the pattern
None of this removes the need for occasional sorting. It changes what sorting is for. Sorting clears what's already accumulated. Addresses, visible next actions, and a bounded holding spot are what stop the next batch from accumulating in the same way. Skip that part and you'll be sorting the same surface on the same schedule indefinitely, wondering why the win from three weeks ago didn't last.
If piles are one part of a much wider pattern of unfinished tasks, missed deadlines, or growing overwhelm that isn't shifting with practical changes, that's worth raising with a GP or a qualified clinician, rather than treating it as something a better system alone should solve.