Progressive Decentralization for DAOs
Start centralized like a startup, then hand control to the community as the protocol matures
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 65%
Progressive decentralization is a mental model Packy uses to explain how crypto projects and DAOs should structure governance over time. Rather than launching fully decentralized (which he sees as often chaotic and slow to make big decisions), a project starts with a small, centralized team empowered to make fast decisions like a traditional startup. As the protocol proves itself, control and ownership are progressively transferred to users, token holders, or the community. This works especially well for infrastructure/protocol-style products where end users can meaningfully participate in governance, versus consumer apps where centralized product decisions may still matter more. The model tries to capture the benefits of decentralization while avoiding the coordination failure of running everything by committee from day one.
Origin
Extracted from Acquired
Core principles
- 01Full decentralization from day one often leads to coordination chaos and slow decision-making.
- 02Centralized control is valuable early because someone needs to make fast, high-stakes calls.
- 03Decentralization should be seeded gradually as the system matures and stabilizes.
- 04This model fits protocols/infrastructure better than highly consumer-facing products.
How to run it
- 1
Launch With Centralized Control
Start the project with a small team (or founder) who can make quick, high-stakes decisions the way a startup founder would.
- 2
Prove the Product/Protocol
Build initial traction and prove the core mechanics work before introducing complex governance.
- 3
Introduce Partial Governance Mechanisms
Add tools like token voting for specific, lower-stakes decisions to start distributing input.
- 4
Progressively Transfer More Control
As the system matures, hand over more meaningful decision rights — treasury, protocol upgrades, etc. — to the community.
Watch out Giving up too much control too early can create the same coordination chaos as launching fully decentralized.
- 5
Reach Full Decentralization
Eventually the community/token holders should be able to fully govern without needing the founding team's centralized authority.
In the wild
Packy joined ConstitutionDAO, which rallied a 20,000-person Discord and raised almost $50 million in about a week to try to buy a copy of the U.S. Constitution, organized as a fully decentralized effort from the start.
→ It proved a DAO could rally huge capital and enthusiasm fast, but also showed how hard it is to make major decisions and coordinate a huge, newly-formed community without any centralized structure in a short timeframe.
Common mistakes
Decentralizing everything immediately
DAOs without a clear final decision-maker often struggle, especially under time pressure, because everyone has been told they have a voice.
Never decentralizing at all
Staying fully centralized forever forfeits the emergent, faster, more responsive behavior that well-run DAOs can achieve.
Is it for you?
Best for
Protocol or infrastructure-layer crypto projects planning long-term community governance
Not ideal for
Time-sensitive, one-off community efforts (e.g., ConstitutionDAO-style sprints) or highly consumer-facing apps needing fast centralized product decisions
From the transcript
“then you go into the idea of like progressive decentralization which i think makes a lot of sense which is start out kind of like…”
“i think eight out of ten dows might totally fail because they they have like kind of that leadership issue or like who is the…”
From the episode
Not Boring (with Packy McCormick)