The 200-person wall — restructuring an org that outgrew its process
The organization that brought us in had never missed a release in its first four years. Then it crossed two hundred people, and the machine that had felt effortless began to seize. Roadmaps slipped by quarters. The same decisions were re-litigated in three different meetings. Senior engineers who had once shipped weekly now spent their days in coordination, and the founders could not name a single thing that had broken — because nothing had. The parts were all still excellent. What had failed was the way they fit together.
This is the pattern SystemsWay exists to name. A group of sharp analytical minds builds a product that transforms its customers' lives, then turns that same analytical reflex on its own operation — optimising each team, each tool, each process in isolation — and is bewildered when the whole slows down. Analytical thinking decomposes; it is superb at the customer's problem and blind to the organization's. This engagement did not add process. It replaced the way the leadership team saw the company: not as a set of teams to be tuned, but as a single living system whose behaviour emerges from its structure.
We did not find a broken team, a bad hire, or a missing tool. We found a structure that made coordination everyone's second job and no one's first. The intervention was not to work harder inside that structure — it was to change it, so the coordination the company needed became a property of how the work was arranged rather than a tax on the people doing it.
Why the diagnosis holds
The evidence was in the flow of decisions, not the org chart. We mapped every cross-team dependency that had touched a slipped deliverable over two quarters and found that four-fifths of the delay traced to a handful of decision points where authority and information sat in different places. That is a structural signature, not a performance problem — no amount of individual effort closes a gap between who knows and who decides. Across the fifty-plus organizations we have worked with, the wall is almost always built from exactly this material.
What the engagement covers
The proposal is a twelve-week engagement in three movements: a structural diagnosis that maps how decisions, information, and authority actually flow; a redesign of team boundaries and decision rights so the common case needs no meeting; and an embedded transition where we coach the leadership team through running the new structure until it holds without us. We measure success against the organization's own numbers — cycle time, re-work, and the share of decisions resolved at the first table — and we stay until the change has taken, which is why ninety-four percent of the leaders we partner with are still practising it a year on.
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
