From firefighting to flow — draining a permanent escalation queue
The delivery organization we were asked to help had a queue that never emptied. Every week began with a triage of production incidents, customer escalations, and half-finished work handed back across teams, and every week ended with the same queue slightly longer than it started. Their best engineers had quietly become their best firefighters — rewarded, promoted, and burned out for heroics that a healthier system would never have demanded. Leadership read the pattern as a staffing problem. It was not. It was a structure that manufactured the very fires it then celebrated putting out.
Firefighting feels like the opposite of dysfunction because it is visibly, exhaustingly productive. That is what makes it so hard to see from the inside. Analytical management responds to a growing queue by adding capacity to the queue — more responders, faster tools, tighter rotations — and each addition buys a few weeks before the backlog reabsorbs it. Systems thinking asks a different question: what property of the organization keeps regenerating this work? Answer that, and the queue stops being something you staff against and becomes something you can design out.
The escalations were not random. Almost every one of them was born at a handoff — a place where one team's definition of "done" was another team's definition of "broken." We were not looking at a team that needed to work faster. We were looking at a system whose interfaces leaked, and every leak became a fire that someone downstream had to fight.
Why the diagnosis holds
We traced ninety days of escalations back to their point of origin and found that the overwhelming majority were seeded at three specific handoffs, long before anyone noticed a problem. That concentration is the tell. Random failure spreads evenly; structural failure clusters. When the same three seams produce most of the pain quarter after quarter, the fix is not resilience training or a bigger on-call rota — it is redrawing the seams so the defects cannot form. This is the difference between an organization that absorbs shocks and one that stops generating them.
What the engagement covers
The proposal runs ten weeks. We begin by mapping the flow of work and the definition of "done" at every handoff, then redesign those interfaces so quality is owned where it is created rather than discovered where it is expensive. The final movement embeds the change: we coach team leads through operating the new interfaces until the escalation queue falls and stays fallen. Success is measured on the client's own instruments — escalation volume, unplanned re-work, and the share of engineering time spent on planned versus reactive work — and we hold the engagement open until the trend proves durable rather than merely momentary.
From the people in the room.
Read what leaders, engineers and executives say about working with Manish and the Systems Thinking practice.
Manish gave our leadership a shared way to see the whole system. The recurring fires we kept fighting turned out to be one structural loop — once we saw it, we could finally design our way out.
Working with Manish felt less like hiring a consultant and more like gaining a thought partner. He helped us redefine our entire service flow — and say less while meaning more.
SystemsWay completely changed how I approach leadership. The systems thinking framework gave me tools to navigate complexity that I use every single day.
We'd tried every process fix on the market. Manish was the first to show us the problem lived in our structure, not our people. That reframe alone was worth the engagement.
I came to Manish to fill a few gaps and ended up rebuilding my entire mental model. He doesn't just hand you frameworks — he teaches you how to reason about systems. That shift has been the most valuable part of the work.
SystemsWay changed how I read our organization. Instead of chasing individual metrics, I can now see the structures driving them — and where to intervene for lasting change rather than a temporary bump.
Working with SystemsWay changed how our executive team makes decisions. We stopped treating symptoms and started redesigning the structures that produced them. The results compounded quarter over quarter.
Manish is not just a true thinker, but also an exceptional teacher. In every element of his job, he embraces the ideas of systems thinking, adding enormous value to every conversation and encounter.
Manish's systems lens carried straight into how we design products. Seeing the loops between teams, users, and incentives made our roadmap decisions far sharper — and far calmer.
Manish helped us see that our bottleneck wasn't effort, it was the way responsibilities were wired together. Rewiring a few of those relationships unblocked the whole team.
.png)
Manish gave me a language for what my company was actually doing wrong. Once I could see the organization as a system, the priorities that had felt impossible to rank suddenly ordered themselves.
They didn't just clarify our messaging — they clarified our business. Our onboarding, pricing, and content all finally speak the same language.
Manish's approach is genuinely refreshing. Instead of pushing us through a checklist of best practices, he starts from how our organization actually behaves. Six months in, my team has noticed the difference.
Working with Manish transformed how I approach complex problems. The systems-thinking method and hands-on sessions gave me the confidence to tackle organizational challenges I once would have escalated and hoped went away.
SystemsWay completely changed how I approach leadership. The systems thinking framework gave me tools to navigate complexity that I use every single day.
We brought Manish's systems-thinking practice to our entire team last quarter. It landed for engineers at very different levels of seniority — everyone walked away seeing our delivery process as one connected system.
Featured programs
