Skip to main content

Insights

The Cost of Keeping Too Many Decisions Open

A finished task and a closed decision are not the same thing — and only one of them stops costing you attention

Summary: Unfinished work is a time cost: it sits inert until you touch it again. An unresolved decision is an attention cost: it keeps resurfacing whether you're working on it or not. This article uses a founder's five-item 'done' list to show how a task can ship while the decision underneath it stays open, why reorganizing that list never closes the decision, and how to find and close the specific question that's still live.

By Stanislav Trifan · Published

Two kinds of debt sit on every founder’s plate, and most people only track one of them.

Unfinished work is the debt everyone can see. It lives on a board, in a backlog, on a list titled “to do.” It is patient. A half-built onboarding flow does not get more expensive while you sleep — it costs nothing until you sit back down and touch it again. Time debt is inert; stop paying attention to it, and it stops charging you.

An unresolved decision does not behave the same way, and almost nobody tracks it as its own category. It doesn’t wait for you to schedule it. It resurfaces on its own — a half-formed thought at eleven at night, a flicker of wait, did we ever actually decide that? mid-conversation, a small flinch when a metric moves and you realize no one agreed what that metric was supposed to prove. You can stop working on a task and pay nothing more for it. You cannot stop deciding on something — an open decision keeps billing you whether or not you’re touching the work it’s attached to.

That’s the paradox worth taking seriously. People who are visibly productive — shipping every week, closing tasks on schedule — can still feel their attention leaking out through holes they can’t point to. This isn’t the familiar trap of not being able to start something, and it isn’t one task quietly refusing to move. Here, everything is technically moving. The cost is in what’s still open underneath the things that already shipped.

A list that looks finished

Picture a founder five weeks into launch. Their list looks clean — five items, all checked or actively in motion:

  • Pricing is live on the page.
  • The onboarding flow ships to every new signup.
  • The first article is published.
  • A retention dashboard is running.
  • Early-user outreach messages have gone out.

On paper, this is a strong week. Every item took real effort and produced something real. And every one of them is quietly still open, because a task list tracks whether the visible work happened — not whether the decision underneath it ever got made.

Pricing. A number sits on the page, but the real decision — who this price is meant to exclude, and whether that trade-off is one you’re actually at peace with — was never made. It was defaulted: competitors charge around this, so we will too. Every future pricing conversation reopens the same argument, because there’s no decided position to point back to. Only a number that happened.

Onboarding. The flow ships, and new users move through it. But nobody decided what a first-time user has to feel by the end of it — confident enough to return, or merely unconfused enough not to leave. Every future tweak re-litigates this from scratch, because there’s no answer on file for what “good” means here.

The first article. It’s published, and that felt like the finish line. But who it’s actually for, and what it’s supposed to earn — trust, signups, nothing measurable at all — was skipped in favor of shipping something. So the next piece of content reopens the exact same unresolved question the first one never answered.

Retention. A dashboard exists, full of numbers. But which single number counts as “working” was never chosen. So every dip in any metric triggers a fresh, unstructured debate about whether things are actually fine, because there’s no prior decision to check the dip against.

Early-user outreach. Messages go out, replies come in. But what happens after someone replies — who follows up, with what, by when — was never assigned. So each reply becomes its own small, un-owned decision, made from scratch, usually under time pressure, by whoever happens to see it first.

Five different areas of a young business. The same shape underneath each one: a task that looks finished, sitting on top of a decision that was never closed — only outrun by the task that shipped in spite of it.

Why the list is clean and the mind isn’t

None of these five items are unusually hard decisions. That’s the point. What makes them expensive isn’t difficulty — it’s that they stayed open. Five forces keep a decision “open” long after its related task has moved on:

Open loops. A decision left dangling behaves like unfinished business the mind won’t stop monitoring, independent of whether any task is currently blocked on it. Klinger’s classic work on “current concerns” (1975) gives this a precise shape: a commitment stays live — actively organizing what you notice and think about — from the moment you take it on until you resolve it or deliberately disengage from it. Nothing in between counts. Shipping the related task isn’t on that list.

Hidden dependencies. The pricing decision looks self-contained, but it silently gates the onboarding copy, the retention story, and outreach framing — three other open threads nobody has mapped back to the one unmade call underneath them.

Competing priorities. None of these five decisions was ever rejected. Each was just outranked “for now,” which keeps it alive and re-litigable instead of closed. A decision still eligible to win an argument is a decision that hasn’t ended.

Ambiguous ownership. Nobody is unambiguously responsible for closing any of these. In a small team that means the founder holds all five at once, each one drifting rather than landing on someone who can end it.

Mental load. Each open decision has to be held in working memory just enough to resurface at the right (or worst) moment — a holding cost paid continuously, not only while the decision is being actively worked. Masicampo and Baumeister (2011) ran six studies on exactly this and found that unfulfilled goals produce measurable cognitive costs even while people are doing something unrelated — intrusive thoughts during an unconnected reading task, worse performance on an unrelated puzzle. The critical finding: simply making a specific plan for the unresolved goal — not completing it, just deciding when and how — eliminated the effect. What turns off the billing is not finishing the work. It’s resolving the open question.

Leroy’s research on “attention residue” (2009) shows the mechanism by which this leaks sideways: moving from an unresolved task to the next one leaves part of your attention measurably behind, degrading performance on whatever comes next. An open decision doesn’t stay contained inside the item it belongs to — it follows you into the next meeting.

Why reorganizing the list doesn’t close anything

It’s tempting to think the fix is a better list — cleaner columns, sharper labels, a status field for “blocked” versus “in progress.” None of that touches the actual decision.

