Skip to content

Search

Find insights, training programs, and workshops

Team Topologies & Organisational Design Workshop
CTO, VP Engineering, Engineering Directors, Principal EngineersTeam topology map, interaction model, platform team charter, cognitive load assessment

Your architecture isn't just a technical choice. It's a consequence of how your teams are structured. Fix the structure, and the architecture follows.

...system that looks like your organisation. That's not a metaphor — it's a law. If you want a different architecture, you need a different team structure first. That one idea changes everything. It turns...

1 DayIntensive
Team BlueprintClear Boundaries
Fitness Functions Instead of Review Boards
Enterprise Architects, CTOs, Review Board Members, Engineering Leaders3-4 hoursA three-tier fitness function plan — your first three invariants automated, and the board agenda they retire

Batch review cannot govern continuous change. How to encode architectural invariants as automated checks — and what still belongs to the board.

...weeks. They arrive with a clipboard. The crew halts work. The inspector walks the site, approves some decisions, tables others for next time, and misses the decisions already buried behind drywall. The crew...

1 DayIntensive
ContinuousNot batched
Delivery Metrics That Mean Something
Engineering Managers, Tech Leads, VP Engineering, CTOs3-4 hoursA delivery scorecard — four DORA signals plus a five-dimension maturity baseline with one named bottleneck

How to replace delivery dashboards that measure activity with signals that tell you which dimension is actually holding delivery back — and what to fix first.

...whether the aircraft is ready to fly. Most organisations do not treat delivery this way. They say: our architecture is maturing, our governance is improving, we are becoming more agile. Those are feelings,...

1 DayIntensive
EvidenceNot feeling
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.

Executive Summary Who this is for: CTOs, Enterprise Architects, AI Governance Leads, Architecture Board Members, Heads of Engineering Problem it solves: Decision rights models exist in most...

Your Platform Team Is Building a Product Nobody Asked For.
Your Platform Team Is Building a Product Nobody Asked For.

Most platform teams build internal products their engineering teams never chose. Platform adoption is not a marketing problem. It is a product governance problem. Here is the model that fixes it.

...decision. The platform team controls what gets built. The engineering teams decide what gets used. These two decisions operate in different governance structures — and the gap between them is where platform investment...

Developer Experience Is Not a Perk. It Is a Delivery Control System.
Developer Experience Is Not a Perk. It Is a Delivery Control System.

Developer experience is not about making developers happy. It is about controlling the conditions that determine delivery output. Organizations that treat DX as a perk have removed the control system from their delivery engine without knowing it.

Executive Summary Who this is for: CTOs, Engineering Leads, Platform Engineering Teams, Architecture Review Boards, Engineering Managers Problem it solves: Organizations invest in developer...

Technology Leadership vs Technology Governance: Why Confusing the Two Creates Structural Instability
Technology Leadership vs Technology Governance: Why Confusing the Two Creates Structural Instability

A structured executive guide explaining the difference between Technology Leadership and Technology Governance, and why confusing the two creates instability in enterprise execution.

...position us competitively? Where should we invest? What must we deliberately not pursue? How should architecture evolve over 3–5 years? Leadership defines ambition. It aligns technology with business...

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.

...production incident Key insight: AIDRA already names the boundaries that matter for individual agent decisions. Applying the same three boundaries to team design means an AI-native team is not defined by...

From Creation to Autonomy: Understanding Generative AI, AI Agents, and Agentic AI Through a Workplace Analogy
From Creation to Autonomy: Understanding Generative AI, AI Agents, and Agentic AI Through a Workplace Analogy

A clear executive guide explaining Generative AI, AI Agents, and Agentic AI using a corporate office analogy to prevent autonomy risks in enterprise AI.

...Governance Need: Content review and data control Generative AI produces output. It does not execute decisions. AI Agent = The Operations Staff Member Now imagine giving that employee system access. The...

AI Policy, Security & Organisational Controls
Beginner to Intermediate4-5 hoursAI policy checklist + security controls map + incident response starter template

Building and enforcing AI policy — the practical mechanisms that turn ethical principles into enforceable organisational rules. Data security, access controls, audit trails, and incident response.

...between. Specific enough to be actionable. Readable enough to be understood. Structured around the decisions employees actually face. Section What it must answer Scope Does this apply to all staff?...

1 DayIntensive
Beginner FriendlyNo legal background required
1···78910