> For the complete documentation index, see [llms.txt](https://inclusivity.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inclusivity.toolkit.citiobs.eu/insight-gathering.md). # INSIGHT GATHERING ## Why is it relevant? Dialogue opens the door; insight gathering helps you understand what you find on the other side. Once conversations have begun, the next step is to develop a deeper, more contextualised understanding of who may be left behind in the specific setting of your initiative — and why. This requires moving beyond general awareness of JEDI and LNOB concepts, and turning those lenses onto your own context: your neighbourhood, your stakeholder network, your city, and the communities within it. The barriers to participation are rarely uniform. They are shaped by the physical environment people inhabit, the histories and inequities embedded in particular places, and the complex web of relationships — formal and informal — that determine who has a voice and who does not. Understanding these factors demands methods that go beyond desk research: methods that invite you to observe, walk, listen, and map alongside the people whose lives and experiences are most relevant to your initiative. The tools in this section offer structured ways to do exactly that — from gaining empathy through shadowing and guided tours of people's everyday environments, to mapping the geographical distribution of environmental burdens and the communities who bear them, to making visible the roles, responsibilities, and power dynamics within your existing stakeholder network. Together, they help citizen science practitioners and citizen observatory teams move from abstract commitment to grounded understanding — a necessary foundation for the planning, outreach, and co-creation work that follows. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://inclusivity.toolkit.citiobs.eu/insight-gathering.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.