Search

Find insights, training programs, and workshops

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.

...clarity. Keep it in mind. Purpose The goal of this workshop is concrete: build leadership capabilities for distributed, AI-augmented organizations with clear decision rights and effective team management for...

2 DaysLeadership
Clear OwnershipAccountability
Operating Model Choices
Advanced (EA, TS)5-6 hoursOperating model design canvas + team topology guide + Conway's Law application worksheet + Communication Structure Heatmap

How the structure of technology teams shapes the structure of the systems they build — covering Conway's Law, centralised vs federated models, platform teams, product operating models, team topologies, and designing the organisation that produces the architecture you want.

Quick Navigation Start here — Conway's Law Centralised vs federated Platform teams Product operating models Team topologies Governance in federated models Choosing an operating model Inverting...

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

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

2 DaysWorkshop
Coming Soon
Architecture Patterns That Travel Across Industries
Architecture Patterns That Travel Across Industries

The patterns that solve your hardest distributed systems problems were already solved — in a submarine, a postal sorting office, and an electrical panel. Most architects never look.

...whether it can be readdressed, returned, or disposed of. The decision is deliberate. Not automatic. In distributed messaging, a dead letter queue works identically. A message cannot be processed. It does...

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.

...grows large enough becomes unmaintainable — unless someone deliberately breaks it into parts. I've seen teams start with a clean monolith and end up with something where every change requires understanding...

1.5 DaysIntensive
FoundationSA · EA
The Minimum Architecture Every Company Needs: The House, the Hallway, and the Doorbell
The Minimum Architecture Every Company Needs: The House, the Hallway, and the Doorbell

A practical architectural model explaining why most companies only need a modular monolith, a workflow orchestrator, and outcome-based events.

...before they actually need them Key outcome: A simple architectural model that scales further than most teams expect Time to implement clarity: 30–60 days Business impact: Faster development, lower operational...

Monitoring Added After Deployment Is Not Observability. It Is Archaeology.
Monitoring Added After Deployment Is Not Observability. It Is Archaeology.

Observability is not a monitoring add-on. It is an architectural constraint. Systems built without observability baked in cannot be understood, cannot be governed, and cannot be improved. The OSAF model tells you exactly where your architecture is blind.

...does degraded-but-functional look like? If you did not design the signal, the system cannot emit it. Teams Own Metrics but Nobody Owns Meaning One team tracks latency. Another team tracks error rate. A...

Your Architecture Diagrams Are Lying to You
Your Architecture Diagrams Are Lying to You

Why architecture diagrams describe a system that no longer exists, and how Observable Architecture uses production telemetry to reveal what is actually running.

...Signals Hidden in Production Production systems generate continuous signals that most architecture teams never examine. Three signals are particularly valuable. Service Call Patterns Every service call...

Your AI Agents Are Making Architecture Decisions. Nobody Assigned Them That Role.
Your AI Agents Are Making Architecture Decisions. Nobody Assigned Them That Role.

AI agents are making micro-architecture decisions in production. No ADR recorded them. No review board approved them. No architect ever saw them. Here is the structural fix.

...in this zone are: Structurally irreversible without significant rework Affecting multiple systems, teams, or deployment units Creating dependencies that outlast the current feature cycle Requiring board...

Your Git History Is an Architecture Health Report. Nobody Is Reading It.
Your Git History Is an Architecture Health Report. Nobody Is Reading It.

A practical architecture technique showing how Git commit patterns reveal structural instability, boundary violations, and ownership gaps in software systems.

...engineers commit changes that reveal: where complexity accumulates which modules are unstable which teams are crossing boundaries which parts of the system have been abandoned This signal already exists....