---
# System prepended metadata

title: Magesmiths 2nd Story Design Sprint - Spencer Diverge

---

# Magesmiths 2nd Story Design Sprint - Spencer Diverge

## Incentivizing "dirty work"
#### Problem
Important "dirty work" like fixing bugs, project management, production support, etc too often gets left underdone

#### 5 whys
1. Because people would rather spend time on other things
2. Because "dirty work" is less rewarding
3. Because its less socially / reputationally recognized
    - Also because building new stuff is typically more fun
5. Because its not as visible to people outside the core dev group
6. Because product value is an indirect result of each piece of "dirty work" compared with a direct result of each new thing built -- sort of a public goods problem


#### Potential mitigations/solutions
- Elevate the output of "dirty work" to be more publicly visible
    - number of bugs fixed this month
    - production support superstars
    - PM attribution in app or code somehow
- Financial rewards
    - more DAI
    - HAUS bonus
- Cultural emphasis
    - "we value this stuff"
- Education bonus
    - get paid to try something new / explore


## Infrastructure vs. Features

- budget / financial
    - carve out consistent budget/team for infra / paying down tech debt
- Cultural / process
    - always ask: "what is the impact of this feature on feature bloat and tech debt?"



## Notes
 - DAO home pages: "why join us"
 - in-app tutorial
 - in-context documentation / education / information
 - regular / periodic UX reviews 
 - is clickup the right place for magesmith tasks?
     - not the most easily accessible for new or prospective contributors
 - define standard task data model
 - DAO summoner coaching
 - customer success
 - p2p summoner knowledge sharing
 - we don't need to pay for everything
 - feature prioritization
     - raw input signal
     - prioritization signal
 - stats and analytics
     - from on-chain activity
     - boost activations
 - prioritize progressive decentralization activities
 - 