Fire the department that always causes trouble, and within six months another one starts.
At a startup, the product team keeps clashing with engineering. Leadership reads it as a culture problem, then a hiring problem, then a communication problem, and finally fires the product VP. Within six months engineering is clashing with design, so they restructure design. Now the CTO is in open conflict with three senior engineers. Every intervention solved the problem it targeted, and the conflict is as alive as ever. Why does the trouble keep moving?
Because none of those people were its source. The founding team has never agreed on whether to optimize for speed or for quality. That tension is intact, and it keeps finding new carriers. Nobody names it, because naming it means saying that the founders are the source, and that is the one acknowledgment the system cannot make.
The identified patient
Family therapists have a name for this pattern. A family that cannot face its contradictions routes them through an identified patient: the black sheep, the troubled child, the one everyone agrees is the problem. The carrier’s distress is real, but it is the family’s distress, and treating the child alone leaves the source untouched. Shadow is a family technology before it is an individual one, and what holds at the scale of a family holds at every scale above it.
In a person, the shadow is the material they cannot acknowledge, like the aggression a “gentle” person denies. In an organization, it is the contradictions the official story cannot hold: the company that professes customer-centricity while optimizing for short-term revenue, or the team that values “honest feedback” while punishing anyone who gives it. These can’t be admitted because they would expose the load-bearing story the organization tells about itself. So the material is exported to whoever is most visible and least protected. The product VP “couldn’t work with engineering.” The sales team “overpromises.” In each case the dysfunction is real, but it belongs to the organization, and the carrier is doing what the system set them up to do.
Exporting also pays. In times of stress, two factions can stabilize their alliance by jointly focusing on a third. At the startup, the founders and engineering found common cause in fixing the product team, and both got what they needed: the alliance, the legitimacy, the story of competence. The underlying tension carried on undisturbed.
Why it gets harder to see
You might expect an organization to learn from the second or third carrier. Usually it learns less over time, because of who leaves. Under the Dead Sea Effect, the people most capable of naming the shadow, the ones who see the dysfunction clearly enough to describe it, are among the first to go, since they are the quickest to conclude that their clear sight isn’t welcome. The people who remain aren’t incapable of perceiving the shadow, but they have survived by not perceiving it. So the shadow grows as the population able to name it shrinks, and each departure looks like the loss of a difficult employee when it is really the loss of someone who could see.
The usual fixes make it worse in a quieter way. Making a problem legible, by putting a metric on it, naming it or building a process around it, makes it look addressed because it is now managed. The problem department gets a performance improvement plan; the culture gets a culture committee. The shadow hasn’t been dissolved. It has been made manageable, which means it can now continue with institutional blessing.
That is the core of it: organizational dysfunction is structural shadow: contradictions the official narrative cannot acknowledge, routed through carriers because the system has no mechanism for integration. Culture programs produce a better story about the shadow without touching the contradiction underneath.
Naming the contradiction
What would work at the startup is a different kind of legibility, one that names the contradiction instead of measuring the carrier: “We cannot optimize for speed and for quality at the same time at this stage, and we have been pretending we can.” That sentence sounds like honesty, but it is also a political act, because it implies that the story holding the company together is a fiction. The only intervention that dissolves organizational shadow is the one that names the contradiction the shadow is carrying — and that intervention is always, structurally, a threat to whoever benefits from the contradiction remaining unnamed. This is why the consultant who names the shadow accurately is rarely hired again, and why the employee who names it too clearly ends up among the departures.
Naming is only the first step. The individual cure for shadow is to give the suppressed trait a form, so it can be wielded deliberately instead of acting from behind. For the startup, that means choosing speed or quality as primary and building the organization around the choice. Some people will turn out to have been building the wrong thing and will need to leave, and the story that “we do both” has to retire. The contradiction doesn’t disappear, but it stops picking carriers and becomes a constraint people can see and design around. Organizations that manage this almost always have someone in power who was willing to name the shadow in a room where naming it was expensive.
Which is why it rarely happens from within, and why the shadow tends to be clearest to whoever is carrying it. The fired product VP probably understood the founders’ conflict better than anyone left in the building. The harder question is how an organization could learn to hear that account before its author is shown the door.