Search

Find insights, training programs, and workshops

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.

Quick Navigation Start here — Solution design Application design Integration patterns API design Interface design Data design Process...

2 DaysIntensive
ComprehensiveSA · EA
Technology, Infrastructure, Cloud & Security Design
Intermediate to Advanced (SA, EA)6-8 hoursInfrastructure decision framework + cloud pattern reference + security controls map

Where abstract architecture meets physical reality — choosing the platforms, compute, networking, and security controls that make the solution work at scale.

Quick Navigation Start here — Technology selection Cloud fundamentals Infrastructure design Cloud patterns Security design Identity and access management Cost and lock-in FinOps Putting...

2 DaysIntensive
PracticalSA · EA
Solution Decomposition
Intermediate (SA, EA)4-6 hoursDecomposition canvas + domain/service/component hierarchy guide

How to break large, complex systems into smaller, independently manageable parts — so different teams can build, own, and change them without stepping on each other.

...decomposition matters Strategies for decomposition Defining boundaries Coupling and cohesion Domain-Driven Design basics Common mistakes Putting it all together Cheat sheet Before we start — the one thing to...

1.5 DaysIntensive
FoundationSA · EA
Common Architecture Patterns
Intermediate (SA, EA)5-7 hoursPattern selection guide + pattern comparison matrix + anti-pattern catalogue

Proven, reusable solutions to recurring structural problems — each with known trade-offs that make it suited to some contexts and unsuitable for others.

...this pattern goes wrong when misapplied. Here's the part that catches people out: a pattern isn't a solution. It's a starting point that you adapt to your context, with known risks you choose to accept....

1.5 DaysIntensive
PracticalSA · EA
Delivery, Implementation & Architecture Runway
Intermediate (SA, EA, TS)4-5 hoursArchitecture runway template + delivery dependency map + agile architecture checklist

How architecture supports delivery instead of blocking it — covering architecture runway, phased implementation, dependency management, keeping teams unblocked, and recovering when architecture goes wrong during delivery.

...drawing. Delivery without architecture is just code that will need rewriting. I've seen architects produce designs that teams couldn't implement, and teams produce code that architects didn't approve. The result...

1 DayIntensive
PracticalSA · EA · TS
Architecture vs Design: Why Most Organizations Confuse Them
Architecture vs Design: Why Most Organizations Confuse Them

A clear explanation of the difference between architecture and design, why organizations confuse them, and how this confusion creates structural instability in technology systems.

Executive Summary Who this is for: CIOs, CTOs, Enterprise Architects, Solution Architects, Engineering Leaders Problem it solves: Persistent confusion between architecture...

Domain-Driven Design & Strategic Design Workshop
Enterprise & Solution Architects, Principal Engineers, Tech LeadsDomain map, bounded context canvas, ubiquitous language glossary, context map

Stop designing systems around databases and frameworks. Start designing around your business domains — and watch your architecture conversations change overnight.

...ownership, autonomy, and business intent. Keep it in mind. Purpose The goal of this workshop is concrete: redesign how your teams think about system boundaries — by drawing them around business domains, not technical...

1-2 DaysFacilitated
Domain MapStrategic Clarity
Enterprise, Solution, and Technical Architects: Who Does What in a Context-Driven Architecture?
Enterprise, Solution, and Technical Architects: Who Does What in a Context-Driven Architecture?

A structured executive guide explaining the difference between Enterprise, Solution, and Technical Architects using Context-Driven Architecture to clarify responsibilities and reduce structural misalignment.

...CTOs, Enterprise Architects, Architecture Leaders Problem it solves: Confusion between Enterprise, Solution, and Technical Architect roles leading to blurred accountability and architectural instability...

Architectural Decision Rights Matrix: Governing Enterprise, Solution, and Technical Architecture
Architectural Decision Rights Matrix: Governing Enterprise, Solution, and Technical Architecture

A governance framework introducing the Architectural Decision Rights Matrix (ADR-M) to clarify accountability between Enterprise, Solution, and Technical Architects in Context-Driven Architecture.

...architects. They fail because they lack decision altitude clarity. Enterprise Architects debate frameworks. Solution Architects redefine platform strategy. Technical Architects override structural principles....

Security Is Not a Gate. It Is an Architecture Property.
Security Is Not a Gate. It Is an Architecture Property.

Security is treated as a gate at the end of delivery. It should be an architecture property designed into three distinct boundaries. Here is the model that fixes the friction between security and delivery.

...at the end of delivery — creating friction, delays, and a false sense of safety — instead of being designed into the architecture as a structural property Key insight: Security decisions belong at the...