Leaders build systems for a simple reason: we want the business to run better and for people to experience less friction in their roles.

As organizations grow, instinct and human glue are no longer enough. What once worked through speed, proximity, and a handful of trusted people begins to strain under the weight of scale. When this happens, communication becomes harder and decisions slow down. What once ran smoothly is now breaking down, creating frustration and friction. Systems promise a solution because they bring structure to complexity and create clarity in how work moves through the organization.

At some point in every growing company, systems become non-negotiable. But a disconnect quietly emerges once those systems are in place; one that leaders rarely talk about, even though many of us experience it: over time, the systems designed to support the strategy can begin to shape it instead.

And if we are not paying attention, the company slowly begins to protect the system rather than pursuing the outcome the system was originally built to support. I recently saw this dynamic play out inside my own company.

When the Process Becomes the Constraint

A few weeks ago, my sales and operations teams were discussing how we should position inventory across our organization. Our headquarters is in Durango, Colorado, yet most of our customers are not anywhere near Durango. Over the past several years, we have opened branch locations closer to our customers because proximity matters. When customers need equipment, they need it quickly.

From a strategic perspective, the decision seemed obvious: we should hold more finished goods closer to those branch locations so we can serve customers faster. But the moment we started talking through the operational implications, the conversation shifted.

Our forecasting and inventory systems were built around a headquarters-centered model. Final assembly in Durango drives how inventory flows throughout the organization. Moving finished goods into branch locations would disrupt that system and increase inventory levels, which, of course, no one wants.

The team's response was thoughtful and completely reasonable: “We can do it, but it will take a lot of work.” That moment captured the tradeoff many scaling organizations eventually face. The system that once helped the company succeed had quietly become a constraint on what the company could do next.

The question then became, “Do we adjust the strategy to protect the system, or do we redesign the system to support the strategy?” There is no formula that answers that question, but it does require judgment.

How Systems Quietly Take Control

Most leaders do not notice when systems begin influencing strategic decisions because the shift happens gradually. At first, systems simply make the business run more smoothly. A process clarifies how work moves through the organization, a workflow reduces friction, and a piece of technology removes manual effort that once consumed valuable time. Because the system works, people begin to rely on it. Roles form around it, metrics are built to measure it, and teams learn how to operate within its structure.

Over time, what started as a helpful tool becomes the default way of working, and eventually the safest path forward. Without realizing it, the organization begins making decisions that protect the system rather than asking whether the system still serves the strategy.

So, when someone proposes a new direction, people push back with responses we’ve all heard before. “The system was not designed for that.” “The process will break.” “The technology will not support it.” “Changing course will take too much effort.”

Sometimes those concerns are legitimate and need to be addressed. Operational complexity is real, and responsible leaders must respect the costs and disruptions that change can entail. But sometimes the root of what’s really going on is more subtle. The organization has grown comfortable operating within the system it built and protecting that system now feels safer than questioning whether it still serves the business.

That is the moment when leadership matters most. Why? Because someone must decide whether the company will protect the process or pursue the strategy.

Strategy Must Lead the System

As companies scale, leaders must continually return to a principle that is easy to forget amid operational complexity. Systems exist to serve strategy. Strategy does not exist to serve systems.

This does not mean leaders ignore operational reality, as every strategic shift carries tradeoffs. Some changes require enormous effort to implement, and some systems are deeply embedded and difficult to redesign. Let’s face it, not everything is easy to change, even when we have a growth mindset.

But when organizations begin making decisions primarily to protect the current system, something important has shifted. The company becomes optimized for yesterday’s model instead of tomorrow’s opportunity. Great leadership requires the willingness to pause and ask a deceptively simple question: “Are we protecting the system, or are we pursuing the strategy?”

What Actually Breaks in Most Systems

In a recent Reflect Forward conversation, I explored this tension with Val Coin, a systems advisor and founder of Via Technology, based in Australia. Val has led more than 150 digital transformation projects across organizations of all sizes, and her perspective reinforced something I have intuitively sensed, and perhaps you have, too: most companies believe they have a technology problem when, in reality, they almost always have a systems problem.

Val approaches systems through three interconnected elements: people, process, and technology. Organizations often focus first on technology because it feels tangible. A new platform or tool promises a quick solution. But technology rarely addresses the real issue.

In Val’s experience, breakdowns almost always begin with process and alignment. Leaders design processes around how they believe people should behave rather than how people actually behave. The system assumes perfect discipline and flawless execution.

But here’s the thing: real organizations do not work that way.

Val encourages leaders to design processes around the path of least resistance while still achieving the intended outcome. Humans naturally gravitate toward the simplest path available, and if a system ignores that reality, workarounds appear almost immediately. Once workarounds appear, the system begins to fracture.

Ownership Is What Makes Systems Work

Another insight Val shared during our conversation was the role ownership plays in successful transformation. Organizations often bring in outside advisors to help redesign systems, and that expertise can be incredibly valuable. But when leaders allow responsibility to shift entirely to the consultant, the transformation rarely sticks because people don’t feel a sense of ownership. Employees inside the organization must be involved in building the system they will ultimately operate.

When teams participate in designing the process, they understand why it exists and how it is meant to work. They develop the judgment needed to refine and improve it over time, and, perhaps most importantly, they feel accountable for its success. Without that sense of ownership, even the best system struggles once it meets the reality of day-to-day work.

The Ongoing Work of Leadership

The longer I lead, the more I realize that systems are never truly finished. Markets evolve, strategies shift, and technology continues to change, which means a process that once worked beautifully can begin revealing its limits faster than we expect. What supported growth in one season of a company’s life may not serve the next.

That is why leadership requires continual reflection, not only on strategy and culture but also on the invisible architecture that holds the organization together. Systems shape how decisions are made, how work flows, and how teams collaborate, even when we are not actively thinking about them.

Eventually, every company reaches a point when the system that once helped it grow begins to hold it back. When that moment arrives, the real question leaders must ask is not operational. It is philosophical. “Are we protecting the system, or are we still building the company we set out to create?”

Continue the Conversation

If this reflection resonates with you, I invite you to listen to or watch the full Reflect Forward conversation with Val Coin, where we explore in greater depth how systems, strategy, and leadership intersect as organizations scale. Many of the ideas behind this discussion are also explored in my book The Ownership Mindset, which focuses on the role leaders and teams play in creating accountable, high-performing cultures. 

I am currently working on my next book, Talk With Trust, which examines how leaders build environments where honesty, accountability, and trust can coexist. And if these themes feel relevant to your organization or leadership community, I would welcome the opportunity to continue the conversation through a keynote or leadership session with your team.