Before You Replace the system

Kristine Goebel
1 day ago
3 min read

"This should have worked."

Have you found yourself saying that?

Maybe you rolled out a new operating system, brought in new technology, stuck to an implementation plan, or even hired a consultant. Still, the question remains:

"Why aren't we seeing better results?"

It’s frustrating to put in so much time, money, and effort into a solution that promised results but didn’t deliver. It’s natural to question the system. But what if we’re not asking the right question? Suppose the system itself did not fail. What if it simply revealed existing issues?

Great systems don't create healthy organizations.

They reveal them.

I've worked with organizations implementing a variety of operating systems and organizational frameworks. One thing has become abundantly clear: the framework alone never determines the outcome. I’ve seen the same framework lead to very different results in different places.

One leadership team becomes more aligned, accountable, and effective.

Another team struggles with missed commitments, poor communication, frustration, and disengagement. The system is the same. The results are not.

Why is that? Because systems don’t run themselves; people do!

Every operating system, change initiative, or strategic plan ultimately depends on people making decisions, communicating clearly, managing conflict, building trust, and holding each other accountable. Those aren’t things a system can do. They're human abilities.

Reframe #1: A system usually exposes problems it didn't create.

When an organization implements a new system, existing weaknesses become more visible.

Unclear expectations, poor communication, leadership misalignment, and accountability gaps become apparent and difficult to ignore.

The temptation is to blame the system because the problems appeared after implementation. But in reality, the system may have just brought out issues that were quietly holding the organization back all along. It’s like turning on the lights in a messy room. The mess was always there, but now you can see it.

Reframe #2: Resistance isn't always the problem.

One of the first things we often hear during implementation is, "Our people are resistant to change." Sometimes that is true. More often, resistance provides valuable information. People resist when they do not understand the purpose, do not see the value, or have not been included in the conversation. Resistance usually indicates a need for clearer communication, not simply greater pressure.

Reframe #3: Every system runs on leadership.

Organizations often invest heavily in improving processes, but far fewer dedicate the same energy to developing the people responsible for executing them. No operating system can compensate for unhealthy or inexperienced leadership.

These platforms cannot replace the trust built between people. Systems provide structure, but people bring them to life. Lead well.

Before You Replace the System...

First, try asking yourself and your team some different questions:

What problem are we trying to solve?
Who on the leadership team is aligned and who is not?
What do employees understand about the purpose behind this implementation?
Have we built trust before asking for commitment?
Where are difficult conversations happening or being avoided?
When was the last time we invested as much in developing our people as we did in improving our processes/systems?

These questions mean you’ll need to look for real answers. Talk with your team, listen, and get their insights directly.

Final Thoughts

I really appreciate a great system. Healthy organizations need clear processes, defined expectations, and consistent execution.

After many years working with leadership teams, I’ve learned something important.

The organizations that achieve extraordinary results are the ones with leaders who invest just as intentionally in developing people as they do in developing processes.

Because in the end, the best operating system in the world can't outperform the health of the people responsible for executing it.

Perhaps the question organizations should ask before replacing the system is:

Is the system really the problem?

Discovery Call with Kristine

45min

Book Now