Search

Find insights, training programs, and workshops

VP Engineering, Platform Leads, Engineering Managers, Principal Engineers3-4 hoursCognitive load assessment per team, an interaction model, and a platform team charter naming what the platform does and does not own

A team can only hold so much — and the interaction modes between teams are what decide whether that limit is respected or quietly exceeded.

...shapes that respect the limit Three interaction modes — the interface is the design The platform as the load-absorbing interface Golden paths, dirt roads, and the museum problem Measuring whether the interface...

1 DayIntensive

CapacityWhat a team can hold

Cognitive Load Team Topologies Platform Engineering Developer Experience View Details

How Architects Think

All levels — SA, EA, TS5-6 hoursSystems thinking toolkit + abstraction ladder + decision heuristics reference card

The cognitive toolkit of architecture — systems thinking, abstraction, balancing business and technical concerns, deciding under uncertainty, and trade-off thinking. Builds the mindset, not just the knowledge.

..."how do I build this?" An architect asks "should this be built, and if so, where does it fit?" The cognitive toolkit of architecture includes systems thinking, abstraction, balancing business and technical...

1 DayIntensive

MindsetNot just methods

Architecture Foundations Systems Thinking Decision Making View Details

Execution Stability: How Structured Refactoring Improves Delivery Predictability

A practical framework for reducing delivery slowdown caused by unmanaged structural code complexity — improving cycle time, reducing regression risk, and clarifying ownership boundaries.

...duplication Improving unit test coverage This is low-risk structural tightening. When to Use Dicing High cognitive load modules Repeated bug patterns Difficult onboarding areas Localized code smells Business...

Leadership Governance Execution Read Insight

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.

...platform, the platform accretes complexity that only one team needs — and every other team pays for in cognitive load. Does this capability already exist — in another platform service, another team's stack,...

Leadership Platform Engineering Governance Read Insight

Execution Stability & Structured Refactoring

CTOs, Engineering Directors, Principal Engineers, Engineering Managers3-4 hoursA classified structural risk map — your top friction modules sorted into dicing, slicing and peeling with a governance rule attached

Delivery slows because structural entropy accumulates unmeasured. Classify refactoring into dicing, slicing and peeling to restore predictability.

...cyclomatic complexity; eliminating duplication; improving unit test coverage. When to use it: high cognitive load modules; repeated bug patterns; areas that make onboarding difficult; localised code smells. Business...

1 DayIntensive

LayersNot cleanup

Execution Stability Refactoring Delivery Predictability Structural Risk View Details

Developer Experience as a Control System

CTOs, Engineering Leads, Platform Engineering Teams, Engineering Managers3-4 hoursA delivery friction map across four sprints, one named constraint pillar, and a traced DX-to-delivery signal

DevEx is not a perk — it is the set of operating conditions that governs how fast and how safely change moves through your delivery system.

...systems one developer must hold in working memory at once — which is the point where this connects to Cognitive Load & Team Interfaces. Feedback Loop Integrity. A developer makes a change, then waits —...

1 DayIntensive

ConditionsNot satisfaction

Developer Experience Delivery Performance Feedback Loops Platform Engineering View Details

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.

...Define interaction modes — how do teams interact? Collaboration, service, or facilitation. Limit team cognitive load — each team must be able to understand their scope. Cognitive load — the constraint:...

1 DayIntensive

StrategicEA · TS

Architecture Operating Model Conway's Law Team Topologies Platform Teams Strategy View Details

Roadmaps & Transformation Sequencing

Intermediate to Advanced (SA, EA, TS)5-7 hoursRoadmap template + transition state design guide + sequencing logic + dependency overlay

How to build multi-year transformation roadmaps that sequence architectural change realistically — accounting for dependencies, capacity, risk, and the fact that the organisation must continue operating while it transforms.

...Account for holidays, attrition, BAU. Parallel work — how many initiatives can run simultaneously? Cognitive load — can teams absorb more change? Dependencies — are teams blocked waiting for others? The...

1.5 DaysIntensive

StrategicSA · EA · TS

Architecture Roadmap Transformation Sequencing Strategy Delivery View Details

Platform as a Product

CTOs, Heads of Platform Engineering, VP Engineering, Enterprise Architects, Platform Product Managers3-4 hoursA three-gate platform governance plan — validated backlog, a written scope boundary, and adoption targets per capability

An internal platform with no product owner builds what nobody asked for and skips what everybody needs — adoption, not completeness, is the only measure that counts.

...and attach a sunset plan to everything on the wrong side. The charter has a second job, covered in Cognitive Load & Team Interfaces: keeping the platform team itself from absorbing every unclaimed responsibility...

1 DayIntensive

AdoptionNot feature count

Platform Engineering Internal Developer Platform Product Governance Golden Paths View Details

Conway's Law & Team Boundaries

CTO, VP Engineering, Engineering Directors, Principal Engineers3-4 hoursTwo-layer boundary map — the official org design set against actual incident load, with every structural gap named

Your architecture mirrors your communication structure whether you designed it that way or not — which makes team boundaries an architectural decision.

...drift. Every incident is a data point. Every escalation is a signal. Every paged engineer is a vote on where load actually concentrates — regardless of what the org chart intended. When an incident fires and an...

1 DayIntensive

BoundariesStructure as design

Conway's Law Team Topologies Organisational Design Team Boundaries View Details

1 2