The Ten Principles for Building a DAO

1. Gael's Law

Effective complex systems often arise from simple and efficient systems. When designing a minimum viable product, one should start with simplicity and gradually evolve into complexity.

2. Pareto Principle

About 80% of significant results come from 20% of core efforts. When planning a DAO, one should identify and focus on the key areas that can bring the greatest impact.

3. Parkinson's Law

Work often expands to fill the available time or budget. Setting reasonable deadlines for the DAO is crucial, providing enough time without being too lenient.

4. Goodhart's Law

When a certain metric becomes a target, it often ceases to be a reliable metric. When designing the incentive mechanism for a DAO, careful selection of evaluation criteria is necessary to avoid creating adverse incentives.

5. Brooks' Law

Adding manpower to a project that is already delayed usually makes it even more delayed. The DAO should maintain a lean team size to avoid overexpansion.

6. Moore's Law

Computing power doubles every two years, while costs are halved. The DAO should fully leverage the opportunities brought by technological advancements and continuously optimize its operations.

7. Metcalfe's Law

The value of the network is proportional to the square of its number of users. The DAO should be committed to expanding the user base to create exponential value growth.

8. Dunbar's number theory

The number of stable social relationships that humans can maintain is limited. Unless necessary, the DAO should keep small teams. If expansion is needed, attention should be paid to the trust patterns between different levels.

9. Unix Philosophy

Emphasize the importance of focusing on a single task, inter-module collaboration, and output reuse. The DAO should adopt a modular design to ensure efficient collaboration among all parts.

10. Conway's Law

The organizational design of a system often reflects its own communication structure. The organizational structure of a DAO should align with the system it develops, paying attention to the overall scalability of the structure.