Writing Useful Acceptance Criteria

The Founder Situation

A founder is turning an idea into a brief that a consultant can estimate and build.

The immediate question is writing useful acceptance criteria. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.

Technical term

Acceptance criteria are observable conditions used to decide whether a workflow or requirement has been completed correctly.

Treat it like a clause in a commercial agreement: its value comes from making expectations and consequences clear, not from sounding formal.

What Matters in Practice

Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.

For this decision, the useful standard is that a real user can complete the intended outcome and the result tests the stated assumption.

Make the decision explicit: Write criteria around user-visible outcomes, important rules, and failure behaviour rather than implementation steps.
Ask what evidence would show that the chosen approach works.
Name the person or provider responsible when the approach fails.
Record the result in the MVP brief and acceptance criteria.

Knowledge Check

Which approach best applies writing useful acceptance criteria to a founder's product decision?

Acceptance criteria are observable conditions used to decide whether a workflow or requirement has been completed correctly. Write criteria around user-visible outcomes, important rules, and failure behaviour rather than implementation steps.Choose the most sophisticated option and document it later.Treat the interface demonstration as proof that the underlying system is ready.Delegate the decision completely because it contains technical terms.

A Proportionate Decision

Write criteria around user-visible outcomes, important rules, and failure behaviour rather than implementation steps.

The principal risk is that the founder and builder declare the same feature complete using different standards. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.

Describe the user or business outcome that must be protected.
Identify the most credible failure and its consequence.
Compare the simplest adequate approach with one realistic alternative.
Set a review point for when the decision may need to change.

Strong Evidence and Weak Reassurance

Proportionate Approach

The choice is tied to a known outcome, risk, owner, and review point.

States what is included and excluded
Produces evidence another person can review
Leaves the company able to change provider or approach

Weak Reassurance

The choice relies on a tool name, successful demo, or untested assumption.

Uses technical vocabulary without consequences
Tests only the easiest path
Leaves ownership or recovery unclear

Exercise

Choose the Useful Consultant Question

A consultant says that writing useful acceptance criteria is covered. Which follow-up gives the founder the most useful evidence?

Can you show how the approach supports this decision: Write criteria around user-visible outcomes, important rules, and failure behaviour rather than implementation steps.Is this the tool you normally use?Can we make the interface look more technical?Can we avoid documenting the choice until after launch?

Knowledge Check

Which risk deserves the most attention when reviewing writing useful acceptance criteria?

the founder and builder declare the same feature complete using different standards.The product uses fewer visual effects than a competitor.The team has not selected a final logo treatment.The first implementation takes more than one working session.

Warning Signs

Nobody can explain how writing useful acceptance criteria changes a user or business outcome.
The proposal does not address this risk: the founder and builder declare the same feature complete using different standards.
The only evidence is a successful demonstration of the easiest path.
The decision has no named owner, boundary, or review point.
A provider-specific feature is being mistaken for a permanent product requirement.

Questions to Ask a Consultant

What decision are we making about writing useful acceptance criteria?
Which user or business outcome does the recommendation protect?
How have we reduced or accepted this risk: the founder and builder declare the same feature complete using different standards.
What evidence can I review without relying on the original implementer?
What is deliberately deferred, and when will it be reconsidered?
Who owns the accounts, data, documentation, and recovery process?

Exercise

Founder Decision Note

Record the decision, its current constraint, recommended option, main reason, primary risk, and the condition that would make you revisit it.

DecisionCurrent constraintRecommended optionMain reasonPrimary riskWhat would make us revisit this

Key takeaway

Acceptance criteria are observable conditions used to decide whether a workflow or requirement has been completed correctly. The founder's job is to make the consequence explicit; the consultant's job is to recommend and demonstrate a proportionate implementation.

The Founder Situation

A founder is turning an idea into a brief that a consultant can estimate and build.

The immediate question is writing useful acceptance criteria. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.

Technical term