# Example Experiment

![An experiment in action!](https://3314128292-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ljru8tSYycVPAJyc14_%2F-Ljt98-Ot6MICP5xFMbJ%2F-LjtBCd5EYzwVzsM-6Hb%2FIMG_20180905_135819.jpg?alt=media\&token=bab1a6c3-b263-4ae6-a3be-be404733d2c5)

![](https://3314128292-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ljru8tSYycVPAJyc14_%2F-Ljt98-Ot6MICP5xFMbJ%2F-Ljt9HE3753GR6uSQOyi%2FMonash%20Experiment%20Sheet%20-%20Example.jpg?alt=media\&token=2e94f818-9587-489a-aad7-d58c7f3a3c8c)

This experiment sheet is an example of one which may be written for a research activity - in this case a workshop which focused on building people's capacity in 'backcasting' - a process to go from big picture 'outcomes' back to every day activities.

The left side of the sheet (yellow) is the part of the experiment which is written _before_ the activity, and the right side (blue) is the summary of what happened.

We will go through this process more, [later in the field guide](../the-experimentation-process/experiment-design).

Key in this experimentation culture, is the idea of documenting the research before and after, in order to retain the granular detail of the research for future reference.&#x20;

Traditionally, design research outcomes might get documented in the form of a stakeholder write up, a published article, or maybe some form of graphic summary, but the raw insights may have their edges sanded down a bit (or a lot).&#x20;

When it comes to referring back to research activities, we often have to lean back into our memories or presentations, which rarely have the full, rich data and insights of an experiment sheet.
