Jameson Durall’s 2010 essay makes a small but useful point: the way you demonstrate a level changes the feedback it receives. A designer who knows every trigger and enemy spawn can breeze through encounters that an ordinary player would experience very differently.
- A fast, efficient walkthrough hides the uncertainty of a first encounter.
- That demonstration can make the team perceive the level as boring or too easy and adjust it for the wrong reasons.
- Review play should communicate the intended pacing and emotion, not simply prove that the route works.
- Reviewers need a representative experience to form useful impressions of what needs changing.
For an indie project, the practical distinction is between a technical walkthrough and an experience review. Both are useful, but they answer different questions: does the level function, and does it feel the way you intended?
The caveat is that pretending to be a newcomer cannot remove your knowledge of the level. Pair this review habit with fresh-player playtests rather than treating a carefully paced demonstration as evidence of what players actually do.