> "Every team reinvents the same component. We only find out at the integration review — sometimes not even then." ^pain A collective-track pain where teams operate as independent organisms because the communication graph does not connect them. The artefacts may exist in each team's own store, the people may be willing to share — but the path from "I am about to start work on X" to "Team B already built X" does not exist. Distinct from the scatter pain: scatter is about *artefacts in many bins*; this pain is about *teams not knowing the bins exist*. ## Discovery questions - "How often do two teams discover they've built the same thing twice — and how late?" - "When does Team A learn what Team B is working on — at planning, at integration, at launch?" - "What's the path for knowledge to flow between teams that don't share a manager?" ^discovery-questions ## Examples - Challenger disaster investigations: information about O-ring concerns was fragmented between NASA and Morton Thiokol teams; critical risk assessments were not effectively shared.[^1] - 9/11 Commission Report: intelligence about al-Qaeda was trapped in agency silos (CIA, FBI, NSA) - "the left hand did not know what the right hand was doing".[^2] - Boeing 737 MAX crises: engineering, software, safety teams, and FAA designees failed to share complete information about MCAS behaviour, contributing to two fatal crashes.[^3] - Mars Climate Orbiter loss: misaligned units (imperial vs metric) and poor cross-team checks between Lockheed Martin and NASA navigation teams - a coordination and interface-knowledge failure.[^4] [^1]: https://history.nasa.gov/rogersrep/v2appf.htm [^2]: https://9-11commission.gov [^3]: https://www.transportation.gov/briefing-room/final-committee-report-boeing-737-max [^4]: https://mars.nasa.gov/msp98/news/mco990930.html