methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Async work run24 to 72 hasynchronousExperiment results

Session: A/B Testing

The plan distributes preparation, review, and outcome work across an asynchronous work run. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Async work run with 1-6. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Experiment results. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Prepare brief

    15-30 min

    Prepare the working question, input, target artifact, and review deadline for A/B Testing. Link relevant data, sources, and existing artifacts.

    OwnerSession brief
  2. 2

    Work asynchronously

    24 to 72 h

    Participants work through the method along the template. Focus: add contributions directly to the artifact, mark assumptions, and link evidence.

    ParticipantsExperiment results
  3. 3

    Consolidate review

    20-30 min

    Cluster comments, contradictions, and open questions. Sort unclear points into decisions, risks, or follow-ups.

    FacilitatorReview notes
  4. 4

    Finalize artifact

    15-30 min

    Create the integrated version, set status, and schedule the next review or decision point.

    OwnerDecision log
  5. 5

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerExperiment results
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: A/B Testing

Goal

Artifact: Experiment results

Working Question

Does the variant deliver a statistically significant effect on the success metric without degrading the counter-metric?

Context

Baseline conversion and variance; known seasonal effects; minimum detectable effect (MDE) as the target; tracking plan for success and counter-metrics; tests already running to check for interference.

Setup

  • Format: Async work run
  • Duration: 24 to 72 h
  • Mode: asynchronous
  • Participants: An experiment owner (Product or Growth); engineer for implementation; data analyst for evaluation; reviewer for brief approval; stakeholder for go-live decision.
  • Owner: An experiment owner (Product or Growth)
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Experiment results. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Experiment tool with bucketing and statistical analysis; experiment brief template (hypothesis, variants, metrics, sample, duration, stop rule); sample-size calculator.

Preparation

Write the experiment brief and have it approved by the reviewer. Calculate sample size with MDE, alpha (0.05), and power (0.8). Implement the variant behind a feature flag. Run a dry test with an internal group before rollout.

Agenda

  1. Prepare brief (15-30 min) Owner: Owner Action: Prepare the working question, input, target artifact, and review deadline for A/B Testing. Link relevant data, sources, and existing artifacts. Output: Session brief

  2. Work asynchronously (24 to 72 h) Owner: Participants Action: Participants work through the method along the template. Focus: add contributions directly to the artifact, mark assumptions, and link evidence. Output: Experiment results

  3. Consolidate review (20-30 min) Owner: Facilitator Action: Cluster comments, contradictions, and open questions. Sort unclear points into decisions, risks, or follow-ups. Output: Review notes

  4. Finalize artifact (15-30 min) Owner: Owner Action: Create the integrated version, set status, and schedule the next review or decision point. Output: Decision log

  5. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Experiment results

Closeout

  • Update result artifact: Experiment results
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Experiment results: A/B Testing

Working Question

Does the variant deliver a statistically significant effect on the success metric without degrading the counter-metric?

Context

Baseline conversion and variance; known seasonal effects; minimum detectable effect (MDE) as the target; tracking plan for success and counter-metrics; tests already running to check for interference.

Participants

  • Owner: An experiment owner (Product or Growth)
  • Participants: An experiment owner (Product or Growth); engineer for implementation; data analyst for evaluation; reviewer for brief approval; stakeholder for go-live decision.

Input

Experiment tool with bucketing and statistical analysis; experiment brief template (hypothesis, variants, metrics, sample, duration, stop rule); sample-size calculator.

Template

A/B Testing Working Template

Goal

Compares two or more variants using defined success metrics.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Experiment Result:
  • Decision Log:
  • Learning Summary:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Experiment results is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

A/B Testing Working Template

View templateCompact working template for A/B Testing with context, input, output artifacts, and next step.
markdown

ab-testing-working-template.md

Compact working template for A/B Testing with context, input, output artifacts, and next step.

A/B Testing Working Template

Goal

Compares two or more variants using defined success metrics.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Experiment Result:
  • Decision Log:
  • Learning Summary:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Experiment results.
  • Unique ID and folder per experiment with brief, code references, analysis, and decision. Version briefs and document changes during runtime. Keep the archive for completed tests searchable.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet