Skip to content

Search

Find insights, training programs, and workshops

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-first" — but cloud-first is a technology choice, not an architecture strategy. Without the distinction, teams pick technologies without understanding how those technologies should be organised, connected,...

1.5 DaysIntensive
StrategicEA · TS
What Architecture Is
All levels — SA, EA, TS3-4 hoursArchitecture definition canvas + what it is / what it isn't reference card

What software and enterprise architecture actually is — its structure, relationships, and decisions — and what it is not. No diagrams. No jargon. Just clarity.

...architects who had produced hundreds of diagrams over eighteen months, and when I asked a developer on the team why a particular technology was chosen, nobody could tell me. Not because the diagrams were bad....

Half-dayIntensive
FoundationFor all roles
Developer Experience as a Control System
CTOs, Engineering Leads, Platform Engineering Teams, Engineering Managers3-4 hoursA delivery friction map across four sprints, one named constraint pillar, and a traced DX-to-delivery signal

DevEx is not a perk — it is the set of operating conditions that governs how fast and how safely change moves through your delivery system.

...context switching is tracked, meeting patterns are governed as a delivery variable, and architecture boundaries are designed to reduce how many systems one developer must hold in working memory at once...

1 DayIntensive
ConditionsNot satisfaction
Execution Stability & Structured Refactoring
CTOs, Engineering Directors, Principal Engineers, Engineering Managers3-4 hoursA classified structural risk map — your top friction modules sorted into dicing, slicing and peeling with a governance rule attached

Delivery slows because structural entropy accumulates unmeasured. Classify refactoring into dicing, slicing and peeling to restore predictability.

...90-day rollout Putting it all together Cheat sheet Before we start — the one thing to hold onto Your team is shipping. But velocity is declining. Cycle time stretches from 5 days to 12. Regression bugs...

1 DayIntensive
LayersNot cleanup
Paying Down Debt Through Feature Work
CTOs, Engineering Leaders, Enterprise Architects, Product Leaders3-4 hoursA feature-driven debt reduction policy — the rule, the visibility mechanism, and the two questions review asks about every feature

Debt accumulates faster than refactoring projects can remove it. Fund architecture improvement through the product roadmap instead of competing with it.

...sheet Before we start — the one thing to hold onto Every engineering organisation recognises technical debt. Teams say: we should refactor this, this module needs redesign, we need to clean up the architecture. Then...

1 DayIntensive
ContinuousNot a project
Architecture Communication & Storytelling
Intermediate to Advanced (SA, EA, TS)5-6 hoursArchitecture communication playbook + executive presentation template + workshop facilitation guide

How to communicate architecture decisions so they are understood, adopted, and acted on — covering audience adaptation, executive communication, architecture papers, diagrams, workshop facilitation, and influence without authority.

...don't know about it. I've seen architects produce 60-page papers that nobody outside the architecture team read, and 45-slide executive decks full of diagrams that overran board meetings with no decisions...

1 DayIntensive
CriticalSA · EA · TS
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.

...together?" Solution design = six layers of decisions from structure to workflow. Application design — Boundaries, responsibilities, and internal structure You've decomposed a system into components. Now...

2 DaysIntensive
ComprehensiveSA · EA
Capability Mapping & Business Outcomes
All levels — SA, EA, TS4-5 hoursBusiness capability map template + capability-to-outcome linkage model

How to build business capability maps, connect them to technology, and link capabilities to strategic outcomes — the bridge between business strategy and technical architecture.

...maps that were just org charts in disguise — "Salesforce management" listed as a capability, "the KYC team" listed as a capability. Those aren't capabilities. They're temporary structures. A business capability...

1.5 daysIntensive
PracticalMap-building exercise
Future of AI
Intermediate to Senior Leaders3-4 hoursAI horizon scan + strategic implications analysis + preparation roadmap

What's coming in AI — multimodal models, on-device AI, open-source momentum, protocols, regulation, and the shift to AI-native organisations. See around the corner without falling for hype.

...creating an interoperable ecosystem where tools and agents can work together across organisational boundaries. Two open protocols are shaping the future: MCP (Model Context Protocol) creates a universal...

Half DayIntensive
Horizon ScanDeliverable
Event Storming Workshop
Enterprise & Solution Architects, Principal Engineers, Product Managers, Domain ExpertsEvent timeline, domain hotspot map, aggregate boundaries, process ownership canvas

Get your developers, domain experts, and business stakeholders in the same room, speaking the same language, discovering the same system — in one day.

Before we start — the one thing to hold onto Most teams think their biggest problem is documentation. Nobody wrote down how the system works. Nobody knows...

1 DayIntensive
Shared ModelOne Language