Search

Find insights, training programs, and workshops

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.

Quick Navigation Start here — Why communication is an architecture skill Knowing your audience Presenting to executives Writing architecture...

1 DayIntensive
CriticalSA · EA · TS
Complete Enterprise Data Architecture Framework: Business, Logical, Physical Layers with Real Templates
Complete Enterprise Data Architecture Framework: Business, Logical, Physical Layers with Real Templates

Most enterprises build data architectures one layer at a time. Business, logical, and physical layers exist as separate artefacts owned by separate teams. That separation is the structural gap that makes data estates ungovernable.

...rule it was built to enforce. Three layers. Three islands. Zero coherence. That disconnection is not a communication problem. It is a structural failure. And it is the reason data estates drift the moment...

The Capability Map That Cannot Answer a Question Is Not a Capability Map
The Capability Map That Cannot Answer a Question Is Not a Capability Map

Why traditional capability maps fail to support governance decisions and how Queryable Capability Architecture turns static maps into interrogable decision systems.

...The First Planner: A Printed Map A large printed map shows: roads water pipelines electrical grids communication networks It provides a useful overview. But if the planner asks: Which pipelines serve...

Architectural Decision Records (ADR): The Missing Layer Between Strategy and Implementation
Architectural Decision Records (ADR): The Missing Layer Between Strategy and Implementation

A practical guide explaining why Architectural Decision Records (ADR) are the missing link between enterprise architecture strategy and engineering implementation.

...contains five simple sections. Context What problem are we trying to solve? Example: "We need a reliable communication mechanism between microservices." Options Considered What alternatives were evaluated?...

The Minimum Architecture Every Company Needs: The House, the Hallway, and the Doorbell
The Minimum Architecture Every Company Needs: The House, the Hallway, and the Doorbell

A practical architectural model explaining why most companies only need a modular monolith, a workflow orchestrator, and outcome-based events.

...in the house. Important characteristics: Clear module boundaries Shared runtime environment Internal communication through direct calls Consistent data model This structure reduces: network latency operational...

The Strategy-to-Execution Gap: How Enterprise Architecture Bridges the 'What' and the 'How'
The Strategy-to-Execution Gap: How Enterprise Architecture Bridges the 'What' and the 'How'

Why strategic intent evaporates before it reaches engineering teams — and how Enterprise Architecture creates the translation layer that makes organizational strategy executable.

...Gap Is Structural, Not Cultural Most organizations try to close the strategy-to-execution gap with communication. More town halls. Better slide decks. OKRs cascaded to every team. A strategy page in Confluence...

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.

...services the frequency and volume of each call latency and failure rates per path This data reveals the actual communication topology of the system. Not the planned one. Undocumented Dependencies Traces often reveal...

AI Architecture Clarity: Understanding LLM, RAG, Agents, and MCP Through the Brain Model
AI Architecture Clarity: Understanding LLM, RAG, Agents, and MCP Through the Brain Model

A clear executive guide explaining LLM, RAG, AI Agents, and MCP using the Brain model to prevent enterprise AI instability.

...to tools. It defines: How tools are described How context is passed How capabilities are exposed How communication is structured MCP is not intelligence. It is not business rules. It is structured communication...

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.

...teams implement the same integration differently No canonical contract governs how boundary-crossing communication occurs The domain-agnostic statement is the search query. Not the technology vocabulary....

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.

...Before we start — the one thing to hold onto The architecture of the systems you build will mirror the communication structure of the teams that build them — whether you design it that way or not. This is...

1 DayIntensive
StrategicEA · TS