Brief: completion-bias

Research brief for completion-bias · how it was made.

Research brief - `completion-bias`

Field	Value
Slug	completion-bias
Working title	Completion Bias
Article shape	Specimen Record
Category	Behavioral Traps (`bt`), after Vertical Line Failure
Intent tags	decision-biases, at-work
AI authors credited	Grok 4.7 (research, draft, publish check)
Reviewer or checker	none
Date	2026-09-28

1. Concept gate

Reader's real question:

Why do I finish a bad movie, a book I stopped enjoying, or a project nobody wants, just because I started it?
Is that the same as fearing uncertainty, or the same as refusing to waste what I already spent?

Why this belongs in the catalog:

The catch is specific: an open unit feels like a debt, and the debt gets louder as the end gets close, even when the remainder is not worth the time.
Sunk Cost Fallacy already owns "I paid, so I stay." Intolerance of Uncertainty owns distress at an unknown future, which usually stalls action. Vertical Line Failure owns a failing step-by-step plan. None of them teach the checkmark itself as the reason.
Experiments that unconfound percent-complete from money already spent find a completion pull. A reader can run the check: if nothing had been spent, would I still stay just to close the loop?

Bug claim in one sentence:

The bug is Completion Bias, where an unfinished unit makes stopping feel like a broken duty, which makes the remaining time harder to judge on its own.

What this bug is not:

Not a claim that follow-through is foolish. Promises, shifts, and repairs still get finished because the remainder serves the original reason.
Not sunk cost restated. A free stream can still get watched to the credits. A paid ticket mixes both; the money reason stays on the sunk-cost page.
Not intolerance of uncertainty. That distress is about not knowing, and it often blocks the start. Here you often already know the thing is bad, and you refuse the stop.
Not a claim that sunk cost is unreal. Other studies find it. These studies show a second pull that older designs often bundled with the money already spent.

Nearby bugs to check:

Nearby bug	Difference
Sunk Cost Fallacy	Stay because resources were already spent. Completion bias stays because the unit is unfinished, including when almost nothing was spent.
Intolerance of Uncertainty	Distress that an outcome is unknown; usually worry, checking, and delay. Completion bias closes a started unit you may already have judged.
Vertical Line Failure	Keep walking a rigid sequence after it has failed. Completion bias does not need a plan or a method, only an open unit.
IKEA Effect	Overvalue something after you have built it. Completion bias is the pull to finish before that value judgment.
Search Satisficing	Stop a search at the first good-enough option. Completion bias refuses to stop a unit that is no longer good enough.

Concept gate: Is this specific, distinct, grounded, and correctable? yes

2. Sources and research

Source / concept	Year	What it supports	URL / DOI / note
Conlon, D. E., & Garland, H. The role of project completion information in resource allocation decisions. Academy of Management Journal, 36(2), 402-413.	1993	Separated sunk cost from percent complete. Closeness to completion predicted willingness to keep funding; once unhooked, the sunk amount did not. They describe goal substitution: finishing replaces the original aim, and the wish to finish grows as the end nears.	https://doi.org/10.5465/256529
Garland, H., & Conlon, D. E. Too close to quit: The role of project completion in maintaining commitment. Journal of Applied Social Psychology, 28(22), 2025-2048.	1998	Replication with bank managers, Chinese graduate students, and MBA students. Completion drove investment intentions; typical sunk-cost effects did not show in those studies. Goal substitution is the explanation they argue for.	https://doi.org/10.1111/j.1559-1816.1998.tb01359.x
Boehne, D. M., & Paese, P. W. Deciding whether to complete or terminate an unfinished project: A strong test of the project completion hypothesis. Organizational Behavior and Human Decision Processes, 81(2), 178-194.	2000	People had a sales price they could use, and had to explain their reasoning. Projects close to finished were still recommended when finishing was a poor deal. The sunk-cost manipulation had virtually no effect.	https://doi.org/10.1006/obhd.1999.2877

Do not invent titles, years, DOIs, or effect sizes. If a source is uncertain, say so.

The Zeigarnik memory finding (unfinished tasks are recalled more readily) is left out. It is adjacent and easy to overclaim as a decision result. The article uses the project-completion studies only.

3. Article plan

Explained boundary:

Follow-through is how promises get kept. The distortion is when the checkmark replaces the reason you began. Separate a free bad movie (completion) from a ticket already bought (sunk cost, often mixed) and from distress at an unknown future (intolerance of uncertainty).

Examples planned (4-8 quote examples):

Awful movie, but I have to see how it ends.
Book no longer enjoyed, too far in to stop.
Miserable game level, one more try and it's cleared.
Thread went nowhere, won't leave it unanswered.
80% built, finish it even if nobody wants it.
Rest of the season, because I started it.
Decision already made, stay so the meeting feels finished.

Real-world scenarios, if useful:

Free stream, book past enjoyment, game level, near-done product nobody wants, meeting after the decision.

Impact:

Time spent on remainders already judged as not worth it.
Teams treat percent-complete as an argument and ship the wrong thing.
Open units get treated as debts, so quitting a bad fit feels like a character flaw.

Causes:

Goal substitution: finishing replaces fun, learning, or profit, and the motive strengthens near the end.
Follow-through is praised, and percent complete is a visible number while forward value is not.

Self-spotting signs, if useful:

The reason is "I started" or "I'm almost done."
You would not begin the remainder as a new choice today.
You already know it is bad and you stay.
Relief is about the checkmark.
You would tell a friend to leave.
The last stretch pulls harder than the start.

Prevention moves (3-6):

Name the original goal and ask if the remainder still serves it.
Set a quit point before the end gets close.
Ask whether you would start the remainder today.
Close the loop in a sentence: deciding it is not for you is a completed decision.
On a project, read forward value beside percent complete.
Use a low-stakes quit (a show, a chapter) as practice.

Questions & Answers, if genuinely sharp:

When is finishing still the right call?
Does a short remainder make staying rational, since almost-done is when the pull is strongest?
Is a paid ticket this bug or sunk cost?
Is wanting the ending the same as intolerance of uncertainty?

Reframing examples (2-3):

Label	Original thought	Reframed thought
Bad movie	I started it, so I have to see the ending.	The ending is not a debt. I'll stop, and "this one wasn't for me" closes the loop.
The book	I'm this far in, so I should finish.	Distance from the last page is not a reason. I'll stop where it stopped being worth reading.
Near-done project	We're 80% built, so we should ship.	Percent complete is not demand. I'll ship only if the remaining work still serves the original goal.

Related thinking bugs:

Bug	Difference note
Sunk Cost Fallacy	Past spend versus an open unit.
Intolerance of Uncertainty	Unknown future versus a started unit you may already have judged.
Vertical Line Failure	A failing sequence versus any open unit.
IKEA Effect	Value after building versus the pull to finish.
Search Satisficing	Stopping a search too early versus refusing to stop a unit.

4. Rewrite inventory (only for existing pages)

Current sections:
Current examples worth preserving:
Current sources:
Current reframes:
Current related links:
What can be removed, and why:

5. Sign-off

☑ Belonging test passed
☑ Nearby bugs checked
☑ Sources verified or uncertainty labeled
☑ Examples are concrete
☑ Reframes are realistic, not forced optimism
☑ Credits model/person named