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

# Discover & Testing Methodology

#### Discovery

- Interviews
- Script
- Time boxed format
- Schedule
- Execution
- Data affinity mapped via Travi's workshop
- Personas
- HMW Questions > User Stories
- Red Routes
- Sitemap

**Key Deliverable:** a novel sitemap for a speculative DM, which may or may not align with the original DMv1 build.

#### Testing

- 1:1 Testing with RG members
- ID scenarios to test
- script for tester
- data extraction method
- ID Users / Use Cases
- RG Clerics
- RG Jesters (meeting facillitators)
- Members seeking info
- Members seeking to update raid/RIP status
- etc.
- Iteration
- every interview refines questions for User IDs in relation to actual experiences
- Red Routes of frictions (Tension Map)
- mapped on the existing product
- clearly ID'd pain points, bugs
- "Dark" Sitemap

#### Analysis/Synthesis

- Compare discovery *light* sitemap with testing *dark* sitemap
- Analyze the differences..
- in a report to the guild
- as recommendations to structure the build
- Used to scope the timeline/budget for Proposal #2

**Key Deliverable:** a clearly rendered sitemap of the existing product build, including friction/pain points for the current users of RG

---

### Anticipated Proposal #2
*Expected delivery of Proposal #2 is Q1-2022. This content is subject to change.*
- Final polished build of DMv2
- Justified/evidenced by the learnings of Proposal #1
- Useable Documentation of DMv2 for RG members
- Sketched in Proposal #1, executed as a discrete docs site for Proposal #2
- New design elements for DMv2
- Expand and improve upon RG component library
- Link symbols so that future changes will populate throughout the app
- Potentially SOP for how future RG branded products can incorporate this SOP to keep our design flow consistent