Engineering

From Architecture to Teams

How system structure and team structure co-design each other — a rigorous path through sociotechnical foundations, cognitive load, bounded rationality, Conway's Law, distributed cognition, affordances, DDD, Team Topologies, psychological safety, organisational learning, platform and enabling teams, and the politics of change.

13 modules
01

Sociotechnical Foundations

Why you cannot optimize systems and teams separately
02

Cognitive Load Theory: The Science Behind Team Limits

Why working memory constraints are a non-negotiable input to architecture and team design
03

Why Organizations Cannot Optimize

Bounded rationality, satisficing, and the information-processing roots of organizational form
04

Conway's Law and the Inverse Conway Maneuver

Why your org chart is already your architecture diagram — and what to do about it
05

Distributed Cognition and the Artifact Layer

Why your codebase, dashboards, and documentation are not outputs — they are the cognitive system
06

Affordances: How Structure Shapes What's Possible

Why the same system affords different behaviors to different teams — and what that means for how you design both
07

Bounded Contexts and DDD

Language, boundaries, and the organizational logic of domain-driven design
08

Team Topologies: Four Types, Three Modes

Why team design is cognitive load design, and how interaction modes govern architectural coupling over time
09

Psychological Safety and High-Performing Teams

Why the shared belief that it is safe to take interpersonal risks is the load-bearing condition underneath team learning, voice, and performance
10

How Organizations Learn — and Why They Usually Don't

Single-loop learning, double-loop learning, and the sensemaking gap in engineering organizations
11

Platform and Enabling Teams

Cognitive load reduction, political economy, and the lifecycle of teams that exist to serve other teams
12

Architecture Changes Are Organizational Changes

Power dynamics, coalition formation, and sensegiving in engineering-led change
13

The Honest Map

Critique, synthesis, and judgment across the full curriculum

How this plan was made

Each plan on learnings is built by a hand-crafted agentic pipeline: research agents gather primary sources, a claim reviewer verifies facts against them, and a sequencer orders modules for how people actually learn. The curation — topic selection, framing, editorial standards — is Nicolas's. The research and writing is AI-assembled.