Radical Therapy for Software Teams
summary
Claims measurable results: a merge product and developer backlogs policy, an enforced commit code on day one rule, and built tooling—buley product Labs with AI built‑in knowledge—that surfaces decisions and feedback. AI testing covers both model outputs and production inputs, and compensation rules are made transparent. Cited examples include Google Atlassian Zappos IBM fairness360 and Netflix and a McKinsey stat of 35% better performance (McKinsey) for inclusive teams. Open Build and a Foundry program exist; transparency-first projects aim to reduce time to market.
AI-written summary · about
chapters (17)
- 0:00Introduction and Company Overview
- 0:20Radical Therapy for Software Teams
- 2:22Principles of Transparency
- 2:53Data-Driven Decision Making
- 3:32Inclusivity and Diversity
- 4:00Combining Product and Developer Backlogs
- 4:20Promoting Cross-Functional Collaboration
- 6:23Establishing a Culture of Open Communication
- 7:33Transparent Performance and Compensation Policies
- 8:09AI Ethics and Testing
- 8:49Enhanced Innovation and Problem Solving
- 10:24Team Morale and Communication
- 11:48Empowering Teams with Autonomy
- 12:05Running a Product Like a Lean Startup
- 15:19The Radical Process
- 19:27Building Trust and Open Communication
- 20:02Conclusion and Call to Action
related talks
05mRadical Transparency for Software Teams
46mLeading with Radical Transparency: Empowering Product Teams
34mBuilding a Culture For Developer Productivity
34mNative Agile Psychology of Teams and Individuals
47mThe Psychology of Software Teams
55mThe Gig is Up: Radical Shifts That Save Cultures, Teams, and Companies
18mAgile leadership and technical mastery, a harmonious alliance
51mSabotaging a Transformation