> For the complete documentation index, see [llms.txt](https://docs.holons.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holons.io/daos/managing-your-organization.md).

# Managing your organization

Once your organization is set up, it's key to manage and maintain its structure for effectiveness. Here's how you can do it with the Holons Bot:

1. **Define Purpose:** Make clear what the purpose of the (sub) holon is, so that everyone can be driven by it
2. **Assign Roles**: Clearly define and assign roles within each holon to ensure clarity in tasks and responsibilities.
3. **Communication**: Use the bot to facilitate communication across different holons and levels, preserving transparency.
4. **Adaptation**: Regularly assess and adapt the holarchy as the organization evolves, using insights and feedback obtained through the bot.
5. **Review and Feedback**: Implement periodic reviews of processes and solicit feedback to enhance collaboration and efficiency.
6. **Expand**: As your organization grows, utilize the bot to seamlessly add new members and holons, ensuring consistency in the scaling process.

Implementing these strategies will help maintain a robust and dynamic organizational structure, enabling sustainable growth and responsiveness.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.holons.io/daos/managing-your-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.