Kanban Rescue — Turning Around a Drowning Support Team
Rescued a 12-person support team buried under 200+ open tickets by implementing Kanban with strict WIP limits and triage cadences. Reduced average response time from 48 hours to 6 hours and cleared the backlog in 4 weeks.
Challenge
A 12-person support team with 200+ open tickets, no prioritisation, and 48-hour average response times was at risk of losing a key client contract.
Solution
Implemented a Kanban board with strict WIP limits, a daily triage cadence, and clear escalation policies to restore flow and accountability.
Result
Average response time dropped from 48 hours to 6 hours, ticket backlog cleared within 4 weeks.
The Problem
I was asked to step in and assess a production support team at a mid-size SaaS company that was, frankly, drowning. The team of 12 engineers had over 200 open tickets in their queue. There was no meaningful prioritisation — tickets were worked on based on who shouted loudest or which customer escalated to the CEO. Average response time had ballooned to 48 hours, and for lower-priority issues, some tickets sat untouched for weeks.
The team was not lazy — they were overwhelmed and lacked structure. Engineers were routinely juggling 8-10 tickets simultaneously, context-switching constantly, and finishing nothing quickly. A major client had formally complained, and the account was at risk. Leadership wanted a turnaround plan within a week.
What I Did
I started with observation. I spent two days sitting with the team, watching how work flowed (or did not flow), and mapping where time was actually spent. The diagnosis was clear: no intake process, no WIP limits, no visibility into what was in progress, and no escalation criteria.
I introduced Kanban as the operating model. We set up a board with explicit columns — Triage, Ready, In Progress, In Review, Done — and established strict WIP limits. Each engineer could have a maximum of two tickets in progress at any time. This was uncomfortable at first, but it forced completion over accumulation.
I implemented a daily 15-minute triage ceremony every morning. The team lead and I reviewed new incoming tickets, categorised them by severity, and assigned them to the Ready column. Critical issues went straight to the top. Anything that had been open for more than 5 days without progress triggered a mandatory review.
For the existing backlog of 200+ tickets, I ran a one-time triage blitz. We spent a full day categorising every open ticket. About 40 were duplicates or already resolved. Another 30 were no longer relevant. The remaining tickets were prioritised and fed into the Kanban system over the following weeks.
I also created a simple escalation policy — if a critical ticket was not picked up within 2 hours, it automatically escalated to the team lead. This closed the gap on high-severity items that had previously been lost in the noise.
The Outcome
Within two weeks, average response time dropped to under 8 hours. By week four, it was consistently at 6 hours, and the full backlog was cleared. The at-risk client received a personal update on the changes and renewed their contract. The team's own morale improved visibly — engineers said the WIP limits were the single biggest factor, because they could finally focus and finish. The Kanban system remains in place today with the team continuing to iterate on their process.