Short answer: your Finish What You Start result names a primary pattern and a secondary one, each with a real strength and a real cost. That is a useful mirror, but it will not close a single open project for you. Pick one small thing you have not finished, use your result as a question to ask about that specific project, and fill out a one-page finish decision card: purpose, minimum acceptable completion, the one remaining action, who needs the handoff, and whether you finish it, deliberately pause it, or retire it. Then check that decision again in a week.
I have a folder on my desktop called “later” that is, if I am honest, a graveyard. A half-built workshop deck. A spreadsheet that needs one more tab. An email I have reread four times and never sent. If you just took the quiz and got your result, you probably have your own version of that folder, and you already know the pattern description fits. The part nobody hands you next is what to actually do with one specific thing sitting in it. That is the only job of this article.
What does your Finish What You Start result actually tell you?
The Finish What You Start quiz runs you through 22 questions about how you behave in the middle and at the end of projects, not how motivated you feel about them in general. It takes about five minutes, and it hands you a primary pattern, the one driving most of your unfinished work, and a secondary pattern, the one that tends to show up once the first has already spent itself on a longer or harder project.
This is a self-report tool, and it is worth saying plainly: it describes a tendency in how you answered, not a scan of your brain and not a verdict on your character. The quiz page itself includes a section framed as the brain science behind your pattern. Treat that as a plausible explanation offered alongside your result, not as an established fact about what is happening in your head. What the result is actually good for is naming your pattern clearly enough that you can ask a sharper question about a real project, instead of circling the same vague guilt about “the pile.”
If you have not read the full breakdown of all five patterns yet, the Ninety Percenter article covers the strength and the friction inside each one. This piece has a narrower job: once you already have a result, how do you use it on one actual thing on your desk.
What question should your result make you ask about a real project?
Here is the shift that matters. Your result is not a rule that assigns you a fix. It is a question you check against a specific project, and the answer might surprise you.
| If your pattern is | The question to ask about this one project |
|---|---|
| The Sprinter | Did the pull on this disappear when the “new” feeling wore off, or is something else going on? |
| The Polisher | Is “not done” actually true here, or have I just not decided what done means? |
| The Pivot Artist | Did a genuinely better idea replace this one, or did I just get bored and call it better? |
| The Plate Spinner | Is this project still open because it matters, or because closing it never made the list? |
| The Ninety Percenter | Is the remaining work hard, or is it just the part where someone else finally sees it? |
Notice none of these questions comes with a built-in answer. A Sprinter result does not mean every stalled project should be abandoned, and a Ninety Percenter result does not mean every unsent thing should be sent today. Some of what is sitting in your folder deserves to stay closed. The question just forces you to look at the actual project instead of the general pattern.
What are your three honest options for any one open project?
Most advice about unfinished work assumes the only acceptable ending is finishing. That is not true, and pretending otherwise is part of why the pile keeps growing. Every open project has exactly three honest endings.
| Option | What it means | When it actually fits |
|---|---|---|
| Finish it | Do the specific remaining work and close it out | The purpose still matters and the remaining work is genuinely small |
| Deliberately pause it | Name a clear restart condition and set it down on purpose | The purpose still matters but now is not the right time, and you know what would change that |
| Retire it | Call it done being worked on, with no guilt attached | The purpose no longer matters, or a better version already replaced it |
A deliberate pause is not the same as the drift that put the project in your folder in the first place. Drift has no restart condition and no deadline. A real pause names both. A retired project is not a failure either. It is a decision, made on purpose, instead of a thing that just quietly stopped without anyone saying so.
How do you build a finish decision card for one project?
Pick one project right now, something small enough to actually resolve this week, not your biggest unfinished thing. Fill in five fields.
Purpose: why did this project exist in the first place? One sentence, written in plain language, not the ambitious version from when you started it.
Minimum acceptable completion: the smallest version that would actually count as done, stated in checkable terms. Not “really good,” which has no finish line. “Three sections, sent to Dana, no further edits” is checkable.
Remaining action: the single next physical step, small enough to do in one sitting. Not “finish the deck.” “Write the three bullet points on slide 9.”
Who needs the handoff: the person who is actually waiting on this, or would receive it if it shipped. If the honest answer is no one, that is useful information on its own.
Decision: finish, deliberately pause with a named restart condition, or retire. One of the three, chosen on purpose.
What does a blank finish decision card look like?
Copy this onto a sticky note or the top of the project file.
- Project:
- Purpose, one sentence:
- Minimum acceptable completion:
- Remaining action, one physical step:
- Who needs the handoff:
- Decision: Finish / Pause until _ / Retire
- Date I will check this decision again:
What does a filled-in example look like?
This is a clearly hypothetical example, not a real client or a real project, just here to show the shape.
- Project: the onboarding guide I started for new hires in March
- Purpose, one sentence: so new hires stop asking me the same five questions in their first week
- Minimum acceptable completion: one page covering the five actual questions, sent to the team lead, no formatting polish required
- Remaining action, one physical step: write the answer to question three, the only one still blank
- Who needs the handoff: the team lead, who currently answers those questions by hand every time
- Decision: Finish. The purpose still holds, the remaining work is one paragraph, and someone is actively absorbing the cost of it staying unfinished.
- Date I will check this decision again: one week from today
Notice the decision here was not automatic just because the result named a pattern. It came from looking at this specific project: a real person absorbing a real cost, and one paragraph standing between here and done.
How do you review the decision after a week without turning it into another verdict on yourself?
Set a single calendar reminder for one week out. When it fires, answer three short questions, nothing more.
Did I follow through on the decision I made? Yes, partly, or no. If the decision was finish and you did not finish, that is data, not proof of anything about your character. Go back to the three options and pick again, this time being honest about what actually happened in that week.
If the decision was pause, is the restart condition met yet? If not, the pause is still valid and needs no action. A pause without a check-in date quietly turns into drift, which is the exact thing this process exists to prevent.
If the decision was retire, does it still feel right a week later? Usually yes, and that is the whole point: a project you deliberately closed stops taking up space in your head the way an undecided one does.
One finish decision card will not empty your folder, and it is not supposed to. The goal is one project resolved on purpose, with a result that actually held up a week later. Do that enough times and the folder gets smaller the honest way, one real decision at a time, instead of one more sweeping resolution that quietly joins the pile.
Frequently asked questions
Does my quiz result predict whether I will finish this specific project?
No. The result names a pattern in how you report handling the middle and end of projects generally. It does not know anything about this particular project, who is waiting on it, or how much work is actually left. Use it to generate a sharper question, not a prediction.
Is retiring a project the same as giving up?
No. Giving up is what happens by default when a project drifts without anyone deciding anything. Retiring is a decision, made on purpose, usually because the purpose no longer applies or something better already replaced it. A retired project frees up attention that a drifting one does not.
What if I cannot tell whether to finish, pause, or retire?
Go back to the purpose field. If you cannot write an honest one-sentence reason this project should exist, that is itself an answer, usually pointing toward retire or a long pause. If the purpose is clear and specific, the decision between finish and pause usually comes down to whether the remaining action is small enough to do this week.
Can I use this process on more than one project at once?
You can, but start with one. Filling out five fields for ten projects at once tends to turn into another form of avoidance. Resolve one project fully, including the week-later check-in, before you run the process on a second one.
What if my primary and secondary pattern point in different directions for the same project?
That is common. Your secondary pattern tends to show up once your primary has already spent itself on a longer or harder project. Ask both questions from the table above about the same project and see which one actually matches what happened. You are checking the pattern against the project, not assuming the pattern decides it for you.
Does a deliberate pause need a specific date, or is “later” close enough?
It needs a specific, checkable restart condition. “After the Q3 launch ships” is checkable. “Later” is not, and “later” is usually how projects end up in the folder in the first place. If you cannot name a real condition, you are probably looking at a retire decision instead.
What is the one move to make today?
Pick one small project sitting unfinished right now, not your biggest one, and fill out the blank card above before you do anything else with it. If you have not taken the quiz yet, the free Finish What You Start quiz takes about five minutes and gives you a primary and secondary pattern to start from. If the pattern underneath this is less about finishing and more about never starting, this piece on getting unstuck at the start covers that half of the same cycle. If you want to talk through a specific pile of projects with an actual person, a free coaching consultation is a no-pressure next step.
Your result is not a verdict on everything you have not finished. It is one pattern, checked against one project, turned into one decision you can actually review. That is the whole process, and it is enough.
Related reading: The Ninety Percenter: Why You Never Quite Finish ยท How to Stop Procrastinating When Your Brain Won’t Start
