How a team experiments matters as much as what
In this episode of Datadrivet, Joni Lindgren and Jasmin Yaya look at why the pace of experimentation stalls. They draw on a workshop Jasmin ran for a cross-functional team. The team had scaled from zero to five experiments a month and wanted to reach ten.
The hosts argue that the ceiling came from how the team worked together rather than from what they tested.
The team had to agree on what counts as an experiment before they could move faster.
Several questions had no shared answer: what team members expected of each other, who was responsible for what, and how they communicated internally. Without those answers the team got stuck in discussion and frustration instead of getting experiments out the door.
The workshop named the frustration and the obstacles first. Then it proposed new ways of working and a clearer split of the work.
If your team wants help setting up how it runs experiments, the hosts invite you to reach out to scilla.studio or contact them on LinkedIn.
Listen to the full episode of Datadrivet for the discussion of the workshop and what changed.
See where your numbers actually land
Plot your retention, CAC payback, LTV:CAC and K-factor against the B2B and Consumer bands, and find out whether a good-looking number is real or sitting on a leaky retention curve.
Run the growth diagnostic →