---
# System prepended metadata

title: Notes for DM Test Session - Part 1 & 2
tags: [Dungeon Master]

---

---
###### tags: `Dungeon Master`
---

# Notes for DM Test Session - Part 1 & 2

### Sasquatch "I am a Cleric"

- Try to connect with a RAID that came through the submission queue.
- Wallet Connect: successful. 
- Long loading screen. Need to refresh.
- Looking for consultation. Consultation sort should be separated from the rest of the terms.
- Consultations should be the landing page. First thing to care about.
- Clicks on details of a consultation to view. Scanning and browsing by using back button.
    - Q: What are the priorities for ordering? 
    - A: Descending by date. If/when staking is implemented, the consultations should be ordered by most staked.
```
- Paid/un-paid consultations are showing up: is this still a thing?
    - If a RaidGuild member submits a consultation they don't pay a fee?
    - Iterations - **need to confirm the appropriate flow with the guild.**
        - No payment
        - 500 DAI rolled into the Raid if it is accepted
        - 500 DAI with a Raid bid to increase priority in the consultation queue
        - Free submission option
        - If SEO Rodeo RIP is successful:
            - Submission for information, or
            - 500 DAI for consultation
```
- Elements of the consultation card: what elements are important?
    - Pending consultation tag = yes
    - Submission time = yes
    - Product type = no
    - Budget = yes
    - Who submitted = yes
    - Services Required = yes (should be *Skills needed*)
    - Summary text = yes (should be clearly labeled as project details/summary)
    - Raid Category = no
    - Desired delivery = yes
    - Spec = uncertain, yes (scope, whitepaper) Seeing this provides a clearer understanding of the client's needs
    - Project type = uncertain
    - Client point of contact = should be revealed by default, not hidden
    - **Legacy ID** = *very* important (would be nice to click the ID and be transferred to the Smart Escrow site)
    - Missing:
        - Skills needed - in this example client doesn't know what they need
    - Consultation hash = yes (the txn for submitting the consult)
    - 
- Referencing the HireUs page:
    - *What services are needed?* should be updated
- Clicks "Create Raid". Leads to Active Raid card.
- Elements of the active raid card:
    - Recruiting: should trigger an action, sends a link to the raid with a tag displaying what is needed
    - "Create Raid" = create 2 channels needed on the RG Discord, camp channel and Raid channel, with a generic message about starting the raid
    - When adding a raider to the raid, should automatically add the raider to the Discord channel = Discord integration
    - Product Tags = no, confusing why this is important, seemingly useless
    - Status Updates = no, this is not meaningful to a Cleric, should go away, unless its integrated with Dework or other project management tool.
        - Now: serves no purpose. Shouldn't be here. Updates happen in Discord or Trello.
        - What would be useful: just a link to the Discord channels, Escrow, milestone updates.
        - From a Clerics perspective, there is no reason for this.
        - Q: Would there be any kind of status update that would be important to a Cleric?
        - A: Updates should be related to recruiting, the raid party roster, more general project updates
- A cleric would setup the raid in Discord. As many integrations into the Discord server that would help with setting up the raid and gathering information on the raiding members would be helpful.
    - Once the cleric knows the raid party they are trying to recruit, they want more information on the individual raider.
    - Not recognizing the "Members" tab as a destination for member information.
    - Cleric flow: *Who is Available* channel on Discord. Really desires a list of Raiders sorted by skill set and active status.
- Q: Raid party is setup. What next?
- A: 
    - Make a proposal. 
    - If client agrees, setup the Escrow. 
    - Escrow Index is populated. 
    - "Locker Hash" is confusing, should be the multisig link.
    - Change status to "raiding".
    - Wants an update when escrow is released.
- Q: Once a raid is raiding, what are your clerical information needs? Is it handed off?
- A: Haven't found a project management tool that everyone wants to use and works well, so this amounts to lots of manual project updates.
    - Change orders. Would like to see this under "Status Updates"
- Navigates to Members menu.
- Scrolling to see if members have more than one role, but everyone has one.
- This is what was desired earlier. Didn't find it because it wasn't in the work flow of the Cleric.
- Now that he has found it, it seems important.
- Needs a Monk. Clicks navigation.
- There should be a link in each raid card that navigates directly to member information.
- Wants to see: 
    - previous raids of the member: 
        - raids they are on, previously completed, to clarify a CV of experience plus their availability/bandwidth
    - Hours per week available
    - Desired hourly wage
