# Introduction **Why are we building a DAO?**\ \ In most crypto projects, decision-making power is concentrated in the hands of a small number of investors and team members. This can create a risk that decisions will be skewed toward them and fail to represent the collective will of everyone who has a stake in the project, such as the project community, creators, and normal investors. Furthermore, as leaders tend to have different interests and priorities, it can become difficult for them to reach an agreement on important issues. Due to these reasons many projects in the cryptocurrency space fail. Decentralized Autonomous Organizations (DAOs), intend to solve this power concentration issues by giving every member of the community and the project a voice in how it operates and what goes on inside it. In other words, helping projects foster a culture of collaboration by dispersing power among those who make decisions so they don’t feel their voice is being ignored or suppressed by any one leader or a group of investors. **What is Mizu DAO?** Mizu is a DAO organization focused on Web 3 projects that will use the power of community and collaboration to grow the space. Mizu will focus on incubating and promoting projects to join its ecosystem, serving as a bridge between projects and a sustainable autonomous organization. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mizudao.gitbook.io/mizudao-whitepaper/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.