Test two new designs for the first screen after onboarding

… you must A-B test everything. You have your control version, the version of your app currently, and the new version being A-B tested. And after at least two weeks of running the experiment, you then analyze the data and really know what is happening to the users. For example, this is what we call Evelyn, Experiment Velocity Engine List in your numbers. Here we have all of our A-B test tracks. This is a database that comes from user interviews.

it's user interviews that show us the user problem then we do the hypothesis and then we do the experiments these experiments are being tracked in postdoc so here we track everything and we can see how everything is running for example this was an experiment i mentioned earlier about the page you see after the onboarding where you see your workouts you see here we tested two different variants apart from the control and they moved nothing the metrics absolutely nothing and they were completely different designs this tells us hey let's not focus on here again this is an inconclusive test this focus on other areas of the app. For example, this experiment is just one screen at the end of the onboarding, where you commit to like workout.

So you're like signing, hey, I'm going to work out. That's it, one screen. Just look at how the metrics move. It's increased 3% retention, adding one screen. That is why you have to A-B test everything. Yeah, I was going to chime in with a quick thought, which was like, I didn't start building anything until all these AI coding tools came out. And I definitely fall into the trap of like, oh, that would be cool. That'd be cool if it existed …