Each story follows the same structure: what the practitioner was working with before, the moment something shifted, and what became possible after. The path they completed is linked.
arrow_back
Before
Coaching Agile transformation without a diagnostic model for why transformations stall at the leadership level — attributing the problem to framework adoption rather than leadership behaviour
Strong practitioner vocabulary (Scrum, Kanban, SAFe) but no strategic leadership theory for conversations with executive sponsors who resisted change without being able to name why
Coaching interventions that addressed process compliance rather than the leadership mindset shift the transformation actually required
arrow_forward
After
Active Inertia as a working diagnostic: the recognition that leaders resist transformation not because they are wrong, but because the instincts that made them successful are now the primary obstacle
Coaching conversations that could meet executive sponsors at the level of leadership identity rather than process compliance — explaining their own resistance to them in language they recognised
A shared vocabulary across the coaching engagement for distinguishing technical problems (which Agile frameworks solve) from adaptive challenges (which require genuine leadership change)
The turning point
The Active Inertia framework — the recognition that the same instincts, capabilities, and commitments that built Wells Fargo's previous success were now operating as active resistance to the transformation. Naming this to an executive sponsor changed the conversation from "why aren't you adopting the framework?" to "what are you being asked to give up that worked before?" The executive engagement changed the same week.
"The sessions were informative and are an eye opening on how to run a successful Agile Transformation."
Inez Eldewek · Agile Transformation Coach, Wells Fargo
arrow_back
Before
Strategic planning that produced documents rather than decisions — plans that sat in decks rather than shaping what teams actually executed against week to week
No visible connection between the strategy the leadership team owned and the capability investments being made — development spend allocated opportunistically rather than derived from strategic direction
Strategic conversations that could identify priorities but could not explain the cause-and-effect logic that connected those priorities to organisational outcomes
arrow_forward
After
A strategy map that made the cause-and-effect logic of the strategy visible — giving every team a direct line of sight to the organisational outcomes their work contributed to
Capability investment decisions that could be traced back to specific strategic requirements — and two capability areas that were deprioritised because the map revealed they were not connected to any strategic outcome
A shared vocabulary across the leadership team for the distinction between strategic priorities (which drive capability investment) and operational noise (which consumes it)
The turning point
Building the strategy map in the Session 2 activity. Writing out the cause-and-effect logic explicitly made visible that three of the five initiatives the leadership team considered strategic were not connected to any capability the organisation was actually building. The map didn't reveal a planning failure — it revealed that the strategy and the capability investment had been operating as separate conversations for years.
The concrete difference
The organisation stopped investing in two capability areas and concentrated the released resources on the three that the strategy map showed were genuinely load-bearing. This reallocation had been discussed before the path and never actioned — because without the visual logic of the map, there was no agreed basis for making it. The map provided the basis.
"The ADAPT Program has been a game changer for our org."
Dorothy Aubrey · Business Leader, Kobumura LLC
arrow_back
Before
A change programme with strong executive mandate, a well-designed implementation plan, and 34% active adoption at month six — resistance attributed to employee attitude rather than programme design
Executive sponsors who were visible at launch and absent during implementation — no architecture for what executive sponsorship required after the announcement was made
Communication designed as message delivery — clear, frequent, consistent — producing surface compliance rather than genuine understanding of what the change required from each team
arrow_forward
After
A resistance map that traced the 34% adoption gap to three specific design elements in the programme — not employee attitude, but design choices that had been producing defensive behaviour
An executive sponsorship architecture with explicit post-launch accountabilities, a visibility cadence, and a protocol for sponsors to intervene when compliance replaced adoption
Communication redesigned as dialogue — with structured feedback loops that surfaced what different teams actually understood about what the change required from them, rather than whether they had received the message
The turning point
The diagnostic question from Module 3 of the Change Management path: at what point in the programme was resistance first detected, and what design element was in place at that point? Tracing the resistance to a specific design choice — the absence of manager involvement in shaping the message — rather than attributing it to employee attitude made it possible to redesign the element rather than pressure the people.
The concrete difference
Active adoption moved from 34% at month six to 71% at month nine — not by adding more communication or increasing programme pressure, but by redesigning the three elements the resistance map identified. The same executive mandate, the same timeline, the same team. The design changed; the outcome changed.
"Repeatable capability is what separates a good Helix engagement from a great one."
Kyle McAdams · Programme Lead, Concord Servicing
