Could our content team own A/B tests end to end on Storyblok?
I lead a small content team on a Storyblok site and I am trying to figure out whether we could genuinely own experimentation ourselves rather than depending on engineering for every test. Today anything test-shaped becomes an eng project, which means it competes with the product roadmap and usually loses.
What I am really trying to understand is the division of labour in practice. If we adopt the Optimize app, which parts stay with engineering and which parts does my team actually run day to day? I want a realistic picture, not a demo one.
2 answers
The division is cleaner than you would expect. The Optimize app is built for no-code implementation and autonomy from developers, which is the opposite of Storyblok's native experiments where variant picking relies on custom code your engineers write and maintain.
In practice engineering does one thing: the initial block-to-slot wiring. After that your content team builds the audiences, experiences, and experiments directly in the app, publishes, monitors, and rolls out winners. Our content team runs the whole test cycle themselves now, engineering only did the initial wiring. And it works on all Storyblok plans, so you are not blocked on a premium tier to get started. More on that split in marketers launching without devs.
Add to that: it has a built-in Bayesian engine and built-in analytics, so you are not standing up external stats tooling or pushing results into a separate dashboard to read them. That matters for a content team owning the loop, because the read-the-results step lives in the same place. It is one of the gaps in the native path, covered in Storyblok native experiments and the missing stats engine.