This page is for the questions that often come before a first conversation: what the work is, who it is for, how the Diagnostic works, what happens afterwards, and how confidentiality is handled.
This work is for leaders, founders, sponsors, transformation leaders, program leaders, consulting partners, and senior operators who sense that the pressure they are carrying is not only personal.
It is especially relevant when responsibility has grown faster than mandate, when a transformation is busy but not clearly moving, when trust depends too heavily on informal holding, or when one person has quietly become the structure that keeps everything together.
The conversation always starts from the perspective of whoever is holding the field — the person responsible and in a position to act on what becomes visible. What the Diagnostic actually examines may extend well beyond them: a team, an organisation, or a transformation programme. But the entry point is always their view of it.
Neither, exactly. Most leadership work focuses on capability, behaviour, mindset, or performance. This starts somewhere different — asking what the leader or system is being asked to carry because the surrounding Architecture isn’t holding it cleanly. That means looking at roles, rhythms, mandate, access, agreements, decision lines, and the lived felt state of the system, not adding another model on top of what’s already there.
The aim isn’t to coach someone into tolerating a bad system. It’s to help them see and redesign the Architecture they’re inside.
Yes. It often strengthens them.
Because this work addresses alignment and trust at a structural level, it often helps other investments — strategy, culture, coaching, transformation work — land more cleanly.
It does not compete with what you are already doing. It helps clarify what is shaping whether those efforts work.
Sometimes you can.
But when you are inside the system, you may also be part of the structure that is compensating for it. That makes it harder to see where pressure is actually being generated.
The Diagnostic gives you an external structural read: what is holding, what is under strain, what you may be carrying because the system is not holding it, and which first Pathway of rebuild is most relevant.
The point is not to hand over responsibility. It is to see the Architecture clearly enough to act with more precision.
A structured process of focused conversations and structural analysis, closing with a written synthesis of what’s happening and what should happen next. See How it works on the Diagnostic page for the full process.
A clear structural read — the pressure, the pattern underneath it, the relevant Design Conditions, and a recommended first Pathway and next move. Not a thick report; enough clarity to act.
You don’t choose it in advance. The Diagnostic reveals which of the four Pathways — Leadership Clarity, Leadership Capacity, Leadership Signal, or Collective Alignment — is most likely to create movement.
Depending on what it reveals: a smaller move you test yourself, a focused Sprint, a deeper Partnership, or — where the wider system needs more mapping first — an Architecture Audit or Resonance Scan.
A light Diagnostic may involve one focused conversation and a short written note.
A standard Diagnostic usually includes preparation, one or two Diagnostic conversations, structural analysis, a Structural Reflection Session, and a concise written synthesis.
A more complex context may require additional conversations, selected artefacts, or one or two additional perspectives.
The right scope depends on the pressure, the level of system involved, and what would make the work useful.
Yes, where useful. The Diagnostic starts with whoever is closest to the pressure, but if it shows that wider involvement would help, it can extend to a team, sponsor group, partner interface, or wider leadership system.
You do not need a perfectly defined problem.
It is enough that something is live, repeated, or costly enough to examine properly.
Useful starting points include: a recurring pressure, an unclear mandate, repeated alignment effort, leadership overload, sponsor friction, a founder bottleneck, internal/external partner tension, or a sense that the formal story no longer matches the lived reality.
Not always many.
For an individual or leader-centred Diagnostic, one or two focused conversations may be enough to create a useful first structural read.
For wider system questions, selected additional perspectives may be useful. The Diagnostic remains proportionate: enough input to see the pattern, not an exhaustive organisational study.
No. What matters is being close enough to the pressure to see it, and positioned to act on what becomes visible — not a specific title or seniority level.
The first conversation is free — a short conversation to understand what’s live and whether a Diagnostic would be useful.
Beyond that, investment depends on the complexity of the situation: whether the work is focused on one leader, a leadership team, or a wider transformation system. For a contained leadership context, the Diagnostic is a clear, proportionate first step; where multiple stakeholders or a wider system are involved, scope is agreed before work begins.
Any further work — Sprint, Partnership, Audit, or Resonance Scan — is scoped and priced separately once the Diagnostic shows what’s actually needed.
I am based in Switzerland and work with clients internationally.
Most Architecture of We work can be done remotely. The Leadership Architecture Diagnostic, review conversations, advisory sessions, and many Sprint or Partnership elements work well online, especially when supported by relevant materials such as role descriptions, programme summaries, organisation charts, leadership communications, meeting rhythms, or other artefacts that show how the work is currently held.
For some team, sponsor, or transformation contexts, in-person work may be useful, particularly where the quality of interaction in the room matters. We can decide that together once the situation is clearer.
Confidentiality is central to the work.
The Diagnostic often involves sensitive material: pressure, trust, authority, compensation, friction, informal workarounds, or private doubts about how the system is functioning.
We agree what can be recorded, what can be shared, and who has access to any written synthesis. Client material is treated as confidential unless explicitly agreed otherwise.
Felt sense matters, but it is not used on its own.
The work pays attention to Resonance — the felt signal of coherence or distortion in a system — but always pairs it with observable evidence: language, behaviour, role design, decision patterns, agreements, artefacts, access, rhythm, and outcomes.
In plain terms: if something feels off, we do not stop there. We look for the structure producing it.
Yes.
The work may include emotion, behaviour, and personality dynamics because leadership pressure is experienced by human beings.
But it does not treat personality as the first or final explanation.
Sometimes what looks like a personal or behavioural issue is also a response to the conditions around the work. When authority is unclear, agreements are weak, access is uneven, roles are overloaded, or trust has become thin, people often adapt in ways that make sense locally but create noise across the wider system.
The Diagnostic looks beneath the visible behaviour to ask what the Architecture is producing.
When the underlying structure becomes clearer and better held, some of the behavioural noise can reduce or disappear. People no longer need to compensate, protect themselves, over-control, chase alignment, or carry ambiguity in the same way.
The purpose is structural clarity: what is being carried, what conditions are shaping the behaviour, and what would need to change for the work to be held more cleanly.
Often, yes.
Political behaviour frequently appears when decision rights, mandate, access, trust, or sponsorship are unclear.
The Diagnostic does not begin by blaming individuals. It asks what conditions are causing people to behave as they do, what is not being held clearly enough, and what would need to become true for the pressure to reduce.
If anything here matches what you’re sensing, that’s worth a short conversation.