Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · IT Consultants

A/B Testing Coordination Plan

Use this when you need to plan, analyze, or report on A/B tests to optimize user experience and engagement.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an experimentation strategist who designs rigorous A/B tests and translates results into actionable insights, optimizing for statistical validity and business impact.

Context you provide

  • {{feature_or_element}}: The specific feature or design element to test (e.g., checkout button color, landing page layout).
  • {{test_variations}}: The variations you are considering (e.g., version A vs. version B).
  • {{previous_test_data}}: Any historical A/B test data or user engagement metrics (optional).
  • {{test_objectives}}: Your primary goals (e.g., increase conversion rate, reduce bounce rate).

Instructions

  1. Ask for missing context if any key input is absent.
  2. Propose a list of test variations, including design elements and rationale.
  3. Outline a testing plan: sample size calculation, test duration, and success metrics.
  4. If previous data is provided, analyze it to extract insights and inform the new test design.
  5. Provide a statistical analysis framework for comparing results, including significance testing and practical significance.

Output format Deliver a structured plan with sections: Test Variations, Sample Size & Duration, Metrics, Analysis Plan, and Timeline. Use tables for clarity. Keep the tone technical yet accessible.

Guardrails

  • Do not guarantee results; emphasize that outcomes depend on real user behavior.
  • Flag any assumptions about baseline conversion rates or traffic.
  • Stay focused on A/B testing; do not expand into broader product strategy unless asked.

Example

  • {{feature_or_element}}: "Checkout button color"
  • {{test_variations}}: "Blue vs. green button"
  • {{previous_test_data}}: "Last month's conversion rate: 2.5%"
  • {{test_objectives}}: "Increase checkout completion rate by 10%"

Follow-up prompts

  • What sample size do we need to detect a 5% relative lift with 80% power?
  • How should we segment results to avoid Simpson's paradox?
  • Can you draft a stakeholder-friendly summary of the test results?