Why Broken Systems Stay in Place Even When Everyone Sees Them
- Maria Mor, CFE, MBA, PMP
- 2 hours ago
- 8 min read
Most business owners I speak with are not blind to the problems in their operations. They know the approval process takes too long. They know the handoff between departments creates rework. They know the reporting their team produces every week does not drive any actual decisions. They have known these things for months, sometimes years.
The system stays broken anyway.
That is not a mystery rooted in incompetence. It is a pattern with a name, a mechanism, and a financial consequence that compounds the longer it goes unaddressed. Understanding why broken systems stay in place is the prerequisite to doing anything meaningful about them.
Table of Contents
The Problem Is Not Awareness
The assumption buried inside most operational improvement efforts is that broken systems persist because no one has identified them yet. So companies run diagnostics. They hire consultants. They conduct employee surveys. They generate reports.
Then the reports sit in a shared drive, the consultants leave, and the system continues running exactly as it did before.
Awareness is not the bottleneck. The bottleneck is what happens after someone sees a problem and decides whether or not to say anything about it.
In organizations where silence has taken root, that decision is already made before the conversation starts. The team member who notices the gap does a quick internal calculation: the cost of speaking up versus the cost of staying quiet. When the environment has taught people that raising problems leads to being labeled difficult, or that nothing changes anyway, staying quiet becomes the rational choice.
Research on organizational behavior has documented this pattern across industries and company sizes. According to Ethical Systems, employees are significantly less likely to voice concerns when they perceive that doing so will damage relationships or produce no meaningful response. The silence is not passive. It is a learned, active behavior that employees reinforce in one another over time.
That reinforcement is exactly what makes why broken systems stay in place such a durable problem.
What Organizational Silence Actually Looks Like
Organizational silence is not a single event. It is a climate, and it builds gradually through small, repeated signals.
A team member points out an inefficiency in a Monday meeting. The response is defensive. No follow-up comes. The next time something is broken, that person says nothing. A colleague who watched the exchange files the lesson away. Within a few months, the unspoken agreement is that problems are observed but not named.
This shows up in predictable ways inside companies with 10 or more people:
Meetings run long without producing decisions, and the decisions that do get made get quietly undone afterward by whoever holds the informal authority.
Workarounds multiply. Every department has at least one process that exists entirely because a formal system failed and no one fixed the original failure.
New hires learn within their first 90 days what can and cannot be said, and to whom. That knowledge is never written down.
Problems that surface in one meeting reappear in the next without resolution, until they stop being raised at all.
Leaders interpret the absence of complaints as evidence that things are working.
That last point carries particular weight. When leadership reads silence as satisfaction, the feedback loop breaks entirely. The organization loses its ability to self-correct. Problems do not disappear because they go unspoken. They accumulate.
Revenue comes from the front office. Profit is protected in the back office. When silence is the operating norm in the back office, the leaks that drain profit become invisible by design.
The Self-Deception Layer
Physicist Richard Feynman, in his 1974 address "Cargo Cult Science" at Caltech, offered a principle that applies here with uncomfortable precision: you must not fool yourself, and you are the easiest person to fool.
The broken system persists not only because teams go quiet, but because the people closest to the system have the hardest time seeing it clearly. This is not a character flaw. It is a structural condition.
A founder who built the approval process in 2020 when the company had eight people does not experience it as broken. They experience it as familiar. Familiarity reads as function. The process that now creates a four-day bottleneck for a team of 40 still feels to them like the process that worked, because they remember it working. What has changed is everything around it: the team size, the volume, the complexity of decisions. The process itself never got updated.
The same dynamic applies to leaders who inherited broken systems from predecessors. Changing the system means implying that something was wrong. In organizations where accountability moves upward instead of outward, that implication is enough to keep the system exactly where it is.
This is the self-deception layer: the gap between what a business owner believes about their operations and what is actually happening inside them. No internal survey closes that gap. No software implementation closes it either. The owner cannot audit their own blind spots. Not because they lack capability, but because proximity is structural. You cannot see what is broken in a system you built and live inside every day.
Why Broken Systems Stay in Place Inside the Numbers
The financial consequence of organizational silence is not abstract, but it rarely shows up as a single line item. It distributes itself across the income statement in ways that look like other problems.
Rework costs show up as labor expense. Bottlenecks in approvals slow revenue cycles, extending the time between service delivery and invoice collection. Workarounds require additional headcount to manage processes that a functioning system would handle automatically. Exit interviews from strong employees who grew frustrated with broken processes show up as recruiting costs.
None of these is labeled "we did not fix this process." All of them are funded by profit.
There is also a compounding effect that rarely gets calculated. The longer a broken system stays in place, the more infrastructure gets built around it. Teams develop tools to work around it. Training programs teach new hires how to navigate it. Tribal knowledge accumulates in the people who know where the edges are. When the system eventually does get fixed, there is an entire ecosystem of workarounds that also has to be dismantled.
Companies that address operational problems early spend significantly less on the fix than companies that wait until the system is load-bearing and surrounded by workarounds. The silence tax is real. It compounds quarterly.
The Question That Changes the Calculation
The starting point is not a process audit or a workflow redesign. It is a single question applied consistently: what in this company are we not allowed to question?
That question surfaces what silence has buried. It also changes the calculation for everyone in the room. When leaders demonstrate that naming a problem will not result in punishment or dismissal, the incentive structure shifts. Silence loses its protective function.
The companies I have seen get this right share one characteristic: the questioning is protected at the leadership level, not delegated to a survey or an anonymous submission box. When a founder actively names a process that is not working, they give the rest of the team permission to do the same.
That permission has to be demonstrated, not announced. A policy that says we value transparency does nothing if the last person who raised a concern was sidelined. Culture is not what is written on the wall. It is what happened the last time someone spoke up.
Business Process Improvement is the work that follows from that permission. Once the silence breaks, the gap between what the system looks like on paper and what it does in practice becomes visible. That is the gap where the operational work happens.
Take the CEO Time Audit
If you are reading this and recognizing a pattern in your own operations, the right first step is not a full systems redesign. It is an honest accounting of where the operational bottlenecks are actually costing you time and what that time is worth.
The CEO Time Audit is a free tool that walks you through exactly that. It takes about 15 minutes and identifies where your hours are going, where decision-making is creating delays, and what those delays are costing the business.
Broken systems stay in place partly because no one has connected the time being lost to a dollar amount. The audit makes that connection explicit.
Ready to Talk About What Is Staying in Place in Your Business?
If the pattern described in this post is recognizable in your own operations, the next step is a conversation. Not a sales pitch. A direct look at what is broken, what it is costing, and what fixing it actually requires.
Contact Praxis Hub to start that conversation.
Frequently Asked Questions
Why do broken systems stay in place even when everyone sees the problem?
Broken systems stay in place because seeing a problem and being willing to name it are two different things. In most organizations, employees have learned through observation that raising concerns produces negative outcomes: being labeled difficult, damaging relationships, or being ignored entirely. Research on organizational behavior has documented that the majority of employees have withheld concerns from leadership even when they believed those concerns were important. When silence becomes the norm, operational problems persist regardless of whether anyone is aware of them.
What is organizational silence and how does it affect business operations?
Organizational silence is the pattern that develops when employees consistently choose not to voice problems, concerns, or observations about how the business operates. It is not a single decision but a climate that builds over time through repeated signals about what is and is not safe to say. The operational effect is that leadership loses access to accurate information about what is working. Problems go unaddressed. Workarounds accumulate. The cost distributes itself across the income statement as labor inefficiency, extended revenue cycles, and higher turnover.
How does a business owner's proximity to their own systems create blind spots?
A business owner who built or inherited a system experiences it as familiar, and familiarity is easily mistaken for function. The process that worked when the company had ten people does not automatically break the day the team hits forty, but it gradually creates friction, bottlenecks, and workarounds that insiders stop noticing. This is not a failure of intelligence. It is a structural limitation. The people closest to a system are the least equipped to see where it is failing because they have adapted to its constraints without realizing it.
What is the financial cost of a broken system that stays in place?
The financial cost is rarely labeled directly but distributes across the income statement in predictable ways: rework costs in labor expense, extended revenue cycles from approval bottlenecks, additional headcount to manage workarounds, and recruiting costs from turnover driven by operational frustration. There is also a compounding effect. The longer a broken system stays in place, the more infrastructure gets built around it, which increases the cost of fixing it later. Companies that address operational problems early spend significantly less on the fix than those who wait until the system is embedded in daily operations.
What is the first step to addressing organizational silence in a business?
The first step is asking one question consistently: what in this company are we not allowed to question? That question surfaces what silence has buried. The follow-on step is demonstrating at the leadership level that naming a problem will not result in punishment or dismissal. When the founder or operator actively names a process that is not working, they give the rest of the team permission to do the same. That permission has to be demonstrated through behavior, not announced through policy. A free CEO Time Audit can help identify the specific operational areas where silence may already be costing you time and money.
For more on this series, read:
The Back Office Brief
Get a weekly insight connecting back office operations to profit. Delivered every week, free.
Comments