TQ-28

Acceptance Criteria System Capability Not User Behavior

Text Quality

Default severity: high
ProcessMetrics

What it detects

Acceptance criteria describe system or module capabilities without observable user-facing behavior.

Detection formula

IF AC matches system-capability cues without user outcome/observable patterns THEN FLAG

Examples in practice

  • AC: systém podporuje export modul; backend API poskytuje endpoint.

Suggested response

Phrase AC from the user or operator perspective with visible results, not internal capability lists.

Coaching playbook

Symptom

Acceptance criteria describe system or module capabilities without observable user-facing behavior.

Why it matters

When "Acceptance Criteria System Capability Not User Behavior" 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

Phrase AC from the user or operator perspective with visible results, not internal capability lists.

Facilitation questions

  • What system change would stop "Acceptance Criteria System Capability Not User Behavior" 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-28: Acceptance Criteria System Capability Not User Behavior — FlowAnalyzer