A 2025 meta-analysis by Ghibellini and Meier, reviewing 59 studies of interrupted and unfinished tasks, is useful here for what it rules out. The often-repeated claim that unfinished tasks lodge themselves in memory better than finished ones doesn’t hold up reliably across the literature. What does replicate is narrower: people feel a pull to resume an interrupted activity when given the chance — the Ovsiankina effect. But that pull is about unfinished work. Our founder’s five items aren’t unfinished work; the tasks shipped. There’s nothing left to resume. What’s still open is a question, not an activity — which is exactly why “get back to it” doesn’t fix any of the five items above. There’s only something that was never decided.

It’s also worth ruling out a different intuition: that the problem is simply having too many open items to weigh, and trimming the list would help. A large meta-analysis of choice-overload research (Scheibehenne, Greifeneder, and Todd, 2010, across 50 experiments) found the effect of having more options on decision quality is close to zero. So the fix isn’t fewer decisions to pick from. It’s fewer decisions left open. Volume was never the problem; unresolved status was.

A task list has a field for “done.” It has no field for “decided” versus “defaulted.” Moving “pricing” into a done column changes the label, not the answer underneath it — so the mind keeps treating it as a live current concern, because, by Klinger’s definition, it still is one.

How Pergunta.me applies this

Marking a task “done” and closing the decision behind it are treated as two separate events, not one. When a step ships, Pergunta.me keeps the open question attached and visible instead of letting the task-list label absorb it — so a shipped task can no longer quietly stand in for a decision nobody actually made.

A practical way to find the blocking question

Here is a short test you can run against anything on your own “done” list this week.

  1. Pick one item you’d call finished. Something shipped, checked off, or moved to the next stage.
  2. Say the decision behind it out loud, in one sentence, with a name and a date attached. We decided X, [owner] owns it, we revisit on [date]. If you can say that without inventing it on the spot, the decision is genuinely closed.
  3. If you can’t, close it on purpose. Decide it now, defer it visibly with a named owner and a real date, or actively drop it. The one move that doesn’t work is doing nothing — that leaves the decision exactly where Klinger’s research says it will sit: a live current concern, resurfacing on its own schedule instead of yours.

The test works because it targets the actual gap: a task list tells you what happened, never whether the question behind it has an answer. Most “done” items pass step one instantly and stall on step two — the signal that they were defaulted, not decided.

Product note

Naming the open question is treated as its own unit of work — distinct from the task it sits under. It gets an owner and a revisit date, the same two details the test above asks for, so a defaulted decision can’t quietly pass as a closed one just because the task above it shipped.

The exercise

Take five things you finished this week — not things still on your list, things you’d already call done. Run the test above on each, out loud or in writing. Notice which sentences come out clean and which ones you have to improvise.

The ones you improvise are your real backlog — not the unfinished work, but the decisions still quietly billing you underneath work that already shipped.

In practice with Pergunta.me

Where earlier work in this series looked at why a task won’t start, this is the layer after: Pergunta.me surfaces which already-shipped items still carry an unresolved decision, instead of letting “done” quietly absorb both the finished work and the question still attached underneath it.

None of this is a faster way to decide. It’s a way to notice that a decision was never made, instead of mistaking the shipped task for proof that it was. Earlier work in this series looked at the moment before starting, when familiarity creates false confidence. This is the moment after — the work is already gone, and the only thing left open is a question nobody closed on purpose.

What’s next in this series moves up one more level: even after every task ships and every decision closes, the plan holding them can still be wrong, if reality changed after it was written and nothing forced anyone to look.

Key takeaways

  • Unfinished work is a time cost that goes dormant when you stop touching it; an unresolved decision is an attention cost that keeps resurfacing whether or not you’re working on the related task.
  • A task can ship while the decision underneath it — what it was actually supposed to resolve — stays open, because “done” tracks visible work, not whether a question got answered.
  • The five forces that keep a decision open are open loops, hidden dependencies, competing priorities, ambiguous ownership, and mental load — none of which require the decision to be difficult, only unclosed.
  • Reorganizing or relabeling a task list doesn’t close a decision; only deciding, visibly deferring with an owner and a date, or deliberately dropping it does.
  • The test: state the decision behind a “done” item in one sentence with an owner and a revisit date. If you have to improvise the sentence, it was defaulted, not decided.

Further reading

  • Klinger, E. (1975). “Consequences of Commitment to and Disengagement from Incentives.” Psychological Review, 82(1).
  • Masicampo, E. J., & Baumeister, R. F. (2011). “Consider It Done! Plan Making Can Eliminate the Cognitive Effects of Unfulfilled Goals.” Journal of Personality and Social Psychology, 101(4).
  • Leroy, S. (2009). “Why Is It So Hard to Do My Work? The Challenge of Attention Residue When Switching Between Work Tasks.” Organizational Behavior and Human Decision Processes, 109(2).
  • Ghibellini, R., & Meier, B. (2025). “Interruption, Recall and Resumption: A Meta-Analysis of the Zeigarnik and Ovsiankina Effects.” Humanities and Social Sciences Communications, 12(1).
  • Scheibehenne, B., Greifeneder, R., & Todd, P. M. (2010). “Can There Ever Be Too Many Options? A Meta-Analytic Review of Choice Overload.” Journal of Consumer Research, 37(3).

Pick one thing you finished this week and try to say the decision behind it out loud, with an owner and a date attached. If the sentence falls apart as you say it, use Pergunta.me to name the open question and give it an owner before it quietly reopens on its own.

More Insights