> For the complete documentation index, see [llms.txt](https://wiki.societalthinking.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.societalthinking.org/how-to-apply/how-to-use.md). # How to use It is preferred and recommended that the sprints be executed as per the numbered sequence. However, they can be reordered if required and appropriate, as long as the outputs of all prior sprints / any other inputs are complete, reviewed and shared before entering the session. Each sprint (S0-S8) can be facilitated / practised using five key assets (numbered A1-A5): * **A1: Primer** – helps prepare for the sprint with background information, builds familiarity with why the sprint is important and the key ideas it presents * **A2: Agenda** – defines the overall objectives of the activities in the sprint, gives insight into how long the sprint is and how the total time will be used * **A3: Facilitation material** – typically in the form of slides and videos, this material helps the facilitator navigate the core ideas to be covered in the sprint * **A4: Facilitation guide** – includes additional background, notes, aids, templates and tools that help facilitators customise and prepare for conducting the sprint * **A5: Design document** – a structure to curate outputs, mindset shifts and AHA! moments from each sprint, which will be used to develop a *Blueprint for Exponential Change* The sprint journey is iterative – it is likely that a subsequent phase may require a review / redesign of the outputs of a prior one. Hence, systematic archiving of all outputs is critical. Typically, this journey spans three to four months and may vary depending on the context. --- # 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://wiki.societalthinking.org/how-to-apply/how-to-use.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.