---
# System prepended metadata

title: WarCamp UX Rage Machine Planning
tags: [UX Research, Magesmiths, Meeting Notes, Rangers]

---

---
###### tags: `Magesmiths` `Rangers` `Meeting Notes` `UX Research`
---

# WarCamp UX Rage Machine Planning

March 21, 2022 - from TW's POV
*Essential UX priorities for this week.*

## Magesmiths UX Testing

[Magemsiths Roadmap](https://docs.google.com/document/d/1oZypPzqHVaJecdtTpAhgYG5D9o3iZKGX7H6CRfzkSOA/edit?usp=sharing)

- Alpha testing = internal. Should begin ASAP
- Beta testing = larger community. Might begin around June.

#### 1. DAOhaus v3 Alpha

- Haus Components v0.1
- Haus SDK v0.1
- Summoner Alpha (hard mode)
- Hub Alpha (view all DAOs)
- DAO UI Alpha (limited functionality)

#### 2. Maintenance of v2

- Bug-fixes
- Feature deprecations strategy
- Improve customer service process

#### 3. DevRel Workstream (no support required)

#### 4. Issues in Decentralized App Management

- Apply v3 PM processes to other workstreams
- Identify issues
- Publish learnings in *rage Reports*
- Reseve time for Magesmiths' learnings

#### 5. Redesigned DAOhaus Webite

- Overview of new feature development

---

### Cadence

![](https://i.imgur.com/XOa6XK8.png)

- **Initial testing of Alpha apps can begin immediately** as discreet parts with limited functionality.
    - Need to gather initial testing parameters from Rage/Sage crews. 
    - Do the raw apps get tested as low-fi prototypes separately from the higher-fi designs? Is there a rage UX crew different from a sage UX crew?
- **April/May**: the components will begin to come together. Testing of longer flows can begin.
- We want to encourage **regular 1:1 or group syncs**, with regular updates for **Retro/Demo** (Camp Fire) sessions on alternating Fridays.
- *We are aiming for consistency and reliability over speed.*

---

### V3 Planning

- [DAOhaus Wiki](https://github.com/HausDAO/daohaus-monorepo/wiki) allows for ongoing archiving of project progress across the v3 teams. All of our collective resources are here.
- UX team should integrate testing tasks onto [the shared kanban board](https://github.com/orgs/HausDAO/projects/3/views/3) under the **Testing** column to share the workstream's learnings across the team. 
- Once testing begins, we might consider breaking out to our own project-specific board to integrate into the shared repo.
- Let's be deligent in observing [the best practices,](https://hackmd.io/@daohaus/kanban-best-practices-overview) especially [the v3 project statuses](https://hackmd.io/@daohaus/HJBzBUnbq) to determine when a card in pulled/complete. *This will help keep the flows low friction. The goal is to make the process less complicated.*

---

## Rangers UX Testing

Medium, Substack, Mirror, Twitter...

- Why does Rangers/DAOhaus have 3 competing publication outlets? Might we test these tools against each other?
    - SEO integration
    - Tracking subscribers
    - Native analytics so we can track usage, or integrations. Web3 analytics?
    - Different use cases of content: updates, launches, in-depth articles, features, etc.
    - Web3 community legitimacy
    - Improve messanging to our user base: what are the most important metrics to be tracking? Are the native/built-in metrics actually contributing to the quality of engagement we are trying to foster?
        - Attracting to events like Haus Party Live
        - Summoning new DAOs on the platform
        - Onboarding contributors to WarCamp, Uberhaus, etc.

---

## Paladins UX

- Holocracy + DAOs architecture
    - Uberhaus reboot
    - WarCamp reboot
    - Other self management systems: competitive analysis?
- War Games strategy! Lots of ideas currently in the Discord that we can begin compiling to visualize some strategy and scenarios.

---

## To Do for the Week of March 21-25

- First task: **A/B testing of new language for the core DAO UI in v3 summoning.**
- Setup a kanban board for the UX flows so designers et al can submit tasks.
    - Is it open for anyone to add tasks?
    - Develop a template for the card submission? For example: To Do, Doing, Done; or more granular?
    - Allow to emerge and adapt based on specific/immediate needs. **Use tags** to categorize/filter into discrete buckets.
    - Different scopes:
        - Begin with initial assumption of user activity, put in relation to higher-level DH-wide cultural assumptions. Correlated to 
        - High-level, further out issues. Research concerned with what to do and how we should do it. Content not included in Amos' charts yet.
        - Design iterations, pre-development. Feedback on initial designs before they are put into the dev pipeline. Questions to test, inspiration from the community, testing assumptions of early features.
        - Developed by engineers, post-development. Currently in testing column of V3 kanban board. Allows us to anticipate design>rage flows to initiate appropriate strategies. Features are more firm in the development process, less exploratory and more battletesting (does it work the way we thought it would?).
- DH community is at our disposal.
    - Setup a recurring user gathering for testing?
    - Correlated to a recurring war games iteration?