Search

Find insights, training programs, and workshops

Investment & Prioritisation
Advanced (EA, TS)5-6 hoursInvestment prioritisation model + business case guide (including TCO and unit economics) + sequencing criteria

How to decide which technology initiatives get funded, in what order, and why — connecting architecture to financial decisions and business outcomes.

...business case Value and risk Portfolio prioritisation frameworks Sequencing Architecture's role in investment Common mistakes FinOps as investment input Putting it all together Cheat sheet Before we start...

1 DayIntensive
StrategicEA · TS
Portfolio & Dependency Thinking
All levels — SA, EA, TS4-5 hoursPortfolio map template + dependency radar + investment alignment grid

How to see all systems, initiatives, and investments as a connected whole — understanding dependencies, shared capabilities, and how decisions in one place ripple across others.

...isolation. They're part of a portfolio — a connected collection of systems, programmes, platforms, and investments. Decisions made about one system ripple across others. An investment in one programme constrains...

1 dayIntensive
StrategicPortfolio-level
Technology Strategy & Architecture Strategy
Advanced (EA, TS)5-6 hoursTechnology strategy vs architecture strategy distinction map + strategy brief template

How to distinguish technology strategy from architecture strategy, connect both to business strategy, and define a coherent direction for the organisation's technology investments.

...cloud, AI, and platforms because everyone else is — not because a deliberate analysis connected those investments to business goals. I've seen CTOs announce "cloud-first strategy" — but cloud-first is a...

1.5 DaysIntensive
StrategicEA · TS
The Capability Map That Cannot Answer a Question Is Not a Capability Map
The Capability Map That Cannot Answer a Question Is Not a Capability Map

Why traditional capability maps fail to support governance decisions and how Queryable Capability Architecture turns static maps into interrogable decision systems.

...Better governance decisions, clearer ownership visibility, reduced technology duplication, and improved investment alignment The Capability Map Illusion Almost every large organization maintains a capability...

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.

...architecture for one strategic priority Business impact: Delivery teams that build the right things, investment aligned to strategic intent, and governance that closes the gap between declared strategy...

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.

...where you are before you decide where to go Time to implement: 30–60 days Business impact: Architecture investment targets the right layer at the right time The Pilot Does Not Ask If the Plane Feels Ready...

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.

...alongside office amenities and learning allowances. This categorisation is the problem. Not because the investments are wrong. Because the framing removes DX from the only place where it matters: The delivery...

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.

...Technology Leadership Vision articulation Strategic technology bets Capability roadmapping Talent shaping Investment prioritization Innovation sponsorship Leadership tolerates ambiguity. It operates under uncertainty....

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.

...validation, without product governance, and without a mechanism to retire what nobody uses. Why Platform Investments Fail to Move Adoption Three structural failures produce the same outcome: a platform that...

Architecture Across the Application Lifecycle: Which Architect Is Needed When?
Architecture Across the Application Lifecycle: Which Architect Is Needed When?

A practical guide explaining which type of architect is required at each stage of the application lifecycle to prevent governance friction and structural instability.

...This stage determines structural direction. Mistakes here create strategic misalignment and redundant investment. Who Should Not Lead Here Technical Architects should not define platform posture. Solution...