> For the complete documentation index, see [llms.txt](https://handbook.proanimal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.proanimal.org/for-organizers/model-agendas-and-activities/fast-team-formation.md). # Fast Team Formation Borrowed from the "6 Team Conditions" framework. [Source.](https://6teamconditions.com/blog/fast-team-formation-5-steps-10-minutes) ## Purpose This agenda is useful when assembling a group of people *who do not already constitute a formal team* to accomplish a task together. It can take as little as 10 minutes, or as long as 90 minutes, depending on how much time you have and the scope of the task you're trying to accomplish. ## Principles A few rules for the meeting before you jump in: 1. **Privacy:** Hold the briefing in a place where others cannot overhear it. 2. **Presence:** Begin only when all participants are present. 3. **Faces:** Members are identifiable to each other, and making eye contact. 4. **Fast:** Each step (below) takes no more than 20% of the total time allotted for the meeting. 5. **Facilitator:** One person is responsible for facilitating and keeping time. ## Steps If one person is mainly responsible for convening the group, it may be appropriate for them to drive the conversation and prescribe some answers, especially if time is very short. Otherwise, each person should speak in rounds. ### 1. Primary Purpose What is our primary objective? Does anyone have questions or elaborations? ### 2. People and Resources Each person gives his or her name (no need for pedigrees), and briefly describes any special training or experience that could help the team achieve its purposes. ### 3. Team Roles & Norms What is each person’s role on the team? What must we be sure to always do as we work together? What should we be careful never to do? ### 4. Special Circumstance Are there any special complexities or constraints we need to attend to? How will we deal with them? ### 5. Uncertainties and Concerns What remaining questions or concerns should we address before we begin? *Important:* Each team member is asked in turn for any questions/concerns. --- # 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://handbook.proanimal.org/for-organizers/model-agendas-and-activities/fast-team-formation.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.