Why do most retrospectives fail, and how do you turn them into a real driver of team performance?

In this episode, I sit down with Maria Maunula, Senior Game Producer at Supercell, to break down how to run retrospectives that actually lead to change, not just empty discussions. From vague action items and anonymous feedback to team trust and accountability, we uncover why most teams get this wrong and how to fix it.

We dive into practical frameworks for running better retros, how to structure them for small and large teams, and why frequency, ownership, and follow-up are the difference between stagnation and growth.

If you're a game developer, team lead, or working in a fast-paced creative environment, this episode will fundamentally change how you think about improving your team.

Connect with Maria:
LinkedIn: https://www.linkedin.com/in/mmaunula/
Supercell's games: https://supercell.com/en/games/
Join Supercell: https://supercell.com/en/careers/#join

Connect with Harry:
LinkedIn: https://www.linkedin.com/in/hphokou/
YouTube: https://www.youtube.com/@hphokou
Instagram: https://www.instagram.com/hphokou/

Join our industry events: https://hivemind.world/

Get exclusive podcast recaps & industry insights:
→ Subscribe to The Gaming Playbook Weekly at https://join.thegamingplaybook.com/

Chapters:
00:00 Intro
01:51 From selling toilets to becoming a game producer
03:40 What does a producer actually do?
05:56 What are retrospectives and who needs them?
07:55 Why most retros fail (and what goes wrong)
11:21 Real example: connecting work to meaningful outcomes
13:21 Should retros be emotional?
14:45 Common mistake: focusing on behavior vs outcomes
16:58 How often should you run retros?
19:27 Ideal team size and retro duration
21:25 Structuring a retro: what went well, challenges, actions
24:05 Case study: fixing a real team workflow
26:00 Missing link in remote teams (and how retros fix it)
29:34 Avoiding bottlenecks and empowering the team
32:04 Making retros engaging (Miro, visuals, themes)
36:45 Timeboxing and participation techniques
38:44 Biggest risks: blame culture and conflict
40:37 How to follow up on action items properly
43:19 Should all teams join the same retro?
46:28 Measuring retro success with simple metrics
48:59 Using data to influence leadership decisions
51:29 Hiring insights: how to stand out in applications
59:26 Final advice: making retros actually work