---
# System prepended metadata

title: 'Haus Party Strategy Experiments: DAO Analytics and Physical Publication'
tags: [UX Research, Haus Party Strategy]

---

---
###### tags: `Haus Party Strategy` `UX Research`
---

# Haus Party Strategy Experiments: DAO Analytics and Physical Publication
April 4, 2022 - TW

## Metrics

- Web3-DAO-native system for tracking more relevant metrics.
    - How do we identify these metrics very explicitly?
    - How is the quality of engagement understood in relation to the quantifiable metrics?
    - How might we experiment/implement a system that tracks engagement while also increasing engagement (in a way that maximizes fun for the particpants and researchers)?

### Behaviors

What behaviors do we want to encourage with Haus Party?

- Returning to the next Haus Party
- Engaging on Discord
- Writing a post with key takeaways or alternative ideas
- Sharing on social channels

How might we incentize these behaviors?

## DAO Analytics Schema

- POAPs are distributed during HPL.
- The POAP recipient addresses are co-summoned into a DAO.
    - Can the DAO code integrate Dune analytics or other Web3-native analytics to track participation?
    - The DAO is not a wargame! What kinds of engagement do we want to track?
        - Return visit to Haus Party: tracking POAPs in individual wallets?
        - Interacting with the DH DAO UI through specific proposals, votes, etc. For example, the DAO exercises governance/influence over the topics of next week's HPL.
        - The HPL DAO serves as a PoW platform for participants to spin off their own sub-DAOs?
- We will track the [vesica piscis](https://en.wikipedia.org/wiki/Vesica_piscis) between the DAO (and the tools of the DH UI) and the other social platforms like Twitch, Discord, Twitter, Medium, etc.
    - Discord's metrics show we are very close to having the server status upgraded to increase new discoveries. Goal?
    - Twitch status can be upgraded to further discovery on that platform.
- How might we incentivize participation on all of these platforms?
    - Specialized access to content?
    - Members-only privileges to the DH Discord server? Twitch server?
    - Governance over topics or seasonal directions?
    - Special non-fungible HPL token that is redeemable for "prizes?" NFTs or special POAPs? Physical editions?
    - Let's get creative.

[DAOhaus Dune Analytics](https://dune.xyz/daohaus/DAOHaus-Analytics)
[DAOhaus Discord Metrics](https://discord.com/developers/servers/709210493549674598/analytics/engagement?interval=2&start=2022-02-07&end=2022-04-04)
[Overview of Twitch Analytics](https://www.twitch.tv/creatorcamp/en/level-up/channel-analytics/)

## HPL as a Web3-DAO-Native Publishing Platform

- Streamlining the notes > blogposts (with Otter.ai transcription) to increase the quality of the blog output.
    - Articles become desirable content in themselves, rather than a mere document of a live event.
    - Creates an onboarding funnel to HPL, but also (more importantly) to the DH community/product.
- Let's think bigger than Web2 publication platforms (like Medium, Substack, etc).
    - What does Mirror really offer us? Lacks analytics. NFT minting feels like Patreon - not very useful for our purposes.
- Building off of the AMM (analog meme machine) idea, towards the creation of a physical book.
    - Excellent north start to raise the high water mark for everyone.
    - A chance to honor Adrienne's amazing art and the larger team effort into a more permanent form.
    - Could begin this season, or we can use the final 3 episodes to learn/prepare to implement this strategy for the next season.
    - An opportunity for DAO-to-DAO collabs?
        - Mirror team: wen physical Mirror minting? Invite them to dogfood the process with us.
        - MetaFactory on the ASAP physical edition. Let them rep us while we raise the bar for the whole ecosystem.
    - How might we further decentralize the process?
        - Low lift: at blog editing phase, shift individual voices to collective "we" tense so the content represents the autonomous/anonymous voices of the community. 
        - For example, using the Poster contract/boost/integration to ratify finished docs before publication. Is this even desirable?
            - Pros: dogfood our own culture into the product
            - Cons: slower, increased coordination cost, less control over QA of the end product
- **Primary emphasis: how will we track this positive impact?** Will increasing the quality of the HPL output positively affect the community? Probably yes, but how? Let's keep this central question in mind in relation to all of the above.
