Project Completion Timeline turns 6 observations you can make without any special effort — money invested, how often you SEE it, months since last worked on and external deadline or recipient waiting? — into a project completion timeline score. The input that moves the result most is dormant, so if you are unsure about one figure, that is the one worth getting right.
The model is a weighted sum passed through a sigmoid, which is what keeps the result inside 0–100 no matter how extreme one input gets. Sunk, visibility and dormant push the number up; progress pulls it down. The published weights are the whole model: dormant at +1.1 and progress at -0.9. They are shown in the table below rather than hidden, so you can disagree with a specific number instead of the result as a whole. Anything under 25 reads as the settled case; the top band, furniture made of shame, begins where the pattern is consistent rather than occasional.
Treat the number as a position on a scale rather than a quantity. Where it sits among the 4 bands is the part that should influence a decision. Changing one input at a time is worth more than the first result: it shows you which factor your situation is actually sensitive to. It is a model built on self-reported inputs, so it inherits whatever bias is in your own estimates, and it describes a pattern rather than predicting an outcome. Everything runs in your browser; nothing you enter is sent anywhere or stored.
The formula
w1·sunk- Money invested (weight +0.7)
w2·visibility- How often you SEE it — 0 = boxed away, 10 = daily eye contact (weight +0.6)
w3·dormant- Months since last worked on (weight +1.1)
w4·deadline- External deadline or recipient waiting? (weight +0.5)
w5·progress- How complete is it? — % (weight -0.9)
σ, μ- Sigmoid squash to 0–100, centered on typical values
How it works, step by step
- Rate each input honestly — the Project Completion Timeline score is only as good as your self-assessment.
- Watch the live score and note which factor the result panel names as your strongest driver.
- Read your band below — each range comes with a concrete recommended next step.
- Change one input to simulate a change in behavior and see how much the score moves — that sensitivity is the real insight.
- Re-take the assessment after a few weeks; trends across readings mean far more than any single score.
Worked examples
A low-signal scenario
With every input set well below typical — the quiet version of this situation — the model returns 44, landing in the “Pending decision” band. This is a paused project, not an abandoned one. It fits your energy budget and clutter tolerance; no action or guilt is owed.
A high-signal scenario
Push the main drivers well above typical and the score rises to 60 — the “Actively nagging” band. The project functions as a monument to a former plan. Release it formally — photograph, thank, rehome — and reclaim both the space and the mental rent.
How to read your score
Frequently asked questions
What does the Project Completion Timeline actually tell me?
Where this project sits on the spectrum from healthy pause to guilt monument — by weighing sunk cost, dormancy and visibility against your real capacity to finish. The point is a decision, not a shame score.
Why does visibility matter so much?
Because guilt needs a trigger. A boxed project generates a fraction of the ambient guilt of one in daily eye-line, which is why the model lets honest storage placement genuinely lower your score.
Why do unfinished projects generate guilt at all?
Two well-studied effects compound: sunk-cost aversion (quitting feels like losing the money again) and the Zeigarnik effect (open tasks stay mentally active). Physical visibility multiplies both — the project literally watches you.
How can I restart a long-dormant project?
Shrink the restart: one 20-minute session with zero completion ambition. Momentum research is unanimous that starting tiny beats planning big — and the model’s dormancy weight drops quickly once work resumes.
Should I finish it or let it go?
The model’s verdict logic: strong progress plus available energy says finish; long dormancy plus low progress says release. Both outcomes close the loop — research on task abandonment shows deliberate release relieves nearly as much tension as completion.
Is my information saved?
No — everything computes locally in your browser and vanishes when you leave.