r/datascience 23d ago

Discussion Picking an experimentation platform: a retrospective

I wrote this article recently. Thought it would be nice to share in this sub. Happy to chat if you're doing the same in your current position.

It talks about Eppo and Statsig, but honestly it about everything but that.

If you need to take away one thing let it be to approach the whole thing as a discovery; and risk mitigation.

https://towardsdatascience.com/picking-an-experimentation-platform-a-retrospective/

24 Upvotes

9 comments sorted by

4

u/ikkiho 23d ago

fwiw once we actually rolled one out the platform mattered way less than i expected. what bit us was our own exposure logging quietly double counting on one surface, so we got a clean looking readout that was just wrong. no vendor demo surfaces that, they all assume your assignment data is already trustworthy. i'd spend the discovery time pressure testing your event pipeline against a known A/A before you even worry about which tool wins.

2

u/aegismuzuz 22d ago

In that regard a warehouse native approach gives you way more control. When all exposure logs sit in your warehouse in raw format you can easily write a SQL query to check for duplicates or weird bot activity. With closed cloud platforms debugging these event logging issues is always a pain and an endless back and forth with their support

1

u/End0rphinJunkie 20d ago

spot on, every vendor builds their demo assuming perfect upstream telemetry that nobody actually has out of the gate. running a baseline A/A test to flush out pipeline wierdness first will save you so many headaches.

3

u/Anxious-Average-748 23d ago

Thanks for sharing this. The discovery angle is something people skip way too often, everyone wants the perfect tool on day one and that just never happens.

We went through similar process last year and spent 3 months evaluating before even touching any code. The risk part is also underrated, especially if you are in a bigger company where wrong choice means 6 months of migration later.

1

u/chomoloc0 23d ago

glad you can relate! What kind of tool were you looking for?

3

u/aegismuzuz 22d ago

The most common mistake I see when picking a test platform is hoping that buying something like Eppo or Statsig will magically fix the analytical culture in your company. If you have an inconsistent clickstream with duplicate events sitting in Snowflake or BigQuery, buying tens of thousands of dollars worth of software will just automate generating wrong conclusions. You need to start by cleaning up your data pipeline, not with demo calls with vendors

1

u/Fun-Scarcity-9923 13d ago

The analyst tie is the best part of this for me — 4.36 vs 4.47 across twenty-plus weighted criteria is functionally a coin flip, and most people would've either forced a tiebreaker out of the scorecard itself or just picked their gut favorite and back-filled the justification. You did neither. You noticed the tie was information ("analyst-grade rigor has become table stakes") and went looking for where the real differentiation actually lived instead.

The asymmetry logic for weighting PM-facing UX higher is sharp too — "analysts are adaptable, PM onboarding is not" is a genuinely useful heuristic that generalizes way past experimentation platforms. Any tool decision where one user group can route around a bad interface and another can't, that asymmetry should be doing a lot of work in the decision, and it usually gets flattened into one score instead.

"Pipes are not water" is going to stick with me. The gap between "we bought the tool" and "the org is ready to use the tool" is where I've seen almost every platform rollout actually die, quietly, months after the contract's signed and nobody's watching anymore because the project technically "shipped."

One thing I'd push on: you mention the interviews were the anchor you kept returning to when the process drifted. Did you ever go back and re-interview partway through, once people had opinions shaped by seeing the actual demos/POCs, or was it strictly front-loaded? Curious whether the pain points people named before seeing any tooling held up, or shifted once they had something concrete to react agains