The Acquisition, Expansion, Conversion and Retention groups took part in a Fast Boot in September 2019. The planning issue contains the proposal for Fast Boot, and this page documents our discussions and outcomes.
Fulfillment owns underlying billing, licensing, and transactional system, as well as current portal user experience.
Growth PM’s will own issues for key flows; engineering leaders will help assign work
Long Term: the vision is for the fulfillment team to own the billing and licensing platform, with a set of API’s and SLA’s, so the growth teams can build and curate user experiences on top of them to drive great customer experiences (and resulting KPI’s).
Teardown/journey map existing flow. Leverage demos, videos, screenshots. Ask “experts” to join remotely to demo and share their pain points/opportunities. Session to be led by the product manager.
Discussion led by Jensen, PM for Acquisition, topics covered include:
Discussion led by Sam Awezec, PM for Conversion, topics covered include:
Discussion led by Tim Hey, PM for Expansion. Topics covered:
Discussion led by Mike Karampalas, PM for Retention. Topics covered:
Discussion led by Eli Kastelein, Growth Data Analyst. Topics covered:
During this time we walked through Telemetry as a team and reviewed where we were headed. The main item we covered was the Vision Page in the handbook and how we need to clearly communicate what telemetry is and where to find more information.
Topics covered (which will also be added to the handbook)
Key outcome is to work with the Release team to improve our existing Feature Flags capability in GitLab in order to successfully A/B test Growth experiments.
Right now in order to run an experiment, we need to do additional work to ensure we can measure the results. This work will be bespoke for each experiment while we improve our capability.
We can investigate third party solutions if needed.
At this time the individual Growth teams split into their groups to create and work on issues in their respective areas.