> 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/why-st/do-think-do-to-organise-patterns.md). # Do-Think-Do to organise patterns Could the patterns we had observed be the key to solve problems at scale, with speed, sustainably? Could these be abstracted and applied to create exponential change? **Do** – We began co-travelling with a few change leaders who were on the quest to solve complex problems at scale. With [ShikshaLokam](https://shikshalokam.org), we explored “How to enhance education leadership in India’s 1.5 million schools?” and discovered the power of restoring the agency of education leaders with micro-improvements. [Project ECHO](https://echoindia.in), with the big question “How to move the right healthcare knowledge to the right people at the right time?” led us to think deeply about facilitating value exchange between relevant actors. [eGovernments Foundation](https://egov.org.in) urged us to think beyond point solutions to building ecosystems where actors across civil society, government and market can create and share value by asking “How to ensure accessible and transparent public service delivery for all?” We explored many more big questions with change leaders across 15 countries through [ASPIRe](https://aspire.ashoka.org/stories/aspire-story) – a co-creation with Ashoka – towards learning what it takes to design for impact at scale. **Think** – While learning from these journeys, we sought out 150 thought leaders, academicians, change leaders, and funders. Our objective was to understand if the knowledge we had created and curated while co-travelling would be valuable to share. Through this process, we also wanted to surface blind spots and gain fresh perspectives. **Do** – By practising-organising-practising, we continue to evolve Societal Thinking and explore how to induce exponential change. This GitBook is an effort to curate and organise the latest version of what we have learnt thus far and is expected to evolve with further practice. --- # 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/why-st/do-think-do-to-organise-patterns.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.