Skip to content

[Anchor Proposal]: Team Topologies #632

Description

@rehsack

Proposed Term

Team Topologies

Context

An organisational-design model from Matthew Skelton & Manuel Pais (Team Topologies, 2019) for structuring teams to optimise fast flow and manage cognitive load. It defines four fundamental team types — Stream-aligned, Enabling, Complicated-Subsystem, Platform — and three interaction modes — Collaboration, X-as-a-Service, Facilitating. Operationalises Conway's Law (and the "inverse Conway maneuver") as a deliberate design tool.

Fits software-architecture; relatives in the catalog: conways-law, site-reliability-engineering, clean-architecture, domain-driven-design.

Source: Skelton & Pais, Team Topologies (2019) · https://teamtopologies.com/

LLM Activation Test Result

Model: Claude (Opus 4.8)
Prompt: "What concepts do you associate with 'Team Topologies'?"
Response: Four team types (Stream-aligned, Platform, Enabling, Complicated-Subsystem) and three interaction modes (Collaboration, X-as-a-Service, Facilitating); cognitive load, fast flow, Conway's Law / inverse Conway maneuver, platform-as-a-product; attributed to Skelton & Pais (2019). Rich, consistent, strongly attributable activation.

Pre-submission Checklist

  • I have searched existing anchors and this term is not already included
  • This term refers to a well-established concept (not something I invented)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions