Search

Find insights, training programs, and workshops

Application, Integration, API, Interface, Data & Process Design
Intermediate to Advanced (SA, EA)6-8 hoursIntegration design playbook + API design standards + data movement pattern guide

How the components of a solution are structured internally, how they communicate with each other, and how they connect to the data and processes they depend on.

Quick Navigation Start here — Solution design Application design Integration patterns API design Interface design Data design Process design Putting it together Cheat...

2 DaysIntensive
ComprehensiveSA · EA
MCP Is Not an AI Protocol. It Is a Governance Layer.
MCP Is Not an AI Protocol. It Is a Governance Layer.

MCP is classified as an AI integration protocol. It is actually a governance primitive — the stable interface layer that architecture fitness functions have been missing for years.

...was adopting MCP to connect AI agents to internal systems. The engineering team saw it as a protocol integration. The security team saw it as a data exposure risk. Neither was wrong — but neither was asking...

Application & Technology Landscape
All levels — SA, EA, TS4-5 hoursApplication landscape register + technology heat map + dependency matrix

How to build, read, and use the full picture of what an organisation runs — every application, platform, integration, and technology — and how they depend on each other.

...technology landscape is the full picture of what an organisation runs — every application, platform, integration, and technology — and how they depend on each other. It's the foundation for every rationalisation,...

1 dayIntensive
PracticalLandscape exercise
Automation & Agentic Systems
Intermediate to Advanced (SA, EA, TS)6-7 hoursAutomation opportunity map + agent architecture blueprint + MCP/A2A integration guide + Agentic Risk & Cost Framework

How AI-powered architectures that plan, act, and use tools autonomously are reshaping integration and workflow — covering agentic patterns, MCP and A2A protocols, orchestration frameworks, human-in-the-loop design, guardrails, observability, and economic risk management.

...They're fundamentally different. Agents plan, act, and use tools — the architecture challenge shifts from integration to orchestration. Agentic systems require new architectural patterns — orchestration, memory,...

1.5 DaysIntensive
CurrentSA · EA · TS
Security Is Not a Gate. It Is an Architecture Property.
Security Is Not a Gate. It Is an Architecture Property.

Security is treated as a gate at the end of delivery. It should be an architecture property designed into three distinct boundaries. Here is the model that fixes the friction between security and delivery.

...security. A team builds a service. They design the API. They define the data model. They choose the integration pattern. They run the tests. At the end, security reviews it. The reviewer finds: no encryption...

ADR Templates: 5 Variations for Different Contexts + Governance Automation
ADR Templates: 5 Variations for Different Contexts + Governance Automation

One ADR template does not fit every architectural context. Five purpose-built variations — for standard decisions, agentic AI, cross-domain impact, fast delivery, and high-risk reversals — plus governance automation to make the system run without manual follow-up.

...governance. Template 1 — Standard ADR Context: The everyday architectural decision. A technology choice. An integration pattern. A data model shape. Affects one system. Reversible within a sprint. Made by one...

AI Decision Rights: Who Decides What When No Human Is Watching?
AI Decision Rights: Who Decides What When No Human Is Watching?

Decision rights models assume human decision-makers. AI agents breach that assumption silently. Here is how to extend decision rights to cover autonomous actors before the first ungoverned decision becomes a production incident.

...implement. Boards approve. Governance reviews. Then an agent enters. It routes traffic. It selects integration patterns. It triages incidents. It approves transactions. It resolves ambiguous schemas by...

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.

...levels. Enterprise Architecture Defines strategic direction: Technology standards Platform strategy Integration principles Capability models This answers: What should the technology landscape look like?...

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.

...already capable of: Generating reference architectures Comparing cloud deployment models Suggesting integration patterns Identifying scalability bottlenecks Producing documentation Simulating trade-offs...

Architecture vs Design: Why Most Organizations Confuse Them
Architecture vs Design: Why Most Organizations Confuse Them

A clear explanation of the difference between architecture and design, why organizations confuse them, and how this confusion creates structural instability in technology systems.

...system. It answers questions like: What capabilities must exist? How are major components separated? What integration patterns are allowed? Where are data ownership boundaries? What technology constraints exist? What...