thedixitjain Experimentation Culture Rollout
Use this skill to help teams adopt A/B testing as a normal product and engineering practice. The focus is organizational change: resistance, stakeholder trust, rollout sequencing, education, demand generation, and operating cadence.
Source Traceability
Primary source: Practical A/B Testing by Leemay Nassery. Guidance is transformed and paraphrased from chapter 6 lines 4507-5066, with motivation from the preface lines 270-280 and chapter 1 lines 1019-1078.
Related Advanced Skills
experimentation-strategy-roadmap: use when culture rollout must connect to platform roadmap priorities, company strategy, and rate-quality-cost tradeoffs.experiment-verification-monitoring: use when trust problems come from invalid experiments, weak QA, missing health checks, or poor monitoring.trustworthy-experiment-insights: use when stakeholders need help understanding whether evidence is credible enough to influence decisions.
Reference Routing
| Need | Read |
|---|---|
| Culture and adoption concepts | references/core/knowledge.md |
| Rollout and resistance rules | references/core/rules.md |
| Adoption scenarios | references/core/examples.md |
| Step-by-step rollout plan | workflows/roll-out-experimentation.md |
Workflow
- Identify what resistance is actually about: trust, speed, metrics, ownership, platform friction, or fear of failed experiments.
- Pick a credible first team or product surface.
- Run early tests that answer real stakeholder questions.
- Share results as learning, not just wins.
- Create lightweight templates, office hours, and examples.
- Expand demand through internal proof and repeatable support.
Output Format
# Experimentation Culture Rollout Plan
## Adoption Goal
[What behavior should change.]
## Current Resistance
| Concern | Who Holds It | Response |
|---------|--------------|----------|
## First Rollout Slice
- Team:
- Product surface:
- First experiment:
- Why this slice:
## Enablement
- Templates:
- Training:
- Office hours:
- Decision cadence:
## Adoption Metrics
| Metric | Target |
|--------|--------|
## Risks
- Cultural:
- Technical:
- Data:
Quality Bar
- Do not treat resistance as ignorance; identify the legitimate concern.
- Do not sell experimentation only as a way to win; emphasize learning and risk reduction.
- Do not roll out a process that is heavier than the team's trust in it.
- Use real internal examples as soon as they exist.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/experimentation-culture-rollout/SKILL.md