The Growth Process
A framework for growth teams used at Atlassian.
It’s time to get to work creating and shipping the experiment. Unlike when building products things do not need to be perfect, you are just trying to get some signal that the team is headed in the right direction.
You are finally about to implement the experiment and you want to prepare it well - break down work into smaller tasks, and then estimate and prioritize them to plan your work efficiently.
When the experiment is ready for testing, make sure the check the analytics events that will be used later on in the analysis. Run a QA session with your team to uncover possible bugs and fix them.
Make sure a designer does a review of the experience and provides actionable feedback on execution - you can involve them in QA session or directly in your day to day work.
When the experience is ready to be shipped, raise a pull request and merge it to master. Test the experience once again on production and fix any found bugs and repeat QA if necessary.
The experiment experience is ready. Check if your scheduled launch date is still valid and in case it has changed let the stakeholders know. Then it’s time to enroll the audience who is going to interact with it. With audience enrolled you can start the experiment.
Yay. Just make sure to monitor its health - check “error logs” in and verify that analytic events are being received and look reasonable. Update the experiment status so that stakeholders and your team know that it is running.
A running experiment.