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.

..."The data model doesn't support this use case" Refactor when discovered; document learning Bit rot Technology ages — support ends, versions stale "We're on Java 11; Java 17 is current" Upgrade on schedule;...

1 DayIntensive
StrategicSA · EA · TS
ArchitectureTechnical DebtRationalisationModernisationGovernanceView 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.

...here — the escalation ladder is not a decision rights model Most organisations have a process for technology decisions. It usually looks like this. A team cannot agree. They escalate to the architecture...

1 DayIntensive
AltitudeWho decides what
Decision RightsDelegationGovernanceDecision VelocityView 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.

...decomposition — By domain, capability, data, team There are many ways to break a system apart. The strategy you choose determines what kind of boundaries you get. Four common strategies: By business...

1.5 DaysIntensive
FoundationSA · EA
ArchitectureSolution DesignDecompositionDomain Driven DesignBoundariesView Details
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.

...novel. What standards are not: A straitjacket — teams can request exceptions for valid reasons. A technology mandate — standards include patterns and principles, not just products. A one-time decision...

1 dayIntensive
PracticalStandards exercise
ArchitectureEnterprise ContextStandardsReference ArchitectureGovernanceConsistencyView Details
AI Operating Model & Team Design
Intermediate4-5 hoursAI operating model blueprint + team role map + governance forum design

AI success is not just about tools. It depends on how teams are organised, who owns what, how standards are set, and how delivery, governance, and platform capabilities work together.

...business teams all touch the same workflow with different incentives and no shared operating model. Technology confusion is often organisation confusion wearing a technical mask. The major operating model...

1 DayStrategy
Operating ModelDesign
AI Operating ModelTeam DesignAI GovernanceTransformationPlatform TeamsView 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.

...platform is bad, but because nobody asked the developers what they actually needed. A platform is not technology. It is a product, and your developers are the customers. If they do not choose to use it,...

1 DayIntensive
CapacityWhat a team can hold
Cognitive LoadTeam TopologiesPlatform EngineeringDeveloper ExperienceView Details
Platform as a Product
CTOs, Heads of Platform Engineering, VP Engineering, Enterprise Architects, Platform Product Managers3-4 hoursA three-gate platform governance plan — validated backlog, a written scope boundary, and adoption targets per capability

An internal platform with no product owner builds what nobody asked for and skips what everybody needs — adoption, not completeness, is the only measure that counts.

...Every one of those numbers can rise while the platform's actual usefulness falls. A platform is not technology. It is a product, and your developers are the customers. If they do not choose to use it,...

1 DayIntensive
AdoptionNot feature count
Platform EngineeringInternal Developer PlatformProduct GovernanceGolden PathsView Details
12345