Solution pollution is when a solution creates more or bigger problems than the original problem it was supposed to solve. Most organizational dysfunction is not the absence of solutions — it is the accumulation of solutions that each created new problems, which were solved with more solutions, until the solution layer is thicker than the original problem. You cannot plan your way out of an existential crisis.
Simple Picture
A team adopts a new technology to solve integration problems. Every other team delegates their integration work and blocks on the new technology team. Now one team does all the work, and every other team has a convenient excuse for not delivering. The solution (centralize on new tech) created a bigger problem (single point of failure with no capacity) than the original (distributed but messy integration). The meta-problem: nobody has the authority or incentive to admit the solution was worse than the disease.
The Antipattern Catalog
The Specificity Trap. Excess design meant to reduce uncertainty increases estimation errors when tolerances are exceedingly exact. Like low-tolerance machined parts that get exponentially more expensive, over-specified organizational processes consume exponentially more energy as precision increases. The constraint is not the uncertainty — it is the cost of eliminating it. Some amount of uncertainty is cheaper to live with than to remove.
Code Slums. A tragedy of the commons where no one feels responsible for the shared environment. Everyone is self-focused because of a defensive or scarcity mindset. The slum is not caused by bad engineers — it is caused by an environment where cleaning up after others is not rewarded and making a mess has no consequences. Even God cannot refactor — the giraffe’s recurrent laryngeal nerve loops pointlessly around the aorta because evolution cannot redesign load-bearing systems. Organizations have the same problem: critical legacy code is impossible to clean up precisely because it is critical.
Inverted Hierarchy. When quality of talent and ability decreases as you go up the organizational hierarchy. The Dead Sea Effect produces this over time: the most capable people at each level leave, and what remains is promoted. Eventually the people making decisions are the ones least equipped to make them, but most skilled at appearing to make them. The fog is thickest at the top because individual contribution is most invisible there.
Orphaned Responsibilities. These accumulate like dark matter because of the moral hazard of shooting the messenger. If raising a problem means you own the problem — or worse, get blamed for it — nobody will raise problems. Unowned work grows silently until it causes a crisis. The Copenhagen Interpretation of Ethics deepens this: when you observe or interact with a problem in any way, you can be blamed for it. Even if you make it slightly better. This incentivizes everyone to look away, which is exactly how orphaned responsibilities become catastrophic.
Sweeping the Ocean. It is not a good idea to fight a force of nature. Some organizational problems are structural — products of incentives, market forces, or human nature — and no amount of heroic effort will fix them. Recognizing an unfixable problem is not giving up. It is the precondition for redirecting effort toward something that can actually change.
The Recursive Helplessness Trap
The problem occurs recursively upward: each layer of management feels pressured and helpless, squeezed between the layer above and the layer below. Every opportunity to shield oneself from consequences is taken, creating a leadership vacuum and an organizational culture of cowardice.
Most work becomes optics — 100 hours of visible busywork preferred over 1 hour of genuine thinking. The sabotage is not intentional; it is the natural equilibrium of a system where visible effort is rewarded and invisible results are not. The person who quietly solves a hard problem in an afternoon gets less credit than the person who visibly struggles with a simple problem for a week.
Helping can generate resentment and backstabbing — you do something for someone and don’t even know what you did wrong. In a zero-sum environment, competence is threatening. A disrupted chain of trust among management executives and cancelled projects causes a scramble for visibility, and in that scramble, making simple things convoluted and complex works as a smokescreen. Team growth becomes the goal because larger teams mean more organizational power, even if the additional complexity demoralizes the individuals doing the actual work.
Responsibility hot-potato games are a drag. Nobody wants to own the problem because ownership means accountability without authority. The result: cut twice, measure never. The stable equilibrium of the hot-potato game is CYA culture: nobody catches the potato, but everyone keeps receipts proving they saw it in the air.
Centralization and Narrative
Centralization and legibility are tolerated to the extent that they create agency and make others feel empowered. The moment centralization stops empowering people and starts extracting control, resistance begins — but resistance in organizations is passive (departure, disengagement, quiet quitting) rather than active.
Narratives must be inclusive. A narrative like “React will solve all X problems” naturally creates non-inclusive anti-narratives like “Ruby devs are the problem.” No one buys a technology — they buy a way of doing things. The technology is the visible artifact; the real purchase is the organizational identity that the technology signals.
Everyone would love for you to make some decisions about how to do things and bring some consistency, as long as you choose their current preferred way of doing things.
Most organizations do not have people with the right incentives and vision to push for real change. Getting only part of the formula right leads to no outcome at all. Success becomes about signaling and calling it a success by not measuring any outcomes. The entropic preference for accountability over learning ensures that measuring outcomes is actively avoided, because measurement might reveal that the solution was worse than the problem.
It is not possible to hold teams or individuals accountable to a higher standard than an organization is willing to enforce. To respect history, shame is not a strategy to create change in load-bearing functions — their ossification is a result of their criticality. You cannot code your way out of a problem that is primarily about meetings and mindshare. Vice versa, meetings and mindshare cannot solve a problem that requires code.
Dimwit / Midwit / Better Take
The dimwit take is “bad organizations are caused by bad management — get better leaders.”
The midwit take is “organizational dysfunction is a coordination problem that can be solved with better processes and clearer accountability.”
The better take is that most organizational dysfunction is solution pollution — the accumulation of solutions that each created new problems, layered on top of each other until the solution stack is heavier than the work itself. The entropic organization does not fail because it lacks solutions. It fails because it cannot stop solutioning. Every problem gets a process, every process creates overhead, every overhead gets optimized with another process. The organization that can delete a solution — that can say “we will live with this problem because the solution is worse” — is rarer and more valuable than the one that can add one.
Main Payoff
“Enterprise customers” is not an excuse to build complicated crap slowly. This is the load-bearing excuse of every dysfunctional engineering organization: the work is inherently complex, the domain is inherently difficult, the customers are inherently demanding. Some of that is true. Most of it is camouflage for solution pollution that nobody has the incentive to clean up. The person who sets up as arsonist and firefighter — creating the crises they heroically resolve — is rewarded by a system that cannot tell the difference between genuine complexity and manufactured complexity. Most people do not come into work serving a customer or a user. They serve some process. Working extra hard or extra smart does not create any fundamental new value in such a world. In fact, in a bizarre way, it is the opposite.
References:
- Workplace observations, various organizations