# Conclusion

The process outlined in the above chapter is a cumulation of the capacity building initiative which explored a core process delivered in a number of different ways.

The core process was about:

* Attending to relationship
* Recognising ‘what is’ (or what could be)
* Exposing causality and assumptions
* Designing Experiments
* Reviewing Experiments

Whilst this was run as a finite initiative, the process itself is meant to be ongoing and cyclical, somewhat like this:

![](https://lh4.googleusercontent.com/vNyuyPaut5yvKDQ0dLM5LMis4cDEFWk1FK6I68lCgWuNQ87cjy7BDNCfS6F9yP-HP5bU5jV198ZcdeXMkILY6vgP0vdOQR6eRzu_O8M8fR5wJtl9NDjmwKGxb4kTmt_6Wqotb0pi)

Experimentation is a practice made up of both a mindset/culture and practical process and methods.

Whilst people have experienced this process, they are unlikely to embed it deeply into their practice without associated peer support, adoption of language and practice into cultural norms, and related infrastructure (such as a [research repo](https://docs.google.com/document/d/1v_L5c3bT3t_qlQZf0R3McS8bWNULs5sM3LXZlttF3Rs/edit#heading=h.35lz0nrmpim5)).

However, from my experience working alongside various members of the Research Labs faculties, I found significant interest and enthusiasm for the general culture and mindset of experimentation. I believe further aligning the process with a strategic priority - such as documenting and reporting on non-traditional research outputs’ engagement and impact, would have a positive response and uptake.

Thank you for the opportunity to collaborate on the capacity building initiative, and to complete this field guide.<br>


---

# Agent Instructions: 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:

```
GET https://mada.gitbook.io/experimentation-field-guide/conclusion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.