<aside>
👐
A riff on diverge and converge. We start by converging Mondays on “why are we building?”, “who for”, and “how to launch it”, we diverge on what we’re curious interested in building to help the DAO.
Biz cases, prototypes, or POCs help us think and prioritize.
</aside>
“Ship first” | Stamp alignment | AimIterate to production ready quality | Smash bugs fast
Tl;Dr
Product exists to set direction, bound scope, and close loops. This process is a reset, not to slow shipping, not to out-spec engineers, and not to absorb downstream failures by default.
A. Decision Rights
| Area |
Owner |
Final Decider |
| What problems we work on |
Whole team |
Product |
| Priority / sequencing |
Eng + Product |
Joint |
| How it’s built |
Engineering |
Engineering |
| Scope completeness (surfaces, edge cases) |
Product + Eng |
Joint |
| Release quality & validation |
All |
Joint |
| Emergency ship decisions |
Eng + Product |
Joint |
B. Required Artifacts
Every feature that ships must have at least 2:
- Problem Brief/Business case (≤ 1 page) ⇒ goes to front of project inside initiative. Product writes most of these (but anyone can create one!) || also acceptable is a POC plus the brief or an MVP app that you vibecode… All comunity members are welcome to communicate ideas with the following info:
- What is problem?
- Who it’s for? Who is this not for?
- Why now?
- Expected impact?
- Qualitative is preferred: e.g. this much revenue via swaps
- what does success look like? What’s the CTA? how track this?
- how many new users do we need to keep this?
- What segment of the market does this fit into?
- How does someone use this?
- Including a Walkthrough loom, or scheduling a synchronous meet (if POC ), with live link to reference if replit or v0 etc.)
- Scope Checklist – Product & Eng & DAO (marketing etc.) ⇒ Project & tickets
- User story
- AC
- Web + Mobile QA notes
- filled out as PR’s hit. gotchas, weird quirks. any constraints
- any deliberate omissions
- code that is gnarly flagged for future cleanup
- GTM
- hpayne’s automarketer goes here
- Decision Log – at release on PR
- Why this shipped
- What was consciously not done (on merge)
- What risk was accepted
- What follow on tickets are necessary
No cumbersome PRDs. No long specs. No Figma’s required unless UI changes materially.
C. MPVs POCs & Contributor-Led Initiatives
- Engineers and contributors are encouraged to build POC or prototypes
- POCs do not ship by default.
- Product must respond within 48 hours with one of:
- ✅ Promote to initiative or schedule tinkering time
- 🟡 Park with reason + revisit date
- ❌ Kill with rationale
If Product misses the 48-hour window → escalation to feature is valid.