- Text is difficult to read.
- Clicks on Applications.
    - Should have another section on apprentices (cohort members).
    - This would allow champions to find information to initiate championing.
    - Within the applicant tabs, they should be sortable by skills.
    - All members should be sortable as apprentice, championee, full fledged member, and applicant.
- Biggest problems for Clerics:
    - Finding people that are available.
- Top desired features:
    - Discord integrations
    - Accurate member list, up to date with nice filtering, attention paid to data on member cards

---

### Taekekz "Thriving or just Surviving"
#### General Cleric Needs
- Getting started:
    - Existing vs new clients have different funnels. Start with new client.
    - New client flow: Hire Us form > internal Discord channel > an interested Cleric emojis to take on the consultation
    - Taking on a consultation means entitlement to the $500 consultation fee.
    - Difficult to ensure a consistent experience for the client: ensuring the client felt they received good value for their time.
    - The consultation is itself a high value product; we bring our experience to the first chat.
    - Brought on more apprentices to get exposure to the Cleric process to gain experience, but eventually faded out.
    - Points to a need to standardize the process.
    - Will always require web3 expertise and skillful salesmanship.
- Monitoring the consultation queue and next steps:
    - Checked daily, especially the unread cards.
    - If not already in contact, send a cold email with an introduction and times to meet.
    - Initial convo allows RG to vet the client for seriousness of follow through, viability of concept.
    - Understand the clients needs.
    - If serious, announce a TL;DR at a Raider Roundup call (Tuesdays) for recruitment.
    - Start to conceptualize the team.
- Recruitment:
    - Raider Roundup is important for understanding who is available and active.
    - Clerics will receive DMs from members declaring their availability, but meetings encourage engagement.
    - 70-80% of raid parties are formed during the Tuesday meetings.
    - `Who is Available` is second choice, 20% recruited through this process.
- Kicking off a raid:    
    - Depending on complexity and scope of specs, raids can begin almost immediately.
    - Most will require a design sprint to scope.
    - Some clients want an estimate/quote to decide. Detailed budget could come later.
    - All specs are different. Systemization of the specs would be difficult, but perhaps related to ensuring a consistent experience of high quality and professionalism to the client.
- Upon accepting client work:
    - Client has received a HackMD proposal with a firm price.
    - "Where do I send the money" is the greenlight.
    - Setup the invoice, setup the escrow, client deposits funds, everyone gets to work.
- Discord: Upon making the raid official
    - Setup internal and external channels.
- Kanban board was useful for reasons:
    - Moving cards across the board, adding notes to the cards.
    - Transparency was nice: others can view the work, clear accountability.
    - An archive of historical raids would be important for justifying future decisions.

#### Dungeon Master Focus
- Clearing the queue was historically annoying.
- Major friction atm is the slow loading times.
    - Checking Membership loading screen should not be a pinwheel. Currently infuriating.
- LARPing the Cleric flow:
    - Preparing a raid card.
    - Wants to use the `Add Role` and `Add Raider` features.
    - Wants to observe who is active and available.
- Initial suggestions:
    - Nuke the sort categories.
    - Nuke all unnecessary data: start fresh with new raids.
    - Basically, separating the archived raids from the most contemporary cards.
- What do you want to see on a card:
    - Clients name
    - Ability to add detailed notes.
    - Lost raids need more detail about why exactly that happened so it can become a collective learning experience.
- Cards:
    - Consultations card wants:
        - Who is the cleric assigned to the project? Who is handling the consultation?
    - What is important info on the cards to point to a CTA for the cleric?
        - All relevant info is there.
        - If anything, maybe too much info.
        - Unnecessary:
            - Project Type
            - Services Required - should at least be reduced to 2-3 services
- What are the criteria for sorting?
    - Highest priority = where the client is in the queue, correlated to the amount of staked raid.
- Member Cards:
    - Don't want to see inactive members.
    - If its being used to assemble a raid party:
        - Who is active/available
        - What skills do they have
        - Full member directory is separated from active pool.
        - Overall, the member browse section is not particularly useful; low priority.
        - Wants to be able to submit a DM directly to members.