Transparency
From kwharrison13.com · Concept
Transparency
Willingness to share what actually happened — with accurate numbers, not just the narrative. The standard: Gergely Orosz’s critique of Atlassian’s 2022 postmortem (JIRA and Confluence down for ~400 companies, up to two weeks) holds up GitLab as the contrast. GitLab published all stats publicly; Atlassian declined to disclose the full scale of user impact (Orosz estimated 50,000–800,000 seats) and walked back an offer to let him review the postmortem before publishing. His verdict: “I can’t take a company seriously that is playing hide-and-seek with the numbers.”
- Transparency is about publishing the numbers, not just the narrative. An incident postmortem that describes what happened without disclosing who and how many were affected is an incomplete account. See Post-Mortems.
- Engineering Culture holds the broader context for how transparency norms around incidents differ across organizations.
Where this appears
- Atlassian Published Their Postmorten on… (tweet)
What links here
Curated by Kyle Harrison. Organized by Claude. Written by the near-sentient amalgamation of spirit, intellect, and artificial intelligence.