> For the complete documentation index, see [llms.txt](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/doing-a-dho-and-dao/systems-of-a-dao-and-dho-basic-design-series/seasons-basic-coordination-structures.md). # Seasons: Basic coordination structures > "It's impossible to just be ***partially*** in this ecosystem, there's so much going on it's all consuming." -Many DAO Members * Seasons help us remember that what we're building here is neither a race, nor a marathon. * We're not here to keep up with "bull markets" and "bear markets" and try to "outrun the competition". Those are all features of the economic systems we're leaving behind. There's nothing but burnout, anxiety, and depression down that path. * Instead, we create a sustainable organizational rhythm that nourishes our whole selves year after year all while we still coordinate to achieve systemic change. ## Quick Season Overview > "Nature does not hurry, yet everything is accomplished" - Lao Tzu * Seasons is a protocol for groups to consciously shift where to focus energy throughout the year. To more effectively and joyfully give space to the wide diversity of threads that each group is holding. * [Groups may choose to closely align with the opinionated "Seasons" model of SEEDS to cohere with a wider rhythm of organizations within the Regenerative Renaissance. ](https://explore.joinseeds.earth/1.-seeds-foundations-start-here/seasons-organizational-rhythm/) ### Developer Seasons The Seasons model rhymes with popular development methodologies, such as Agile.\ ![](/files/zBkuMKon6e1jEXQTgEEz) ### Seasonal (\~3 months) flow: * **Week 1 - Onboarding**\ Onboarding new members into the Organization and Season * **Weeks 2 - 12 - Doing the work** * **Week 13 - Review and reflect**\ Prepare a quick overview of Seasonal successes and learnings to share with the organisation and present goals for next season. ### 3x3x3 - 3 goals for 3 months for each Circle (3+ people) * A proposal by a circle for seasonal funding doesn't need to be more than 100-200 words (less than what we're seeing already) and shouldn't require more than 0.5-2 hours max to articulate. * Do not make governance and meta coordination a heavy burden, a few hours each season to signal what we've done in relationship to what we said we'd do - and what we intend to do going forward. * Keep it simple bullet-point format which would greatly help with efficiency both with those writing and those reading. ![https://www.mckinsey.com/business-functions/people-and-organizational-performance/our-insights/intentional-learning-in-practice-a-3x3x3-approach](/files/BdxiAI8JPAINOFcS4LXL) {% embed url="" %} ### Seasonal Themes As we continue to test this model we can share emergent themes below to help focus our seasonal efforts. ### Governance Seasons Focus governance into 2 weeks once every 3 months during the transition point between seasons - then don't look at governance until next season (unless there is an urgent need to do so). ### Examples of Seasonal Coordination Patterns Nambikwara Ethnohistories {% embed url="" %} Culture example {% endembed %} {% embed url="" %} DAO example {% endembed %} {% embed url="" %} DAO example {% endembed %} --- # 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://explore.joinseeds.earth/4.-organisation-tools-daos-and-dhos/doing-a-dho-and-dao/systems-of-a-dao-and-dho-basic-design-series/seasons-basic-coordination-structures.md?ask=&goal= ``` `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.