{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/minimize-the-number-of-teams-that-must-change-together",
  "id": "MHC-D-RESEARCH-9141",
  "version": "0.1.0",
  "title": "Minimize the number of teams that must change together",
  "summary": "Cross-boundary coordination is a cost of architecture.",
  "kind": "heuristic",
  "body": "Map which teams must agree, build, test and release together for a normal change. Redesign boundaries or contracts where one change creates unnecessary multi-team coupling.",
  "limits": [
    "Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner."
  ],
  "topics": [
    "union-systems-strategy-and-leverage-thinking"
  ],
  "intents": [],
  "source_ids": [
    "RS-6F01EE9805D9E655"
  ],
  "evidence": [
    {
      "claim": "Simon described complex systems as often hierarchical and near-decomposable, motivating analysis of relatively strong within-subsystem interactions and weaker cross-subsystem interactions.",
      "source_id": "RS-6F01EE9805D9E655",
      "role": "contextualizes",
      "note": "Near decomposability is a conceptual property, not evidence that any chosen boundary is correct.",
      "locator": "Near-decomposability discussion"
    }
  ],
  "use_when": [
    "When small product changes require synchronized work across many groups."
  ],
  "avoid_when": [
    "Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner."
  ],
  "example": "A field-label change should not require integration, platform and reporting releases if the contract can preserve semantic identity.",
  "check": "Typical changes require fewer simultaneous owners without bypassing controls.",
  "sources": [
    {
      "id": "RS-6F01EE9805D9E655",
      "title": "The Architecture of Complexity",
      "url": "https://www.jstor.org/stable/985254"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-9141",
      "to": "MHC-D-RESEARCH-9142",
      "type": "use_before",
      "url": "/knowledge/make-dependencies-directional-where-possible"
    }
  ],
  "collections": [
    {
      "id": "RC-28D91C30CEA1CB4A",
      "title": "Systems and strategic leverage: feedback, flow, modularity, robust options, and information value",
      "url": "/collections/systems-and-strategic-leverage-feedback-flow-modularity-robust-options-and-information-value"
    }
  ]
}