Why the last ten percent of a task is the hardest
The last ten percent is hard because the interesting problem solving is usually already finished, leaving only small checking details with little pull. It also carries a decision the rest of the task did not: declaring it actually done. Treating the final stretch as its own small task, with its own timer and finish line, closes it faster than muscling through on the middle's energy.
The math is misleading
Ten percent sounds small, which is exactly why it is so easy to underestimate how long it will actually sit unfinished. A report that is written but not proofread, a form that is filled out but not mailed, a project that is built but not tested: each of these looks nearly done from the outside, and that appearance is part of the problem. A task that looks finished generates less urgency than one that clearly is not, so the final stretch quietly loses whatever pressure was pushing the first ninety percent along.
Other people often reinforce this without meaning to. If you mention the report is "basically done," nobody follows up on it the way they would if you said it was half finished, which quietly removes one more source of the pressure that might have pushed the last stretch along.
The interesting part is usually already over
Most of a task's problem solving happens in the middle: figuring out the approach, working through the hard parts, making the decisions. By the time you reach the last stretch, that work is done, and what remains is often smaller and more mechanical: checking for errors, printing, mailing, submitting, cleaning up. For attention that runs on interest, this final stretch offers the least of it, even though it is often the part that actually delivers the result to the world.
Finishing carries a decision the middle did not
There is also a psychological weight specific to the ending that the middle of a task does not carry: declaring it done. Sending the email means it can no longer be revised. Submitting the form means it is out of your hands. For some tasks, especially ones tied to how you will be judged, that finality itself can cause a stall that has nothing to do with the remaining workload and everything to do with letting go of control over something that is about to become fixed.
This is worth naming to yourself directly when it is happening. If you notice you are rereading a finished document for the fourth time looking for one more thing to fix, the task probably is not asking for more editing. It is asking you to tolerate the discomfort of letting it be finished.
A worked example
Say you have written a cover letter for a job application. The writing took an hour and felt purposeful. What remains, proofreading once more and clicking submit, takes maybe five minutes, and yet it sits open in a tab for three days. The stall here is not about difficulty, it is about the small remaining task offering little pull on its own, combined with the finality of clicking submit. Naming the exact remaining action, "read it once out loud, then submit, nothing else," and setting a five minute timer for just that step treats the ending as its own task rather than an afterthought of the one you already did the hard part on.
Give the ending its own timer, separate from the rest
Do not expect the momentum from the middle of a task to carry you automatically through the end. If the last stretch has stalled, set a fresh, short timer specifically for it, the same way you would for starting a task from scratch, an idea covered more broadly in how to use a focus timer with ADHD. The finishing stretch behaves like its own separate task with its own starting problem, not a small tail that will finish itself because the rest is done.
Write the finish line in plain, checkable words
A task that stalls at the end often had a vague sense of "done" to begin with. "Finish the report" is vague. "Read it once, fix any typos, attach it to the email that is already drafted, and hit send" is checkable. The more specific the last step, the less room there is for it to sit half-acknowledged for another week, a habit that connects to finishing tasks, not only starting them, since the two problems usually travel together.
Write the specific last step down the moment you notice the task has stalled, rather than trying to hold it in your head while you decide whether to deal with it now or later. A task that has been sitting for three days has usually lost enough of its original context that reconstructing the exact remaining step takes real effort on its own, effort that a single written line removes entirely.
Common questions
Why does a task that felt almost done sit unfinished for days?
Once the hard thinking is done, what remains is often small, unglamorous, and easy to underestimate, like sending the email or printing the form. Because it feels minor, it is easy to assume it will happen on its own, which is exactly why it often does not.
Is it worth asking someone else to do the final step for me?
Sometimes, especially if the final step is something like a phone call or an errand that keeps stalling. Handing off just the last piece is different from handing off the whole task, and it can be a reasonable trade if that step has stalled more than once already.
Does calling a task "done" at 90 percent count as finishing?
Only if the remaining ten percent genuinely does not matter for the outcome, which is worth being honest about. If a report without its final formatting or a form without a signature does not actually function, 90 percent is not done, it is a different, unfinished task waiting under a name that sounds complete.
This article shares practical organizing ideas. It is not medical advice. For diagnosis or treatment questions, talk with a qualified clinician.