Experimentation Platform Orchestrator
A senior product and engineering leader's playbook for making the experimentation platform decision and recovering from making it wrong.
Picking an experimentation platform is one of those decisions that looks easy at the start and compounds for years afterward. The wrong choice costs you in lost experiments (because the team avoids the painful workflow), in cost (because the wrong pricing model penalizes your usage shape), in vendor lock-in (because migration is real engineering work, not a config change), and in cultural drift (because the platform's defaults shape what your team thinks experimentation is).
This skill is the discipline that makes the decision well the first time and the migration plan when you didn't.
When to use this skill: choosing a platform from scratch, evaluating whether to switch, deciding whether to consolidate from multi-platform to single, or planning a migration that has already been approved.
What this skill is for
This skill spans platform selection, multi-platform decisions, migration planning, and governance setup. It does not cover experiment design (use experiment-design), result interpretation (use experimentation-analytics), or feature flag operations (use feature-flagging). Pair this skill with the relevant integrations microsite when you need platform-specific MCP details.
The audience is a PM, engineering leader, or data lead who is making the decision or recovering from a previous one. The voice is decisive. There is no "it depends, evaluate them all yourself." The decision space has real shape, and a senior advisor can map your situation to a defensible answer in an afternoon.
Reference files
references/platform-decision-matrix.md - Context-to-platform matrix with worked examples for the most common decision contexts.
references/migration-playbook.md - Step-by-step migration patterns for the five common migrations including effort estimates and validation approaches.
references/mcp-capability-comparison.md - Side-by-side MCP capability matrix across the seven platforms.
references/multi-platform-orchestration.md - Ownership boundaries, shared metric definitions, and reconciliation dashboards for genuine multi-platform setups.
references/cost-and-pricing-models.md - Pricing shapes, real-world cost ranges at different traffic tiers, and finance conversation patterns.
references/governance-and-team-setup.md - Permission tiers, audit trail requirements, environment promotion rules, and team fit assessment.
references/common-mistakes.md - Twelve failure patterns with symptom, root cause, fix, and prevention for each.
Conditional methods
Before applying a method below, read its linked section. For a narrow task select only relevant methods; for a full audit/design use the framework and relevant failure patterns. Existing references remain available for deeper details.
- The 7 considerations for the platform decision: method.
- Statsig: method.
- PostHog: method.
- GrowthBook: method.
- Optimizely: method.
- Amplitude: method.
- Eppo: method.
- Kameleoon: method.
- Decision matrix: which platform for which context: method.
- Multi-platform: when warranted, when a mess: method.
- Migration patterns: method.
- The cost reality: method.
- Governance and team fit: method.
- The MCP capability layer: method.
- When to defer the decision: method.
- Common mistakes: method.
- The framework: 11 considerations for sustainable platform choice: method.
- Closing: when in doubt, pick boring: method.
1---2name: "experimentation-platform-orchestrator"3description: "A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting."4metadata:5 source: https://skillmd.com/skills/slipcast-dev/experimentation-platform-orchestrator6---78# Experimentation Platform Orchestrator910A senior product and engineering leader's playbook for making the experimentation platform decision and recovering from making it wrong.1112Picking an experimentation platform is one of those decisions that looks easy at the start and compounds for years afterward. The wrong choice costs you in lost experiments (because the team avoids the painful workflow), in cost (because the wrong pricing model penalizes your usage shape), in vendor lock-in (because migration is real engineering work, not a config change), and in cultural drift (because the platform's defaults shape what your team thinks experimentation is).1314This skill is the discipline that makes the decision well the first time and the migration plan when you didn't.1516When to use this skill: choosing a platform from scratch, evaluating whether to switch, deciding whether to consolidate from multi-platform to single, or planning a migration that has already been approved.1718---1920## What this skill is for2122This skill spans platform selection, multi-platform decisions, migration planning, and governance setup. It does not cover experiment design (use `experiment-design`), result interpretation (use `experimentation-analytics`), or feature flag operations (use `feature-flagging`). Pair this skill with the relevant integrations microsite when you need platform-specific MCP details.2324The audience is a PM, engineering leader, or data lead who is making the decision or recovering from a previous one. The voice is decisive. There is no "it depends, evaluate them all yourself." The decision space has real shape, and a senior advisor can map your situation to a defensible answer in an afternoon.2526---2728## Reference files2930- [`references/platform-decision-matrix.md`](references/platform-decision-matrix.md) - Context-to-platform matrix with worked examples for the most common decision contexts.31- [`references/migration-playbook.md`](references/migration-playbook.md) - Step-by-step migration patterns for the five common migrations including effort estimates and validation approaches.32- [`references/mcp-capability-comparison.md`](references/mcp-capability-comparison.md) - Side-by-side MCP capability matrix across the seven platforms.33- [`references/multi-platform-orchestration.md`](references/multi-platform-orchestration.md) - Ownership boundaries, shared metric definitions, and reconciliation dashboards for genuine multi-platform setups.34- [`references/cost-and-pricing-models.md`](references/cost-and-pricing-models.md) - Pricing shapes, real-world cost ranges at different traffic tiers, and finance conversation patterns.35- [`references/governance-and-team-setup.md`](references/governance-and-team-setup.md) - Permission tiers, audit trail requirements, environment promotion rules, and team fit assessment.36- [`references/common-mistakes.md`](references/common-mistakes.md) - Twelve failure patterns with symptom, root cause, fix, and prevention for each.3738---394041## Conditional methods4243Before applying a method below, read its linked section. For a narrow task select only relevant methods; for a full audit/design use the framework and relevant failure patterns. Existing references remain available for deeper details.4445- The 7 considerations for the platform decision: [method](references/domain-guide.md#the-7-considerations-for-the-platform-decision).46- Statsig: [method](references/domain-guide.md#statsig).47- PostHog: [method](references/domain-guide.md#posthog).48- GrowthBook: [method](references/domain-guide.md#growthbook).49- Optimizely: [method](references/domain-guide.md#optimizely).50- Amplitude: [method](references/domain-guide.md#amplitude).51- Eppo: [method](references/domain-guide.md#eppo).52- Kameleoon: [method](references/domain-guide.md#kameleoon).53- Decision matrix: which platform for which context: [method](references/domain-guide.md#decision-matrix-which-platform-for-which-context).54- Multi-platform: when warranted, when a mess: [method](references/domain-guide.md#multi-platform-when-warranted-when-a-mess).55- Migration patterns: [method](references/domain-guide.md#migration-patterns).56- The cost reality: [method](references/domain-guide.md#the-cost-reality).57- Governance and team fit: [method](references/domain-guide.md#governance-and-team-fit).58- The MCP capability layer: [method](references/domain-guide.md#the-mcp-capability-layer).59- When to defer the decision: [method](references/domain-guide.md#when-to-defer-the-decision).60- Common mistakes: [method](references/domain-guide.md#common-mistakes).61- The framework: 11 considerations for sustainable platform choice: [method](references/domain-guide.md#the-framework-11-considerations-for-sustainable-platform-choice).62- Closing: when in doubt, pick boring: [method](references/domain-guide.md#closing-when-in-doubt-pick-boring).