Roll out an experimentation-friendly culture across product, engineering, data, and leadership teams.
SkillScore86Maintained
Automatic
◆Product Management pack
Last verified 8/16/2026
What it changes
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
Without skill59%
With skill86%
Checks it passed that the model alone missed
Uses the header '## Enablement'
Includes the mandatory section header '## First Rollout Slice'
Categorizes risks into cultural, technical, and data dimensions
and 7 more in the full report
7 fixed12 passed either way2 still failing1 broke
Pass-rate lift
+27 pp
Tokens
-3%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/16/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
I'm leading a product transformation at a SaaS company where leadership is skeptical of A/B testing due to past inconclusive tests and designers fear it limits creative ownership. Could you draft a complete experimentation adoption plan in Markdown? We need an overarching adoption goal, a breakdown of current stakeholder hesitation paired with tailored responses, a specific first rollout candidate team and feature area with rationale, support mechanisms for training and cadence, key adoption metrics with target values, and an overview of key risks.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes the mandatory section header '## First Rollout Slice'
Missed
Passed
Categorizes risks into cultural, technical, and data dimensions
Missed
Passed
Addresses skepticism by presenting experiment results as shared learnings rather than purely success wins
Missed
Passed
case-02 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md82 linessingle file
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.