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 hasynchronousInterest Metrics

Session: Smoke Test

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 Nutzertraffic. 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 Interest Metrics. 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 Smoke Test. 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.

    ParticipantsInterest Metrics
  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.

    OwnerConversion Signal
  5. 5

    Publish artifact

    10 min

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

    OwnerInterest Metrics
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Smoke Test

Goal

Artifact: Interest Metrics

Working Question

Does the minimally visible offer produce a clear interest signal above the predefined threshold?

Context

Hypothesis as one sentence; target signal (for example at least 3% conversion to email submission with 2,000 clicks); target group and channel; budget for ads or outreach; legal and ethical review.

Setup

  • Format: Async work run
  • Duration: 24 to 72 h
  • Mode: asynchronous
  • Participants: One test owner for setup and evaluation; one marketer for traffic and targeting; one analyst for reporting; optionally one copywriter for messaging.
  • Owner: One test owner for setup and evaluation
  • 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 Interest Metrics. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Minimal visibility test (ad, post, short landing page); tracking setup (click, lead, conversion); disclosure page if promise goes beyond current state; definition of success threshold.

Preparation

Minimal setup: short landing page with value proposition, email field or clearly defined lead signal. Tracking implemented and tested. Disclosure about offer status if not self-explanatory.

Agenda

  1. Prepare brief (15-30 min) Owner: Owner Action: Prepare the working question, input, target artifact, and review deadline for Smoke Test. 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: Interest Metrics

  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: Conversion Signal

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

Closeout

  • Update result artifact: Interest Metrics
  • 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

Interest Metrics: Smoke Test

Working Question

Does the minimally visible offer produce a clear interest signal above the predefined threshold?

Context

Hypothesis as one sentence; target signal (for example at least 3% conversion to email submission with 2,000 clicks); target group and channel; budget for ads or outreach; legal and ethical review.

Participants

  • Owner: One test owner for setup and evaluation
  • Participants: One test owner for setup and evaluation; one marketer for traffic and targeting; one analyst for reporting; optionally one copywriter for messaging.

Input

Minimal visibility test (ad, post, short landing page); tracking setup (click, lead, conversion); disclosure page if promise goes beyond current state; definition of success threshold.

Template

Experiment Plan

Hypothesis

We believe that ...

Target audience

Who are we testing for?

Test design

What exactly will participants or users do?

Success criterion

We count the test as positive if ...

Risks and limits

What can the test not prove?

Decision afterward

If positive: ... If negative: ...

Owner and date

...

Completion Check

  • Interest Metrics 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

Experiment Plan

View templateShort plan for hypothesis, test design, success criteria, and decision.
markdown

experiment-plan-markdown.md

Short plan for hypothesis, test design, success criteria, and decision.

Experiment Plan

Hypothesis

We believe that ...

Target audience

Who are we testing for?

Test design

What exactly will participants or users do?

Success criterion

We count the test as positive if ...

Risks and limits

What can the test not prove?

Decision afterward

If positive: ... If negative: ...

Owner and date

...

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Interest Metrics.
  • One entry per experiment with date and hypothesis. Link follow-up experiments to previous learnings. For messaging comparisons, label A/B variants.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.