Radical Transparency: Leading Engineering With Openness
summary
Argues that shared, recorded visibility of decisions stops endless priority churn and shows work’s business impact, with concrete practices: record all staff and customer meetings, publish roadmap and per-team boards, give engineers Salesforce access and public-by-default docs. Fleet layers OKRs/KPIs, GitHub issues, Slack gratitude for docs, and short toes cross-team borrowing. Results: faster alignment and fewer stalled dependencies, plus a new information firehose risk and occasional social-censoring in public channels.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:47Priority confusion in engineering
- 7:50Why measure engineering work
- 9:41Fleet transparency solutions
- 12:30Team priorities visibility
- 13:54Opaque decisions and filtered communication
- 17:02Fleet transparency culture
- 20:18Cost of lack of transparency
- 21:43Steps to improve transparency
related talks
46mLeading with Radical Transparency: Empowering Product Teams
05mRadical Transparency for Software Teams
31mHarmonizing Across Product & Engineering (Cross Team Collab)
43mEmpowerment in action
26mHow a team that communicates well collaborates well
29mCreating a Culture That Thrives with Disruption
59mTech leadership, one year after
21mRadical Therapy for Software Teams