---
# System prepended metadata

title: DM Demo & Testing Method
tags: [Clerics]

---

---
###### tags: `Clerics`
---

# DM Demo & Testing Method

Personna: Cleric
[Referencing the testing sessions with Tae and Squatch](https://hackmd.io/@raidguild/B1h35obHo)

![](https://i.imgur.com/fAQLstD.jpg =x500)

---

## Workshop Flow

### Creating a Raid

- 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` 

> When user clicks `Create Raid` the toast appears, the raid is successfully created, but the user is not self-assigned. There does not appear to be any way to assign a Cleric to the raid.

- Raid status is set to `Preparing` by default

> Actually sets raid status to `Preparing` by default

---

### Initial Contact and Recuiting

- 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 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

> Cannot remove Recruiting Roles at all. Noticed when adding raiders to the raid.

- Browsing member profiles, then DMing them directly

> Feature Request: Should have a link in DM that connects to the member on Discord

---

### Scope / Proposal

- Team conducts scoping sprint with client
    - Generates a proposal. 
    - 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 proposal to Client](https://hackmd.io/@SasquatchTru/SJlYn9Nsi)
- 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 Escrow](https://smartescrow.raidguild.org/), 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

---

### Actively Raiding

- 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.

> Feature Request: `Status Updates` (comments on the raid card) synchronized with the appropriate Discord channels

- Adds/removes raiders as needed.

> Feature Request: 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.

---

### Shipping a Raid

- Work is completed and approved by client. 

> Feature Requst: Escrow release message posted in `Status Updates`
- Cleric changes raid status to `Shipped`

---

## UX Testing Flow

### Persona Scenario: Cleric (Account Manager)- Lifecycle of a Raid

- Tracks raid status from birth through death
- Appropriate the flow from the workshop outlined above

#### Side Quests

- Sort:
    - prioritizing all the existing sort terms
    - identifying missing sort terms
- Search:
    - an active raid
    - an archived raid
    - a specific role
    - a specific member

### Persona Scenario: Jester / Moloch Hunter (Meeting Facillitatooor)

- Synchronize with [Charmverse](https://app.charmverse.io/raid-guild/page-186271037076444)
- Follows the Raider Roundup Meeting format:
    - Props and Shills
    - Preparing Raids
    - In Progress Raids
    - Moloch Sightings 
    - RIPs
    - Other / Open Discussion
- Explore the perspective of raiders looking for work and friction points they encounter during the Tuesday meetings

> Feature Request: Increased fidelity of tracking coordination failures (Moloch Sightings) for the raid card, especially if it is lost/archived

### Persona Scenario: Tavern Keeper (Community Manager) - Facillitating an Apprentice Cohort

- Uses DM to screen applications that enter through the JoinUs submission queue
- Contacting apprentices
- Using DM for championing
    - Staking $RAID
    - Integration with RG Github
    - Auto Discord posting
- Educating apprentices on how to use DM:
    - adding their projects to DM for guild-wide tracking
    - getting familair with all the app features
    - getting familair with Cleric SOP & best practices
- Identify potential integrations with other social and project management tools that TKs use (Miro boards, DeWork and/or Trello kanban boards, Github, etc) 

### Persona Scenario: Hunter (BizDev)

- Wants to add clients directly into the consultation queue
- Discovery:
    - demonstrate their process
    - share what tools they are currently using and their must have features
