Skip to content

Search

Find insights, training programs, and workshops

The Architecture Review Is Broken. Replace It with Fitness Functions.
The Architecture Review Is Broken. Replace It with Fitness Functions.

The architecture fitness function literature solved code-level governance. It never made the claim that the board itself becomes optional. Here is the missing argument — and the economics that prove the board is the slower and more expensive option.

Executive Summary Who this is for: Enterprise Architects, CTOs, Architecture Review Board members, Engineering Leaders, Governance Owners Problem it solves: Architecture...

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.

...Summary Who this is for: Solution Architects, Technical Architects, Engineering Leads Problem it solves: Architecture reviews rely on diagrams and governance documents that often fail to reflect the real system...

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.

Executive Summary Who this is for: Enterprise Architects, CTOs, CIOs, Architecture Leads, Engineering Leaders Problem it solves: Strategic intent evaporates between the boardroom...

You Cannot Improve an Architecture You Have Not Measured.
You Cannot Improve an Architecture You Have Not Measured.

Enterprise architecture maturity is not a feeling. It is a score. Organizations that cannot measure their architecture maturity cannot improve it. The EAMS model gives you the score.

Executive Summary Who this is for: CTOs, CIOs, Enterprise Architects, Architecture Review Boards, Operating Model Owners Problem it solves: Organizations invest in architecture...

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.

Executive Summary Who this is for: CIOs, CTOs, Enterprise Architects, Architecture Leaders Problem it solves: Growing belief that AI can fully design software architecture...

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.

Executive Summary Who this is for: Enterprise Architects, Solution Architects, Architecture Leads, Engineering Managers Problem it solves: A single ADR template applied to every decision...

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.

...this is for: CTOs, Enterprise Architects, Solution Architects, Engineering Leaders Problem it solves: Architecture strategy exists but decision logic is undocumented and lost Key outcome: A structured way...

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.

Executive Summary Who this is for: Enterprise Architects, Solution Architects, Architecture Leads, Domain-Driven Design practitioners Problem it solves: Governance gaps — missing owners,...

Monitoring Added After Deployment Is Not Observability. It Is Archaeology.
Monitoring Added After Deployment Is Not Observability. It Is Archaeology.

Observability is not a monitoring add-on. It is an architectural constraint. Systems built without observability baked in cannot be understood, cannot be governed, and cannot be improved. The OSAF model tells you exactly where your architecture is blind.

...add. It is a constraint you design from. Core outcome: A structured model called Observability Signal Architecture Framework (OSAF) that tells you exactly where your architecture is blind before failure...

1···345···10