Skip to content

Search

Find insights, training programs, and workshops

AI Adoption, Change & Project Delivery
Intermediate5-6 hoursAI adoption playbook + stakeholder engagement plan + delivery framework

Moving AI from exciting pilot to boring-but-valuable production. The people, the process, and the delivery discipline that turns AI potential into daily practice.

...blockers Stakeholder engagement — who needs to be involved Change management — the human transition Delivery framework — pilot to production Culture — what makes it stick The adoption system in one diagram Cheat...

2 DaysIntensive
Adoption PlaybookDeliverable
Developer Experience Is Not a Perk. It Is a Delivery Control System.
Developer Experience Is Not a Perk. It Is a Delivery Control System.

Developer experience is not about making developers happy. It is about controlling the conditions that determine delivery output. Organizations that treat DX as a perk have removed the control system from their delivery engine without knowing it.

...Organizations invest in developer experience as a retention and morale programme — and never connect it to the delivery performance it actually controls Key insight: Developer experience is not a feeling. It is a...

Execution Stability: How Structured Refactoring Improves Delivery Predictability
Execution Stability: How Structured Refactoring Improves Delivery Predictability

A practical framework for reducing delivery slowdown caused by unmanaged structural code complexity — improving cycle time, reducing regression risk, and clarifying ownership boundaries.

...Summary Who this is for: CTOs, Engineering Directors, Principal Engineers Problem it solves: Growing delivery slowdown caused by unmanaged structural code complexity Key outcome: Reduced regression risk,...

Developer Experience as a Control System
CTOs, Engineering Leads, Platform Engineering Teams, Engineering Managers3-4 hoursA delivery friction map across four sprints, one named constraint pillar, and a traced DX-to-delivery signal

DevEx is not a perk — it is the set of operating conditions that governs how fast and how safely change moves through your delivery system.

...the greenhouse does not grow crops by accident The wrong category Why DevEx investment fails to move delivery Five conditions that govern delivery output What breaks when the conditions are ungoverned Tracing...

1 DayIntensive
ConditionsNot satisfaction
Roadmaps & Transformation Sequencing
Intermediate to Advanced (SA, EA, TS)5-7 hoursRoadmap template + transition state design guide + sequencing logic + dependency overlay

How to build multi-year transformation roadmaps that sequence architectural change realistically — accounting for dependencies, capacity, risk, and the fact that the organisation must continue operating while it transforms.

...start — the one thing to hold onto A transformation roadmap isn't a Gantt chart. It's not a list of projects with dates. It's a sequenced set of decisions and transitions that move the organisation from...

1.5 DaysIntensive
StrategicSA · EA · TS
Execution Stability & Structured Refactoring
CTOs, Engineering Directors, Principal Engineers, Engineering Managers3-4 hoursA classified structural risk map — your top friction modules sorted into dicing, slicing and peeling with a governance rule attached

Delivery slows because structural entropy accumulates unmeasured. Classify refactoring into dicing, slicing and peeling to restore predictability.

...a capability problem. It is structural entropy — and it is the most commonly misdiagnosed cause of delivery slowdown, because there is no incident to point at. Refactoring is usually treated as cleanup....

1 DayIntensive
LayersNot cleanup
Requirement Clarity: How Structured Persona Definition Reduces Rework and Misalignment
Requirement Clarity: How Structured Persona Definition Reduces Rework and Misalignment

A structured framework for defining personas that eliminates scope creep, reduces rework, and aligns engineering delivery with actual user needs — before development begins.

...implement: 30–60 days for structured rollout Business impact: Reduced rework, faster approvals, improved delivery predictability The Hidden Cost of Poorly Defined Personas Your team delivered the feature...

Standards & Reference Architectures
Intermediate (SA, EA)4-5 hoursReference architecture library starter + standards register + architecture principles catalogue

How to create, govern, and operationalise architecture standards and reference architectures — the agreed patterns and structures that create consistency, reduce duplication, and accelerate delivery at scale.

...and structures that create consistency across an organisation — reducing duplication, accelerating delivery, and managing risk at scale. Standards settle common questions once, so teams don't have to...

1 dayIntensive
PracticalStandards exercise
The Capability Map That Cannot Answer a Question Is Not a Capability Map
The Capability Map That Cannot Answer a Question Is Not a Capability Map

Why traditional capability maps fail to support governance decisions and how Queryable Capability Architecture turns static maps into interrogable decision systems.

...Gaps Some capabilities appear on strategy maps but lack: a supporting system a responsible team a delivery roadmap These capabilities exist only in presentation slides, not in operational reality. Investment...

The Strategy-to-Execution Gap: How Enterprise Architecture Bridges the 'What' and the 'How'
The Strategy-to-Execution Gap: How Enterprise Architecture Bridges the 'What' and the 'How'

Why strategic intent evaporates before it reaches engineering teams — and how Enterprise Architecture creates the translation layer that makes organizational strategy executable.

...practical three-layer translation model that makes organizational strategy traceable all the way to delivery Time to implement: 30–60 days to establish the translation architecture for one strategic priority Business...