Skip to content

Search

Find insights, training programs, and workshops

Technical Debt & Rationalisation
Intermediate to Advanced (SA, EA, TS)5-6 hoursTechnical debt taxonomy + rationalisation prioritisation framework + modernisation criteria

How to understand, measure, prioritise, and reduce technical debt — the accumulated cost of shortcuts, outdated decisions, and deferred maintenance.

...testing. Detected by process audit. Medium cost — quality and speed impact. Knowledge debt — key-person dependencies, no cross-training. Detected by team assessment. High cost — risk when people leave. The...

1 DayIntensive
StrategicSA · EA · TS
ArchitectureTechnical DebtRationalisationModernisationGovernanceView Details
What Architecture Is
All levels — SA, EA, TS3-4 hoursArchitecture definition canvas + what it is / what it isn't reference card

What software and enterprise architecture actually is — its structure, relationships, and decisions — and what it is not. No diagrams. No jargon. Just clarity.

...classes — the things that teams build around. Relationships — how the parts connect and interact. Dependencies, data flows, contracts, integration patterns. This is where most architecture fails — not...

Half-dayIntensive
FoundationFor all roles
ArchitectureFoundationsDecision MakingView Details
How LLMs Work
Beginner to Intermediate4-6 hoursWorking mental model + reference materials

What actually happens inside a Large Language Model — from the moment you type a prompt to the moment it responds. No math. No fluff. Just a clear picture you can hold in your head.

...One head might focus on grammatical relationships. Another on semantic ones. Another on long-range dependencies across a long paragraph. Their outputs get combined into a richer picture than any one of...

2 DaysIntensive
Beginner FriendlyNo math required
LLMsMachine LearningTransformersGenerative AIView Details
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.

...extracting a legacy core behind stable APIs; introducing asynchronous boundaries; removing shared database dependencies; isolating high-risk legacy subsystems. When to use it: scaling limitations; regulatory...

1 DayIntensive
LayersNot cleanup
Execution StabilityRefactoringDelivery PredictabilityStructural RiskView Details
Fitness Functions Instead of Review Boards
Enterprise Architects, CTOs, Review Board Members, Engineering Leaders3-4 hoursA three-tier fitness function plan — your first three invariants automated, and the board agenda they retire

Batch review cannot govern continuous change. How to encode architectural invariants as automated checks — and what still belongs to the board.

...never reverse; the public API surface must never introduce a breaking change without an ADR; circular dependencies must never exceed a defined threshold; p95 response time under defined load must never exceed...

1 DayIntensive
ContinuousNot batched
GovernanceFitness FunctionsArchitecture ReviewContinuous DeliveryView Details
Solution Decomposition
Intermediate (SA, EA)4-6 hoursDecomposition canvas + domain/service/component hierarchy guide

How to break large, complex systems into smaller, independently manageable parts — so different teams can build, own, and change them without stepping on each other.

...low coupling outside — the decomposition mantra. Try it yourself — The coupling audit List three dependencies between components in your system. Rate each one: Dependency Type of coupling Could it...

1.5 DaysIntensive
FoundationSA · EA
ArchitectureSolution DesignDecompositionDomain Driven DesignBoundariesView Details
Decision Rights & Delegation
Engineering Managers, Tech Leads, Directors, CTO, VP Engineering3-4 hoursDecision rights map by altitude and domain, with every gap, overlap and delay node named

Decisions made at the wrong altitude are the commonest source of both bottleneck and drift — which makes delegation a design problem, not a trust problem.

...teams that cannot move inside the system begin moving around it, with untracked shortcuts and hidden dependencies; the business appears faster while the architecture becomes less governable. And governance...

1 DayIntensive
AltitudeWho decides what
Decision RightsDelegationGovernanceDecision VelocityView Details
Cognitive Load & Team Interfaces
VP Engineering, Platform Leads, Engineering Managers, Principal Engineers3-4 hoursCognitive load assessment per team, an interaction model, and a platform team charter naming what the platform does and does not own

A team can only hold so much — and the interaction modes between teams are what decide whether that limit is respected or quietly exceeded.

...responsibility triggers the question "what does this team stop holding in exchange?" When cross-team dependencies get treated as design failures rather than facts of life. And when the platform team's success...

1 DayIntensive
CapacityWhat a team can hold
Cognitive LoadTeam TopologiesPlatform EngineeringDeveloper ExperienceView Details
Technology Leadership & Organizational Excellence
Intermediate to AdvancedLeadership roadmap and team enablement plan

Learn to lead high-performance engineering organizations with clear decision rights, distributed leadership, and AI-augmented team management for the future of work.

...checklist: [ ] Map current teams and roles [ ] Identify cognitive load issues (too broad, too many dependencies) [ ] Define target team topology (stream-aligned, platform, enabling, etc.) [ ] Create/modify...

2 DaysWorkshop
FoundationFor all leadership roles
LeadershipOrganizational DesignDecision RightsAI Augmented TeamsView Details
Team Topologies & Organisational Design Workshop
CTO, VP Engineering, Engineering Directors, Principal EngineersTeam topology map, interaction model, platform team charter, cognitive load assessment

Your architecture isn't just a technical choice. It's a consequence of how your teams are structured. Fix the structure, and the architecture follows.

...diagram (even a rough one) of what the teams are building and maintaining List of recurring cross-team dependencies and coordination points Recommended team composition: 1-2 Engineering leadership (VP, Director...

1 DayIntensive
Team BlueprintClear Boundaries
Team TopologiesOrganisational DesignConway's LawDelivery ExcellenceView Details
123