Owning the platform is not the outcome.
The value shows up when a customer can make a better decision because the data, the experience, the team and the technology finally agree.
Sometimes that’s a test result. Sometimes it’s a governance rule. Sometimes it’s deciding not to run the campaign you planned.
- Tools
- Data
- Team
- Process
- ProveCan we trust what this test just told us?
- RepeatCan the team run that same process again on its own?
- ConnectDo experimentation, personalization, customer data and content learn from each other?
- CompoundDoes each result make the next decision better, for more teams?
Compound feeds the next round of proof, and the loop runs again
What value means
Success is a better decision system, not a list of lifts.
A lift is one kind of value. Most of what makes an Optimizely program worth renewing shows up in the other five.
Customer value
Someone finds, understands or buys the thing more easily. The partner-click result below is this kind.
Program value
Tests get picked, run and read the same way every time, so results can be trusted and repeated.
Team value
The team makes the call on its own, and new people get productive without a consultant.
Data value
Signals get cleaner and more connected, so the next decision has better evidence.
Platform value
More of what the customer already pays for gets used on purpose, not by accident. The customer value architect idea is how I’d look for it.
AI and automation value
Repeatable steps get done by agents, with people keeping the decisions that matter.
Four stages
Prove, repeat, connect, compound.
This is how I think about where a program is, not a score. Every stage answers a plain question, and skipping one shows up as a program that can’t explain its own wins.
- 1ProveCan we create a result the team actually trusts, not just a dashboard win?
- 2RepeatCan the team run that same process again, on its own, the same way each time?
- 3ConnectDo experimentation, personalization, customer data and content learn from each other, or does each one start from zero?
- 4CompoundDoes each result make the next decision better, and does that hold across more teams, not just the one that started it?
Scale isn’t more tests. It’s more teams, journeys, signals, decisions and reuse, without more chaos.
Prove
Seven experiments in the first quarter. One changed where customers went next.
A B2B brand learning to route people between discovery and buying.
- The context
- A B2B manufacturer was building direct-to-consumer experiences and needed to send visitors between discovery and buying through its partners.
- The result
- In the program’s first quarter the team ran seven experiments. One moved partner clicks from 2.8% to 8.4%, a 204.5% lift at better than 99% confidence.
- My role
- I led the new Optimizely program and presented the quarterly review. The result belongs to the team.
- How to read it
- Only the partner-click result cleared the confidence bar. Other lifts from the same quarter came from small samples, so they aren’t claimed here.
Repeat
Running the process the same way includes running the check that stops a launch.
The growth list was the wrong audience.
- Original assumptionAcquisition: grow membership from this list
- Customer dataCheck the list against membership records first
- The assumption failsNone of the dated profiles were current members
- New decisionWin-back: different message, different success measure
- The problem
- A membership-growth campaign was planned around an audience list, with personalization ready to go.
- What changed
- Before we personalized anything, I checked the growth list against membership data. None of the dated profiles were current members. The campaign became a win-back campaign.
- What it prevented
- A personalized growth campaign aimed at people who weren’t members.
What I did
- Checked the list against membership and customer-data records
- Flagged bounced profiles the customer data platform still counted as reachable
- Flagged consent that was being treated as implied
- Reframed the campaign, its message and its success measure before launch
Connect
I don’t trust an experiment because the dashboard says “winner.”
A result earns trust in steps. I run A/A checks when a program is new, cross-check against an independent analytics tool, and keep guardrail metrics so a win on clicks can’t hide a loss on applications or sales. That cross-checking is what lets experimentation, customer data and measurement work as one system instead of three separate opinions.
- ExposureWho actually saw the change
- Optimizely resultThe testing tool’s answer
- Analytics cross-checkDoes an independent system agree?
- Business outcomeDownstream: applications, accounts, sometimes offline sales
- DecisionShip, iterate or stop, written down
Compound
One team’s decision rules became the whole program’s decision rules.
The fabrics result above and the association call above both fed the same kind of thing: a written rule for how the next decision gets made. A large private university took that habit and pointed it at its entire backlog, not one test at a time.
I reviewed roughly a hundred concluded experiments, some from an older tool and some on Optimizely, and rewrote the decision rules. Enrollment leadership adopted them. That’s how a standard compounds: it outlives the person who wrote it and travels to teams who never saw the original test. The full governance story is told on the Onboarding & Enablement page.
The next step isn’t adding AI to the platform. It’s deciding which work should become agentic.
The next form of scale isn’t more manual work.
Optimizely and related product names are trademarks of their owner. This section reflects my own professional experience with the platform. It is not affiliated with or endorsed by Optimizely, and client examples are described by industry, not by name.