Skip to content

Search

Find insights, training programs, and workshops

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.

...Solution Architects, Engineering Leaders Problem it solves: Persistent confusion between architecture and design in software and technology organizations Key outcome: Clear structural separation between decision-making...

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
Technology Leadership & Organizational Excellence
Intermediate to AdvancedLeadership roadmap and team enablement plan

Learn to lead high-performance engineering organizations with clear decision rights, distributed leadership, and AI-augmented team management for the future of work.

...Leadership = The practice of guiding engineering organizations through AI transformation, distributed team management, and organizational design for high performance. It encompasses: Distributed leadership...

2 DaysWorkshop
FoundationFor all leadership roles
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
Organizational Leadership & Distributed Decision Rights Workshop
Engineering Managers, Tech Leads, Directors, C-level Technology LeadersDecision rights matrix, distributed leadership playbook, OKR implementation

Build leadership capabilities for distributed, AI-augmented organizations with clear decision rights and effective team management.

...leadership capabilities for distributed, AI-augmented organizations with clear decision rights and effective team management for the future of work. I've seen teams scale by adding managers — and then watch decision-making...

2 DaysLeadership
Clear OwnershipAccountability
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.

...Architecture and delivery What architecture runway is Phased implementation Managing dependencies Keeping teams unblocked Spikes and POCs When architecture goes wrong Putting it all together Cheat sheet Before...

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

Run Event Storming Twice. The First Maps the System. The Second Exposes Governance.
Run Event Storming Twice. The First Maps the System. The Second Exposes Governance.

Why the second run of an Event Storming workshop — the one most teams never attempt — is the fastest way to surface governance gaps that architecture diagrams will never show.

...Summary Who this is for: Enterprise Architects, Solution Architects, Architecture Leads, Domain-Driven Design practitioners Problem it solves: Governance gaps — missing owners, conflicting authorities, undecided...

Complete Enterprise Data Architecture Framework: Business, Logical, Physical Layers with Real Templates
Complete Enterprise Data Architecture Framework: Business, Logical, Physical Layers with Real Templates

Most enterprises build data architectures one layer at a time. Business, logical, and physical layers exist as separate artefacts owned by separate teams. That separation is the structural gap that makes data estates ungovernable.

...ecutive Summary Who this is for: CTOs, Enterprise Architects, Data Architects, Chief Data Officers designing or operating enterprise data estates Problem it solves: Business, logical, and physical data...

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.

...days to establish the translation architecture for one strategic priority Business impact: Delivery teams that build the right things, investment aligned to strategic intent, and governance that closes...

123···11