Writing Useful Acceptance Criteria
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.
What You Will Be Able to Decide
- Explain writing useful acceptance criteria in product and business terms.
- Apply this decision: Write criteria around user-visible outcomes, important rules, and failure behaviour rather than implementation steps.
- Recognise this material risk: the founder and builder declare the same feature complete using different standards.
- Ask a consultant for evidence rather than reassurance.
A founder is turning an idea into a brief that a consultant can estimate and build.
Acceptance criteria are observable conditions used to decide whether a workflow or requirement has been completed correctly.
A consultant can recommend and implement the technical approach. The founder still needs to decide which outcome matters, which risk is acceptable, and what evidence is sufficient.
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
Writing Useful Acceptance Criteria
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.
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
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?
Key takeaway
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.