How should I structure my experimentation program test reporting process?

Test reporting is critical to decision making, and also overall program velocity. The faster you can report out, the faster the decision can come. This is Agility as a metric. We think there are two sides to test reporting, the automated, and the bespoke or manual side. 1. BI tools like looker studio and even test tools themselves provide the automated side of things, and 2. the 'story telling' where different metrics are highlighted and the implications and insights are presented is the custom side of things. This blueprint acknowledges the need and balance for these to parts for experimentation test reporting.

Use Cases:

- increase awareness for what goes into a test reporting phase in the experimentation process

- align the team on who does what part, and what part is needs more work

- define your own programs component parts for this process