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 hasynchronousFunnel report

Session: Funnel Analysis

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-5. 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 Funnel report. 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 Funnel Analysis. 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.

    ParticipantsFunnel report
  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.

    OwnerDrop-off analysis
  5. 5

    Publish artifact

    10 min

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

    OwnerFunnel report
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Funnel Analysis

Goal

Artifact: Funnel report

Working Question

At which steps do users lose conversion in each segment, and which hypothesis explains the drop?

Context

Event tracking plan with definitions; time range (for example last 30 or 90 days); segmentation axes (channel, device, plan); known technical drop-offs.

Setup

  • Format: Async work run
  • Duration: 24 to 72 h
  • Mode: asynchronous
  • Participants: A data analyst with tool access; a product owner responsible for the flow; a marketing or UX representative with hypotheses; optional stakeholder for validation.
  • Owner: A data analyst with tool access
  • 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 Funnel report. After the session, the artifact should be shareable, reviewable, or reusable.

Input

BI or product analytics tool with access to event data; table for steps (step, definition, event ID, n, conversion rate, drop); template for segment comparison.

Preparation

Create funnel report in the tool with defined steps in sequence. Set time window and minimum sample size (at least 500 users per step for stable rates). Add baseline comparison period.

Agenda

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

  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: Drop-off analysis

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

Closeout

  • Update result artifact: Funnel report
  • 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

Funnel report: Funnel Analysis

Working Question

At which steps do users lose conversion in each segment, and which hypothesis explains the drop?

Context

Event tracking plan with definitions; time range (for example last 30 or 90 days); segmentation axes (channel, device, plan); known technical drop-offs.

Participants

  • Owner: A data analyst with tool access
  • Participants: A data analyst with tool access; a product owner responsible for the flow; a marketing or UX representative with hypotheses; optional stakeholder for validation.

Input

BI or product analytics tool with access to event data; table for steps (step, definition, event ID, n, conversion rate, drop); template for segment comparison.

Template

Funnel Analysis Working Template

Goal

Analyzes conversions and drop-offs between defined steps.

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

  • Funnel Report:
  • Drop-off Analysis:
  • Optimization Hypotheses:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Funnel report 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

Funnel Analysis Working Template

View templateCompact working template for Funnel Analysis with context, input, output artifacts, and next step.
markdown

funnel-analysis-working-template.md

Compact working template for Funnel Analysis with context, input, output artifacts, and next step.

Funnel Analysis Working Template

Goal

Analyzes conversions and drop-offs between defined steps.

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

  • Funnel Report:
  • Drop-off Analysis:
  • Optimization Hypotheses:

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 Funnel report.
  • Version funnel configuration in the tool (naming convention with date). Archive weekly snapshots as Markdown or PDF. Create a new funnel for tracking changes and archive the old one with reason.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet