Design an ad test that answers one decision, without launching it

An ad experiment plan with an allocation proposal and stopping rules for qualified review, with no launch.

Choose one of three approaches. The steps for that option appear below.

Choose an option above. On a phone, swipe the tabs left or right to see all options →

Claude: proposes the hypothesis table and the plan

Claude proposes the hypothesis table, drafts the experiment plan and cross-checks it. You check both gates and decide.

  1. You

    Assemble the materials

  2. Claude

    Build hypothesis table

  3. You

    Check the table

  4. Claude

    Draft and cross-check

  5. You

    Check and decide

  1. Have ready: ad concepts, baseline data, objective

    Use: You

    Assemble the approved ad concepts, baseline aggregate data, supplied traffic constraints and decision objective, retaining authorised source IDs and dates.

    Check

    Check each item is the approved version, dated and permitted; list anything missing as still to confirm.

  2. Build the hypothesis table

    Use: Claude

    Ask Claude for a hypothesis table: the main measure, what could skew the result and the comparisons that can be run, with source references.

    Details

    What to paste into the tool

    Task: Hypothesis table specifying the main measure, what could skew the result and the comparisons that can be run; source references; uncertain or absent facts; Supplied inputs: Approved ad concepts, baseline aggregate data, supplied traffic constraints and decision objective. Use only the supplied packet. Build a labeled table with source IDs, dates, uncertainty and permitted-use limits on each row. Check the intended message contrast, the main measure, traffic limits, what could skew the result and whether the plan is feasible against approved concepts and baseline aggregate data. Retain the source packet as an unchanged attachment in the output bundle. Keep unresolved facts and approval dependencies explicit. Do not resolve a missing fact by inventing one. Produce a draft only; do not publish, send, deploy, change accounts, spend or launch a campaign

  3. Check the table against the sources

    Use: You

    Compare every table row with the source materials and correct it; resolve or retain missing facts before drafting.

    Check

    Check the message contrast, main measure, traffic limits, skew factors and feasibility against the approved concepts and baseline data.

  4. Draft the plan and cross-check it

    Use: Claude

    Ask Claude to draft the experiment plan with the allocation proposal and stopping rules, then cross-check it against the checked table and correct it.

    Details

    What to paste into the tool

    Task: Draft ad experiment plan with allocation proposal, stopping rules for qualified review and no launch; Open questions and approval dependencies retained beside the recommendations; Reviewer-checked hypothesis table specifying the main measure, what could skew the result and the comparisons that can be run; source references; uncertain or absent facts; Supplied constraints, retained open questions and approval dependencies with source IDs and dates; Supplied inputs: Approved ad concepts, baseline aggregate data, supplied traffic constraints and decision objective. Propose one prospective message contrast and primary decision, the main measure, what could skew the result, allocation and stopping assumptions for qualified analyst review; do not launch. Retain the checked table, constraints and source packet unchanged in the output bundle. Keep unresolved facts and approval dependencies explicit. Do not resolve a missing fact by inventing one. Produce a draft only; do not publish, send, deploy, change accounts, spend or launch a campaign. Second message, after your check: Task: Corrected draft with a change list and unresolved mismatches flagged for the reviewer. Compare the draft with the checked hypothesis table and the retained source packet. Correct every mismatch you find in the draft, keep source IDs, dates, uncertainty and named exceptions, and list each change. Flag anything you cannot settle from the supplied material; do not invent facts, figures, policies or claims. Return preparation material only; publishing, outreach, audience changes, tracking deployment and financial commitments are outside this task.

  5. Check the corrected draft and decide

    Use: You

    Compare the corrected draft and change list with the checked table, confirm the assumptions, then decide; launching stays outside this workflow.

    Check

    Check isolation and statistical assumptions get analyst approval. If a check fails, correct the draft or leave the workflow incomplete.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

The named reviewer compares working records and final drafts against retained source evidence; unresolved questions stay visible.

These are proposed preparation workflows; execution, publication, sending, deployment, account changes and spending are outside scope.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • Quoted vendor mechanics do not establish the scenario-specific operations; each AI requirement remains not yet checked
  • The responsible reviewer must complete the source comparisons and the original check before treating a draft as ready for a decision

Share this page