Let It Be Finished

I.

You can always make another version.

Another headline. Another arrangement. Another color that is technically different from the last color. Somewhere, a folder called FINAL has a folder inside it called FINAL ACTUAL, and neither one feels especially confident about the situation.

The ability to keep improving something is useful. The inability to stop can get expensive.

I care about craft. I also think craft includes recognizing when a piece of work has done what it came to do. Otherwise “high standards” can become a very flattering name for refusing to make a decision.

II.

Finishing requires a little exposure. Once the work leaves the room, somebody can use it, ignore it, misunderstand it, or tell you something you did not want to hear.

While it is still being revised, all of those possibilities remain hypothetical. You can keep working toward an imaginary version that will make everyone understand exactly what you meant. That version is wonderfully cooperative. It has never met a customer.

I think there is a point where another revision is mainly protecting the maker from that encounter.

That is an opinion, not a diagnosis of every slow project. Sometimes the work is simply unfinished. Sometimes the stakes demand more care. But it is worth being honest about what the next round is supposed to resolve.

III.

Imagine a small service page with a clear job: explain who the service is for, what happens next, and how to get in touch.

In this hypothetical example, those things work. The information is correct. The page is readable on a phone. The form sends to the right place. The people responsible for the service have checked the promises.

Now someone wants to revisit the headline because a new phrase occurred to them during lunch.

That phrase might be better. It might also be a perfectly good idea for later. The existence of an alternative does not, by itself, establish a problem with the version in front of you.

I would want to hear what the new version helps someone understand. If the answer is clear, make the improvement. If the answer is mostly that we have been staring at the current one for a while, perhaps the page should meet somebody else.

IV.

A definition of finished helps before the room gets tired.

What must be true? Who needs to review it? Which problems prevent release? Which imperfections can be corrected later without misleading someone or creating unnecessary trouble?

Those questions make the decision less dependent on the mood of the last person who opened the file.

They also make room for different standards. A factual error deserves a different response from a personal preference. A broken interaction deserves a different response from a sentence that could have a little more rhythm. Everything cannot be the same level of urgent just because everything is visible.

I want the important problems fixed. I want enough judgment left over to recognize which ones they are.

V.

There is a second responsibility after finishing: let the work exist long enough to learn something from it.

If you change the message, the design, the offer, and the destination every time you get uncomfortable, it becomes difficult to understand what people are responding to. Even without a formal experiment, continuity gives you something to inspect.

That does not mean ignoring a mistake. Fix the broken form. Correct the wrong detail. Take down a claim you cannot support. Completion is not permission to become incurious.

But keep a place for ideas that do not require immediate action. Write them down. Give them a review date. Let a considered revision become its own piece of work instead of allowing every passing thought to reopen the current one.

The next good idea deserves attention. It does not always deserve an interruption.

VI.

I like the satisfaction of a thing with edges. A question answered. A problem resolved. A useful piece of work somebody can finally put into use.

It is easy to talk about ambition as the next thing you are going to add. Finishing asks for a different kind of confidence: enough conviction to decide that this version is ready for its purpose, with its limits understood.

You can still care about it tomorrow. You can still make it better. You can still learn that a decision needs to change.

Today, if the work is ready, let it leave the folder.