> 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/what-is-st/what-is-societal-thinking.md). # What is Societal Thinking? In order to structure Societal Thinking as a systemic approach, we learnt more about established methodologies such as Design Thinking and Systems Thinking. Design Thinking offers a pathway to solve deeply contextual problems with empathy, affordance and iterations. Systems Thinking emphasises interconnectedness, feedback loops and emergence to navigate complex systems. Societal Thinking draws from emerging developments over the last few decades in how networks, ecosystems and technology can accelerate sustainable change at scale. It is grounded in fundamental ideas such as agency, abundance, diversity, and networks. It focuses simultaneously on enhancing the ability of people closest to problems to solve and that of the system to shift, setting in motion a generative cycle of change. Societal Thinking is a systemic approach to reimagine and realise exponential change. To apply Societal Thinking, we need to appreciate its four core components – the Societal Model and the mindset shifts, Core Values and design principles essential to design with the same. --- # 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 dynamically 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/what-is-st/what-is-societal-thinking.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 `build a script that syncs our docs to a CMS` 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.