methodatlas
Session Builder

Plan my session

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

Method session3-4 h workshop, plus 2 weeks validationWorkshop or asyncNorth Star metric

Session: North Star Metric

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 North Star metric. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Define customer value

    30 min

    Define in one sentence which core value the product delivers, referencing Jobs-to-be-Done or an Aha moment. Quote examples from user interviews. Hint: If the sentence contains features instead of outcomes, rewrite it. Customer Value is what the user achieves, not what the product does.

    FacilitatorNorth Star metric
  2. 2

    Phase 2: Collect candidates

    45 min

    Generate 5-10 metric candidates. For each candidate: definition, formula, data source, update rhythm. Examples: active users per week with minimum action, completed orders per month, messages sent between participants. Hint: Candidates must represent value actions, not just activity. Login count is vanity, completed core workflow is value.

    FacilitatorInput metric tree
  3. 3

    Phase 3: Evaluate against criteria

    45 min

    Score each candidate against five criteria (value, growth correlation, measurability, influenceability, abuse resistance) on a 1-5 scale. Data analyst checks historical correlation with revenue or retention. Hint: If a candidate scores 1 or 2 in any criterion, exclude it. A North Star should score at least 3 across all criteria.

    FacilitatorMeasurement cadence
  4. 4

    Phase 4: Build input tree

    45 min

    Set the winner as the root. Add 3-5 drivers as second level, each with formula relationship. For each driver, 2-3 sub-drivers that teams can work on. Hint: If no team owns a sub-driver, the metric is not currently controllable in the organization. Either adjust team setup or choose a different metric.

    FacilitatorNorth Star metric
  5. 5

    Phase 5: Validation and rollout

    30 min workshop, 2 week data check

    Specify dashboard mock-up and owners per driver. Run two-week shadow mode: track metric daily, test against business events. Then make Go/No-Go decision. Hint: Shadow mode reveals data defects and wrong correlations. Without validation the metric is quietly retired after three months.

    OwnerInput metric tree
  6. 6

    Publish artifact

    10 min

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

    OwnerNorth Star metric
Usable artifact

Session Brief

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

session-brief.md

Session Brief: North Star Metric

Goal

Artifact: North Star metric

Working Question

Which one metric reflects the value the product creates for users and correlates with sustainable growth?

Context

Current top metrics; market examples; definition of Customer Value in the product; known vanity metrics to remove; list of active teams and initiatives.

Setup

  • Format: Method session
  • Duration: 3-4 h workshop, plus 2 weeks validation
  • Mode: Workshop or async
  • Participants: One owner (Product Lead, GM, or CEO in early stage); two to five people from Product, Data, Marketing, and Customer; one data analyst who can validate values immediately.
  • Owner: One owner (Product Lead, GM, or CEO in early stage)
  • 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 North Star metric. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with three columns (candidates, evaluation, input tree); data snapshot from the last 6-12 months; template for metric card (name, definition, formula, source, update frequency).

Preparation

Create three columns. Make criteria visible: reflects customer value, correlates with long-term revenue, is measurable in current data pipeline, and is team-influencable, and cannot be gamed by a single action.

Agenda

  1. Phase 1: Define customer value (30 min) Owner: Facilitator Action: Define in one sentence which core value the product delivers, referencing Jobs-to-be-Done or an Aha moment. Quote examples from user interviews. Hint: If the sentence contains features instead of outcomes, rewrite it. Customer Value is what the user achieves, not what the product does. Output: North Star metric

  2. Phase 2: Collect candidates (45 min) Owner: Facilitator Action: Generate 5-10 metric candidates. For each candidate: definition, formula, data source, update rhythm. Examples: active users per week with minimum action, completed orders per month, messages sent between participants. Hint: Candidates must represent value actions, not just activity. Login count is vanity, completed core workflow is value. Output: Input metric tree

  3. Phase 3: Evaluate against criteria (45 min) Owner: Facilitator Action: Score each candidate against five criteria (value, growth correlation, measurability, influenceability, abuse resistance) on a 1-5 scale. Data analyst checks historical correlation with revenue or retention. Hint: If a candidate scores 1 or 2 in any criterion, exclude it. A North Star should score at least 3 across all criteria. Output: Measurement cadence

  4. Phase 4: Build input tree (45 min) Owner: Facilitator Action: Set the winner as the root. Add 3-5 drivers as second level, each with formula relationship. For each driver, 2-3 sub-drivers that teams can work on. Hint: If no team owns a sub-driver, the metric is not currently controllable in the organization. Either adjust team setup or choose a different metric. Output: North Star metric

  5. Phase 5: Validation and rollout (30 min workshop, 2 week data check) Owner: Owner Action: Specify dashboard mock-up and owners per driver. Run two-week shadow mode: track metric daily, test against business events. Then make Go/No-Go decision. Hint: Shadow mode reveals data defects and wrong correlations. Without validation the metric is quietly retired after three months. Output: Input metric tree

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: North Star metric

Closeout

  • Update result artifact: North Star metric
  • 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

North Star metric: North Star Metric

Working Question

Which one metric reflects the value the product creates for users and correlates with sustainable growth?

Context

Current top metrics; market examples; definition of Customer Value in the product; known vanity metrics to remove; list of active teams and initiatives.

Participants

  • Owner: One owner (Product Lead, GM, or CEO in early stage)
  • Participants: One owner (Product Lead, GM, or CEO in early stage); two to five people from Product, Data, Marketing, and Customer; one data analyst who can validate values immediately.

Input

Whiteboard or Miro board with three columns (candidates, evaluation, input tree); data snapshot from the last 6-12 months; template for metric card (name, definition, formula, source, update frequency).

Template

Strategy Brief

Context

Why is this strategic clarification needed now?

Target state

What should be different in 6-12 months?

Priorities

  1. ...
  2. ...
  3. ...

Non-goals

  • ...

Metrics

  • North Star Metric:
  • Guardrail Metrics:

Risks

  • ...

Decisions

Which decisions should follow from this?

Completion Check

  • North Star metric 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

Strategy Brief

View templateCompact briefing for strategic context, target state, priorities, and non-goals.
markdown

strategy-brief-markdown.md

Compact briefing for strategic context, target state, priorities, and non-goals.

Strategy Brief

Context

Why is this strategic clarification needed now?

Target state

What should be different in 6-12 months?

Priorities

  1. ...
  2. ...
  3. ...

Non-goals

  • ...

Metrics

  • North Star Metric:
  • Guardrail Metrics:

Risks

  • ...

Decisions

Which decisions should follow from this?

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits North Star metric.
  • Profile with date and version. Archive previous version when definition or formula changes and document reason. Add end-of-quarter review entry to document.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet