Skip to content

Search

Find insights, training programs, and workshops

Decision Velocity Is Not a Leadership Problem. It Is an Architecture Problem.
Decision Velocity Is Not a Leadership Problem. It Is an Architecture Problem.

Decision velocity is not constrained by leadership intent but by architectural design. Governance systems built for slower eras create mechanical delay between insight and execution.

...CIOs, Enterprise Architects, Strategy Leaders, Operating Model Owners Problem it solves: Strategic decisions move faster than execution because governance still operates on slower architectural rhythms Key...

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.

...model called Decision-Data Latency Alignment (DDLA) that matches data freshness to the cadence of the decisions it serves Time to implement: 30–60 days Business impact: Reduced infrastructure waste, eliminated...

Nobody Uses ADRs as an Agentic Decision Log. They Should.
Nobody Uses ADRs as an Agentic Decision Log. They Should.

Why Architectural Decision Records are the only structure most organizations already have that can govern AI agent accountability — and how to extend them into an Agentic Decision Log before the EU AI Act deadline.

Executive Summary Who this is for: Enterprise Architects, CTOs, Solution Architects, Architecture Governance Teams Problem it solves: Organizations deploying AI agents have no structural...

Your HCI Proof of Concept Measures the Wrong Thing.
Your HCI Proof of Concept Measures the Wrong Thing.

Most organizations evaluate private cloud and HCI platforms by running a technical POC. The POC passes. The platform fails. The reason is structural — and fixable. The Platform Fitness Evaluation Model (PFEM) tells you what to measure instead.

...platform succeeds Time to implement: 30–60 days before any platform commitment Business impact: Platform decisions that survive year two — not just the boardroom The Surgeon and the Operating Theatre Imagine...

Requirement Clarity: How Structured Persona Definition Reduces Rework and Misalignment
Requirement Clarity: How Structured Persona Definition Reduces Rework and Misalignment

A structured framework for defining personas that eliminates scope creep, reduces rework, and aligns engineering delivery with actual user needs — before development begins.

...adoption is low. Stakeholders question priorities. Scope shifts mid-sprint. Requirements get rewritten. Architecture decisions are challenged weeks after approval. This is not a capability problem. It is...

Application, Integration, API, Interface, Data & Process Design
Intermediate to Advanced (SA, EA)6-8 hoursIntegration design playbook + API design standards + data movement pattern guide

How the components of a solution are structured internally, how they communicate with each other, and how they connect to the data and processes they depend on.

...an illusion because two components could write the same data. Solution design is the set of layered decisions — application structure, integration patterns, API contracts, interface design, data ownership,...

2 DaysIntensive
ComprehensiveSA · EA
Application & Technology Landscape
All levels — SA, EA, TS4-5 hoursApplication landscape register + technology heat map + dependency matrix

How to build, read, and use the full picture of what an organisation runs — every application, platform, integration, and technology — and how they depend on each other.

...the landscape Reading the landscape Technology heat maps Dependency analysis Using the landscape for decisions Putting it all together Cheat sheet Before we start — the one thing to hold onto Most organisations...

1 dayIntensive
PracticalLandscape exercise
Requirements, Constraints, Trade-offs & Compromise
All levels — SA, EA, TS5-6 hoursTrade-off framework + constraint register template + requirements classification guide

The art of making the best possible architectural decision given what is required, what is constrained, and what must be sacrificed.

Quick Navigation Start here — What architecture really is Functional vs non-functional requirements Constraints Competing priorities Trade-off...

1 DayIntensive
PracticeReal decisions
Future Operating Model
Advanced (EA, TS)5-6 hoursFuture operating model scenarios + AI-native organisation design principles + transition pathway + Communication Structure Heatmap

How organisations will need to restructure their technology capabilities, teams, and governance as AI, automation, and platform thinking reshape what it means to run a technology function.

...changing The AI-augmented technology function Platform-based operating models The evolving role of architecture Skills and capabilities Governance in a future operating model Designing the transition AI...

1 DayIntensive
StrategicEA · TS
Roadmaps & Transformation Sequencing
Intermediate to Advanced (SA, EA, TS)5-7 hoursRoadmap template + transition state design guide + sequencing logic + dependency overlay

How to build multi-year transformation roadmaps that sequence architectural change realistically — accounting for dependencies, capacity, risk, and the fact that the organisation must continue operating while it transforms.

...transformation roadmap isn't a Gantt chart. It's not a list of projects with dates. It's a sequenced set of decisions and transitions that move the organisation from its current architecture to its target architecture...

1.5 DaysIntensive
StrategicSA · EA · TS
1···567···10