Define Done as Thinking

Done is not the last box on a checklist. Done is the first thinking move.

Before you open the chat, before you name a model, before you polish a prompt: you decide what must be true when the work is finished. If you skip that, you're not running a session. You're spinning a wheel and calling the lucky stop "progress."

This essay is about that move as an approach. Not a form. Not a pipeline recipe. Not a dump of the ordered course. For practice in sequence, take Define outcomes, then build digital products. Here we stay on how you face the problem.

The first move

Most people start with a wish. "Write me a landing page." "Fix the auth." "Make it feel premium."

A wish is not done. A wish is a direction of travel without a destination you can mark.

I treat define done as the first act of craft. Same as a director who will not call "action" until the shot list can fail or pass on set. The thinking is the contract. Everything after it is labour against that contract.

If you cannot say what done looks like in checkable terms, you're not ready to run a model. You're ready to think harder. That is not a delay. That is the work.

What "done" means

Checkable done answers three questions a stranger could use without your private intent.

What must exist. The observable thing: a file, a route, a render, a shipped behaviour. Not a vibe. Not "better." Something you can point at.

What evidence counts. Tests, screenshots, a click path, a measurement, a diff you inspect. Evidence is what you accept as proof. Without it, "done" is a story the session tells itself.

What you reject. Failure modes that block completion even when the output looks plausible. Wrong audience. Voice that is not yours. A green report with a black screen. Scope that quietly grew. If you never name reject criteria, the model invents success for free.

Exists. Evidence. Reject. That triad is enough to hold the approach. You do not need a longer ritual to start thinking this way. You need the habit of refusing to run until the triad is clear enough to grade.

Outcome as approach, not paperwork

People hear "define the outcome" and reach for a template. Templates can help later. They are not the point.

The point is a stance: I will not buy labour until I can accept or reject the result.

Paperwork is what happens when you fill fields after you already opened the chat and need something that looks organised. Approach is what happens when the definition shapes what you ask for, what you pack into the room, and when you stop.

An outcome is how you decide what the work is. It is not a form you attach so the session feels professional.

When the definition is sharp, the prompt gets short. When the definition is soft, the prompt gets long and still fails. Length is not the fix. Clarity of done is.

Failure: the prompt as substitute for done

The common failure is substitution.

You feel the missing definition as unease. Instead of writing the brief, you write a longer prompt. More adjectives. More "make sure." A system message that tries to carry the whole contract. Then another model. Then another pull.

That is the slot machine. A prompt without done is a wish with better grammar.

The model will fill gaps. It fills them with averages. Averages look finished until you hold them against reject criteria you never wrote down. Then you burn a cycle "refining the prompt" when the real miss was never stating what success and failure are.

Scar pattern I trust: ambiguous instruction, reasonable model interpretation, wasted evening. The junior on set would have made the same wrong shot. Fix the definition. Do not blame the hands.

How this sits in the cluster

This is spine one of Context Is King: define the outcome before you touch the prompt.

The sibling spine is systems and context: hold the problem as a room that outlives the chat. That branch is Hold the System.

The older public home of the same thesis is Stop Prompting. Start Defining Outcomes.. Historical essay. Same bloodline. This page is the library branch for done-as-thinking.

Library here. Course there. Mentality and free roam in outcomes-and-systems. Ordered product practice at /courses/define-outcomes-build-products. Shared thesis. Separate jobs. No lesson dump on this page.

The move, one line

Define done first. Make it checkable: what exists, what proves it, what you refuse. Then run labour. If you skip the thinking, the prompt is only a substitute, and substitutes do not pass when the work has to land.