Skip to content

Search

Find insights, training programs, and workshops

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.

...Navigation Start here — the law you are already obeying The org chart is a hypothesis Where the real boundaries show up Four signals that expose the boundary you actually have The two-layer map Redrawing...

1 DayIntensive
BoundariesStructure as design
Conway's LawTeam TopologiesOrganisational DesignTeam BoundariesView 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.

...helps functions redesign workflows? Who decides what gets scaled? Who handles risk review? Who trains teams? Who measures value? If those questions are unresolved, the organisation will look busy while capability...

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.

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
Cognitive LoadTeam TopologiesPlatform EngineeringDeveloper ExperienceView 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.

...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
Team TopologiesOrganisational DesignConway's LawDelivery ExcellenceView Details
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...

LeadershipPlatform EngineeringAiGovernanceRead Insight
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...

LeadershipPlatform EngineeringGovernanceRead Insight
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.

Quick Navigation Start here — Why decomposition matters Strategies for decomposition Defining boundaries Coupling and cohesion Domain-Driven Design basics Common mistakes Putting it all together Cheat...

1.5 DaysIntensive
FoundationSA · EA
ArchitectureSolution DesignDecompositionDomain Driven DesignBoundariesView Details
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
ArchitectureOperating ModelConway's LawTeam TopologiesPlatform TeamsStrategyView 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.

...Leadership = The practice of guiding engineering organizations through AI transformation, distributed team management, and organizational design for high performance. It encompasses: Distributed leadership...

2 DaysWorkshop
FoundationFor all leadership roles
LeadershipOrganizational DesignDecision RightsAI Augmented TeamsView Details
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.

...structural code complexity Key outcome: Reduced regression risk, improved cycle time, clearer ownership boundaries Time to implement: 60–90 days for structured rollout Business impact: Higher engineering throughput...

LeadershipGovernanceExecutionRead Insight
1234567