Team first
summary
Claims a concrete "Team First" framework with behavioral rules for leaders developers and teams and a checklist of practices: build trust give overview let people champion subjects put engineers in front of clients and insist on definition of ready and refusing scope creep. Includes a demo anecdote of a Wi‑Fi scale that tweets via serverless functions, cites agency-scale experience (multi‑office teams, 2494‑attendee conference) and digs into low‑context vs high‑context communication plus tactical moves like helicopter view and explicit handoffs.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:50Team first
- 2:17Highquality technology
- 2:58About me
- 4:50Star Trek
- 5:16Challenges
- 7:39The framework
- 8:41Make the team feel responsible
- 9:04Provide trust
- 13:19Know yourself
- 18:31Be one team
- 21:09Low context vs high context
- 26:16Assumptions
- 27:44Conclusion
related talks
21mPeople First Leadership
44mFundamentals & Practices for getting a High-Performance Team
27mTheory to action: Architecting and implementing your team operating system
11mLeading without committing: Managing teams outside your tech stack
46mLeadership for Engineering Teams in Remote Work Era | Panel Discussion
32mBuild Teams as an Engineer
20mBuilding Alignment - Team Working Agreements
28mFramework for Thriving Remote Leadership