Embedded Files
Growth Retainers Explained:
Growth Retainers Explained:
This guide outlines the process for managing A/B tests for Shopify stores using our Asana board. The goal of engaging clients in a growth retainer is to continually create and present value to them. We do this by strategically identifying key performance indicators (KPIs) that we feel we can improve on by making changes to their Shopify stores. We do this by forming a hypothesis (or asking questions) and then implementing, monitoring, analyzing A/B tests - with the goal of continually improving the site and ultimately generating more revenue.
Task Template Information
Task Template Information
Tasks start as normal tasks in the "Ideas" section of this board. Once an idea has been "green-lighted" to be implemented as an A/B test, the PM should apply the "Task Name" [ A/B Test ]" template to the task. This will essentially just add an "A/B Test" image to the task as well as a sample task description. However, these elements signal to the PM that the following task custom fields can be used.
- Purpose
Helps in categorizing and understanding the focus of each test.
- Target Metric
The key performance indicator or metric this task aims to influence. Helps in measuring the success of the test.
- Sample Size
The planned number of users or transactions needed to achieve statistical significance in the test. If applicable, this may just include a link to a customer segment, particular landing page, etc.
- Test Link
A link to the text/experiment within the A/B testing tool.
- Test Launch Date
The date that the test was launched
- Test Completion Date
The date that the test was completed
- Test Duration
Automatically calculated. The planned or actual duration of the test. Helps in ensuring tests run long enough to gather meaningful data.
- Test Summary
How were our questions answered with this test?
- Next Step
After reviewing the results of the test, how should we proceed?
Asana Board Sections
Asana Board Sections
Section 1: Ideas
Section 1: Ideas
Purpose
Purpose
Capture and store potential A/B testing ideas.
This can also be used as a typical "backlog" to potential future dev tasks
Process
Process
Add new A/B testing ideas as tasks in this section.
Provide a brief description and potential impact for each idea. This should include the driving factor (what lead you to this idea) as well what questions do we intend to answer with these potential tests
Section 2: A/B Tests
Section 2: A/B Tests
Purpose
Purpose
Manage and track all active A/B tests.
Process
Process
Move tasks from Ideas to A/B Tests when ready to start testing.
When doing so:
Apply task template "Task Name" [ A/B Test ] to the task
Change the "Task Name" to a descriptive task title
Fill out necessary fields in the task template, including Objective, Hypothesis, Target Metric, etc.
Update the task regularly to reflect test progress.
Custom Field: "Next Steps"
You should expect different actions depending on how this field is set.
"Successful - Implement", an automation rule will move the task to the "Current Sprint" section and the PM should assign a developer to provide an estimate and start with a typical development process.
"Inconclusive - Keep Testing", an automation rule will reset the "test complete date" field, and the task remains here for further testing.
"Inconclusive - Discard", an automation rule will move the task to the "Complete" section, and the PM will not interact with this card again.
"Failed - No Changes Required". There are no automation rules for this. The PM must decide whether the A/B test should be re-implemented with more/different variations or if the task should be moved to the "Complete" section to be "discarded".
Section 3: Current Sprint
Section 3: Current Sprint
Purpose
Purpose
Development work for successful A/B tests.
Process
Process
Tasks with "Next Steps" field set to “Successful - Implement” automatically move here.
Developers estimate, work on, and QA these tasks.
Once development and QA are complete, move the task to "In Review".
Section 4: In Review
Section 4: In Review
Purpose
Purpose
Final review of completed tasks
Developer QA
PM QA
Peer QA
Client Review
Process
Process
Review the work done by developers.
If the task meets all requirements, move it to "Complete".
If further work is needed, move it back to "Current Sprint".
Section 5: Complete
Section 5: Complete
Purpose
Purpose
Archive of all completed tasks.
Process:
Process:
Tasks that have been fully QA'd, Client reviewed/approved, and launched on the Client's store are moved here.
Tasks in this section are considered fully implemented and archived.
General Reminders
General Reminders
Communication: Always keep the task comments updated with the latest information.
Documentation: Link any relevant documents or external resources in the task.
Collaboration: Work closely with team members across different stages for a seamless process.
Feedback: Encourage feedback and suggestions to continuously improve the process.
Page updated
Report abuse