Some of the most significant shadow work I have facilitated has happened in leadership teams that would never have used the word “shadow”, and would have rejected the framing if I had offered it.
This has been one of the more important lessons of the last decade of the work. The language of depth psychology is useful for practitioners. It is often counterproductive in rooms that associate the vocabulary with therapy, with softness, or with things they believe do not belong in the commercial conversation.
When the label would close the room, the practice can still be offered. In the language the room can actually hold.
A team that did the work without the vocabulary
The team in question was the senior leadership of a manufacturing business — seven people, most of whom had come up through operations, engineering, and commercial functions. The referring issue was not an obvious call for depth work. It was a persistent pattern of the same problems appearing in their monthly reviews, the same conflicts re-emerging between the same two members, and the unmistakable sense that the formal agenda of every meeting was secondary to an invisible agenda that everyone could feel but no one addressed.
The HR Director who brought me in had considered, and rejected, several more standard interventions. A team effectiveness workshop would have produced familiar frameworks that the team had already been exposed to. A personality-based diagnostic would have described individuals rather than dynamics. A conflict resolution facilitator would have addressed the surface tension without reaching what was producing it.
What she wanted, and what the team would not have named if they had been asked, was the material underneath — the things the team had quietly agreed not to examine, the patterns no one could change because no one would acknowledge them, the dynamics that were running the meetings from beneath the agenda.
The language the room could hold
I did not describe what we were doing as shadow work. I did not describe it as depth work. I did not use the word “archetypal”, or “projection”, or any of the vocabulary that names these phenomena in the practitioner literature.
What I offered them instead was a sequence of conversations framed in the language they already spoke.
What patterns show up in this team under stress?
What does this team not quite say out loud?
What is easier to say about each other than to each other?
What gets carried in this team that no one has explicitly named?
None of these questions requires the word “shadow”. All of them invite the material that shadow work addresses. The team, which would have politely declined a depth-psychology workshop, engaged with remarkable seriousness with the invitation to name what had been going unnamed.
Over four months of monthly sessions, the material surfaced. Not dramatically. In the ordinary register of senior operators describing their working reality more honestly than they had previously done together. The Commercial Director articulated a frustration with the Operations Director that turned out, on reflection, to be a projection of his own anxiety about commitment. The CEO discovered that her discomfort with one team member’s style was partly a mirror of a pattern in herself that she had been unable to see in her own behaviour. The team, as a whole, began to name the implicit rules it had been running by — rules about what could and could not be said, who could disagree with whom, what forms of dissent were welcome and what forms were quietly punished.
What made the work work
Two things, in my assessment, distinguished this engagement from ones that would have failed.
The first was the quality of the container. Not the vocabulary used to describe what we were doing, but the consistency of the structure, the reliability of the relationship I offered each member, and the clarity of the process. The team needed to know what to expect in each session, that the material would be handled with discretion, and that I was not attempting to produce a particular insight — I was simply holding the conditions under which the team’s own material could surface at the pace it was going to surface at.
The second was the refusal to insist on vocabulary the room did not want. This was, initially, harder for me than it looks. The practitioner part of me wanted to name what was happening in technical language, because technical language is satisfying to the practitioner. The work required me to trust that the language of the room was sufficient, and that my job was to hold the process, not to prove the framework.
The team transformed. Not completely — no team completely transforms — but substantially, and in ways that the CEO later described, in a subsequent conversation, as having changed the character of how the business was led. None of them, asked now, would describe what they had done as shadow work. The label would not have helped them. The practice did.
The principle, stated plainly
The container matters more than the label. This is not a claim that language is unimportant — it is a claim that the vocabulary that serves the practitioner is not always the vocabulary that serves the room.
For facilitators and internal practitioners reading this: the material that depth psychology names is present in every team, whether the team uses the vocabulary or not. The work of surfacing it can be offered in the language the team already speaks. Asking “what does this team avoid?” will produce the same material as asking “what is this team’s collective shadow?” — and in most commercial contexts, the first question will produce considerably more material, because it has not tripped the defensive response that the technical vocabulary can sometimes activate.
For senior leaders reading this: if your team is showing the signs of unprocessed collective material — recurring conflict that no intervention resolves, patterns that re-emerge across every restructure, the sense that the real conversation is happening underneath the stated one — you may not need a programme labelled as depth work to begin addressing it. You may need a facilitator capable of offering the work without requiring the vocabulary, and a team willing to answer honestly a small number of well-chosen questions.
The material is already there. It has been waiting. What it needs is an invitation offered in language the team can meet.
The Alchemy of Leadership: Five Elements Workbook
The full developmental architecture of the five-element sequence, including the principles of facilitating depth work in environments that do not use the technical vocabulary. Available free.