Better Work
The gentle discipline of finishing one thing
Why protecting the last 20 percent matters more than starting another task.
FOCUS
IS NOT
A MOOD.→Starting rewards curiosity. Finishing requires judgment: defining what usable means, protecting the dull final stretch and handing the result to its next owner.
Start with the real friction
Unfinished work often survives because “done” was never made observable. A draft can absorb endless polishing; a deliverable has an owner, a destination and a clear acceptance test.
A CONCRETE EXAMPLE
For a report, the finish line might be “three recommendations sent to the project owner by 3 p.m.” That is more useful than “make the report excellent.”
Define the delivery, not the activity
Imagine a proposal that is almost complete but still needs a price, a link and a recipient. “Work on proposal” leaves the finish line open. “Send a readable proposal with the agreed price to the client” gives you a delivery that someone else can recognize. Write that sentence above the document before opening another task.
A closing checklist for unfinished work
- Separate required fixes from optional improvements. A missing number is required; another font experiment probably is not.
- List the remaining actions as verbs: verify the number, export the PDF, check the link, send the message.
- Ask who can accept the result. If approval is needed, your deliverable may be a review-ready draft rather than a final publication.
- Choose one stopping condition and one time boundary. When the boundary arrives, either deliver or name the single blocker.
Dependencies need a different response from distractions. If a colleague must supply a figure, send a specific question and mark the task “waiting.” Do not spend an hour pretending to finish it. Move to one other bounded task and leave a restart note containing the next action, file location and missing input.
For a task that keeps expanding, make a second list titled “after delivery.” Put improvements there without treating them as obligations today. The aim is a usable result, not rushing work that affects safety, money or another person’s rights.
A three-step experiment
- Write a one-sentence finish line before you begin.
- When the task is 80 percent done, stop opening new work.
- Close the loop: file it, send it and name the next action.
TRY AND REVIEW
A bounded next step
Choose one small deliverable each working day. Record whether it was delivered, blocked by a named dependency or intentionally stopped. Review unfinished items for unclear acceptance criteria rather than simply adding longer work hours.
How to know it is working
The signal to watch: The work leaves your private task list and becomes usable by its next person.
Where this advice stops
Finishing is not the same as forcing. Deliberately abandoning work that no longer matters is also closure.
Published by The Lived Manual using AI-assisted drafting and editing. This is an educational checklist, not a report of a personal field test or a professional assessment. Examples are illustrative. Revised October 28, 2026 to replace repeated passages with topic-specific steps. Preparation and corrections policy.