Search

Find insights, training programs, and workshops

Build / Buy / Partner / Participate — Ecosystem Strategy
Intermediate to Advanced (SA, EA, TS)5-6 hoursBuild/buy/partner/participate decision framework + vendor and ecosystem evaluation scorecard + exit and switching cost analysis template

How to decide what to build, what to buy, what to access through partners, and what to participate in through ecosystems — covering differentiation vs commodity analysis, vendor evaluation, total cost of ownership, interoperability velocity, exit strategy, and lock-in risk.

...partner When to participate Evaluating vendors Total cost of ownership Interoperability velocity Exit strategy Lock-in risk Putting it all together Cheat sheet Before we start — the one thing to hold onto...

1 DayIntensive
StrategicSA · EA · TS
ArchitectureSourcing StrategyEcosystemBuild vs BuyVendor ManagementStrategyView Details
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.

...Medium Medium Dead letter queues, retries Event-driven (Pub/Sub) Loose Eventual Variable High Event sourcing, idempotency Batch (ETL/ELT) Loose Delayed High Medium Retry whole batch, data validation When...

2 DaysIntensive
ComprehensiveSA · EA
ArchitectureSolution DesignIntegrationAPI DesignData DesignView Details
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.

...designing a single service or an entire organisation. A component-level decision — like "use event sourcing in this service" — ripples upward. Suddenly you need event infrastructure. Suddenly other teams...

Half-dayIntensive
FoundationFor all roles
ArchitectureFoundationsDecision MakingView Details
Why Architecture Exists
All levels — SA, EA, TS3-4 hoursArchitecture purpose framework — complexity · alignment · risk · change · shared understanding

Why architecture exists — managing complexity, aligning technology with business, reducing risk, enabling change, and creating shared understanding across teams.

...problems. I've seen it. A team spent six months building a beautiful microservices architecture with event sourcing and CQRS. The business needed a working checkout. They built the wrong thing beautifully. Without...

Half-dayIntensive
PurposeWhy it matters
ArchitectureFoundationsComplexityBusiness AlignmentView Details