> 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/the-sprints/sprint-1-arriving-at-a-big-question.md).

# Sprint 1: Arriving at a big question

To probe and unpack the social problem, arrive at a big question, and identify friction to orchestrating change at scale, with speed, sustainably.

As we embark on our journey, we will first pause and reflect. Design for exponential change begins in earnest when we anchor it to a big question – the social problem that we desire to tackle, the momentum we wish to create with the ecosystem (domino effect), towards the impact we wish to see at scale. However, on this journey to answer a big question, the ecosystem encounters friction of multiple types. This is where we identify them and name them.

**Pre-requisite:** An updated overview including responses to open questions or further research

**Pre-requisite:** An updated version of the design document (SDA5) based on sprint 0 outputs

**Downloadable assets** that are useful for preparing for / facilitating this sprint:

* [S1A1](https://drive.google.com/file/d/18Bu3_dItpt_aQpaTrXpGTDJoZzIsvEND/view?usp=drive_link): A primer on the big question and categories of friction
* [S1A2](https://drive.google.com/file/d/1zrhMY9GChRY7wJb_aUsw-frh1fiSsnfE/view?usp=drive_link): Objectives and agenda for the time we will spend together
* S1A3: A slide deck to help learn and practise the key concepts
* S1A4: A guide to enable those who want to facilitate this sprint
* [SDA5](https://drive.google.com/file/d/10y8qmaoIwF_dkMgaZmURZHNQmHczUzV8/view?usp=drive_link): The design document where all sprint outputs are curated

Please email <design@societalthinking.org> to request a copy of A3 and A4 assets.

**Post-work:** The big question and the list of key friction that impede progress towards it

**Post-work:** An updated version of the design document (SDA5) based on sprint 1 outputs

\ <br>


---

# 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/the-sprints/sprint-1-arriving-at-a-big-question.md?ask=<question>&goal=<user_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.