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 hasynchronousClick Data

Session: Fake Door 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 Click Data. 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 Fake Door 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.

    ParticipantsClick Data
  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.

    OwnerInterest Signal
  5. 5

    Publish artifact

    10 min

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

    OwnerClick Data
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Fake Door Test

Goal

Artifact: Click Data

Working Question

Does the measured demand at the fake-door entry clearly confirm the demand hypothesis above the predefined success threshold?

Context

Demand hypothesis as one sentence; target signal (for example, at least 5% click-through at 10,000 impressions); legal and ethical review (GDPR, consumer protection); plan for informing people who clicked.

Setup

  • Format: Async work run
  • Duration: 24 to 72 h
  • Mode: asynchronous
  • Participants: A Product Manager who sets the hypothesis and threshold; an engineer for tracking and explanatory page; an analyst for interpretation; a customer support owner for incoming questions.
  • Owner: A Product Manager who sets the hypothesis and threshold
  • 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 Click Data. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Visible entry point (menu item, button, card) in an existing product or marketing surface; tracking setup (analytics event); explanatory page or modal after click; definition of success.

Preparation

Place the entry point in the live product. Click leads to a transparent explanatory page ("This feature is still being developed, we are collecting interest"). Implement and test tracking events.

Agenda

  1. Prepare brief (15-30 min) Owner: Owner Action: Prepare the working question, input, target artifact, and review deadline for Fake Door 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: Click Data

  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: Interest 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: Click Data

Closeout

  • Update result artifact: Click Data
  • 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

Click Data: Fake Door Test

Working Question

Does the measured demand at the fake-door entry clearly confirm the demand hypothesis above the predefined success threshold?

Context

Demand hypothesis as one sentence; target signal (for example, at least 5% click-through at 10,000 impressions); legal and ethical review (GDPR, consumer protection); plan for informing people who clicked.

Participants

  • Owner: A Product Manager who sets the hypothesis and threshold
  • Participants: A Product Manager who sets the hypothesis and threshold; an engineer for tracking and explanatory page; an analyst for interpretation; a customer support owner for incoming questions.

Input

Visible entry point (menu item, button, card) in an existing product or marketing surface; tracking setup (analytics event); explanatory page or modal after click; definition of success.

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

  • Click Data 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 Click Data.
  • One entry per experiment with date and hypothesis. Link prior experiments. Record learning decision as status in header (Build/Pivot/Kill).
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet