Reading the game: Mental skills for high-performing engineering teams
summary
Claim: team performance is roughly 80/20 mental vs technical. Evidence comes from observing real matches and meetings, timing substitutions, keeping mental notes, and running low‑stress paired drills that fix interpersonal friction; outcome: quieter, more cooperative players and at least two previously clashing teammates who start collaborating. Tools include user manuals, longer pre‑match briefings, role clarification, and a practiced mental skills game plan (imagery breathing self‑talk); these interventions consistently raise confidence and reduce blame.
AI-written summary · about
chapters (7)
- 0:00From player to coach
- 2:14Psychology in team sports
- 4:50Observing team patterns
- 8:07The importance of timing
- 10:32Strategies for coaching
- 16:31Building self-sufficient teams
- 20:04Mental game plans
related talks
21mGetting an engineering team to eat their vegetables
44mFundamentals & Practices for getting a High-Performance Team
39mGame Theory and the Art of Teamwork in Software Development
43mAttitude Determines Altitude: Engineering Yourself & Your Teams
47mThe Psychology of Software Teams
02mHigh-performance teams
01h 02mMore Cards Against People Mismanagement
30mNavigating team friction