The SRE Backlog Anti-Pattern Trap

An SRE team with a 200-item backlog is not winning. The signs you have fallen into the backlog trap and how to dig out.

Signs of the trap

More than 50 open SRE tickets that have been open for >30 days.

New incidents create new tickets that nobody works because the backlog is overwhelming.

The team feels like firefighters; the work that prevents fires never happens.

Cause

Reactive bias. The team handles incidents as they come; nobody has bandwidth for proactive work.

Optimistic capacity assumption. The team committed to 5 things; it can do 2.

No retirement policy. Tickets never close, never get rejected, never get marked as 'will not fix.'

Dig out

Triage the backlog. Anything older than 90 days that has no recent activity: close as 'will not fix' unless someone fights for it.

Cap the active backlog. Maximum 30 in-flight tickets; new ones queue.

Reserve 30% of team capacity for proactive work. Block the time on calendars; defend it.