Skip to content

Search

Find insights, training programs, and workshops

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.

...carrying Four team shapes that respect the limit Three interaction modes — the interface is the design The platform as the load-absorbing interface Golden paths, dirt roads, and the museum problem Measuring whether...

1 DayIntensive
CapacityWhat a team can hold
Complete Enterprise Data Architecture Framework: Business, Logical, Physical Layers with Real Templates
Complete Enterprise Data Architecture Framework: Business, Logical, Physical Layers with Real Templates

Most enterprises build data architectures one layer at a time. Business, logical, and physical layers exist as separate artefacts owned by separate teams. That separation is the structural gap that makes data estates ungovernable.

...solves: Business, logical, and physical data architecture layers built in isolation — by different teams, in different tools, with no connecting model Key outcome: A coherent three-layer framework called...

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.

...days to establish the translation architecture for one strategic priority Business impact: Delivery teams that build the right things, investment aligned to strategic intent, and governance that closes...

Application & Technology Landscape
All levels — SA, EA, TS4-5 hoursApplication landscape register + technology heat map + dependency matrix

How to build, read, and use the full picture of what an organisation runs — every application, platform, integration, and technology — and how they depend on each other.

...organisations don't have an accurate picture of what they're running. Systems were built by different teams, in different years, for different reasons. Nobody mapped the whole thing. When someone asks "what...

1 dayIntensive
PracticalLandscape exercise
Technology, Infrastructure, Cloud & Security Design
Intermediate to Advanced (SA, EA)6-8 hoursInfrastructure decision framework + cloud pattern reference + security controls map

Where abstract architecture meets physical reality — choosing the platforms, compute, networking, and security controls that make the solution work at scale.

...onto Architecture decisions live in the abstract until they're made real by technology choices — the platforms, the compute, the networking, the security controls. I've seen teams choose technology for...

2 DaysIntensive
PracticalSA · EA
Delivery, Implementation & Architecture Runway
Intermediate (SA, EA, TS)4-5 hoursArchitecture runway template + delivery dependency map + agile architecture checklist

How architecture supports delivery instead of blocking it — covering architecture runway, phased implementation, dependency management, keeping teams unblocked, and recovering when architecture goes wrong during delivery.

...Architecture and delivery What architecture runway is Phased implementation Managing dependencies Keeping teams unblocked Spikes and POCs When architecture goes wrong Putting it all together Cheat sheet Before...

1 DayIntensive
PracticalSA · EA · TS
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.

...months later the same friction is back in a different shape. The people weren't the problem. Your teams will build a system that looks like your organisation. That's not a metaphor — it's a law. If you...

1 DayIntensive
Team BlueprintClear Boundaries
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.

Executive Summary Who this is for: CTOs, Engineering Leads, Platform Engineering Teams, Architecture Review Boards, Engineering Managers Problem it solves: Organizations...

Monitoring Added After Deployment Is Not Observability. It Is Archaeology.
Monitoring Added After Deployment Is Not Observability. It Is Archaeology.

Observability is not a monitoring add-on. It is an architectural constraint. Systems built without observability baked in cannot be understood, cannot be governed, and cannot be improved. The OSAF model tells you exactly where your architecture is blind.

Executive Summary Who this is for: CTOs, Platform Engineers, Enterprise Architects, Engineering Leads, System Design Owners Problem it solves:...

Security Is Not a Gate. It Is an Architecture Property.
Security Is Not a Gate. It Is an Architecture Property.

Security is treated as a gate at the end of delivery. It should be an architecture property designed into three distinct boundaries. Here is the model that fixes the friction between security and delivery.

Executive Summary Who this is for: CTOs, CISOs, Enterprise Architects, Platform Engineering Leads, Heads of Engineering Problem it solves: Security is treated as a gate at...

123···8