$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-social-satisfaction-matrixEvaluate a game's social features and multiplayer elements by their potential to create social satisfaction versus social dissatisfaction. Use when auditing chat, voice, friend systems, gifting, lobbies, social hubs, guilds, reporting tools, cooperative mechanics, profile surface
| 1 | # Game Design Social Satisfaction Matrix |
| 2 | |
| 3 | Use the Social Satisfaction Matrix to classify social elements by how much they can increase social satisfaction, how much they can create social dissatisfaction, and what that implies for design priority. |
| 4 | |
| 5 | This skill is especially useful when a team knows a feature is "social" but does not yet understand whether it is an expected basic, a risky high-impact critical element, a nice booster, or mostly secondary. |
| 6 | |
| 7 | ## Core principle |
| 8 | |
| 9 | Not all social features matter in the same way. |
| 10 | |
| 11 | Some social elements are basic expectations that rarely delight but cause frustration when missing. Some are high-risk, high-value systems that can either deepen connection or amplify harm. Some are nice boosters. Some barely move the needle. The point of the matrix is to stop treating all social features as equally important or equally dangerous. |
| 12 | |
| 13 | ## The matrix |
| 14 | |
| 15 | Classify elements into four categories: |
| 16 | |
| 17 | ### Basic |
| 18 | Must-do elements. |
| 19 | |
| 20 | - low potential to create delight |
| 21 | - high potential to create dissatisfaction if missing or weak |
| 22 | - expected foundations of the social experience |
| 23 | |
| 24 | Typical examples: |
| 25 | - friend list |
| 26 | - stable party formation |
| 27 | - baseline group management |
| 28 | - basic reporting access |
| 29 | |
| 30 | ### Critical |
| 31 | Make-or-break elements. |
| 32 | |
| 33 | - high potential to create satisfaction |
| 34 | - high potential to create dissatisfaction |
| 35 | - socially valuable but risky if handled poorly |
| 36 | |
| 37 | Typical examples: |
| 38 | - voice chat |
| 39 | - open text chat |
| 40 | - matchmaking surfaces that strongly affect teammate quality |
| 41 | - live team communication systems |
| 42 | - public social reputation surfaces |
| 43 | |
| 44 | ### Booster |
| 45 | Could-do elements that add satisfaction. |
| 46 | |
| 47 | - can make the experience nicer, warmer, or more memorable |
| 48 | - low downside if absent |
| 49 | - usually not necessary for functional play |
| 50 | |
| 51 | Typical examples: |
| 52 | - lightweight gifting |
| 53 | - celebratory emotes |
| 54 | - temporary cosmetic sharing |
| 55 | - playful social acknowledgements |
| 56 | |
| 57 | ### Secondary |
| 58 | Low-impact elements. |
| 59 | |
| 60 | - low potential to create strong satisfaction |
| 61 | - low potential to create strong dissatisfaction |
| 62 | - may matter for niche segments, but not majorly for the overall social experience |
| 63 | |
| 64 | Typical examples depend heavily on audience and context. Something secondary for one game or segment may be critical for another. |
| 65 | |
| 66 | ## What to produce |
| 67 | |
| 68 | Generate: |
| 69 | 1. **Audit target** - what game, mode, or set of social elements is being reviewed |
| 70 | 2. **Element map** - where each chosen element sits in the matrix |
| 71 | 3. **Rationale** - why each element belongs there |
| 72 | 4. **Risk and opportunity view** - what the matrix reveals about the current social landscape |
| 73 | 5. **Improvement priorities** - what to fix, protect, redesign, add, or deprioritize |
| 74 | 6. **Sweet-spot judgment** - where the design should aim to increase satisfaction without creating disproportionate social risk |
| 75 | |
| 76 | ## Process |
| 77 | |
| 78 | ### 1. Define the social scope |
| 79 | |
| 80 | Clarify: |
| 81 | - what game, feature set, or mode is being audited |
| 82 | - which social elements are in scope |
| 83 | - what audience or segment matters most |
| 84 | - whether the team cares more about retention, safety, delight, community health, matchmaking quality, or social stickiness |
| 85 | |
| 86 | Write: |
| 87 | - **Target** |
| 88 | - **Audience context** |
| 89 | - **Business/design concern** |
| 90 | |
| 91 | ### 2. Choose the elements to map |
| 92 | |
| 93 | Pick one or more social elements. |
| 94 | |
| 95 | Good candidates include: |
| 96 | - game mechanics with social consequences |
| 97 | - chat and voice systems |
| 98 | - nonverbal communication systems |
| 99 | - friend, guild, or party tools |
| 100 | - shared activities |
| 101 | - reporting and moderation surfaces |
| 102 | - profile and identity surfaces |
| 103 | - social hubs or hangout spaces |
| 104 | - gifting, acknowledgements, and reciprocal mechanics |
| 105 | - goal-setting systems that require or encourage social participation |
| 106 | |
| 107 | ### 3. Assess satisfaction potential |
| 108 | |
| 109 | For each element, ask: |
| 110 | - can this create positive social moments? |
| 111 | - does it help players bond, coordinate, celebrate, contribute, or belong? |
| 112 | - does it increase trust, recognition, or meaningful cooperation? |
| 113 | - does it align selfish goals with prosocial outcomes? |
| 114 | - can it make the game feel warmer, stickier, or more socially rewarding? |
| 115 | |
| 116 | Possible satisfaction sources: |
| 117 | - prosocial action |
| 118 | - bonding and familiarity |
| 119 | - positive recognition |
| 120 | - meaningful contribution |
| 121 | - active participation |
| 122 | - shared accomplishment |
| 123 | - belonging and group identity |
| 124 | - balanced interdependence |
| 125 | |
| 126 | ### 4. Assess dissatisfaction potential |
| 127 | |
| 128 | For each element, ask: |
| 129 | - can this facilitate harassment, griefing, or cheating? |
| 130 | - does it depend on trust that may not exist? |
| 131 | - can it create con |