---
# System prepended metadata

title: UX Workstream Meeting Notes 03-15-22
tags: [UX Research]

---

---
###### tags: `UX Research`
---
# UX Workstream Meeting Notes 03-15-22

## Agenda
- Quickly review prep materials:
    - Triage of topics
    - First pass of process
    - Ontological heady stuff
- Haus Keeping:
    - Setup a PM repo to capture docs and learnings - TW can focus on this so it doesn't become a burden for anyone else, supplemented by our resident genius of e2t
- Define focus areas:
    - High-level research
        - WarCamp org architecture that will also scale to the Uberhaus reboot?
    - Product features
        - MVP Summoner? Hub? Explorer?
- Identify Methodology
    - "Self Management Scale" convo with Dekan and UI369 today. TW can attend to take notes and identify opportunities.
    - Begin user testing with prototypes for specific product areas?
        - What level of fidelity?
        - Where to pull users? From DH community or beyond?

---

## Talking Points
- Personna work is important!
    - Who is actually using the platform? To guide conversations in design meetings about what particular features are necessary.
    - Currently a huge blindspot.
    - We require some concrete evidence - that is battle tested - to justify our decisions.
    - This workstream hopes to help alleviate the mental anguish of uncertainty without pulling attention resources from the building.
- Towards a Consistent Pipeline
    - Consistent focus from a local group that keeps the conversation going, iterating on process
    - Provides an important learning opportunity for onboarding in a meaningful way. => UX workstream as a funnel for quality contributors.
- How is DAOhaus used?
    - Need to gather specific metrics about users and use cases.
    - High-level perspectives combined with local, specific, product-oriented feature testing. These influence each other!
    - How are various components (Hub, Explorer, Summoner) tested to reach towards various learnings?
- Front End // Back End
    - For example, UI vs component library
    - Different users requiring different personnas > stories > flows
- Reorganization Issues
    - Rather than guild-based groups, might we approach the formation of this workstream as a **project** that doesn't require the same architecture as the other WarCamp **circles**?
    - Let's start with 1-2 potent reports and see how that goes before gathering too many cooks in the kitchen.
    - Potentially folding in to Designers meetings or Dragon Den. 
    - Rangers articles elaborating design problems of the Web3 space.

