experimentation-culture-rollout
Roll out an experimentation-friendly culture across product, engineering, data, and leadership teams. Use when introducing A/B testing to an organization, overcoming resistance to experiments, shifting teams away from launch-by-opinion, increasing experiment demand, defining rollout tactics, or creating an experimentation adoption plan.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- experimentation-culture-rollout
- license
- MIT
- metadata
- { "tags": "practical-ab-testing,ab-testing,experimentation,product-culture,change-management", "version": "0.1.0", "category": "Product Management", "displayName": "Experimentation Culture Rollout" }
- description
- Roll out an experimentation-friendly culture across product, engineering, data, and leadership teams. Use when introducing A/B testing to an organization, overcoming resistance to experiments, shifting teams away from launch-by-opinion, increasing experiment demand, defining rollout tactics, or creating an experimentation adoption plan.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 5
- 参考文档guidelines.md1.3 KB
- 参考文档references/core/examples.md1.3 KB
- 参考文档references/core/knowledge.md1.9 KB
- 参考文档references/core/rules.md1.5 KB
- 参考文档workflows/roll-out-experimentation.md1.9 KB
03 SKILL.md 正文
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.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.