# Levels of Organising Groups of humans work significantly differently at different scales and the practices we use for organising need to change with them. What works amazingly well for 7 people won't work for 12. There are only so many retreats we can go to a year before we get fatigued. Collaboration has a cost and we need to spend our attention wisely. The same water molecules behave very differently when in different patterns of ice, liquid or steam. So too do groups have different properties as the number of people increase. ## Individual Our pyschology has evolved in an environment which is very different from todays world. Many things are the same and we are nothing if not adaptable but much is fundamentally different. One of the most important levels to consider when designing systems is how people will relate with them at an individual level. At the end of the day the only thing we control is ourselves. ## Pod Small, diverse teams of people in groups from 4 to 9 are the core unit of organising. Pods can be tight where people work with each other every day or loose where people touch base once a month. Pods have clear boundaries with explicit joining and leaving protocols. ## Community Both Individuals and Pods can be part of a Community. Communities are easy to join and hard to stay. The key aspects of healthy communities are interdependence and trust. In a community reputation can be maintained implicitly and the friction of collaboration is low. They provide resilience and natural safety nets. ## Network Networks are the key to unlocking scale. They are built with permissionless protocols that anyone can join as long as they communicate in the right way. A network of networks is just a network and their nature does not fundamentally change as they get bigger. --- # 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://enspiral.gitbook.io/os-draft/en/levels_of_organising.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.