---
###### tags: `UX Research`
---

# DAOhaus User Persona Templates - Moloch v3

**Current Persona Outline**
https://daohaus.club/docs/handbook/summoners/summoners-best-practices/

**DAO Process Library Index**
https://hackmd.io/lj6CVKKzT42nB1lwXk28GQ

**User Stories by Christina**
https://hackmd.io/THkVIQYCQCqR9nlbFMGR5w?both

## Web3 Workstreams (contributor teams)

### Goal
empower web3 workstreams with dynamic coordination tools and flexible governance/incentive models

### Why DAOhaus?
- why do they need to use DAOhaus above all other options?
- why do they need flexible governance structures?
- why do they need a treasury with ragequit?

### Relevant features
- full suite of DAO tools
- manage books
- task manager
- safe minions
- shamans
- snapshot
- easily deploy custom boosts
- dev tools/libraries
- templatized organizational setup (TOS)
- github template
- all-in-one DAO framework
- manifesto
- constitution
- process/structure docs
- static site
- compensation models
- forms for PM
- flexible governance structure
- transferable vs nontransferable gov power
- shared treasuries
-
- RageQuit

### Processes
- customizing the TOS
- step-by-step on customizing the TOS to fit the project's culture
- how to workshop a manifesto and constitution with team and/or community
- summoning a DAO
- step-by-step instructions with recommended configurations based on user persona
- settings & boost configurations
- determining intial members and share distribution
- how to identify the initial members of your DAO?
- how to determine the right amount of shares to start with
- how to fairly distribute them among the initial members
- evenly or based on something like coordinape
- incentive model / compensation structure
- outline a few different models
- coordinape - contribution value based on consensus
- revenue sharing - how to manage value flow via vaults
- when to give gov share vs loot
- stable payments vs native token payments
- DAO ops (haus keeping)
- proposal management
- regularly checking on proposal status
- making sure members vote
- facilitating transactions
- performing transfers
- minion interactions
- budgeting / comp support
-
- onboarding new contributors
- onboarding flow from web/discord to DAO
- onboarding models
- reputation building (contributions)
- progression system (discord role/channel access)
- value consensus (coordinape)
- treasury management
- ragequittable vs non-ragequittable vaults
- safe minions & DeFi
- treasury diversification
-
- managing multiple products/work streams
- workflow models
- product dev organizational methods
- self/team assessments
- self organizing / bottom up design
- communication channels
- joining and participating in UberHAUS
- what is UberHAUS
- what are the benefits of UberHAUS
- what's required to join
- what's required to maintain active membership
- how to maximize value creation via UH

### To-do list
1. templatize important processes
1. curate a list of teams currently using DAOhaus to coordinate
1. interview them to identify what they like and don't like
1. build templatized organizational setup (TOS)
1. build a list of potential projects to onboard
1. pitch deck/1 pager
1. possibly design an incentive model for teams to use DH

## Open source (web2) communities

### Goal
onboard existing web2 communities that are building open source software in order to make it easier for them to contribute and coordinate around a transparent treasury with voting rights.

### Why DAOhaus?
- Why do they need a DAO in their lives?
- Why do they need a transparent treasury?
- Why do they need a voting mechanism?

### Relevant features
- transparent treasury to manage grants
- flexible governance structure
- templatized Organizational Setup (TOS)
- ragequit & side vaults

### Processes
- summoning a DAO
- determining intial members and share distribution
- customizing the TOS
- incentive model / compensation structure
- DAO ops (haus keeping)
- onboarding new contributors
- treasury management
- joining and participating in UberHAUS
- managing multiple products/work streams

### To-do list
1. templatize important processes
2. language crafted specifically for web2 communities building open source software that explains the benefits of using web3 coordination tools.
3. build a list of potential projects to onboard
4. templatized organizational setup (TOS)
5. interview them to identify needs and gaps
6. pitch deck/1 pager

## NFT Communities

### Goal
become the standard for NFT communities to DAO up and empower their collections and contributors

### Selling points
- NFT based governance
- shares based on NFT ownership
- transferable membership
- NFT treasury management (collect NFTs as a DAO)
- templatized organizational setup (TOS) [github template]
- flexible governance structure
- RageQuit

### Processes
- summoning a DAO
- determining intial members and share distribution
- customizing the TOS
- incentive model / compensation structure
- DAO ops (haus keeping)
- onboarding new contributors
- treasury management
- joining and participating in UberHAUS
- managing multiple products/work streams

### Why DAOhaus?
- why do they need to use DAOhaus above all other options?
- why do they need flexible governance structures?
- why do they need a treasury with ragequit?

### To-do list

## Major social clubs
Shared treasury, coordination and transparency with a premium on community.

## Nonprofit organizations (web2/3)
> [name=Bill Warren - Think this would also cover Grant Orgs like MGD / MetaCartel?]
web2/3Shared treasury, coordination and transparency with a premium on the transparency / results

### Goal
Be the first place that non-profit orgs and grant DAOs think of for managing their grant programs.

### Selling Points
* Permissioned DAO with open applications mean Org has more power over who makes a final choice on grants, but is open enough to recieve applications from anyone
* Treasury management is easy with Safe integrations (i.e. don't need to worry about voter rage quitting grant funds)
* Support multiple networks, so your grant DAO can exist where it's cheap or where your protocol lives

### Processes
- summoning a DAO
- determining intial members and share distribution
- customizing the TOS
- define grant application process
- DAO ops (haus keeping)
- sourcing new applications
- treasury management
- joining and participating in UberHAUS
- managing multiple work streams

### Why DAOhaus?
- why do they need to use DAOhaus above all other options?
- why is a permissioned DAO better for them?
- why do they need flexible governance structures?
- why do they need a treasury with ragequit?

### TODOs
* Use Metacartel processes and constitution as a good template for ToS and grant process
* Take some PeepsDAO learnings re: non-profits initial resistance to MolochDAO structure (mostly RQ)
* Consider more protocol / large project grant DAOs and why / why not DAOhaus (often it has to do with level of customization desired)

## Investment groups
Shared treasury, coordination and transparency with a premium on treasury tracking and compliance.

### Goal
DAOhaus as the premier place for investment DAOs.

### Selling Points