Each engagement is tailored around what you take away. Four movements, not a linear process: we move between them as the system tells us to, and hand the language back to your team so the work continues after we leave.
What is actually breaking, and why.
Where care needs to head, made concrete, and the decision framed for the room.
The workflow rebuilt as the unit of design, with the team rather than for it.
Built to hold. Capability and systems that stay when conditions change.
Every intervention strengthens clinical judgement rather than replacing it, builds internal capability rather than external dependency, and treats technology as a consequence of good design, never the starting point.
No one wakes at 3AM needing a workshop. They wake with a question the organisation cannot yet answer. Four of those questions come up more than the rest. For each, we read the presenting complaint, name the mechanism we usually find underneath, and describe the shape of engagement that resolves it.
Pilots stall at the pilot ward. Tools reach the demo, not the bedside. Adoption plateaus once the launch team leaves. The workflow was not the design object: the model, the platform or the vendor was, and the clinical work around it absorbed the change alone.
Usually opens as a workshop with clinical and digital leads in the room, rebuilding one workflow end to end. Where the pattern repeats across services, it becomes an advisory engagement over one to three quarters.
The presenting complaint is rarely the mechanism. Leadership is optimising a variable that was inherited, not chosen: a KPI from the last strategy, a boundary drawn by procurement, a target set for a system that no longer exists. The work reads busy and moves nothing.
A short diagnostic in the room, sometimes a masterclass giving the leadership team a shared method for re-framing, then a workshop that fixes the frame the organisation will work from.
Clinical AI, autonomous decisioning, data sharing across institutions. The rules were written for a different system and are now the bottleneck, not the guardrail. Clinicians route around them; boards approve what they cannot yet supervise.
A masterclass on clinical AI governance for the executive and board, then a workshop drafting governance by design for one specific decision. Advisory alongside where the mandate is ongoing.
Capability drains out with the consultants. Systems revert under the first real pressure. The work was done for the team, not with it, and the language was never handed back. What was built lives in a deck, not in daily practice.
Advisory shaped around the handover from the start: the method, vocabulary and decision rights transfer to your people in step. Designed for the day we leave and the pressures that arrive after.
Formats are delivery, not the offer. The problem chooses the shape. Below is the vocabulary: what a masterclass is, what a workshop is, and what an advisory relationship is.
Open-enrolment, single-topic sessions for a senior cross-organisation cohort. One subject, taught by the practitioner who built it.
Closed, facilitated sessions for one leadership team, built around a live decision you own. You leave with something usable: a framing, a plan, a draft governance model.
A senior-level relationship for executive teams and boards. Direct access to practitioners for strategic direction, governance and the decisions that do not get a second take. As light or as deep as the problem demands.