Skill Profile
Playtesting & Iteration
"Watching people play an unfinished build without helping them, recording what they actually do rather than what they say, and changing the game on the evidence — repeatedly, before the thing is finished enough to be comfortable showing."
YOUR SKILLS
Skill Breakdown
Playtesting is the part of development where an opinion becomes a measurement. The discipline is mostly restraint: setting a question before the session, giving the player no instructions the shipped game would not give, staying silent while they struggle, and writing down the moment they hesitated rather than the reason they later invented for hesitating. It runs at two scales — a few people watched closely, which tells you why something fails, and telemetry from many, which tells you how often. Both are useless without the second half of the name: iteration means the build actually changes, and changes again, which rests on a team culture that can hear that a favourite feature is not working.
Problems This Skill Solves
- A tutorial that is clear to everyone who built it and to nobody else
- A difficulty curve tuned by people who have played the game a thousand times
- Feature arguments that run on opinion because nobody has watched a stranger try it
- A mechanic that tests well in a room and falls apart over a twenty-hour play session
Roles That Use This Skill
1 total · 1 industryThis skill is concentrated in one industry.
Video Games / Interactive Entertainment / Software
"Ask testers what they would change."
Players are expert at noticing that something is wrong and unreliable at diagnosing why. "Make the boss easier" and "I could not tell which attack was coming" are the same session; only one of them is usable. The skill is in taking the observation and discarding the prescription.
"Playtesting is what you do near the end, once there is something worth showing."
The cheapest change is the earliest one. A greybox level with placeholder art answers most navigation and pacing questions, and answers them while they still cost hours instead of months. Waiting until the build is presentable is waiting until the findings are unaffordable.
Research & Outlook
Games user research has become a recognised specialism with its own bodies and practice literature, and the methods have hardened accordingly — moderated sessions, unmoderated remote testing, and large-scale telemetry are now used as distinct instruments rather than interchangeably. The open question is ethical as much as methodological: the same telemetry that diagnoses a confusing tutorial also supports engagement optimisation, and the line between the two is a design decision, not a technical one.
Future Trajectory
How Playtesting & Iteration Has Evolved
Training testers to play the game is documented as part of the level designer's own work, not a separate department's
Diagnosing and fixing errors in complex technical systems is a named duty in the Level 7 standard — testing evidence is what makes that diagnosis possible
Planning and coordinating delivery within a development team is a named duty, which is where iteration rounds are actually scheduled or squeezed out
Ways to Learn
Games Research and User Experience SIG — IGDA
Professional Community (Free)Usability testing method guides from established UX research bodies
Practice Literature (Free)Game jams — build, test on strangers the same day, iterate
Practical Route (Free)Unity Learn — playtesting and iteration project tracks
Official Tutorials (Free tier)See This Skill In Action
Watch a professional demonstrate Playtesting & Iteration in a real working environment — what it looks like, how it's applied, and why it matters.
Creative Technology / Game Development
Playtesting & Iteration
Also Known As
Growth Path
Can get a build in front of someone who did not make it and resist explaining how to play.
Sets a research question, runs a structured session, separates observed behaviour from reported opinion, and turns findings into specific changes.
Designs a testing programme across a project — which questions get small qualitative sessions, which need telemetry at scale — and builds the team habit of acting on it.
How to Practise
- 1.Sit behind one person playing your build and say nothing at all for ten minutes — the discomfort is the lesson
- 2.Write the question you want answered before the session, then check afterwards whether you answered it
- 3.Record where every tester hesitated and cross-reference the list rather than acting on the loudest comment
- 4.Instrument one metric — time to first objective, say — and watch it move as you change the build
How to Prove
- ·Publish a playtest log showing rounds of observation and the specific change each round produced
- ·Show a before-and-after metric from an instrumented build alongside the design change that moved it
- ·Run sessions for someone else's project and produce a written findings document they acted on