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.

...authorities, undecided policies — stay invisible until production fails Key outcome: A structured second Event Storming pass that turns a domain model into a governance gap register Time to implement: 30–60...

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.

...developers, or drawing diagrams nobody agrees on. Your system is a sequence of things that happened — domain events. If you can name every significant event in order, you understand the system. If you can't, no...

1 DayIntensive
Shared ModelOne Language
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.

...SLAs Interface specs, SLAs Variable Contractual Take one architecture decision — "We are migrating to event-driven integration" — and translate it for each audience: Audience Translation CEO "This reduces...

1 DayIntensive
CriticalSA · EA · TS