methodatlas
Session Builder

Plan my session

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

Method session90-180 min initial, then continuousWorkshop or asyncKPI-Baum

Session: KPI Tree

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 3-8. 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 KPI-Baum. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Define top metric

    15 min

    Capture the top metric with numerator, denominator, aggregation period, and source. Document current value. Set target value (for example quarterly or annual target). Hint: If the top metric is unclear, the tree is fragile. The definition must be repeatable in one sentence. Anyone asking "what do we mean by Y" reveals an unclear root.

    FacilitatorKPI-Baum
  2. 2

    Phase 2: First-level drivers

    30-45 min

    Decompose the top metric mathematically or causally into 2-5 sub-metrics (for example Active Users = New Users + Returning Users; Revenue = ARPU * Active Users). Define each node. Hint: Mathematical decomposition is the gold standard. Causal decomposition (for example "Activation drives Retention") needs stronger rationale. A mix is allowed, but mark it clearly per node.

    FacilitatorOwner-Liste
  3. 3

    Phase 3: Second-level levers

    30-45 min

    For each level-1 node, further decompose into levers and sub-metrics. Typically 2-4 child nodes per node. Add owner and current value for each node. Hint: The second level is often the action level with the levers teams can influence. Deeper than 3 levels becomes hard to read; move detail to separate subtree sessions.

    FacilitatorKPI-Baum
  4. 4

    Phase 4: Owners, data, and review cadence

    15-30 min

    Assign owners by name per node, data source (dashboard link), and review cadence (typically weekly for operational metrics, monthly for strategic). Hint: A node without an owner becomes wall art. Each node should have a concrete person accountable for movement. Name one primary owner when multiple owners are involved.

    OwnerOwner-Liste
  5. 5

    Publish artifact

    10 min

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

    OwnerKPI-Baum
Usable artifact

Session Brief

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

session-brief.md

Session Brief: KPI Tree

Goal

Artifact: KPI-Baum

Working Question

How does the top metric decompose into controllable sub-metrics, which one contributes how much, and who is responsible for each lever?

Context

Top metric with definition (numerator, denominator, aggregation period); current value; funnel data; known leverage hypotheses; owner candidates for sub-metrics.

Setup

  • Format: Method session
  • Duration: 90-180 min initial, then continuous
  • Mode: Workshop or async
  • Participants: A facilitator with analytics understanding; a Product Lead or Growth Lead; Data Analyst for metric definitions; 2-4 additional team members; a scribe for owners and data.
  • Owner: A facilitator with analytics understanding
  • 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 KPI-Baum. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with hierarchical structure (root at top, sub-nodes below); top metric with current value; list of data sources; pens; tool for persistent maintenance (Notion, Looker Studio, dbt).

Preparation

Set the top metric at the top of the board as the root. Node template: name, definition, current value, owner, lever. Limit hierarchy depth to 3 levels for visibility.

Agenda

  1. Phase 1: Define top metric (15 min) Owner: Facilitator Action: Capture the top metric with numerator, denominator, aggregation period, and source. Document current value. Set target value (for example quarterly or annual target). Hint: If the top metric is unclear, the tree is fragile. The definition must be repeatable in one sentence. Anyone asking "what do we mean by Y" reveals an unclear root. Output: KPI-Baum

  2. Phase 2: First-level drivers (30-45 min) Owner: Facilitator Action: Decompose the top metric mathematically or causally into 2-5 sub-metrics (for example Active Users = New Users + Returning Users; Revenue = ARPU * Active Users). Define each node. Hint: Mathematical decomposition is the gold standard. Causal decomposition (for example "Activation drives Retention") needs stronger rationale. A mix is allowed, but mark it clearly per node. Output: Owner-Liste

  3. Phase 3: Second-level levers (30-45 min) Owner: Facilitator Action: For each level-1 node, further decompose into levers and sub-metrics. Typically 2-4 child nodes per node. Add owner and current value for each node. Hint: The second level is often the action level with the levers teams can influence. Deeper than 3 levels becomes hard to read; move detail to separate subtree sessions. Output: KPI-Baum

  4. Phase 4: Owners, data, and review cadence (15-30 min) Owner: Owner Action: Assign owners by name per node, data source (dashboard link), and review cadence (typically weekly for operational metrics, monthly for strategic). Hint: A node without an owner becomes wall art. Each node should have a concrete person accountable for movement. Name one primary owner when multiple owners are involved. Output: Owner-Liste

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

Closeout

  • Update result artifact: KPI-Baum
  • 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

KPI-Baum: KPI Tree

Working Question

How does the top metric decompose into controllable sub-metrics, which one contributes how much, and who is responsible for each lever?

Context

Top metric with definition (numerator, denominator, aggregation period); current value; funnel data; known leverage hypotheses; owner candidates for sub-metrics.

Participants

  • Owner: A facilitator with analytics understanding
  • Participants: A facilitator with analytics understanding; a Product Lead or Growth Lead; Data Analyst for metric definitions; 2-4 additional team members; a scribe for owners and data.

Input

Whiteboard or Miro board with hierarchical structure (root at top, sub-nodes below); top metric with current value; list of data sources; pens; tool for persistent maintenance (Notion, Looker Studio, dbt).

Template

KPI Tree Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • KPI tree:
  • Owner list:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • KPI-Baum 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

KPI Tree Working Template

View templateCompact working template for KPI Tree with context, input, output artifacts, and next step.
canvas

kpi-tree-working-template.md

Compact working template for KPI Tree with context, input, output artifacts, and next step.

KPI Tree Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • KPI tree:
  • Owner list:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits KPI-Baum.
  • Re-evaluate tree structure quarterly. Keep current values updated continuously (dashboard integration). Structural changes with date and rationale. Archive previous versions.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet