You have a testing tool, you have analytics....
but do you have an "experimentation management and analysis platform"?
Here's my POV on how to set one up:
(btw, no, it's not just 'Airtable' nor is it your testing tool + BigQuery)
Step 1. Benchmark the program maturity and capabilities across teams.
- mainly needs to have A to Z questions, to identify gaps and critical drivers. (e.g., where are you now vs where you want to be...). This is the heart of usefulness of Speero's Program Maturity Benchmark Audit.
- capabilities are the key here. Esp ones that speed the flywheel of feedback and insight generation. (e.g., Leadership Buy-In, Evangelism, Collaboration, Personalization, Targeting, Strategy, Test Complexity, Tool Investment, Tracking and KPIs, Research Knowledge base, Hypothesis Generation, Prioritization Framework, Roadmapping, Quality Assurance, Pre-Test Analysis, Communication, etc., etc, etc)
Step 2. Plan against a north star for the program
- yes have your goal tree map, and Goal vs Driver vs Guardrail metrics (input/output/outcome metrics too)
- but also have a 'remit' for your org on what the experimentation program means to you and the team. Purpose & Motivation, Mission & Tenants, Mechanisms to invest in (tied to the capabilities audit above).
Step 3. Document language (the heart of standardization)
- Nouns and verbs, types and categories... a data dictionary or semantic library for your org.
- The MVP is two columns of data, no joke. And it's what's lacking at 90% of orgs and is the 80/20 of good uses of AI btw.
- This is the connective tissue across the teams and touchpoints and such that the testing program touches. It's what creates the leverage points for automations and AI to grab hold of.
- This is also what Chad Sanderson won't stop talking about, for good reason. You can't align people if you don't have a shared language.
Step 4. Standardize artifacts and rituals
- If the data language documentation are the notes, the rituals and artifacts (tools) you use are the music that you play.
- This is the 'drumbeat' of your org. How your team finds a rhythm.
- Speero blueprints are ALL about this step 4.
- Not all these tools and cultural practices will make it into the 'platform', but you *shouldn't* build that platform without having this figured out.
Step 4. Standardize platform architecture
- how the data flows
- who sees what, when, and how
- what happens, when, and why
- tables, Interfaces, and Actions
- This step is the actual building of the bespoke 'platform' that is your testing program.
Step 5. Test&Learn, with Experimentation Consultants to advise
- Like an annual medical check, vitals being velocity and impact, and ultimately your organization's ability to adapt.
- this is where you bring in me, Speero to check your work
- this is where you bring in consultants like Lukas Vermeer, Craig Sullivan, Iqbal Ali, Simon Jackson, Liam Furman, Roderik Koenders to check your work
- do it ;)
CEO @ Speero | Experimentation for SaaS, Ecommerce, Lead Gen
1yhere's a preview of the slide deck.... not passing this one out quite yet, it has some work still to do