The archetypal audit is a diagnostic framework that asks a different question than personality-based team tools. Not: who are these individuals? But: which archetypal positions are being carried in this team, by whom, and what is being left uncarried?

The distribution of archetypes across a team determines what the team can see, resolve, and produce — often more so than the individual competence of its members. And unlike personality distribution, which varies by the people currently in post, archetypal distribution can be deliberately mapped, named, and addressed.

The four archetypal positions

The framework I work with identifies four archetypal functions that, together, constitute the capacity of a mature senior team. Each carries essential material. Each, when absent or in shadow, leaves a specific structural gap.

The Sovereign carries authority — the capacity to hold decisions, close discussions, and bear the weight of consequence. Teams without functioning Sovereign capacity drift. Teams with Sovereign in shadow produce compliance and call it alignment.

The Magician carries transformation — the capacity to work with what is not yet, to hold paradox, and to see what could become possible. Teams without Magician capacity cannot innovate beyond their current model. Teams with Magician in shadow produce endless optionality without commitment.

The Coach carries developmental attention — the capacity to hold the team itself as the unit being developed, to notice the state of the people doing the work, and to advocate for the conditions that allow humans to contribute at their best. Teams without Coach capacity burn through their talent. Teams with Coach in shadow become enabling and conflict-averse.

The Oracle carries systemic wisdom — the capacity to perceive patterns not yet fully visible, to integrate information across time horizons, and to hold complexity without collapsing it prematurely. Teams without Oracle capacity cannot see what they are avoiding. Teams with Oracle in shadow produce private certainty without public contribution.

How the audit works

The audit is conducted in three stages. It can be done with outside facilitation or, with enough maturity in the team, internally.

Stage one: private mapping. Each team member is given a short briefing on the four archetypes and then answers three questions privately, in writing: Which archetypal function do I most naturally carry in this team? Which do I most naturally avoid or underplay? Which archetype, from what I can observe, is missing from this team altogether?

Written, individual, before any discussion. The constraint matters. Discussion-based mapping tends to produce consensus that obscures the real distribution.

Stage two: comparison. The answers are compiled and shared, usually with the mapping visible to everyone at once. What emerges is a specific portrait of the team’s archetypal distribution — who is carrying which function, where there is overlap, and where there are gaps.

The comparison is usually revealing. Most teams discover that their archetypal distribution is significantly less balanced than they had assumed. It is also common to find that the archetype most members agree is missing is not, in fact, missing in the sense they had thought — someone is carrying it, but in shadow form that the team was not recognising as the function in question.

Stage three: implication. The team then has a structured conversation about what the distribution is producing. What decisions are the team making that the distribution is shaping? What conversations are the team avoiding because no one is in the position to surface them? What failure modes are structurally likely, given what is present and what is missing?

This is where the audit becomes useful rather than merely descriptive. A team that knows its Magician is in shadow and its Oracle is entirely absent is a team that can now make conscious decisions about how to compensate, where to draw on external capacity, and which kinds of decisions it should be especially cautious about making.

The distribution of archetypes across a team determines what the team can see, resolve, and produce — often more so than the individual competence of its members.

What the audit surfaces that personality tools cannot

Personality tools describe disposition. They tell you that Paula is introverted and analytical, that Mark is extroverted and assertive, that Yusuf is reflective and collaborative. This information is useful, within limits.

What it cannot tell you is what functional role these individuals are currently playing in the team, and what is being left unplayed. A team of three introverted analytical thinkers will produce meaningfully different outcomes depending on whether those three are each carrying Oracle function (in which case the team has depth but may struggle with decisiveness), or whether one is Oracle, one is Coach, and one is Magician (in which case the team has more diverse capacity but lacks Sovereign).

Personality does not determine archetypal function. Position and development do. And the same individual will carry different archetypal functions in different teams, depending on what the team structurally needs and what the person has been developed into.

This is why the audit is generative where personality mapping plateaus. It identifies structural conditions that can be worked with — not fixed traits that must be accommodated.

Common patterns from conducting this with senior teams

Three patterns recur with enough frequency to be worth naming.

The overloaded Sovereign. Many senior teams have one person carrying all the Sovereign weight, usually the CEO or the dominant personality on the team. The rest of the team has, often unconsciously, withdrawn from the authority function, leaving one person both doing the work and being blamed for doing too much of it. The audit usually reveals that several other team members have available Sovereign capacity they have been suppressing for political reasons.

The invisible Oracle. The Oracle function is almost always the most commonly under-recognised. One person on the team is usually carrying it — they see the pattern, hold the question, notice what the team is avoiding — and because their contribution is quiet and often inconvenient, they are systematically under-valued by the same team that most needs their function. The audit frequently produces genuine surprise when this person is named.

The missing Coach. Teams that have optimised for execution and performance often have no one structurally holding the developmental function. The Coach position is empty. The team burns through people, cannot understand why, and reliably replaces them with similar people who will also burn. This is particularly common in high-performance commercial environments and in founder-led organisations where the founder is carrying everything except this.

The decision the audit produces

Once the distribution is visible, the team faces a specific choice. The gaps in the distribution can be addressed in three ways: by developing a current team member into a function they are not yet carrying; by deliberately recruiting for the missing archetype; or by bringing in external capacity to hold the function temporarily while the team’s internal work matures.

None of these is trivial. All of them are easier to decide about once the gap itself has been accurately named. Which is the work the audit is for.

Referenced framework

The Alchemy of Leadership: Five Elements Workbook

The full architecture of the Four Archetypes — Sovereign, Magician, Coach, Oracle — including the diagnostic framework behind the archetypal audit and worked examples from senior team practice. Available free.

A confirmation email will arrive shortly. We treat your inbox as we would our own; you may unsubscribe at any time.