> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/leadership/meetings/all-hands.md). # All-hands All-hands meetings, also known as town hall meetings, are regular gatherings that bring together all employees of an organisation. These meetings are designed to foster transparency, communication, and alignment within the company. During an all-hands meeting, leaders share important updates on the company's performance, goals, and strategic direction. This includes discussing recent achievements, challenges faced, and future plans. It's also an opportunity to celebrate milestones and recognise individual or team contributions. Beyond information sharing, all-hands meetings encourage open dialogue and feedback. Employees are given a platform to ask questions, voice concerns, and provide suggestions. This two-way communication helps build trust and a sense of ownership among employees. These meetings can boost employee morale and foster a stronger company culture by reinforcing the company's values and mission. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.designreference.xyz/leadership/meetings/all-hands.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.