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.

...nothing ships independently." Consider organisations that spend a year trying to build independent microservices with teams that still share a database, a release process, and a weekly coordination meeting....

1 DayIntensive
BoundariesStructure as design
Conway's LawTeam TopologiesOrganisational DesignTeam BoundariesView Details
Architecture Governance
Intermediate to Advanced (SA, EA, TS)5-6 hoursGovernance model canvas + architecture principles register + escalation path template

How to design, implement, and measure architecture governance — the mechanisms that ensure decisions are made consistently, applied correctly, and aligned with strategy.

...that meets the need because complexity increases cost of change. This means we choose monolith over microservices when a single team can own the system, and choose managed services over self-hosted when...

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

...data platform" Data platform reference — ingestion, storage, processing, serving layers "We need a microservices foundation" Microservices reference — service mesh, observability, deployment pipeline...

1 dayIntensive
PracticalStandards exercise
ArchitectureEnterprise ContextStandardsReference ArchitectureGovernanceConsistencyView Details
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.

...requirements. Containers (Docker/K8s) — application-level control, medium overhead (orchestration). Best for microservices, portable workloads. Serverless (Lambda/Functions) — minimal control, low overhead (pay...

2 DaysIntensive
PracticalSA · EA
ArchitectureSolution DesignCloudInfrastructureSecurityFinOpsView Details
Requirements, Constraints, Trade-offs & Compromise
All levels — SA, EA, TS5-6 hoursTrade-off framework + constraint register template + requirements classification guide

The art of making the best possible architectural decision given what is required, what is constrained, and what must be sacrificed.

...Data consistency Strong consistency Eventual consistency Latency vs accuracy Deployment Monolith Microservices Simplicity vs independence Integration Synchronous Asynchronous Simplicity vs resilience...

1 DayIntensive
PracticeReal decisions
ArchitectureFoundationsRequirementsTrade OffsDecision MakingView Details
What Architecture Is
All levels — SA, EA, TS3-4 hoursArchitecture definition canvas + what it is / what it isn't reference card

What software and enterprise architecture actually is — its structure, relationships, and decisions — and what it is not. No diagrams. No jargon. Just clarity.

...Requirements change. Technology moves. Teams grow. The structure that made sense when you had three microservices and one team makes no sense when you have thirty microservices and eight teams. There...

Half-dayIntensive
FoundationFor all roles
ArchitectureFoundationsDecision 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.

...systems that don't solve the right problems. I've seen it. A team spent six months building a beautiful microservices architecture with event sourcing and CQRS. The business needed a working checkout. They...

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

...mistakes are predictable. They appear again and again. Mistake 1: Decomposing too early. Splitting into microservices before understanding the domain creates boundaries in the wrong places. Moving a boundary...

1.5 DaysIntensive
FoundationSA · EA
ArchitectureSolution DesignDecompositionDomain Driven DesignBoundariesView Details
Technology Strategy & Architecture Strategy
Advanced (EA, TS)5-6 hoursTechnology strategy vs architecture strategy distinction map + strategy brief template

How to distinguish technology strategy from architecture strategy, connect both to business strategy, and define a coherent direction for the organisation's technology investments.

...AI initiatives fail — no data to train on. Resolution: build data platform first, then AI. "We need microservices" but no platform — teams build micro-infrastructures — fragmentation. Resolution: build...

1.5 DaysIntensive
StrategicEA · TS
ArchitectureTechnology StrategyBusiness StrategyDirectionEnterprise ContextView 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.

...managing around. I've worked with organisations that had spent a year trying to build independent microservices with teams that still shared a database, a release process, and a weekly coordination meeting....

1 DayIntensive
Team BlueprintClear Boundaries
Team TopologiesOrganisational DesignConway's LawDelivery ExcellenceView Details
123