Systems Thinking.
Six smart people. Six explanations. One Problem.
Most problems inside a company come back. The late project, the team that's always underwater, the integration that stalls in month six. They come back because the fix went after the symptom, and whatever produced it never changed. Systems Thinking is how Stonehill finds it: the connections between strategy, organizational design, and operations, and how one perfectly reasonable decision turns into a problem three departments away. Change that, and the results change with it.
What is Systems Thinking?
Systems Thinking is a way of understanding a business as a set of connected parts rather than a collection of separate departments. It asks how decisions, handoffs, incentives, and information flows interact to produce the results you see today. Every organization is perfectly designed to get the results it gets. A sales team rewarded on volume will discount. A PMO measured on status reporting will produce immaculate dashboards. A team that absorbs every new request will stay underwater no matter how many people you hire. None of these are people problems. They are system problems. That's good news, because everyone in the room still has to work together tomorrow.
In practice, Systems Thinking comes down to four habits:
See the whole. Follow how work actually moves, not how the org chart says it should.
Notice what repeats. When the same problem keeps showing up, something in how the business is built is producing it.
Find the few changes that fix the most. Usually one or two decisions, handoffs, or incentives are holding everything else in place.
Think one step ahead. Ask what a change will do downstream before it ships, not after.
Strategy, structure, and operations: one system
Strategy, organizational design, and operations are usually owned by different people and fixed at different times. In practice they are one system, and most performance problems live in the gaps between them.
Strategy sets where the business is going and how it will win. Organizational design decides who owns which decisions, how teams are structured, and where accountability sits. Operations is how the work actually gets done every day: the processes, handoffs, systems, and metrics. A strategy is only as good as the organization's ability to execute it, and an organization is only as effective as the operations it runs on.
When one layer changes without the others, the system pushes back. A growth strategy launched on an org built for the old plan stalls in approval queues and unclear ownership. A reorganization that ignores how work flows adds layers and cost without adding capacity. Operations improved one function at a time get faster locally while pulling against the strategy as a whole.
Systems Thinking keeps the three aligned. We trace each strategic priority down to the decisions, roles, and processes it requires, and trace each operational problem back up to the structural and strategic choices that created it. That is how a plan on paper becomes the way the business actually runs.
Why it matters
Middle-market companies rarely fail for lack of good ideas. They stall because initiatives collide with the way the business is wired. Systems Thinking matters most in the moments when that wiring is under the most strain:
After a deal. Two companies bring two sets of processes, incentives, and cultures. Integrations that only combine org charts miss the connections that make each business run, and value leaks in the gaps.
During rapid growth. What worked at $50M breaks at $250M. Adding people to a broken structure adds cost without adding capacity.
When results plateau. Benchmarking and best practices make an operation cleaner but rarely make it different. Leverage comes from changing how the parts work together.
When initiatives compete. Too many priorities pulling on the same people creates the late projects and burnout leaders try to fix one at a time.
For CEOs, CHROs, and PE sponsors, the payoff is the same: fewer initiatives that look right on paper and fail in practice, and more change that holds after the consultants leave.
Systems Thinking and AI
AI does not fix a broken system. It runs the broken system faster. It's why so many AI pilots make a great demo and very little difference to the business.
Most companies start with the tool and look for tasks to automate. Systems Thinking starts with the system and asks where intelligence would change the outcome. The difference shows up in three ways:
Better targets. Automating one step in a slow process often just moves the bottleneck downstream. Mapping the whole flow first shows where AI removes the constraint instead of relocating it.
Better designs. AI agents now take on real work: drafting, routing, reconciling, deciding. Each one becomes a new participant in the system. Roles, handoffs, controls, and accountability have to be redesigned around it, not bolted on.
Better adoption. Tools fail when incentives, workflows, and skills stay the same. Treating AI as an organizational change, not a software install, is what turns pilots into results.
Stonehill's AI, automation, and analytics work follows this sequence: understand how the business really works, find the one or two places where AI changes the outcome, then apply the right technology, with governance designed in from the start.
The cornerstone of how Stonehill works
Every Stonehill engagement, whether it is an integration, an org design, or an AI rollout, starts from the same question: what is the system producing these results, and what would actually change it? From there, we design strategy, structure, and operations together, never one in isolation.
Start with the people doing the work. We find the person closest to the problem and ask them to walk us through a day. That's usually where the real story is.
Draw what we heard. We let the conversation run, then sketch it: how work, decisions, and information actually move, and where one reasonable choice creates a problem somewhere else. We share the drawing with a light touch. Nobody is on trial.
Fix the few things that matter most. We focus on the one or two changes across strategy, org design, and operations that fix the most, and make sure each one supports the other two.
Try it before scaling it. Small pilots and prototypes prove a change works in the real business before it gets funded everywhere.
Leave it better than we found it. Clear ownership, simple measures, and a steady rhythm keep the business improving after we're gone.