Rewiring the operating model — from local optima to one system
Every team in this organization was succeeding, and the organization was failing. Sales hit its numbers by promising delivery dates the delivery team could not honour. Delivery protected its numbers by refusing scope the product team had already sold. Product optimised for launches that support was not staffed to absorb. Each team was rational, measured, and rewarded on its own terms — and the sum of all that local excellence was an organization quietly at war with itself. The leadership team kept asking which department was the problem. The honest answer was: none of them, and all of them, because the problem lived between them.
This is the most expensive failure mode in a well-run company, precisely because every part looks healthy under inspection. Analytical management is built to optimise the parts; give it a whole that is underperforming and it will tune each component harder, deepening the very misalignment it is trying to fix. Systems thinking starts from the opposite end — with the behaviour of the whole — and asks what set of incentives, boundaries, and shared goals would make each team's local best also the organization's best. When the parts are pulling apart, you do not push them harder. You change what they are pulling toward.
Nobody in the company was acting in bad faith. Each team was doing exactly what its metrics told it to do — and those metrics, added together, described an organization no one would have chosen to build. We were not there to fix a department. We were there to redesign the incentives so that doing right by your own team and doing right by the whole stopped being a trade-off.
Why the diagnosis holds
We mapped each team's goals against the organization's stated outcomes and found direct contradictions at four of the handoffs between them — places where one team was measured on precisely what made another team's job impossible. Conflict that shows up reliably at the same seams is not interpersonal; it is designed in, however unintentionally. That is good news, because a misalignment you can locate in the structure is a misalignment you can engineer out — which is the work behind every one of the fifty-plus transformations we have led.
What the engagement covers
The proposal is a fourteen-week operating-model redesign. We begin by making the cross-team contradictions explicit — the exact metrics and boundaries where local success buys global failure. We then redesign incentives and shared goals so the common path for each team also serves the whole, and we rewire the handoffs where the conflicts were born. The final movement embeds the model, coaching the leadership team through running it until the teams stop pulling apart. Success is measured on end-to-end outcomes the whole organization shares, and we hold the engagement open until those outcomes, not the departmental ones, are the numbers that move.
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
