TQ-17
Subjective Unverifiable Acceptance Criteria Wording
Text Quality
Default severity: high
ProcessMetrics
What it detects
AC uses subjective adjectives without measurable or observable checks (Tabuľka 1 #8).
Detection formula
IF AC has subjective wording AND no Given/When/Then or measurable cues THEN FLAGExamples in practice
- UI should be intuitive and show sufficient information.
Suggested response
Replace vague adjectives with numbers, states, or visible facts.
Coaching playbook
Symptom
AC uses subjective adjectives without measurable or observable checks (Tabuľka 1 #8).
Why it matters
When "Subjective Unverifiable Acceptance Criteria Wording" 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
Replace vague adjectives with numbers, states, or visible facts.
Facilitation questions
- What system change would stop "Subjective Unverifiable Acceptance Criteria Wording" 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.