GrowthBook

You spent weeks building the feature. Nobody used it. This happens more often than most product teams admit. And the default response is to move on and build something else. Kameron Tanseli at Fyxer does the opposite. His approach: ship the core experience, then immediately start running experiments to drive adoption. Watch daily active usage in Metabase. As it climbs, check whether it's moving revenue. The launch isn't the finish line. It's the starting line for a new set of experiments. This matters because almost no one uses a new feature on day one. The people who do are already highly engaged. The rest of your user base needs a nudge — the right message, the right moment, the right onboarding flow. That's not a product problem. It's an experimentation problem. Fyxer's growth team of 4 ran 360 experiments last year. A huge portion of that work wasn't building new things — it was running tests on features that already existed to find out why people weren't using them. The result: a referral loop where 33% of invites are accepted. A trial-to-paid conversion that went from 5% to 35%. A shift to annual plans that now accounts for 50% of subscribers. None of those came from launching something new. They came from testing what was already there. What feature have you shipped that underperformed — and what did you do about it? 🎙️ Full episode + case study in the first comment 👇 #ProductManagement #GrowthEngineering #ABTesting #Experimentation #PLG

Only one snapshot so far — the engagement-over-time curve appears once the daily scrape has captured this post at least twice.