TQ-13
Missing Outcome or Purpose in Description
Text Quality
Default severity: high
ProcessMetrics
What it detects
Summary and description lack outcome or purpose language such as so that / aby (Tabuľka 1 #4).
Detection formula
IF issue.type IN ac_required_types AND combined summary+description lacks outcome indicators THEN FLAGExamples in practice
- Description jumps straight to UI solution with no goal or benefit.
Suggested response
State who benefits, why the work matters, and how success will be recognized.
Coaching playbook
Symptom
Summary and description lack outcome or purpose language such as so that / aby (Tabuľka 1 #4).
Why it matters
When "Missing Outcome or Purpose in Description" 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
State who benefits, why the work matters, and how success will be recognized.
Facilitation questions
- What system change would stop "Missing Outcome or Purpose in Description" 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.