> 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/communication-strategies-how-do-we-make-sense-of-the-world/the-stand-up.md).

# The Stand Up

{% hint style="info" %}
**Ideal for**\
Great for small teams maintaining sync on projects. 
{% endhint %}

## Structure

A periodic (daily, weekly, etc) meeting where all team members on a project join to discuss and coordinate tasks.

Teams are encouraged to build the agenda asynchronously (when big agenda items arise) before the meeting and to **only bring agenda items that benefit ALL members in the group to discuss.**

### Examples include:

* a daily/weekly standup,
* etc.

### Suggested When:

Teams are creating regularly together.

### Known Pitfalls:

Teams holding the meeting when there is no need (if everyone is already focused and effective).

Teams forgetting to create an agenda async before and discussing topics that aren't important.

#### Authored by Rieki Cordon, Hypha DHO


---

# 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/communication-strategies-how-do-we-make-sense-of-the-world/the-stand-up.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.