> "Things looked fine on paper until they suddenly went wrong — but the engineers had been worried for months." ^pain A collective trust pain that affects the artefacts at the top of the hierarchy. Information is sanitised flowing up: optimistic timelines, hidden implementation challenges, curated narratives. The senior team's knowledge graph is a lossy projection of the team's actual knowledge graph, and the loss is structured — it discards inconvenience. ## Discovery questions - "What's the gap between what your senior team thinks is true about delivery and what your engineers would say privately?" - "When was the last time a project went sideways and the warning signs were visible to your team weeks before they reached you?" ^discovery-questions ## Examples - Boeing 737 MAX / MCAS: internal emails revealing employees calling the aircraft "designed by clowns" while official reports to regulators presented it as safe.[^1] - NASA Challenger Rogers Commission: management's launch-readiness reports ignored engineers' concerns about O-rings and cold weather.[^2] - NASA Columbia CAIB: "normalised deviance" where upward reporting repeatedly downplayed foam-strike risk.[^3] - Knight Capital 2012 trading disaster: internal risk controls and tech-readiness reporting failed to reflect the true fragility of deployment processes.[^4] - Wells Fargo accounts scandal: sales performance dashboards celebrated growth while internal reports showed fake accounts and unethical pressure.[^5] [^1]: https://www.reuters.com/article/us-boeing-737max-emails-idUSKBN1Z72FM [^2]: https://history.nasa.gov/rogersrep/v1ch5.htm [^3]: https://www.nasa.gov/columbia/home/CAIB_Vol1.html [^4]: https://www.sec.gov/litigation/admin/2013/34-70694.pdf [^5]: https://www.nytimes.com/2016/09/09/business/dealbook/wells-fargo-fined-for-years-of-harm-to-customers.html