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.

Quick Navigation Start here — the law you are already obeying The org chart is a hypothesis Where the real boundaries show up Four signals...

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

1 DayIntensive
StrategicEA · TS
ArchitectureOperating ModelConway's LawTeam TopologiesPlatform TeamsStrategyView 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.

...problem. Your teams will build a system that looks like your organisation. That's not a metaphor — it's a law. If you want a different architecture, you need a different team structure first. That one idea...

1 DayIntensive
Team BlueprintClear Boundaries
Team TopologiesOrganisational DesignConway's LawDelivery ExcellenceView 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.

...function. By team — split along organisational boundaries. What can a single team own end-to-end? Conway's Law in action. No single strategy is always right. Most real systems use a mix — domain boundaries...

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

...of work requires understanding somebody else's system. The fix is boundary redesign — the subject of Conway's Law & Team Boundaries. Carrying the wrong things. The team's load is the right size but the...

1 DayIntensive
CapacityWhat a team can hold
Cognitive LoadTeam TopologiesPlatform EngineeringDeveloper ExperienceView 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.

...is why boundary design and decision rights belong together. That side of the problem is covered in Conway's Law & Team Boundaries. Domain — which concern the decision belongs to Altitude alone is not...

1 DayIntensive
AltitudeWho decides what
Decision RightsDelegationGovernanceDecision VelocityView Details
How Architects Think
All levels — SA, EA, TS5-6 hoursSystems thinking toolkit + abstraction ladder + decision heuristics reference card

The cognitive toolkit of architecture — systems thinking, abstraction, balancing business and technical concerns, deciding under uncertainty, and trade-off thinking. Builds the mindset, not just the knowledge.

...Design for change — assume requirements will change. YAGNI — don't build for hypothetical futures. Conway's Law — design team structure to match desired architecture. Chesterton's Fence — don't change...

1 DayIntensive
MindsetNot just methods
ArchitectureFoundationsSystems ThinkingDecision MakingView Details
Why Architecture Exists
All levels — SA, EA, TS3-4 hoursArchitecture purpose framework — complexity · alignment · risk · change · shared understanding

Why architecture exists — managing complexity, aligning technology with business, reducing risk, enabling change, and creating shared understanding across teams.

...decisions using the same criteria. Common context — everyone knows what other teams are doing and why. Conway's Law says it plainly: "Organisations which design systems are constrained to produce designs...

Half-dayIntensive
PurposeWhy it matters
ArchitectureFoundationsComplexityBusiness AlignmentView 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.

...load) Assign teams based on domain boundaries Avoid "spanish孵化器" (team that owns too many domains) Use the Conway's Law corollary: team boundaries shape system boundaries Implementation checklist: [ ] Map current...

2 DaysWorkshop
FoundationFor all leadership roles
LeadershipOrganizational DesignDecision RightsAI Augmented TeamsView Details