Yesterday's comic was, of course, in reference to Twyman's Law.
Applicable not only to experiment analysis, but also life. If it looks too good to be true, then it probably is π
| GrowthBook Homepage | https://growthbook.io |
Yesterday's comic was, of course, in reference to Twyman's Law.
Applicable not only to experiment analysis, but also life. If it looks too good to be true, then it probably is π
Your PM: "What happened with that experiment?"
You: Opens 17 tabs, 3 spreadsheets, and a Slack thread
Sound familiar? We fixed that.
Introducing Experiment Dashboards in GrowthBook 4.1:
β
Create custom views for each experiment
β
Highlight the metrics that actually matter
β
Add context that explains the "why" behind the numbers
β
Share a single link instead of a dissertation
The best part? You control exactly what stakeholders see. Because great experiments deserve great storytelling.
It's a hard truthβbut we're not all SQL geniuses.
Get a little (or lot of help) with your next query by using our new natural language to SQL generation feature. Ask, for example, to list the top 10 pages by view count in the past 3 months and get back a crisp SELECT statement.
See Graham demo it in the vid.
New tutorial: Run A/B tests without deploying code π
Connect #Sanity + GrowthBook + #Next.js so content editors can test directly from Sanity Studio.
No more eng bottlenecks for headline tests.
Guide β https://docs.growthbook.io/guide/sanity
What integration should we build next?
The velocity of change is changing.
π Ford Model T β 1 million sold: 13 years
π Google β 1 million searches/day: 1 year
π± iPhone β 1 million units: 74 days
π¬ ChatGPT β 1 billion searches/day: <1 year
This isn't just accelerationβit's a fundamental shift in how quickly markets transform. In the AI era, you don't have a decade to figure it out. You might not even have a year.
The takeaway? Place big bets fast. But use experiments as your hedgeβfail small to win big.
Cut feature flag latency to practically zero when you integrate GrowthBook with @Vercel Edge Config.
Here's why it's a game changer for technical teams:
β Built for devs: Works seamlessly with @vercel/flags SDK and Vercel Toolbar
β Advanced statistics: Bayesian, Frequentist, CUPED, Sequential testing built-in
β Precise targeting: User attributes, location, device type, custom rules
β Full visibility: Real-time feature flag analytics and debugging tools
Like an erstwhile PSA: "Do you know where your feature flags are?" As part of our 4.0 launch, we shipped feature flag usage analytics, which means that for every feature flag, you now know:
ποΈ How often it's been evaluated
π Which values are being served
π Which rules are being hit
π And more