Better Playtesting for Indie Developers
summary
Claims a practical indie workflow: treat design choices as testable hypotheses, recruit representative players via competitor communities and a mailing list (MailChimp/ConvertKit) using a screener and incentives (credits or game keys), schedule with Calendly, record sessions with OBS or Windows Game Bar, or remote via Zoom/Google Meet. Run small tests — watch 2–3 players with think‑aloud — split findings into behavior vs opinion data, prioritize objective behavior (who went wrong, where) and iterate. Playtest kit and templates make this repeatable.
AI-written summary · about
chapters (21)
- 0:00Start
- 6:28Play Test Process
- 8:25Finding Play Testers
- 10:53Improve the Quality of Play Testers
- 11:58Defining Your Target Player
- 17:59Recognition
- 25:15Target Audience
- 26:13Scheduling
- 27:44Pool of Play Testers
- 35:01Surveys
- 40:03Screen Sharing
- 42:12Handle that Play Test Data
- 42:23Remember Why You Run the Play Test
- 42:43Behavior Data
- 42:58Behavioral Data
- 45:09Opinion Data
- 47:14Deciding What To Do
- 51:28Play Test Kit
- 53:53Should Age Be a Factor in Who's Play Testing
- 55:25Gamer Demographics
- 59:49Would It Be Better To Have Play Testing before or after Anime Ai Is Implemented
related talks
41mHow to Avoid a Bad Steam Score?
35mQA in GameDev. How to: build outsource processes, hire right people, successfully release projects
37mTesting Games
45mBuilding Tools to Free up Exploratory Testers
01h 34mShift left in testing: Find bugs before they’re implemented
38mA Game of Testing
23mChaos Survival Guide: How to Start Testing if There is Nothing to Help You
48mUser testing in production: how to run a public beta