When you are developing a growth strategy, it is very important to have a backlog in place in order to track all the experiments that you will carry out. This backlog should be shared with your whole team so that everyone can be up to date about the experiments underway, and can suggest new ideas.
That's why we have decided to build our Azendoo Backlog using Azendoo...because what could be better for this than a teamwork tool?!!
In order to do so, I have created a subject called “Backlog Growth” on the “Our Azendoo” workspace.
I have invited those members of the team who are likely to want to participate in the experiments.
Using the Activity feed, we are able to exchange our ideas, the new tools we have found, and so on.
In the Tasks section, I have creation 4 separators:
- Experiments Suggestions
- Experiments in Progress
- Experiments Analysis
- Experiments Systemizing
1 - Ideas For each new idea for an experiment, an un-assigned task is created under the separator called “Experiment Suggestions”.
2 - Testing As soon is the timing is right to launch a given test, I attribute the task to someone and I move it under the “Experiments in Progress” separator.
At this stage, I supplement the task with a task description; I add the test document (here is an example of one such document); and I set the task to repeat, depending on the number of days across which I need to run this particular experiment.
I also set a due date on which I will run the analysis.
3- Analyse So once the experiment is finished, I then move the task under the separator called “Experiments Analysis”, and I start to analyse the findings from my test, with the help of our analytics tools: Kiss Metrics, Google Analytics, App Annie, Intercom, etc.
4 - Iterate If the results are good, I can move the task into “Experiments Systemizing”, in order to automate it. Otherwise, I make the necessary adjustments to the test and I move the task back under “Experiments in Progress” in order to run it again, this time with the modifications.
5- History Once the experiment is finished, I can mark the task as done and it goes into the “Completed” category, where I keep it as a trace of everything that has been carried out so far.
Thanks to this process, the whole of the Azendoo team is able to follow the progress of the experiments, and can suggest new experiments to be run.
On the other hand, if I need some help on the design or dev side of things, I just have to invite the right person to the task, and ask him or her to lend me a hand.
Tracking experiments is thus clear and transparent, which allows me to optimize the process from day to day.