WarGames Sprint 5-26-22

--- ###### tags: `WarGames` --- # WarGames Sprint 5-26-22 ### Divisions of Battle Field *What we will review today* - Research D&D-style GM (game master) handbook. Appropriate some format for the lore playbook. *Ongoing*. Should we start a study group? 😛 [Here's a new lorecrafting guide.](https://hackmd.io/@daohaus/WarGamesLorecraftingGuide) - Review the UH onboarding documentation and flow diagrams. Appropriate for lorecrafting template. - Outline the script that needs to be delivered during launch (tomorrow). Delegate someone to read it. Make sure they know when and how. - [Review the script](https://hackmd.io/@daohaus/rk1lLOVD9). - Review the ubermeta UX methodology. This will comprise the bulk of this sprint. - Learnings will be captured in a Figma jam and added to the [Game Index](https://hackmd.io/@daohaus/HkwX30cLc) by TW --- ### Divisions of the War Room *How we might structure our meetings moving forward* - Rangers (Mondays): - tracks lorecrafting - marketing, tweets - event creation - articles that review WG like announcements of *airdrops* - UXR&T (Tuesdays): - reviews the problem space of the test - hypothesis of why it's significant - how we will test (method) to gather group input - review generated data - discuss how the learnings can best be conveyed to the WC circles to influence our product/org design - WarGames Sync (Thursdays): - track/review the **Captain's Log** - align on the details of the scenario we are testing - review the previous weeks events, scrutinize the script to make sure it makes sense - review technical needs/changes - prepare for Friday events --- ### Clearing the Fog of War *How do we capture the important data from our games?* 1. Objective Observation - diligently documented by a scribe that attends the event. *Not a player, admin, or holding any other responsibilities.* 2. Subjective Observation - user tester that is playing the game and recording their experience. *This should not be Dekan, Jeremy, Travis, or others focusing on the UX, as it will corrupt the data. (Maybe Travis since he hasn't been playing yet?)* - volunteer tester will commit to the following: - performing a checklist of game actions (following directions) - recording their screen in a standardized way and submitting the video to DH - submitting a form that reviews their experience - successful testing epochs will receive a reward ##### UX Tester Incentives *How do we incentivize user testing, ie: participation in WarGames? A big topic! Let's collect ideas.* - Collectible tokens: POAPs, PFPs, sellable NFTs - HAUS token: needs clear strategy to encourage utility in the DH community - Encourage participation in UH: - [using HPL to encourage NFT collection and WGs participation](https://hackmd.io/@daohaus/Hy_4sXVvq) - [conga line NFTs](https://hackmd.io/@daohaus/rJH7zy7U9) - Encourage evangelism of DH, UH, and WGs through the games themselves ##### Details on Data Collection 1. Screen Recording - Instructions for an easy way for the user to capture their own screen. *Should be standardized and free.* - Instructions for how to voice-over narrate the user experience. - Create a tutorial that demonstrates how to do this. Added to the WG docs. - Uploaded to a Github repo? Other private video repo? - UXR&T will review the data and present learnings 2. Forms 🙄 - Personna Survey - *This is different from the in-game character creation form* and is more concerned with building realistic UH user personnas, but links to the fictional character. - Quick, easy form that captures essential demographics of the user tester. - Exit Survey - Ratings-based (scale of 1-10? 1-5?) that quickly captures the subjective experience of *the specific points we are testing.* - Comments section to capture qualitative experience. Questions: - Can these forms be integrated into the character/faction selection form already created? - Do we want all players to be obligatory testers, or do we want this to be self-selected and optional? - Should we integrate this form-based feedback into the UH flow, at least during the intro launch phase? --- ### The War Within the War *What are the game-only elements? Are they really?* - Airdrop of SPICE to players - Can it be automated? - Won't we airdrop HAUS to new UH members? Should we? - Will UH have it's own Discord server? - Has strong impact on how we test - Might be its own comparative analysis study? - Does DH facillitate the UH experience or do we support UH autonomy? - Does UH make this decision? - Discord channel architecture - Should replicate actual UH channels for testing purposes - Including perms/roles/admin. Important attack vectors and biases here that we should test! --- ### Security Checkpoints *What are we actually testing? Let's get specific with UH/WG stack. We need to test each phase independently. We are not responsible for the UX of each app, but are responsible for their integration into our flow.* #### DAOhaus Platform/UI - UX of the interface - Proposal flow, especially initial membership proposal - Understanding Boosts - Generates essential data for Magesmiths for ongoing product development - HAUS token utility in relation to governance weight [(to be developed in a later game)](https://hackmd.io/@daohaus/HyGyUFTH5) #### LightHaus: Discord, Discourse, Snapshot - Implementation of token-gated access - Bots that automate the social flow, notifications, roles/perms *Huge attack vector!* - **Define the red route user flows between apps** - Transitioning experience between apps (UX) - Transitioning conversation between apps: when does Discord chatter become a Discourse forum post become a Snapshot proposal? Does this require policy? #### Yeeter - Yeeter experience for UH - Instructions/clarity on shares vs loot terminology, what it means to *Yeet* - LightHaus vs PowerHaus clarity - Transition from soft gov to hard gov #### PowerHaus (when UH get ubermeta): Back to DH UI - Clarity on the relationship between UH and DH/WC: who is accountable to who - Clarifying stewardship of the HAUS token, opportunities for supporting DH with LPing, other opportunities/rewards/incentives - Responsibility to participate, otherwise UH fails and what are the implications - Philosophical exploration into Uber governance as a DAO-of-DAOs, Federation, etc. What could it become? - Instructions on UH 2 body governance and how UH members can ratify new policies