Game Design Player Segment Perception Audit
Check not only who the feature is for, but who will see it, misunderstand it, resent it, or feel left out by it.
Use this skill to audit a feature through the eyes of different player segments. The goal is not to please every segment equally. The goal is to understand who the feature is actually serving, what other groups will perceive, and where update visibility, access, and expectation can create disappointment or wasted communication.
Read references/segment-layers.md when mapping the main audience groups.
Read references/perception-failures.md when diagnosing common update-perception mistakes.
Read references/recommendation-patterns.md when deciding how to adjust targeting, access, or messaging.
What to produce
Produce:
- Feature read - what the feature is and who it seems intended for
- Target segment read - which cohort is supposed to care most and why
- Cross-segment perception - how other player groups are likely to interpret it
- Access and visibility mismatch - who will hear about it versus who can actually use it
- Risk diagnosis - what disappointment, alienation, or wasted hype may result
- Recommendation - how to retarget, reframe, gate, soften, or broaden the feature rollout
Process
1. Clarify the feature and its intended audience
Ask:
- what is being added or changed?
- which player segment is the real target?
- why would that segment care?
- what specific value does the feature create for them?
2. Map the main player segments
At minimum consider:
- new players
- midgame players
- elder/endgame players
Also consider when relevant:
- free players
- spenders
- competitive players
- collectors
- social players
- lapsed returners
3. Audit visibility versus access
Check:
- who will see this feature in patch notes, ads, art, store pages, or UI surfaces?
- who can actually access it soon?
- who must wait, grind, pay, or reach a threshold first?
- is the feature headline content for players who cannot meaningfully touch it?
4. Audit perception by segment
For each important segment ask:
- will they care?
- will they understand why it matters?
- will they feel invited, excluded, indifferent, or misled?
- does the update strengthen their sense of future aspiration or create disappointment?
5. Diagnose mismatch risk
Look for patterns such as:
- excitement generated for the wrong audience
- feature aimed at elder players but marketed broadly to everyone
- midgame players ignored even though they are the pipeline to elder status
- access friction turning aspiration into resentment
- feature value obvious only to one cohort while others see noise
6. Recommend a better segment strategy
Possible moves:
- target communications more narrowly
- create smaller companion value for non-target segments
- adjust unlock timing or access path
- reduce visible hype for inaccessible content
- provide aspiration framing without overpromising immediate relevance
Response structure
Feature Read
- ...
Target Segment Read
- ...
Cross-Segment Perception
- ...
Access and Visibility Mismatch
- ...
Risk Diagnosis
- ...
Recommendation
- ...
Fast mode
- Who is this really for?
- Who else will see it?
- Who will care, who will not, and who will feel disappointed?
- Is the visibility broader than the access?
- What is the best fix: targeting, framing, or access?
Style rules
- Do not assume one feature must serve all players equally.
- Distinguish target audience from visible audience.
- Pay special attention to middle cohorts, not just new and elder players.
- Be concrete about disappointment mechanics, not just vague sentiment.
- Treat aspiration carefully; it can motivate or alienate depending on access.
Working principle
A feature is not experienced only by the players who use it. It is also experienced by the players who see it, anticipate it, misunderstand it, or discover they are excluded from it.
Part of the Game Design Skills Bundle by Stanislav Stankovic. Licensed under PolyForm Noncommercial 1.0.0 — free for personal, academic and nonprofit use. Commercial use requires a licence, sold as skill packs. See https://github.com/Stanestane/game-design-skills-bundle for terms.
Required Notice: Copyright Stanislav Stankovic (https://www.stane-island.net/)
