Search

Find insights, training programs, and workshops

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.

...to implications. A bad principle: "We prefer simplicity." A good principle: "We prefer the simplest solution that meets the need because complexity increases cost of change. This means we choose monolith...

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

...systems you build will mirror the communication structure of the teams that build them — whether you design it that way or not. This is Conway's Law, and it's not a suggestion. It's a description of reality....

1 DayIntensive
StrategicEA · TS
Current State & Target State Architecture
All levels — SA, EA, TS4-5 hoursAs-is / to-be architecture canvas + transition state design + maturity scale + AI readiness assessment

How to document what exists today, define what must exist tomorrow, and design the transition states that get you there — the discipline of architecture that connects present reality to future goals.

...target is where transformation planning lives. None of these are optional. Skip current state and you design in a vacuum. Skip target state and you drift without direction. Skip transition states and you...

1 dayIntensive
PracticalCanvas exercise
Architecture Patterns That Travel Across Industries
Architecture Patterns That Travel Across Industries

The patterns that solve your hardest distributed systems problems were already solved — in a submarine, a postal sorting office, and an electrical panel. Most architects never look.

Executive Summary Who this is for: Enterprise Architects, Solution Architects, Senior Engineers, Architecture Leads Problem it solves: Architects solve problems...

Run Event Storming Twice. The First Maps the System. The Second Exposes Governance.
Run Event Storming Twice. The First Maps the System. The Second Exposes Governance.

Why the second run of an Event Storming workshop — the one most teams never attempt — is the fastest way to surface governance gaps that architecture diagrams will never show.

Executive Summary Who this is for: Enterprise Architects, Solution Architects, Architecture Leads, Domain-Driven Design practitioners Problem it solves: Governance...

Your Architecture Diagrams Are Lying to You
Your Architecture Diagrams Are Lying to You

Why architecture diagrams describe a system that no longer exists, and how Observable Architecture uses production telemetry to reveal what is actually running.

Executive Summary Who this is for: Solution Architects, Enterprise Architects, Senior Engineers, Security Architects Problem it solves:...

Event Storming Workshop
Enterprise & Solution Architects, Principal Engineers, Product Managers, Domain ExpertsEvent timeline, domain hotspot map, aggregate boundaries, process ownership canvas

Get your developers, domain experts, and business stakeholders in the same room, speaking the same language, discovering the same system — in one day.

...it) Developers and Engineers who build and maintain the system Product Managers and Business Analysts Solution Architects and Tech Leads Typical team size: 8-15 participants (larger is possible with co-facilitation) Format:...

1 DayIntensive
Shared ModelOne Language
Architecture Across the Application Lifecycle: Which Architect Is Needed When?
Architecture Across the Application Lifecycle: Which Architect Is Needed When?

A practical guide explaining which type of architect is required at each stage of the application lifecycle to prevent governance friction and structural instability.

Executive Summary Who this is for: CIOs, CTOs, Enterprise Architects, Solution Architects, Technical Architects Problem it solves: Architectural overreach or absence at different...

Your Git History Is an Architecture Health Report. Nobody Is Reading It.
Your Git History Is an Architecture Health Report. Nobody Is Reading It.

A practical architecture technique showing how Git commit patterns reveal structural instability, boundary violations, and ownership gaps in software systems.

Executive Summary Who this is for: Solution Architects, Technical Architects, Engineering Leads Problem it solves: Architecture reviews...

Architecture in the Age of AI: What Can Be Automated — and What Cannot
Architecture in the Age of AI: What Can Be Automated — and What Cannot

A governance-driven perspective explaining why software architecture cannot be automated because decision accountability and consequence ownership cannot be delegated to AI.

...CTOs, Enterprise Architects, Architecture Leaders Problem it solves: Growing belief that AI can fully design software architecture Key insight: AI can generate architectural options, but it cannot own architectural...