The Operating System Deception
Your Operating System is Deceiving You
You bought the system because something was broken. Meetings ran long. Priorities slipped. Accountability felt like a ghost in the building. So you implemented the framework (such as, EOS®, Scaling Up®, OKRs, Gazelles®, pick your system). You ran the rocks, the scorecards, the weekly meetings, the issue lists, one page plan, etc. And things did get better. Calendars filled up. Reports came in on time. Numbers showed up on dashboards. Order came from chaos.
That's the trap.
Order is not the same as health. Activity is not the same as accountability. And efficiency, no matter how clean it looks, is not leadership.
Here's what most owners and CEOs miss eighteen months into their operating system: The dashboard is green, the meetings end on schedule, and the team still doesn't trust each other. The same problems that pushed you toward a framework in the first place are now hiding behind underneath paperwork. Your operating system has become the ‘elephant-in-the-room’ unrecognized for the problems it is creating for you.
I'm not anti-operating-system. I've spent nearly two decades watching these tools pull closely-held businesses out of chaos. I was a Certified EOS Implementer®. They gave structure where there was none. They forced conversations that needed to happen. They took a founder's instinct and translated it into something a team can follow. That's real value, and I won't pretend otherwise or demean those benefits.
But here is the deception: The system was never designed to be your leadership model. It was never designed to be your accountability model, despite in many cases, they being sold as if they were. It was built to organize work. Somewhere along the way, owners started treating it, perhaps subminally, like leadership itself, like running the rituals was the same as leading the company. It isn't and never will be.
Watch what happens in a typical weekly leadership meeting after the framework has been in place for two to three years. People come in with their issues list. They march through, efficiently, the cadence. They follow the clock. They check the boxes (‘done, not done’). Someone gets called out. Someone gets defensive. Everyone leaves with a task list and also with a low-grade case of resentment. The numbers improved. The culture didn't. Efficiency is not an attractive culture, drawing no one in to believing that it is to be praised. “Yippee, I work for a very efficient company!” It’s activity dressed up as outcomes.
This is the part nobody warned you about: A well-run system can quietly produce compliance accountability instead of real accountability. People learn to perform the framework. To game it. They learn what looks good on the scorecard. They stop telling the truth in the room because the room is no longer safe for truth, it's a performance stage for status updates.
The appearance of order is not the same as the presence of order.
What's Really Happening Beneath the Forms:
The reports look fine. Revenue is on plan. The scorecard is mostly green. Your operating system tells you the company is healthy.
Your best people would tell you something different; if you asked and if they trusted you with the answer.
This is the gap between the system and the people. The system shows you the activity. The spaces, that is, between people, between leaders and teams, between what's said and what's meant, show you the truth. And in a lot of companies running a strong operating system, the spaces have gone cold and rigid or not recognized at all.
Here are the four defining gaps I see, again and again, in client after client.
Empathy has collapsed. The framework rewards crisp updates and measurable progress as activities, with the result the harder, slower work of understanding each other gets pushed aside. People stop asking why a colleague is struggling. They just note that their own rock is at risk and move on. Over time, the team forgets how to be human with each other. Activity is the focus.
Conflict has gone underground. A good system should surface tension and resolve it. What happens is that disagreement gets routed into the issues list, where it gets "solved" in seven minutes by the loudest person in the room. The unresolved part, e.g., the part that needed real conversation, human conversation, goes home with people. It shows up later as turnover, quiet quitting, or a two-week notice from your strongest manager.
Accountability has flipped from commitment to compliance. The framework asks: Did you do what you said? That's a fine question. But it's not the appropriate, more meaningful question. Real accountability also asks: Did we do the right thing? Did we tell the truth? Did we own the outcome/results, not just the activity? When the answer to "done?" is ‘Yes’ but the work didn't move the business, the system keeps scoring it as a win. At that point, the system is the focus, the rationale for work and existence. That's not accountability nor outcomes. That's performance theater.
Purpose has been swapped for process. People came to your company for a reason. They wanted to build something that mattered. Eighteen months into a tightly-run operating system, many of them can recite the priorities but can't tell you why the work matters. The cadence, particularly the focus on the short-term (two week To-Do’s, weekly scorecard, quarterly rocks) all chipped away at the meaning of Why we work, our passion, our purpose.
None of this shows up in the system; it’s not on the scorecard. None of it triggers an alert. The system is doing exactly what it was built to do, that is to organize activity. It was never going to surface trust, truth, or human connection. Those live somewhere else.
Beyond the System — Where Real Leadership Lives
So your operating system is doing its job. And your culture is still in trouble. What now?
Stop asking the system to do work it was never built for. Frameworks organize activity. They don't build trust. They don't surface truth. They don't restore meaning to people who have stopped feeling it. If you keep adding more priorities, more scorecards, and more meetings to fix a culture problem, you'll just get a tidier, tighter version of the same problem and more compliance accountability.
Look at what the framework can't see. I call this truth architecture, the deliberate design of how truth moves through your company. Truth architecture is not a meeting cadence. It's the set of conditions that determine whether people will say the hard thing out loud without fear. It includes who has permission to challenge whom, how disagreement is treated, and whether the leader can hear bad news without flinching. No operating system on the market will build this for you. You build it by how you behave and lead, every day.
Develop conflict intelligence on your leadership team. Most teams don't have a conflict problem, they have a conflict avoidance problem dressed up as a process. Conflict intelligence means a team can disagree directly, stay in the room, and come out with a better answer than any one person walked in with. That's leadership work which cannot be subsumed into an operating system framework.
Take the generational compact seriously. Your younger employees are not asking for ping-pong tables or snack room. They are asking whether the work matters, whether their voice counts, and whether the company will treat them like adults. A well-run operating system that focused on short-term activity and ignores this question will lose them, quietly and steadily, while the dashboard and rocks stays green.
Recover the purpose imperative. Why does this company exist? Whose life is better because you do the work you do? When people can answer those questions in their own words, accountability stops being something you enforce and starts being something they own. Compliance becomes commitment. The framework becomes a tool again, instead of a substitute for leadership.
None of this requires you to throw out your operating system. Keep it. Use it well. But stop letting it deceive you into thinking the rituals equal results, that short-term activity equals long-term change, and that it is a leadership model. It is not. You are.
The numbers on your dashboard are real. So is the work happening underneath it. The dashboard you can manage with an operating system. The work underneath, you have to lead.
That's the part the framework was never going to do for you. That's the part only you can do.
Just published, Accountability Shift: Tips, Traps, and Techniques, proves that the harder you push for accountability, the less you get and gives leaders a practical replacement that works. It is for CEOs, business owners, executives, leaders at every level, HR and OD professionals, management consultants, and executive coaches. Buy it here.
Norman’s previous book, Supercharge: A New Playbook for Leadership provides the full methodology for leaders who are ready to build organizations that adapt, respond, and perform in any conditions. Find it here.
David Norman works with business leaders who are ready to build organizations capable of performing not just when conditions cooperate but especially when they do not. Learn more at https://www.davidtnorman.com/resources.
Subscribe to this Substack at DavidTNorman Newsletter; it’s currently free and will remain so for early subscribers.
