Search

Find insights, training programs, and workshops

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.

...and what happens when it conflicts with another? For every hotspot, one question: Is this a domain complexity or a governance gap? The bottom row will always be longer than the top. The Governance Storm...

Solving Technical Debt Through Feature Development: Turning Product Delivery into Architecture Improvement
Solving Technical Debt Through Feature Development: Turning Product Delivery into Architecture Improvement

A practical framework explaining how organizations can systematically reduce technical debt while delivering new features, instead of running disruptive modernization programs.

...Refactor the Area You Touch When implementing a feature: improve the module being modified simplify complexity in that component remove obsolete code paths introduce better patterns Do not attempt to fix...

Your HCI Proof of Concept Measures the Wrong Thing.
Your HCI Proof of Concept Measures the Wrong Thing.

Most organizations evaluate private cloud and HCI platforms by running a technical POC. The POC passes. The platform fails. The reason is structural — and fixable. The Platform Fitness Evaluation Model (PFEM) tells you what to measure instead.

...infrastructure — not in ideal conditions, but under real operational pressure? What to evaluate: On-call complexity: How many people need to be available for a Severity 1 incident on this platform? Compare...

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.

...Application concerns serve one team. When application logic enters the platform, the platform accretes complexity that only one team needs — and every other team pays for in cognitive load. Does this capability...

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.

...misses a sprint commitment. The retrospective lists the usual suspects. Unclear requirements. Unexpected complexity. Integration issues. Nobody measures the sixteen hours of friction that consumed half the...

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.

...pick microservices because it was trending, then spend eighteen months fighting distributed systems complexity for a product that three people used. Every pattern solves a specific problem and sacrifices...

1.5 DaysIntensive
PracticalSA · 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.

...choose what actually runs the solution — and every choice is a trade-off between capability, cost, complexity, and lock-in. The decisions that matter most: What to run it on — cloud provider, service...

2 DaysIntensive
PracticalSA · EA
Effective Prompt Engineering
Beginner to Advanced6-8 hoursFull prompt design framework + personal prompt library

Every major prompt engineering technique — from basic clarity to advanced agentic reasoning. Not a list of tips. A mental model you can apply to any task, any tool, any context.

...Foundation techniques apply to almost every prompt. Reasoning techniques apply when the task has real complexity. Advanced techniques apply when you're building systems or need maximum quality. Start with...

2 DaysIntensive
19 TechniquesComplete Coverage
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.

...Components need to communicate. How they communicate determines the coupling, the reliability, and the complexity of the entire system. There are four fundamental integration patterns, each with distinct...

2 DaysIntensive
ComprehensiveSA · EA
Architecture Governance
Intermediate to Advanced (SA, EA, TS)5-6 hoursGovernance model canvas + architecture principles register + escalation path template

How to design, implement, and measure architecture governance — the mechanisms that ensure decisions are made consistently, applied correctly, and aligned with strategy.

...prefer simplicity." A good principle: "We prefer the simplest solution that meets the need because complexity increases cost of change. This means we choose monolith over microservices when a single team...

1 DayIntensive
PracticalSA · EA · TS