Radical Transparency for Software Teams
summary
Worked a rollout across 26 countries and builds a tooling-backed process that opens surveys, commits, releases and bugs so everyone sees decisions and blockers; secrecy repeatedly causes missed launches in the fictional “Thermos” example and real failures like the Newton MessagePad and ARA. Concrete practices: daily commits from day one, code reviews from day two, daily pull requests, post standups to Slack, include product managers, document conversations, start small and scale transparency.
AI-written summary · about
related talks
24mRadical Transparency: Leading Engineering With Openness
21mRadical Therapy for Software Teams
11mLeading without committing: Managing teams outside your tech stack
43mManaging Releases by the Numbers (Really?)
06mHow Sonar Builds a Culture of Innovation and Accountability
32mDeveloper productivity 2.0
45mClosing Keynote
26mHow a team that communicates well collaborates well