Six steps to build effective experiments from Growth University
Epic Web3 Weekly Newsletter
Hey, growth folks 👋
Each week we send you an email with helpful insights on product and career growth. We also share key takeaways from our videos with community experts.
👀 New case study
Craig Zingerline, Founder & CEO at LAUNCH Growth University, has gone through hundreds of experiments, both successful and unsuccessful ones. He experienced that there was no standardized playbook to build an effective experiment so he decided to make his own.
Here are six steps to follow:
Build a testable hypothesis. By [doing] or [not doing] some [action] we believe that [a metric] can be impacted. Switch things in brackets for your experiment.
Determine your control. A control is what you’re measuring against — it can be some amount of historical data or even something from scratch.
Write down the variants. A variant is an entity that you’re changing, adding, or removing, and then measuring against your control. It’s also important to include all the context your internal teams may need to be aware of.
Determine how you will measure the results and learn what changes impact which metrics.
Track the results. Discover the outcomes from each iteration of the experiment and then track detailed notes and metrics on a daily or weekly basis.
“Kill, scale, or hold steady.” Decide whether you should run another iteration, reject this hypothesis, or try something else.
🧑💻 Community insights on public roadmaps. Or should we share our product plans with customers.
1/ Bandan Jot Singh, Product Lead at Booking.com, believes that companies shouldn’t keep their roadmap secret. Indeed, by making it public, they can constantly receive customers’ new ideas for free and build a trusting relationship with them.
2/ Zac Prutzman, Head of Growth at WellTheory & Author of the Happy Users newsletter, describes what a public roadmap entails. He states that it allows you not only to save time spent on prioritization but also reduce churn because users see that you’re listening to their needs.
3/ Rory Woodbridge, Head of Product Marketing at Pleo, also prefers a public roadmap over a private one. He believes that this way your existing users feel heard, the number of newcomers grows, and the community starts engaging with your brand.
4/ However, there’s always the other side of the coin. Robin Labrot, Product Manager at lempire, drops a thought that because of immense pressure and requests coming from users, going public will make you less agile.
Thanks for reading, hope you enjoyed this week’s dose 👋
See ya,
The Epic Web3 team