Skip to content

Search

Find insights, training programs, and workshops

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.

...systems Problem it solves: Structural drift caused by AI agents making undocumented, unreviewed architecture decisions at runtime Key outcome: A clear governance model that defines exactly where agents act freely,...

Review Forums & Decision Authority
Intermediate (SA, EA, TS)3-4 hoursArchitecture board design guide + review charter template + decision rights matrix

How to design, run, and improve architecture review forums — the structured spaces where decisions are evaluated, challenged, approved, and communicated.

...Navigation Start here — Why reviews exist Types of review Who sits in which forum Running effective reviews Decision authority Technical leadership groups Common failure modes Putting it all together Cheat sheet Before...

Half-dayIntensive
PracticalSA · EA · TS
AI Decision-Making & Human Oversight
Beginner to Intermediate3-4 hoursHuman oversight framework + decision rights map + review checklist

AI can assist decisions, but accountability still belongs to people. Learn the operating rules for review, approval, escalation, confidence, and human authority in AI-supported work.

...mistake everyone makes The control principle Assistance is not authority Levels of human oversight Decision support vs decision delegation Confidence, escalation, and review When not to automate decisions Designing...

Half DayPractical
Control ModelDecision Ready
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.

...Architects, Solution Architects, Engineering Leaders Problem it solves: Architecture strategy exists but decision logic is undocumented and lost Key outcome: A structured way to capture architectural decisions...

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.

...cannot own architectural accountability Core outcome: Clear distinction between mechanical design and decision governance Time to implement: 30–60 days Business impact: Protects structural stability in...

Batch vs Real-Time Is the Wrong Debate.
Batch vs Real-Time Is the Wrong Debate.

Organisations debate batch versus real-time as if it is a technical preference. It is not. It is a structural mismatch between data freshness and decision cadence — and the mismatch is where the cost lives.

...it solves: Organisations choosing data pipeline patterns based on technical preference rather than decision cadence requirements Key outcome: A structural model called Decision-Data Latency Alignment...

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.

...Architecture Leads, Engineering Managers Problem it solves: A single ADR template applied to every decision produces incomplete records, ignored fields, and governance that nobody trusts Key outcome:...

AI-Native Teams Don't Need New Titles. They Need Named Owners.
AI-Native Teams Don't Need New Titles. They Need Named Owners.

AI-native team redesigns keep adding new job titles and calling it done. The actual failure mode sits at the decision boundary. Here is what changes when you apply AIDRA to team design instead of headcount.

...redesigns focus on new job titles and shrinking headcount, while the actual failure mode — an unowned AI decision boundary — goes unaddressed and shows up later as an unowned production incident Key insight:...

Stakeholder Management & Politics
Intermediate to Advanced (SA, EA, TS)5-6 hoursStakeholder map template + conflict resolution framework + executive alignment guide

How to navigate organisational dynamics, manage conflicting priorities, resolve decision deadlocks, and build executive alignment — because the best architecture recommendation fails without stakeholder alignment.

...an architecture concern Stakeholder mapping Managing conflicting priorities Difficult stakeholders Decision deadlocks Executive alignment Organisational resistance Putting it all together Cheat sheet Before...

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.

...whole subject of this module. The org chart is a hypothesis — Team boundaries are the architectural decision Every org chart is a hypothesis. It says: if we assign these people to these domains, ownership...

1 DayIntensive
BoundariesStructure as design