Find insights, training programs, and workshops
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...
How to design, run, and improve architecture review forums — the structured spaces where decisions are evaluated, challenged, approved, and communicated.
Quick Navigation Start here — Why reviews exist Types of review Who sits in which forum Running effective reviews Decision authority Technical...
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.
Executive Summary Who this is for: CTOs, Enterprise Architects, Architecture Leads designing or operating AI-powered systems Problem it solves: Structural drift caused...
Batch review cannot govern continuous change. How to encode architectural invariants as automated checks — and what still belongs to the board.
Quick Navigation Start here — the inspector who visits once a month What the review board actually governs The batch problem What makes a fitness function a fitness function Three...
How to create, govern, and operationalise architecture standards and reference architectures — the agreed patterns and structures that create consistency, reduce duplication, and accelerate delivery at scale.
Quick Navigation Start here — What standards are Types of standards What reference architectures are Creating standards that get adopted Governing standards Reference architecture examples Consistency...
Why architecture diagrams describe a system that no longer exists, and how Observable Architecture uses production telemetry to reveal what is actually running.
...Solution Architects, Enterprise Architects, Senior Engineers, Security Architects Problem it solves: Architecture diagrams describe the intended system, not the running system — creating an invisible gap...
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.
...designing or operating enterprise data estates Problem it solves: Business, logical, and physical data architecture layers built in isolation — by different teams, in different tools, with no connecting model Key...
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.
...delivery — creating friction, delays, and a false sense of safety — instead of being designed into the architecture as a structural property Key insight: Security decisions belong at the architectural level...
A clear explanation of the difference between architecture and design, why organizations confuse them, and how this confusion creates structural instability in technology systems.
...Architects, Solution Architects, Engineering Leaders Problem it solves: Persistent confusion between architecture and design in software and technology organizations Key outcome: Clear structural separation...