The One Value That Matters: Trust
summary
Teams scale from a few dozen to 1000+ engineers by shifting who gets attention and how trust is tracked: use pulse surveys twice a year, run a fast feedback loop (inspired by No Rules Rules) and a Friday fives workflow that lists three wins and two improvements. Leaders spend 60 days listening, take notes on personal goals, admit failures openly, and measure success when hard, transparent conversations still happen and work keeps shipping.
AI-written summary · about
chapters (7)
- 0:00Welcome
- 3:16Defining trust
- 6:50Trust at scale
- 13:33Building trust tips
- 21:00Culture of feedback
- 24:51Measuring high trust
- 27:21Closing
related talks
27mLeading a Team with Values
31m5 Things I Wish I'd Known Sooner About Scaling Teams
32mDo You Trust Me? A look at Trust, Time, and Teams
23mGad Salner- How to scale a unicorn-building engineering team (and stay sane)
09mBuilding High-Trust Teams to Supercharge Product Development
44mTeams That Propel People Forward
46mTrust as foundation of DevOps
28mFramework for Thriving Remote Leadership