TQ-14

Acceptance Criteria Task List Not User Outcome

Text Quality

Default severity: high
ProcessMetrics

What it detects

AC reads as implementation tasks or DoD instead of observable user outcomes (Tabuľka 1 #5).

Detection formula

IF AC matches task/implementation patterns without outcome or observable checks THEN FLAG

Examples in practice

  • Bullets: create API, update schema, deploy service — no user-visible result.

Suggested response

Rewrite criteria as what the user or stakeholder can observe after delivery.

Coaching playbook

Symptom

AC reads as implementation tasks or DoD instead of observable user outcomes (Tabuľka 1 #5).

Why it matters

When "Acceptance Criteria Task List Not User Outcome" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.

What you can achieve

Rewrite criteria as what the user or stakeholder can observe after delivery.

Facilitation questions

  • What system change would stop "Acceptance Criteria Task List Not User Outcome" from firing again?
  • What do the cited issues have in common — same root cause or same workaround?
  • Who owns the two-week experiment and how will we verify on the next import?

Run this rule against your own tracker data with Flow Analyzer.

Product tourSign in
TQ-14: Acceptance Criteria Task List Not User Outcome — FlowAnalyzer