What Actually Tires You Out Is the Thinking You Keep Deferring

"What wears people out is not just information overload, but deferred thinking. Every saved link feels harmless in the moment, but over time it turns into a growing pile of 'I should engage with this later.' That pile is mentally expensive even before you read a single thing."

That is from someone on r/PKMS, and it names something most save-it-later advice misses entirely. The usual story is that you have too much stuff. Too many tabs, too many bookmarks, too many screenshots. So the usual fix is to cut down, clean out, declare bankruptcy on the list and start fresh. But that framing gets the weight wrong. The thing pressing on you is not the volume of items. It is the stack of small unmade decisions sitting underneath them. Every saved link is a thought you started and then set down: I should read this, I should reply to this, I should decide what to do with this. The reading never happens, so the decision never closes, so it just stays open in the back of your mind, quietly costing you.

This piece is about that hidden cost. Why a pile of saved things tires you out before you have read a word of it, why your brain is genuinely bad at holding all those open loops, and how to set things up so saving stops feeling like deferring.

The pile is heavy before you read it

Notice the order of operations in the quote. The exhaustion comes first, the reading comes never. You feel the weight of the list while every item in it is still unread. That is the part that does not fit the information-overload story, because there is no information getting into your head. Nothing has been processed. And yet it is tiring.

The reason is that each saved item is not really an item. It is a held thought. When you bookmark an article, you are not storing the article, you are storing a tiny promise to yourself: I will come back and think about this. You have opened a loop and left it open. One open loop is nothing. A few hundred of them, accumulated across bookmarks and tabs and a camera roll full of screenshots, is a low background hum of unfinished business that never goes quiet, because none of those loops ever get the five minutes that would close them.

So the pile is expensive in exactly the way the quote says: before you read a single thing. The cost is not in the content you are behind on. It is in the dozens of decisions you have postponed and the part of your attention that keeps them faintly alive.

Your brain was never built to hold the backlog

There is a hard biological reason this gets heavy so fast. Working memory, the mental workspace where you actually hold and juggle things, is tiny. For years the rule of thumb was the famous seven, plus or minus two. The careful research revised it down sharply. Reviewing decades of evidence, psychologist Nelson Cowan found that the real limit for things you can hold in mind at once is closer to four, somewhere in the range of three to five (Cowan, 2001, Behavioral and Brain Sciences).

Four. That is the working capacity you are trying to manage a backlog of hundreds against. Your mind cannot hold the open loops, so it does the only thing it can: it keeps a vague, anxious awareness that the loops exist, somewhere, unresolved. You do not remember the 300 specific things you meant to get to. You just carry the steady sense that there are 300 things you meant to get to. That diffuse pressure is what the backlog actually feels like from the inside, and it is the direct result of asking a four-slot system to track an unbounded list.

This is why willpower never fixes it. You cannot discipline your way past a structural limit. The brain is not failing to organise the pile. It was never able to hold it in the first place. What it needs is somewhere outside itself to put those open loops, so it can stop spending attention keeping them faintly alive.

Deferring is fine. The trap is deferring with no way back

Here is the part worth being honest about: deferring is not the problem. Setting something aside to deal with later is a completely reasonable thing to do. You genuinely do not have time to read the long piece right now. You should save it and move on. The trap is not the saving. The trap is saving into a place that gives you no way to actually come back, so later never arrives and the loop never closes.

Think about what closing a loop requires. You either deal with the thing, or you decide it does not matter and let it go. Both of those need the thing to come back to you at a moment when you can act on it. A bookmark cannot do that. It sits in a list, waiting for you to remember it exists, find it among hundreds, and recognise it from a truncated title. That is more work than you had when you saved it, so you do not do it. The loop stays open not because you are lazy but because the tool never hands the thing back. You deferred, and the system quietly turned defer into never.

That is the real failure mode behind every graveyard of saved links. Not that people save too much. That they save into places that only take things in and never give them back. The decision you postponed had nowhere to land, so it stayed in your head, where it is heaviest.

A place that hands things back closes the loop for you

The fix is not to stop saving and it is not to finally read everything. It is to save into something that returns things to you, so deferring actually ends in a decision instead of a permanent open loop.

That is the shape dEssence is built around. You save anything from anywhere, a link, a screenshot, a PDF, a voice note, forwarded from Telegram or your browser or the web app, with no folder to choose and no decision to make on the way in. The point is that capturing should cost nothing, because the open loop is the expensive part, not the click.

Then, instead of the saved thing waiting in a list you never reopen, it comes back. You can ask for it in plain language whenever the topic returns, describing the moment rather than recalling the title, and dEssence brings it up on its own when it becomes relevant again. That is what turns deferring back into a real decision. When the thing actually reappears at a usable moment, you finally do the small thing the loop was waiting for: read it, use it, or decide it does not matter and let it go. Either way the loop closes, and your attention gets to stop holding it. It also works wherever you already think, so you can pull a saved thing straight into a chat with ChatGPT, Claude, or Gemini without going to dig for it first.

What lifts when the loops can close

When saving stops meaning deferring, the pile stops being a pile. You can capture as freely as you already do without each save quietly adding to the weight, because nothing you save is stranded anymore. The thing you set aside comes back when it is useful, you act on it or release it, and the open loop ends.

That is the shift worth aiming for. Not a smaller list. Not a heroic afternoon of finally reading everything. Just a setup where deferring is allowed to be temporary, where the four slots in your head are not being asked to track three hundred unfinished thoughts, and where the weight you have been carrying around since long before you read anything finally has somewhere to go.

FAQ

Why does a pile of unread saves feel tiring when I have not read any of it? Because the cost is not in the content, it is in the open decisions. Each saved item is a small thought you started and never closed. Your working memory can only hold about four things at once, so the rest sit as a vague, ongoing pressure, which is tiring even though nothing has been read.

So I should just stop saving things? No. Deferring is reasonable. The problem is saving into a place that never hands things back, so later never comes. Saving into something that returns things to you keeps the convenience of deferring without leaving the loop open forever.

How does this actually close the loop? The saved thing comes back to you, either when you ask for it in plain language or when it becomes relevant again on its own. At that point you can finally act on it or let it go, which is the decision the open loop was waiting on.