What does 'define what done looks like' mean in automation?

"Define what done looks like" sounds abstract until you try to automate a workflow without it.

Then everything gets fuzzy very quickly.

Was the invoice processed? Or just extracted? Was the lead routed? Or just enriched? Was the onboarding step completed? Or only started?

That is why every serious workflow needs a clear definition of done before anyone builds anything.

What a done definition actually is

A done definition is the measurable finish line for the workflow.

It tells you:

• when the work starts
• when the work is complete
• what outputs must exist
• what exceptions break the happy path
• what should be logged for review

Without that definition, teams end up automating fragments instead of outcomes.

Why this matters so much

Most workflow problems are not caused by a lack of software.

They are caused by ambiguity.

If nobody agrees on what "complete" means, it becomes hard to answer basic questions:

• Did the automation work?
• How much labor did it remove?
• What should trigger a human review?
• What should the buyer pay for?

That is why defining done is not just an implementation step.

It is the thing that makes the whole workflow economically legible.

Examples of weak vs strong definitions

Weak:

• invoice reviewed
• lead processed
• onboarding handled

Strong:

• invoice extracted, coded, approved, and posted to ERP
• lead enriched, deduped, assigned, and SLA timer started
• onboarding document set collected, validated, and next task assigned

The stronger definition is better because it gives the workflow a real end state.

Why buyers should care

If a vendor cannot define what "done" means, the buyer usually ends up with:

• vague success metrics
• messy exception handling
• unclear pricing
• hard-to-defend ROI

That is one reason many AI pilots sound promising and still fail to turn into production systems.

The workflow was never defined tightly enough to measure.

A better buying question

Before approving any automation work, ask:

What exact unit of work will be completed, and how will we know it is complete?

That question is more useful than broad discussions about model quality or tool sophistication.

It gets you to the operating contract.

If you want to see how we think about units of work and workflow economics, see our pricing page and run the calculator. If you want help defining the first workflow sharply, book a workflow audit.