Search

Find insights, training programs, and workshops

Domain-Driven Design & Strategic Design Workshop
Enterprise & Solution Architects, Principal Engineers, Tech LeadsDomain map, bounded context canvas, ubiquitous language glossary, context map

Stop designing systems around databases and frameworks. Start designing around your business domains — and watch your architecture conversations change overnight.

...It's a domain boundary problem. You'll leave with a domain map your whole organisation can read, a bounded context canvas for each core domain, and a ubiquitous language your developers and business stakeholders...

1-2 DaysFacilitated
Domain MapStrategic Clarity
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.

...engineers avoid documentation. The problem is that one template cannot serve five different decision contexts. What Makes a Decision Context Different Before building templates, the dimensions of difference...

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.

...Void. The capability exists. The authority to invoke it does not. Signal 4: Undecided Boundary Two bounded contexts share a concept. Neither team is willing to own it entirely. Neither team is willing...

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.

...cycle Requiring board or governance review Examples: Establishing a new integration pattern between bounded contexts Introducing a new shared infrastructure dependency Defining a new event schema that...

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.

...Touchpoints which teams modify which components Layer 3 — Architectural Domains mapping code to system modules or bounded contexts Combined together, this reveals: structural instability zones boundary violations ownership...

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.

...reference to implementation detail Phase 2: Stand Up the MCP Governance Server (Weeks 3–4) Select one bounded context as the pilot. Work with the delivery team to stand up an MCP server that implements the...

Solving Technical Debt Through Feature Development: Turning Product Delivery into Architecture Improvement
Solving Technical Debt Through Feature Development: Turning Product Delivery into Architecture Improvement

A practical framework explaining how organizations can systematically reduce technical debt while delivering new features, instead of running disruptive modernization programs.

...Before a team could add a new payment method, they had to extract the payment processing logic into a bounded context. Each feature delivery automatically improved the architecture. Within six months, the...

The Architecture Evolution Model: How Architecture Changes from Startup to Enterprise
The Architecture Evolution Model: How Architecture Changes from Startup to Enterprise

A practical framework explaining how software architecture evolves from startup experimentation to enterprise-scale governance, and what architectural practices are needed at each stage.

...and designed the minimum governance structure needed for their size. The key change was introducing bounded contexts with clear ownership — teams could make decisions within their context without escalating...

Context-Driven Architecture: Why Software Design Must Adapt to Business Geography
Context-Driven Architecture: Why Software Design Must Adapt to Business Geography

Just as buildings must adapt to snow, desert, or tropical climates, software architecture must align with business geography to improve predictability and reduce complexity.

...environment — and redesigned the architecture to fit the new context. The monolith was decomposed into bounded contexts with clear ownership. Multi-tenant isolation was introduced at the database level. The...

Responsible AI — Ethics, Risk & Governance
Beginner to Intermediate4-5 hoursAI risk map + personal responsibility checklist + governance starter framework

Using AI responsibly — covering ethics, bias, hallucination risk, data privacy, accountability, and organisational governance. The judgment to use AI fairly, safely, and in a way you can defend.

...broken button in a product is annoying. Fix the code, redeploy, the button works again. The harm is bounded and reversible. A biased AI hiring tool is different. It doesn't fail for one person on one afternoon....

1 DayIntensive
Beginner FriendlyNo legal background required