Stop at Good Enough

Work does not go unfinished because you are lazy. Often the opposite is true. You think a little more polishing would make it better, you repeat that little, and the deadline passes. The deliverable stays in a drawer and never reaches the world.

You need to practice stopping at good enough. That does not mean sloppiness. It means setting a standard. Who reads this document? What has to be communicated? By when is it needed? Once those three questions have answers, the point to stop becomes visible.

Finished beats unfinished

One finished draft is more useful than ten unfinished masterpieces. A finished thing gets read, corrected and used. An unfinished thing does nothing. It gets no feedback, no revision and no next step.

Quality usually rises in the second version. But a second version only exists if the first one goes out into the world. If you wait for perfect, you lose the chance to reach that second version at all.

Building a stopping point

One method that works in practice: when you start, write the deadline and the standard together. "By Friday this week, to the level where two colleagues understand it." Written down like that, you can ask yourself at each round of polishing: is this edit needed to meet the standard, or am I just touching something that already meets it?

Stopping at good enough lets you move to the next thing. Stopping is not giving up; it is the door to what comes next. Finish today's work and tomorrow's work has somewhere to start.