| name | dao-failure-pre-mortem |
| description | When a DAO is planning a marketing initiative, screen for the three structural failure modes (Creative Consensus Paradox, Accountability Vacuum, Execution Gap) and route to one of three working models (Enlightened Dictator, Specialist Delegation, Professional Core + Community Amplification). DAO marketing fails by default because consensus produces beige output; success requires concentrated power with community amplification. |
| composition_level | atom |
| extraction-lens | principle |
| source_attribution | Matt Bond (Hivemind Library) |
| license | pending-consent |
| status | candidate |
DAO Failure Pre-Mortem
When to use
- DAO planning a marketing initiative or campaign
- Treasury allocation decision for marketing / comms work
- Repositioning a DAO that has tried community-driven creative and gotten beige output
- Evaluating whether to bring in external creative agencies
When NOT to use
- Centralized companies (use brand-narrative tools)
- DAOs whose mandate explicitly excludes marketing (e.g., pure infrastructure DAOs)
- Tactical execution work within an existing working model
Core thesis
Great marketing requires singular vision. DAOs are built for consensus.
When you need 51% approval for every decision, you get the marketing equivalent of beige.
Average DAO marketing costs 3-5× centralized approaches, takes 5-10× longer, and delivers mediocre results. Without genuine accountability, there's no evolutionary pressure to improve.
The three structural failure modes
Screen the proposed initiative for each:
1. Creative Consensus Paradox
- Symptom: every decision requires 51% approval
- Result: inoffensive, unmemorable output that pleases nobody
- Anchor failure: Uniswap rebrand — watered-down compromise
2. Accountability Vacuum
- Symptom: responsibility so diffused that failures barely register
- Result: no consequences = no improvement pressure
- Anchor failure: ApeCoin DAO allocated millions with negligible measurable results
3. Execution Gap
- Symptom: elaborate planning without operational discipline
- Result: strategies look great in proposals; nothing ships well
If the initiative shows any of these patterns, it will fail predictably. Don't let it through governance until restructured.
Three working models
Route the initiative into one of these:
Model 1: The Enlightened Dictator
- Delegate to a benevolent dictator (individual or small team) with minimal oversight
- Anchor success: Nouns DAO funded creators with autonomy → Super Bowl ad executed by professionals
- Best when: clear creative vision, trusted operator available, community willing to accept individual creative authority
Model 2: Specialist Delegation
- Concentrate power in proven specialists for specific decision domains
- Anchor success: Optimism's Delegates program
- Best when: decision-making can be split into domains with clear specialist matches
Model 3: Professional Core + Community Amplification
- Core team handles strategy + execution; community amplifies and distributes (doesn't create)
- Anchor success: Yearn Finance
- Best when: the DAO accepts a clear creative/marketing core with community as multiplier rather than co-creator
Decision rule
Effective marketing > decentralization ideology.
If the DAO can't accept this trade-off, the initiative will fail. Don't waste treasury on it.
Output format
INITIATIVE: [what's being proposed]
FAILURE MODE SCREEN:
- Creative Consensus Paradox: detected | not detected (evidence)
- Accountability Vacuum: detected | not detected (evidence)
- Execution Gap: detected | not detected (evidence)
IF ANY DETECTED:
- Required restructure: [specific change to remove the failure mode]
RECOMMENDED MODEL: Enlightened Dictator | Specialist Delegation | Professional Core + Amplification
- Why this model fits: [reasoning]
- Specific accountability mechanism: [who owns the outcome]
- Community role: [amplification, not creation]
Failure modes (meta — when this skill itself goes wrong)
- Treating decentralization as the goal rather than effectiveness. The skill tells the user something they may resist. If they're committed to "true decentralization in all aspects," apply judgment before forcing the conversation.
- Skipping the model recommendation. Just diagnosing the problem without proposing a working model leaves the team stuck.
Related skills
community-diagnostics — adjacent diagnostic for non-DAO community structureslaunches-as-micro-economies — Layer 3 (Governance) addresses similar concerns at the launch levelcontrarian-strategy-reframes — Reframe 3 (cultural architecture > technical) applies here
