My Team is a Brick Wall
summary
Indie teams (target 2–20 people, cited from a GDC survey of ~3,000 devs) get more output by funding individual success (buy an artist a tablet, offer accommodations), building communication and belonging (regular nonwork activities, better channels), then adding outside perspectives via playtests or short-term hires. Claim: equity strengthens the bricks, inclusion is the mortar, and only after those come true gains from diversity as perspectives; age diversity shows measurable benefit while unmanaged diversity raises conflict.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:05Brick wall analogy
- 3:13Purpose of a brick wall
- 6:46Brick wall metaphor
- 9:58Stronger teams with mortar
- 13:03Team building in game dev
- 14:27Individual team members
- 21:17Diversity equity and inclusion strategy
- 29:54Empower team members
- 30:59Inclusion as mortar
- 34:38Diversity beyond demographics
- 43:17Equity inclusion and diversity cycle
- 46:11Key takeaways
- 50:42Q&A
related talks
25mBuilding Antifragile Teams
29mThe Inclusive Leader: Tips for Developing Diverse Teams
39mContinuous improvement, developing yourself and others
49mBuilding Great Teams
31mBuilding High-performing, Diverse Teams
46mPanel Discussion | Building Strong Testing Teams: Management, Development, and Diversity
06mWere our values a lie? Leading teams through diversity’s collapse
18mRethinking Team Building: how a 30-person Startup serves 50 Million Users