FI-13
No Flag Usage on Slow Issues
Flags
Default severity: medium
ProcessOutputRisk
What it detects
Computes a composite flag discipline score (0-100) per team based on all FI rules. This score summarises how effectively the team uses the flag mechanism as an escalation tool. A low score indicates either avoidance (too few flags, fast removals) or neglect (flags ignored, no comments, long ages).
Detection formula
FOR each_team T: flag_score(T) = 100 flag_score -= weight(FI-01) * COUNT(long_lived_flags, team=T) / max(1, total_flags) // age penalty flag_score -= weight(FI-02) * COUNT(no_comment_flags) / max(1, total_flags) // no context flag_score -= weight(FI-03) * COUNT(no_response_flags) / max(1, total_flags) // ignored flag_score -= weight(FI-04) * COUNT(silent_removals) / max(1, total_flag_removals) // no resolution note flag_score -= weight(FI-06) * COUNT(recurring_flags) / max(1, total_issues) // repeat blocks flag_score -= weight(FI-09) * COUNT(open_at_sprint_end) / max(1, sprint_committed) // unresolved flag_score -= weight(FI-11) * consecutive_zero_flag_sprints * 5 // suppression flag_score = MAX(0, MIN(100, flag_score)) IF flag_score \< config.fi.flag_score_warning // default: 60 THEN FLAG poor_flag_discipline IF flag_score \< config.fi.flag_score_critical // default: 40 THEN CRITICAL Report: score breakdown by component with per-team comparison tableExamples in practice
- A team shows computes a composite flag discipline score (0-100) per team based on all fi rules while flag score warning is set to 60.
- Example signal: Computes a composite flag discipline score (0-100) per team based on all FI rules.
Suggested response
Close the loop on flags—link blockers, set owners, and clear impediments with traceability.
Coaching playbook
Symptom
Computes a composite flag discipline score (0-100) per team based on all FI rules. This score summarises how effectively the team uses the flag mechanism as an escalation tool. A low score indicates either avoidance (too few flags, fast removals) or neglect (flags ignored, no comments, long ages).
Why it matters
When "No Flag Usage on Slow Issues" 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
Close the loop on flags—link blockers, set owners, and clear impediments with traceability.
Facilitation questions
- What system change would stop "No Flag Usage on Slow Issues" 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.