The process usually unfolds in three parts: a Diagnostic, a focused Sprint, and — where needed — a deeper Partnership over time.
Not every engagement moves through all three. Some leaders need clarity first. Others need to test one structural shift. Some need longer support because the pressure is more deeply embedded in the system.
The aim is always the same: to see clearly what is happening, test what needs to change, and strengthen the Architecture around what the situation now requires.
This is the usual starting point. The Diagnostic helps clarify where the pressure really sits: in the leader, the team, the role, or the wider structure around the work.
It is designed for moments when something feels heavy, unclear, or increasingly dependent on personal effort, but the real source of that strain has not yet been made visible.
By the end, there is more clarity about what is actually happening, what kind of shift is needed, and whether the next step is a Sprint, a Partnership, or a smaller move that can be acted on immediately.
A Diagnostic is a contained process — usually two conversations and a written synthesis — that makes the invisible visible and gives the work a clear starting point.
Typical use cases:
A Sprint is a contained intervention designed to test one meaningful change in the real system.
It is useful when the pressure has been made clear enough to act on, but the work does not yet require a longer Partnership.
This might involve redesigning a role boundary, clarifying an overloaded interface, changing a decision rhythm, or testing a new way of carrying leadership pressure so the system is doing more of the holding.
The point is not to redesign everything at once. It is to make one structural move that can be felt in practice.
Typical use cases:
Some situations need more than a Diagnostic or a single intervention. They need deeper work over time because the pressure is held in the architecture itself: roles, rhythms, agreements, decision-making, trust flow, or the way leadership is currently being carried.
A Partnership is designed for that kind of deeper structural work.
It creates enough continuity to work with what is systemic rather than symptomatic, and enough flexibility to adapt as the deeper architecture comes into view.
Typical use cases:
The usual starting point is a short conversation, followed by a Leadership Architecture Diagnostic.