GROW

Experimentation

Learn the customer, business, technology, AI, controls, and KPIs for experimentation.

Learning model: business goal → customer journey → systems/data → failure modes → AI opportunity → human control → KPIs.

Agent patterns

Experimentation Copilot

Copilot for Experimentation, using approved data and bounded actions.

Blueprint

Experimentation Monitor

Monitor for Experimentation, using approved data and bounded actions.

Blueprint

Experimentation Recovery Agent

Recovery Agent for Experimentation, using approved data and bounded actions.

Blueprint

Experimentation Analyst Agent

Analyst Agent for Experimentation, using approved data and bounded actions.

Blueprint

Experimentation QA & Control Agent

QA & Control Agent for Experimentation, using approved data and bounded actions.

Blueprint

36 prompts

/human

Experimentation — /human

/human Explain Experimentation to a fresher using a human story, then a D2C example, workflow, risks, and KPIs.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/visualize

Experimentation — /visualize

/visualize Visualize Experimentation as an end-to-end D2C flow with customer actions, systems, decisions, exceptions, and outcomes.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/diagram

Experimentation — /diagram

/diagram Create an architecture diagram for Experimentation, showing storefront, services, APIs, data, events, and human approvals.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/flowchart

Experimentation — /flowchart

/flowchart Create a decision flowchart for Experimentation, including normal path, exception path, retry, escalation, and safe stop.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/mindmap

Experimentation — /mindmap

/mindmap Create a mind map for Experimentation: customer, business, data, technology, AI, risks, KPIs, and owners.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/analysis

Experimentation — /analysis

/analysis Analyse Experimentation performance for a fictional D2C electronics business. Segment results, find root causes, quantify impact, and recommend actions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/RCA

Experimentation — /RCA

/RCA Create an RCA for a failure in Experimentation: timeline, symptoms, hypotheses, evidence, root cause, containment, corrective action, prevention, and owner.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/BRD

Experimentation — /BRD

/BRD Write a detailed BRD for improving Experimentation: problem, users, scope, process, rules, integrations, errors, analytics, acceptance criteria, and exclusions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/PRD

Experimentation — /PRD

/PRD Create a product requirements document for an AI-enabled Experimentation capability with user needs, UX, logic, APIs, controls, metrics, and rollout.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/userstories

Experimentation — /userstories

/userstories Write user stories and acceptance criteria for Experimentation across customer, operations, support, product, and admin personas.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/testcases

Experimentation — /testcases

/testcases Generate 50 test cases for Experimentation: happy, negative, boundary, integration, performance, security, accessibility, and business-rule cases.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/UAT

Experimentation — /UAT

/UAT Create a UAT plan for Experimentation with scenarios, preconditions, data, steps, expected result, owner, severity, and sign-off.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/API

Experimentation — /API

/API Design APIs for Experimentation: endpoints, request/response JSON, validation, idempotency, errors, auth, rate limits, and observability.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/JSON

Experimentation — /JSON

/JSON Create realistic JSON payload examples for Experimentation, including success, failure, partial, retry, and exception states.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/SQL

Experimentation — /SQL

/SQL Write SQL analysis questions and example queries for Experimentation: funnel, failures, cohorts, anomalies, SLA, and business impact.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/dashboard

Experimentation — /dashboard

/dashboard Design an executive and operations dashboard for Experimentation with metric formulas, dimensions, thresholds, alerts, owners, and decisions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/KPI

Experimentation — /KPI

/KPI Define a KPI tree for Experimentation: north-star, leading, lagging, customer, commercial, operational, quality, and risk metrics.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/agent

Experimentation — /agent

/agent Design an AI agent for Experimentation: objective, trigger, state, tools, APIs, memory, rules, confidence, approval, audit log, KPIs, and tests.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/multiagent

Experimentation — /multiagent

/multiagent Design a multi-agent workflow for Experimentation, separating planner, specialist agents, deterministic services, and human approval.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/automation

Experimentation — /automation

/automation Map Experimentation and label every step: deterministic automation, AI assist, agent action, human approval, or human only.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/guardrails

Experimentation — /guardrails

/guardrails Create AI guardrails for Experimentation: permissions, PII, policy grounding, confidence, financial thresholds, irreversible actions, audit, and rollback.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/evaluate

Experimentation — /evaluate

/evaluate Create an evaluation framework for AI in Experimentation: accuracy, hallucination, precision/recall, latency, cost, safety, and business impact.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/monitor

Experimentation — /monitor

/monitor Design production monitoring for AI-enabled Experimentation: technical health, model quality, drift, customer harm, business metrics, and alerts.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/incident

Experimentation — /incident

/incident Create an incident playbook for Experimentation: detect, classify, contain, communicate, recover, reconcile, and learn.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/SOP

Experimentation — /SOP

/SOP Write an operations SOP for Experimentation with roles, prerequisites, normal process, exception handling, escalation matrix, and daily controls.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/checklist

Experimentation — /checklist

/checklist Create a launch-readiness checklist for Experimentation: business, UX, content, data, API, QA, security, analytics, support, and rollback.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/roadmap

Experimentation — /roadmap

/roadmap Create a 90-day roadmap to improve Experimentation: baseline, quick wins, experiments, AI opportunities, dependencies, milestones, and KPIs.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/prioritize

Experimentation — /prioritize

/prioritize Prioritise 15 improvement ideas for Experimentation using impact, effort, confidence, customer value, risk, and dependency.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/executive

Experimentation — /executive

/executive Create a one-page executive review for Experimentation: performance, customer impact, revenue impact, top risks, actions, owners, and decisions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/interview

Experimentation — /interview

/interview Create 20 interview questions and model answers about Experimentation for ecommerce, product, and AI manager roles.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/quiz

Experimentation — /quiz

/quiz Create a 15-question quiz on Experimentation: beginner to advanced, with answers and explanations.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/project

Experimentation — /project

/project Create a portfolio project for Experimentation using fictional data: problem, dataset, analysis, AI solution, architecture, prompts, evaluation, and presentation.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/promptEvolution

Experimentation — /promptEvolution

/promptEvolution Improve a weak Experimentation prompt through beginner, structured, expert, and agent-level versions.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/sales

Experimentation — /sales

/sales Create five D2C sales scenarios for Experimentation, including intent, recommendation logic, objection, guardrail, and conversion KPI.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/cs

Experimentation — /cs

/cs Create five customer-service scenarios for Experimentation, including customer message, system checks, grounded response, escalation, and KPI.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.

/ops

Experimentation — /ops

/ops Create five operations scenarios for Experimentation, with exception, evidence, decision, owner, SLA, and preventive control.

Expected: Structured answer with assumptions, data, workflow, controls, KPIs, and actions.