--- ###### tags: `Dungeon Master` --- # DM Workshop ## Workshop Principles ### outcome-driven key “take aways” from the perspectives of the participants ### immersive people learn best by doing, not by being “told” ### focused keep the flow concentrated on achieving impact ### measurable make sure you can tangibly measure the results ## ??? What do you want participants to walk away with? --- ## Needs - Format - Exercise(s) - Visual Aids - Presentation Flow ## - Articulate goals overall - Outline an activity for each section - Time box each section - User feedback after each activity What do we want the outcome to be? Is this a workshop or a testing session? Are we teaching them how to use the tool? ### Intended Workshop Outcomes - Make it relatively entertaining! #### Primary: Increase Usage - Increasing the familiarity of other guild members with the tool to **increase daily active users** by demonstrating and canonizing SOP for Clerics for guild-wide adoption. #### Secondary: Identify Missing Elements - Demonstrate the dependencies between DM, Discord, and the whole RG stack. - Highlight missing features of the consultation process. #### Tertiary: Gather Feedback - Fast and direct feedback to populate backlog of bug reports and enhancement requests: allow everyone to leave comments in real time ### Immersion #### Who is the target segement? - Clerics - Do we want to be presciptive of the flow or highlight the differences in the approaches of Tae and Sasquatch #### What is the life cycle of a raid? ie: general Cleric flow [Referencing the testing sessions with Tae and Squatch](https://hackmd.io/@raidguild/B1h35obHo) - Client submits to the consultation queue. - Client fills out HireUs form. - Client stakes $RAID to move up the queue. - Notification in Discord: `#client-submissions` channel - An interested Cleric emojis to take on the consultation (should be synchronized with adding their name to the raid card in DM) - Consultation appears in DM - Cleric self-assigns to the consultation - Clicks `Create Raid` - Raid status is set to `Awaiting` by default - Cleric reaches out to the client to gather more information: preliminary scope info. Needs to determine if this will actually become a raid. - Based on first contact, Cleric adds roles to the raid card. - Cleric changes the raid status to `Preparing` - Cleric announces the raid and its needs during a Tuesday RoundUp meeting. DM is used to facillitate meetings. - Members are recruited to the raid: - In real time, during the meeting, then... - Posting in the *Who is Available* channel, then... - Add recruiting role tags to raid card - Adding roles to recruiting sends a role tagged notification on Discord: `#who-is-available` channel - Browsing member profiles, then DMing them directly - Should have a link in DM that connects to the member on Discord - Team conducts discovery scoping sprint with client - Generates scope doc. - Doc is uploaded to raid. Discovery sprint should be standardized. `There is currently no way to edit raid card details, upload spec docs, or otherwise add information that was gathered during the consultation process. Much needed feature for v2!` - Cleric presents scope doc to Client. - If the client denies or ghosts = changes raid status to `Lost`. - Cleric sends scope doc, budget, and timeline to client. If approved: - Setup escrow through Smart Invoice, referencing the `Raid ID` on the raid card. - Client deposit funds to begin work. - Cleric changes raid status to `Raiding` - Request:`Status Update` posted to the raid card when escrow is established, funds are deposited and released - Work commences. Cleric stewards the status of the raid: - Creates 2 channels needed on the RG Discord, camp channel and Raid channel, with a generic message about starting the raid and pings the raid party members. - Adds comments (`Status Updates`) on the raid card in DM. - `Status Updates` (comments on the raid card) synchronized with the appropriate Discord channels - Adds/removes raiders as needed. - When adding a raider to the raid, should automatically add the raider to the Discord channel = Discord integration - Continue to add/remove recruiting roles as needed. - Work is completed and approved by client. - Escrow release message posted in `Status Updates` - Cleric changes raid status to `Shipped` --- #### Random Desired Features - Applications card: should be an option to stake as a champion before turning into a member. - Member cards: Cleric wants to know their availability and desired hourly wage to know if they are appropriate to recruit.