Align your Team Efforts 

with a Growth Meeting

Why and how to hold your meetings in Experiments

Start a Free Trial

THE COMPANIES THAT MAKE THEIR LIFE SIMPLE WITH

Create Your Idea Backlog with Experiments

© Copyright 2020
Start a Free Trial

How will Experiments help you?

Experiments has a built-in Growth Meeting Feature. When you start a growth meeting in Experiments, you will be able to zoom out and update your metrics and KPIs, as well and have a pit stop for updating the team about the experiments that are in progress as well as recent learnings. You will then move into planning your next sprint with easy visualization of the ideas the team has nominated for the meeting. All ideas will be pitched and the ones selected for the sprint can be moved to up "in progress". You can also set integrations that can make collecting results much more simple.

Frequently Asked Questions

How often should a Growth Meeting take place?

The meetings will define the next sprint of your team, therefore it should happen before every sprint starts. The most common is that teams will have weekly growth meeting, but there are teams that so it every two weeks, or every month.

Who should be in the growth meeting?

Everyone in the growth team, plus anyone who has an idea nominated who wants to pitch it to the growth team.

What is Experiments?

Experiments is a software designed for Growth Teams to plan, execute, and measure the tests they run to impact certain company KPIs they believe are at the core of driving their company's growth at any given time. It was developed by GrowthHackers and Sean Ellis, who coined the term Growth Hacking in 2010. With Experiments, everyone in your team can suggest ideas to be tested that are directly linked to the objectives set by the growth team. Teams can move across projects and share results of their findings, all in one place, allowing for more ideas to be tested and validated in a high-velocity ongoing process.

Who is Experiments for?

Experiments was designed for companies of any size that have reached product-market fit and want to grow their business. It can be useful for businesses in nearly every vertical. The + 3000 teams that use Experiments range from mobile apps, fintechs, SaaS, e-commerce, to energy, construction, manufacturing, consulting, and many others.

For how long can I try Experiments for free?

Once you sign up for a trial, you have 2 weeks to use the platform, in full.



What our costumers have to say about Experiments

“It’s fairly simple: If you don’t test, you can’t learn. And that means learning about your organization and its systems and processes, your users, your products, and the abundance of explosive opportunities that might be right there in front of you if you only took the time to collect and analyze the right data, ideate, hypothesize, and execute."

Jason Barbato, Vice President of Growth

Nancy Hensley, Chief Digital Officer

“First it [Experiments] will help consolidate all the experimentation in one place and it gives all the cross-functional teams a great way to contribute to the ideas. Now that everyone truly values experimentation all the way up to the Senior Leadership team, we needed to get more organized. I also think this will help to make everyone feel more empowered to participate and collaborate on growth."

The One Meeting That Matters

A well-structured growth meeting is a fundamental step for having a well-oiled growth process. It is the moment where the growth team gets together to discuss the status and results of their experiments and objectives, and to pitch and discuss the ideas that have been nominated for the Growth Meeting. As a result, the team will have a clear idea of what are the tasks involed for the next sprint, and can decide together how to get organized and who to involve to bring experiments to live. Here are the 4 steps for an effective Growth Meeting:

Add current measurments of your objectives

One common pitfall of growth teams is to focus on micro-level growth and forget about macro-level growth. To avoid that hyper-focus on what matters less, we recommend companies to start by adding the current measurement of their objectives. This allows the team to zoom out of their experiments and look at how are the results of the tests from your previous sprints actually impacting the team objective and, consequently, the company growth (NorthStar Metric)

The Importance of The Growth Meeting To Your Growth Process

The growth meeting is a pivotal step in the Growth Process. It is the moment the teams get together to speak up, propose their ideas, and come together with solutions for the execution of new ideas. Sharing learnings is also an important step for improving the process. This is why it's important it becomes a ritual in a growth-driven company, with a set day that everyone knows of.

Analyse the Results of Your Tests

This is the time to allocate resources, build the team or squad responsible for running everything, setting up assignees and deadlines, and checking whether you need some “external” resources, such as the help of the engineering team, etc. This is also the moment to draw an expected hypothesis, meaning, what are the results you expect from this test? We usually recommend that you measure as precisely as possible. Otherwise, the data gathered might lead you somewhere inconclusive.

Build Up Your Experiments

Pitch the Nominated Ideas or Hypotesys

step 1

step 4

step 3

step 2

Prior to the growth meeting, each participant should go to the backlog and nominate the ideas that they believe are worth testing. Ideally, the whole company should be engaged in idea suggestions. This gives your employees a feeling of belonging, a feeling that they are heard, and that incentivizes them to speak up and share their thoughts. The team then decides which ideas will move up to the nexrt sprint, and wich ones will stay in the ideas backlog

That’s the time to zoom in and analyze the results of the tests that happened during the past sprints. Every test should have an owner, and you should only analyze its results once you have gathered enough data. Start with the quantitative part (a) adding the numbers, (b) any screenshot or proof-of-concept that proves your point, then move up to the qualitative part interpreting the results and writing down the lessons you’ve learned, and last but not least, (d) sharing your wins and deciding about scaling that up or not.

What else can you do with Experiments?

Define Objectives and KPIsCreate an Idea BacklogPrioritize and Nominate IdeasHave Growth MeetingsExecute Experiments
Share Progress and ReportsBuild a Knowledge BaseKeep Your Data SafeIntegrate to Automate