Team Topologies & Organizational Flow

Manual chapter on designing teams for modern delivery.

Source: content/manual/05-team-topologies/index.md

Structure determines speed. Use team topology decisions to reduce handoffs, lighten cognitive load, and create space for automation—including AI agents. This chapter explains the four primary team types, the operating cadences that keep them healthy, and the playbooks that sustain momentum.

Core team types

Stream-aligned: Own a customer-facing value stream end to end. Success hinges on low cognitive load, autonomy, and tight feedback loops.
Enabling: Pair with stream teams to introduce new capabilities (observability, testing, security). Engagements are short, time-boxed, and outcome-driven.
Complicated subsystem: Maintain components requiring deep expertise or specialized knowledge (e.g., ML platform, billing engines).
Platform: Provide reusable services, golden paths, and governance so stream teams deliver faster.

Operating system for organizational flow

Charter clarity: Workshop charters for each stream-aligned team. Define mission, KPIs, dependencies, and escalation paths. Use playbooks/stream-aligned-teams/checklist.md as the facilitation script.
Support network: Stand up enabling teams to coach on new practices using playbooks/enabling-teams/index.md. Keep an intake process, set engagement SLAs, and publish learnings.
Load management: Run quarterly cognitive load assessments (playbooks/cognitive-load-assessment/index.md) and feed insights into platform roadmaps, hiring, and onboarding.
Leadership cadence: Align executives around flow using playbooks/leadership-for-flow/index.md. Fund platform work, remove systemic blockers, and celebrate learning publicly.
AI augmentation: When rolling out AI agents, ensure mentorship bandwidth, audit trails, and outcome metrics align with the chosen topology (see manual/03-ai-agents/index.md).

Diagnostic questions

Symptom	Likely root cause	Playbook or action
Frequent cross-team escalations	Blurry charters or overloaded streams	Revisit charters, run `stream-aligned-teams` workshop
Platform backlog overwhelms one team	Missing enabling capacity or unclear intake	Launch `enabling-teams` engagements
Burnout or onboarding friction	High cognitive load or too many dependencies	Execute `cognitive-load-assessment` and adjust scope
Leadership reverts to approvals	Lack of flow visibility or trust	Apply `leadership-for-flow` checklist and improve transparency

Cadence checklist

Bi-weekly: Leadership sync on stream health, staffing, and cross-team blockers.
Quarterly: Charter review to detect scope creep and update interfaces.
Semi-annual: Org-wide value stream mapping to validate topology still matches product strategy.
Ongoing: Share success stories and metrics (lead time, deployment frequency, satisfaction) to reinforce desired behaviors.

Common pitfalls

Moving people without transferring responsibilities or updating access, causing shadow ownership gaps.
Overloading stream teams with platform chores or shared services that belong elsewhere.
Neglecting enablement, leaving teams stranded with new tooling.
Ignoring cultural change—psychological safety and communication must evolve alongside structure.

References and further learning

“Team Topologies” by Skelton & Pais for foundational patterns.
“Accelerate” for linking organizational design to DORA metrics.
Use your audience personas or stakeholder briefs to tailor communication for executives, platform leads, and stream teams.
Org maps and historical notes under notes/ for context on previous restructuring efforts.