Building Effective Teams of Competent, Friendly People
summary
Leads teams of about 15–30 people with 4–8 Android developers and proves a reproducible approach: require competent, friendly baseline hires, enforce a 40-hour week rhythm, and apply the RAMPS checklist (rhythm, autonomy, mastery, purpose, safety). Concrete practices include setting clear codebase boundaries (one MVVM pattern, avoid sprawl like multiple RecyclerView frameworks), giving autonomy by letting devs pick risky tasks, and shipping tooling such as mocked-API integration tests that jump straight to deep screens to cut iteration time.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:18Foundation of competent friendly teams
- 9:18RAMPS framework for team growth
- 11:05Rhythm and sustainable work hours
- 15:15Autonomy and trust in development
- 20:35Mastery and self-improvement
- 23:07Purpose and team motivation
- 26:58Safety and psychological security
- 38:45Handling mistakes and forgiveness
- 41:34Asking junior engineers for help
- 43:46Q&A on team dynamics
related talks
43mThe Engineering Playbook for Growing Android Teams
01h 00mAndroid at Scale
29mGrowing Your Team While Remaining Efficient
43mHow to Lead? Testimonial of a Lead Android Engineer
17mHow to Do Great Work
47mRoundtable: process for your Android team
01h 32mLeveling Up: Panel Discussion
33mBuilding Sustainable Teams to Handle Uncertainty