Skip to content

Search

Find insights, training programs, and workshops

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.

...k Navigation Before we start — the organisational mistake behind many AI failures Why organisation design matters The major operating model patterns Platform, product, and governance roles Decision rights...

1 DayStrategy
Operating ModelDesign
AI-Native Teams Don't Need New Titles. They Need Named Owners.
AI-Native Teams Don't Need New Titles. They Need Named Owners.

AI-native team redesigns keep adding new job titles and calling it done. The actual failure mode sits at the decision boundary. Here is what changes when you apply AIDRA to team design instead of headcount.

...utive Summary Who this is for: CTOs, VPs of Engineering, Heads of Platform, Engineering Directors, Team Leads adopting agentic workflows Problem it solves: AI-native team redesigns focus on new job titles...

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
Conway's Law & Team Boundaries
CTO, VP Engineering, Engineering Directors, Principal Engineers3-4 hoursTwo-layer boundary map — the official org design set against actual incident load, with every structural gap named

Your architecture mirrors your communication structure whether you designed it that way or not — which makes team boundaries an architectural decision.

...They hire, they reorganise, and six months later the same friction is back in a different shape. Your teams will build a system that looks like your organisation. That is not a metaphor — it is a law. If...

1 DayIntensive
BoundariesStructure as design
Operating Model Choices
Advanced (EA, TS)5-6 hoursOperating model design canvas + team topology guide + Conway's Law application worksheet + Communication Structure Heatmap

How the structure of technology teams shapes the structure of the systems they build — covering Conway's Law, centralised vs federated models, platform teams, product operating models, team topologies, and designing the organisation that produces the architecture you want.

Quick Navigation Start here — Conway's Law Centralised vs federated Platform teams Product operating models Team topologies Governance in federated models Choosing an operating model Inverting...

1 DayIntensive
StrategicEA · TS
Domain-Driven Design & Strategic Design Workshop
Enterprise & Solution Architects, Principal Engineers, Tech LeadsDomain map, bounded context canvas, ubiquitous language glossary, context map

Stop designing systems around databases and frameworks. Start designing around your business domains — and watch your architecture conversations change overnight.

Before we start — the one thing to hold onto Most teams think they have a naming problem. Services called , , . They rename things, argue about it in code...

1-2 DaysFacilitated
Domain MapStrategic Clarity
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.

Quick Navigation Start here — the limit nobody put in the plan What a team is actually carrying Four team shapes that respect the limit Three interaction modes — the interface...

1 DayIntensive
CapacityWhat a team can hold
AI Workflow Design & Process Redesign
Beginner to Intermediate4-5 hoursAI workflow map + redesign canvas + exception-handling pattern

Most organisations do not need more prompts. They need better workflows. Learn how to redesign work around AI, human review, exceptions, and measurable outcomes.

...disappoints Why prompt-first thinking is too small The workflow lens Where AI belongs in a process Designing handoffs and review Exceptions, failures, and recovery The redesign sequence How to redesign...

1 DayHands-on
Workflow DesignPractical
Application, Integration, API, Interface, Data & Process Design
Intermediate to Advanced (SA, EA)6-8 hoursIntegration design playbook + API design standards + data movement pattern guide

How the components of a solution are structured internally, how they communicate with each other, and how they connect to the data and processes they depend on.

Quick Navigation Start here — Solution design Application design Integration patterns API design Interface design Data design Process design Putting...

2 DaysIntensive
ComprehensiveSA · EA
Your Platform Team Is Building a Product Nobody Asked For.
Your Platform Team Is Building a Product Nobody Asked For.

Most platform teams build internal products their engineering teams never chose. Platform adoption is not a marketing problem. It is a product governance problem. Here is the model that fixes it.

...Engineering, Enterprise Architects, VPs of Engineering, Platform Product Managers Problem it solves: Platform teams invest months building capabilities that engineering teams work around, bypass, or ignore — because...

12···11