Skip to content

Search

Find insights, training programs, and workshops

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.

...produce domain models but never surface ownership gaps… if governance conflicts only become visible when delivery has already stalled… or if policy decisions are still being made in incident retrospectives...

Your AI Agents Are Making Architecture Decisions. Nobody Assigned Them That Role.
Your AI Agents Are Making Architecture Decisions. Nobody Assigned Them That Role.

AI agents are making micro-architecture decisions in production. No ADR recorded them. No review board approved them. No architect ever saw them. Here is the structural fix.

...behaviour aligned with architectural intent No over-engineered frameworks. No restrictions that slow delivery. Just boundaries that make intelligent systems governable. → Book an Agent Governance Session or →...

Technical Debt & Rationalisation
Intermediate to Advanced (SA, EA, TS)5-6 hoursTechnical debt taxonomy + rationalisation prioritisation framework + modernisation criteria

How to understand, measure, prioritise, and reduce technical debt — the accumulated cost of shortcuts, outdated decisions, and deferred maintenance.

...the system becomes legacy, where change isn't just slow but dangerous. I've seen leadership ask why delivery is slowing while keeping the same number of engineers. The answer is always debt — invisible,...

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

...purpose Putting it all together Cheat sheet Before we start — the one thing to hold onto Most leaders treat delivery friction as a people problem. The wrong engineers. Not enough of them. Low motivation. They...

1 DayIntensive
BoundariesStructure as design
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.

...They're discovered late — in testing or production. Expensive to fix — architecture rework, delayed delivery. How to classify requirements: Ask two questions for every requirement. Does it describe what...

1 DayIntensive
PracticeReal decisions
AI Procurement, Vendor Evaluation & Tool Selection
Beginner to Intermediate3-4 hoursVendor evaluation scorecard + tool selection checklist + risk review template

Choosing AI tools is not a beauty contest. Learn how to evaluate vendors, compare capabilities, assess risk, avoid lock-in, and buy systems that your organisation can actually govern and adopt.

...pressure not to be left behind. Internal stakeholders bring different priorities: security wants control, delivery teams want speed, finance wants clarity, and end users want the tool that feels easiest. In...

Half DayDecision Focused
Vendor SelectionPractical
Architecture Communication & Storytelling
Intermediate to Advanced (SA, EA, TS)5-6 hoursArchitecture communication playbook + executive presentation template + workshop facilitation guide

How to communicate architecture decisions so they are understood, adopted, and acted on — covering audience adaptation, executive communication, architecture papers, diagrams, workshop facilitation, and influence without authority.

..."This reduces our outage risk by enabling systems to fail independently. It also accelerates feature delivery by removing integration bottlenecks." CTO "We are moving from synchronous REST calls to Kafka-based...

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

...decisions, architecture drift, surprises in production, and rework. The cost is higher ops, slower delivery, and security gaps. Governance is how architecture turns principles into practice — through...

1 DayIntensive
PracticalSA · EA · TS
Investment & Prioritisation
Advanced (EA, TS)5-6 hoursInvestment prioritisation model + business case guide (including TCO and unit economics) + sequencing criteria

How to decide which technology initiatives get funded, in what order, and why — connecting architecture to financial decisions and business outcomes.

...translation guide: Technical need Business case translation "Refactor the monolith" "Reduce feature delivery from 6 weeks to 2 weeks — 3x velocity improvement" "Adopt event-driven integration" "Decouple...

1 DayIntensive
StrategicEA · 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.

...domain teams — autonomy within guardrails. Implementation owned by stream teams — full ownership of delivery. Transitioning from centralised to federated: Centralised — everything through one body. Delegate...

1 DayIntensive
StrategicEA · TS