The decision bottleneck — rebuilding the leadership layer
The company had grown from twelve people to two hundred on the strength of one exceptional founder's judgement. That same judgement had become the ceiling. Every decision of consequence — a pricing change, a key hire, a shift in roadmap — waited in a queue for a single desk, and the queue only lengthened as the company grew. The founder was working eighty-hour weeks and was still, structurally, the slowest part of the business. The instinct in the room was to clone the founder. The real work was to build an organization that no longer needed one.
A bottleneck at the top is rarely a talent problem in the layer below; it is a capacity problem in how the organization holds decisions. Analytical leaders try to solve it by delegating tasks — handing out the work while keeping the judgement — and are then frustrated when everything still comes back to them for a verdict. Systems thinking treats decision-making itself as the thing to be distributed: not the tasks, but the authority, the context, and the shared frame that let a decision be made well without the founder in the room. You do not relieve a bottleneck by asking it to route faster. You relieve it by giving the system somewhere else for decisions to go.
The people around the founder were not less capable. They were less equipped — starved of the context, the criteria, and the explicit permission that would have let them decide. Every judgement that flowed upward was a judgement the structure had quietly told them was not theirs to make. Change that structure, and the capacity was already there, waiting to be used.
Why the diagnosis holds
We logged a month of decisions and asked, for each, why it had reached the founder's desk. Almost none arrived because they genuinely required the founder's unique knowledge; they arrived because the criteria for deciding lived only in the founder's head and the authority to act had never been made explicit. That is a design flaw you can name and remove. It is also why the organizations we partner with retain their leaders — ninety-four percent are still practising a year on — because rebuilding the layer below the founder is what makes the growth survivable for everyone in it.
What the engagement covers
The proposal is a sixteen-week leadership programme in three movements. First, we surface the decision criteria that currently live only in the founder's judgement and make them explicit and teachable. Second, we redraw decision rights so the leadership layer owns whole classes of decisions outright, with the founder setting direction rather than adjudicating cases. Third, we coach that layer through real decisions until confidence and consistency hold without escalation. We measure the share of consequential decisions resolved below the founder, and we stay until that number moves and stays moved.
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
