Skip to main content

No Jargon · 09/03/2026

Don't Make Business Stakeholders Write Acceptance Criteria

I have sat with a clerk who could name who approves an exception, then watched us ask her for acceptance criteria until she no longer recognized her week.

Acceptance criteria are useful to builders and testers. Making a business stakeholder author them is where usefulness becomes theater. I have watched a payroll manager apologize for not knowing Given/When/Then while knowing every exception that could bankrupt the Friday run.

I have watched product people “write it up” until the original sentence was gone. The criteria were elegant. QA tested the elegance. The export still failed on Friday.

The template is not the request

“Given a finance clerk, when they click download, then they are more efficient” is a stand-in. “I email last month’s report to four people every Friday, and two of them already have a copy” is a week. Only one of those can be checked without a decoder ring.

If you must use criteria later, keep the clerk’s sentences attached. Do not let the template replace them. I have never seen a Given/When/Then line survive contact with Tuesday better than the original complaint.

Keep clarification in ordinary language

Once the week is written, requirements gathering software can ask who approves an exception, what happens when the file is empty, and which Friday counts as done. Those are facts. “Write the acceptance criteria for the persona” is stairs.

Put the first paragraph in software project intake so nobody has to study a template to file a complaint. The criteria format can wait for a team that already shares it. The request cannot wait for a format.

Hand builders the witness, not the rewrite

One write-up that turned “the night crew cannot see yesterday’s tickets” into acceptance criteria about visibility. We shipped a dashboard. The night crew still could not see yesterday’s tickets. The criteria closed. The week did not. The loss began when the project office became the intake translator, not in the stakeholder’s vocabulary.

For more detail, see Why agile jargon kills stakeholder alignment. Ceremony words are one problem. Asking a stakeholder to speak QA is the next one. Leave the voice alone. Review for gaps. If the requester cannot read the criteria, you already left the hallway.