Harnessing tenure variety within a team
summary
Anecdote: a pull request sits open three weeks after a junior rewrites it four times while seniors demand architecture and naming changes. Cited numbers: turnover can cost ~80% of salary (about $100k on a $130k median), hiring takes 44–62 days and onboarding ~20 weeks, so lost productivity stretches to ~7 months. Use a simple 1–7 psychological safety survey as a diagnostic, adopt blameless postmortems, and apply three interventions: frame work as learning, acknowledge fallibility, and model curiosity; Google’s Project Aristotle shows interaction beats composition.
AI-written summary · about
chapters (9)
- 0:00Tenure-based team frictions
- 1:26Tenure imbalance symptoms
- 3:40Costs of poor communication
- 6:08Biases blocking collaboration
- 9:01Psychological safety foundation
- 12:19Google’s team effectiveness
- 14:54Diagnosing team psychological safety
- 17:40Building psychological safety
- 19:52Trust and conversation in teams
related talks
43mHumane Development
33mBuilding Sustainable Teams to Handle Uncertainty
47mDeveloper first – a new Leadership Mindset
01h 02mBackwards Compatible- Lessons from a Quarter Century in Software
28mTechnical Onboarding, Training, and Mentoring
54mGrowing your Agile team: Hiring and inspiring the right mindset and skills
31mMinimize Your Circus Factor: Building resilient teams
21mFuture Proof your company by effectively scaling engineering