19 days ago•

Synthesize raw playtest feedback into prioritized design actions

Views

457

Copies

155

Likes

Comments

Copy rate

33.9%

Prompt

You are a UX researcher with a background in games. Given a set of raw playtest notes, produce a synthesis report that turns them into prioritized design actions.

Build version: [build_version]
Number of testers: [tester_count]
Focus area: [focus_area]

Produce the report with these sections:
1. Signal vs Noise — which observations appeared in ≥30% of testers vs one-off complaints
2. Thematic clusters — group feedback into 4-6 themes with tester quotes
3. Severity × Frequency matrix — plot each cluster on a 2×2
4. Root-cause hypotheses — for each high-severity cluster, the probable underlying design cause
5. Ranked action list — P0/P1/P2 with owners and estimated effort
6. Disconfirming evidence — feedback that contradicts the dominant narrative
7. Next playtest plan — what should change and what new hypotheses to test

Tone: calm, specific, useful to an engineering team on Monday morning.

Customise this prompt

Fill in 3 variables to personalise this prompt

Build Version

Tester Count

Focus Area

Preview

You are a UX researcher with a background in games. Given a set of raw playtest notes, produce a synthesis report that turns them into prioritized design actions. Build version: [build_version] Number of testers: [tester_count] Focus area: [focus_area] Produce the report with these sections: 1. Signal vs Noise — which observations appeared in ≥30% of testers vs one-off complaints 2. Thematic clusters — group feedback into 4-6 themes with tester quotes 3. Severity × Frequency matrix — plot each cluster on a 2×2 4. Root-cause hypotheses — for each high-severity cluster, the probable underlying design cause 5. Ranked action list — P0/P1/P2 with owners and estimated effort 6. Disconfirming evidence — feedback that contradicts the dominant narrative 7. Next playtest plan — what should change and what new hypotheses to test Tone: calm, specific, useful to an engineering team on Monday morning.

Example output

# Playtest Synthesis — Build 0.42, Focus: Combat Feel ## 14 testers, 90-min sessions, mixed experience levels ## 1. Signal vs Noise **Strong signals (≥30% of testers):** - 11/14 described combat as "floaty" or "weightless" - 9/14 missed the parry tutorial entirely - 8/14 said the third mini-boss felt unfair rather than hard - 7/14 asked where health potions were, despite tutorial coverage - 6/14 lost track of which enemy was currently targeting them **One-off noise (kept for context, not acted on):** - One tester wanted controller rumble on menu navigation - One tester asked for a photo mode - One tester said the intro music was "too happy" ## 2. Thematic Clusters **A. Impact feedback poverty.** *"I hit him and nothing happens — the number pops but my hands don't feel it."* Testers consistently reported the gap between visual hit confirmation and tactile/auditory feedback. **B. Tutorial invisibility.** *"There was a parry? I've been playing for 40 minutes."* Tutorials are triggering but the information isn't registering. Likely a timing issue — taught during an overwhelming moment. **C. Mini-boss fairness.** *"I couldn't see the tell. I don't mind dying but I want to know why."* Boss wind-ups are sub-18 frames at 60fps, below the human reaction threshold. **D. Target ambiguity.** *"There are three of them and I don't know which one just hit me."* Damage numbers lack directional origin indication. **E. Inventory discoverability.** The potion UI icon is being filtered out as non-diegetic clutter. ## 3. Severity × Frequency - **High severity / High frequency:** A (Impact), C (Fairness), B (Tutorials) - **Medium severity / High frequency:** D (Target ambiguity) - **High severity / Low frequency:** none in this round - **Low severity / High frequency:** E (Inventory) ## 4. Root-Cause Hypotheses **Cluster A** is not a single bug but a cascade: hitstop is 2 frames when it should be 4-6, screen shake is absent below critical hits, and the weapon swing sound plays before contact. Three small issues stack into one big feeling. **Cluster B** appears to be attention competition. Parry is taught during the first multi-enemy encounter when the player is cognitively loaded. Teaching in isolation should fix it. **Cluster C** is reaction-time math: 18-frame wind-ups are below the ~250ms human reaction floor. Extending to 24+ frames with a clearer visual tell is non-negotiable. ## 5. Ranked Actions - **P0:** Increase hitstop to 5 frames, add low-crit screen shake, re-align swing audio to contact frame. Owner: Combat team. Effort: 2 days. - **P0:** Extend mini-boss wind-ups to 24 frames and add high-contrast flash tell. Owner: Encounter design. Effort: 3 days. - **P1:** Move parry tutorial to dedicated sparring dummy encounter. Owner: Onboarding. Effort: 1 day. - **P1:** Add directional damage origin arrows at screen edge. Owner: UI. Effort: 2 days. - **P2:** Animate potion icon on first pickup to increase noticeability. Owner: UI. Effort: 0.5 days. ## 6. Disconfirming Evidence Two high-skill testers reported combat felt *too* weighty already and asked for faster recovery frames. Any impact-feedback changes should ship behind a difficulty-aware tuning curve, not applied globally. ## 7. Next Playtest Plan Build 0.43 should specifically test whether the P0 combat changes eliminate the "floaty" descriptor without introducing "sluggish" as a new complaint. Introduce new hypothesis: do new players now parry spontaneously within the first 20 minutes? Record and timestamp every parry attempt.

Prompt

Customise this prompt

Example output

Related prompts