The Ten Principles for Establishing a DAO

1. Gael's Law

Effective complex systems often originate from simple and effective systems. This principle is especially important for designing minimum viable products, reminding us to start with simplicity and gradually evolve into more complex structures.

2. Pareto Principle

Also known as the 80/20 rule, it reveals that 20% of key efforts often yield 80% of effective results. When designing a minimum viable product, attention should be focused on the core features that can bring the most value.

Parkinson's Law

Work often expands to fill the available time or budget. Setting moderate deadlines is crucial, as it provides sufficient time while avoiding overly lax conditions that can lead to inefficiency.

Four, Goodhart's Law

When a certain metric becomes a target, it often ceases to be a good metric. When building complex systems, such as public goods fundraising or identity verification mechanisms, this principle needs to be considered carefully.

Five, Brooks's Law

Adding more manpower to a software project that has already been delayed may cause further delays. This reminds us to maintain a lean team size rather than blindly expanding personnel.

Six, Moore's Law

The number of transistors on a chip doubles approximately every two years, while the cost is halved. This observation reveals the exponential nature of technological advancement and is a key factor in creating significant value in the technology sector.

Seven, Metcalfe's Law

The value of a network is proportional to the square of its number of users. This principle emphasizes the importance of building systems that can achieve exponential value growth.

Dunbar's Number

The number of stable social relationships that humans can maintain is limited. This reminds us to consider cognitive limits when designing organizational structures, appropriately control team sizes, and adopt suitable trust models when necessary.

9. Unix Philosophy

Emphasize three core concepts in software development: focus, modularity, and collaboration. This philosophy encourages us to build modular software systems that allow various components to work together efficiently.

Ten, Conway's Law

The system structure designed by the organization often reflects its internal communication structure. This suggests that we should draw on software development methods when designing the organization, while also being cautious of the scalability limitations of the overall architecture.