xtremflow/_bmad/bmgd/workflows/gametest/playtest-plan/playtest-template.md

Playtest Plan: {BUILD_NAME}

Version: {BUILD_VERSION} Created: {DATE} Session Date(s): {PLAYTEST_DATES}

---

Overview

Objective

{What are we trying to learn from this playtest?}

Build Information

• Version: {version}
• Platform: {PC/Console/Mobile}
• Content: {What's included in this build}
• Known Issues: {List any known bugs to ignore}

Success Criteria

{How will we know the playtest was successful?}

---

Participants

Target Profile

• Player Type: {casual/core/hardcore}
• Genre Experience: {familiar/unfamiliar with genre}
• Age Range: {if relevant}
• Other Criteria: {specific requirements}

Recruitment

• Count: {number of participants}
• Source: {internal/external/panel}
• Compensation: {if applicable}

---

Session Structure

Pre-Session (15 minutes)

1. Welcome (5 min)

   • Introduce yourself and the team
   • Explain what they'll be doing
   • Emphasize: "We're testing the game, not you"

2. Consent & Setup (5 min)

   • Recording consent: {yes/no}
   • NDA: {yes/no}
   • Collect demographic info: {yes/no}
   • Hardware preferences

3. Instructions (5 min)

   • "Play as you normally would"
   • "Think out loud if you're comfortable"
   • "Ask questions anytime"
   • "You can stop at any time"

Gameplay Session ({DURATION} minutes)

Free Play vs Guided Tasks

• Free play - Let player explore naturally
• Guided tasks - Specific scenarios to complete

Focus Areas

1. {Area 1 - e.g., Tutorial effectiveness}
2. {Area 2 - e.g., Combat feel}
3. {Area 3 - e.g., Navigation clarity}

Intervention Threshold

Only intervene when:

• Critical bug prevents progress
• Player is genuinely distressed
• Session time is running out
• Player explicitly asks for help

Post-Session ({POST_DURATION} minutes)

Immediate Reactions

1. "What was your overall impression of the game?"
2. "What moment stood out the most?"
3. "Would you play this again? Why or why not?"

Feature-Specific Questions

1. {Question about focus area 1}
2. {Question about focus area 2}
3. {Question about focus area 3}

Open Feedback

1. "Is there anything you wish the game had?"
2. "Anything else you'd like to share?"
3. "Questions for us?"

---

Observation Guide

What to Watch For

Signal	Examples	Action
Confusion	Pausing, circling, re-reading	Note location, duration
Frustration	Sighing, repeated attempts, quitting	Note cause, frequency
Engagement	Leaning in, exclaiming, "one more try"	Note feature
Boredom	Checking phone, rushing, disengaging	Note when drop-off begins
Discovery	"Oh!", trying things	Note what triggered it

Metrics to Collect

• Time to complete tutorial
• Number of deaths/failures per section
• Features/items discovered
• Total session duration
• Completion rate

---

Note-Taking Template

Participant: ___  Date: ___  Observer: ___

TIME | LOCATION | OBSERVATION | REACTION | NOTES
-----|----------|-------------|----------|------
     |          |             |          |
     |          |             |          |
     |          |             |          |

Key Moments:
1.
2.
3.

Overall Impression:

---

Team Roles

Role	Responsibilities	Assigned To
Facilitator	Welcome, instructions, interview	{name}
Note-taker	Observations, timestamps	{name}
Tech Support	Build, recording, troubleshooting	{name}

---

Logistics

Equipment

• Game build installed and tested
• Controllers/input devices
• Recording equipment (if applicable)
• Consent forms
• Observation templates (printed)
• Compensation (if applicable)

Environment

• Quiet, private space
• Comfortable seating
• Water/snacks available
• Clock/timer visible

---

Post-Playtest Process

Same Day

• Quick team debrief (15 min)
• Consolidate raw notes
• Flag critical issues

Within 48 Hours

• Synthesize findings
• Identify patterns
• Draft playtest report

Report Delivery

• Due Date: {date}
• Distribution: {team/stakeholders}
• Format: {document/presentation}

---

Notes

{Any additional notes, special considerations, or reminders}