methodatlas
Session Builder

Plan my session

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

Method session5-15 minWorkshop or asyncVC-check note

Session: 5-Minuten VC-Check

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 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 VC-check note. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Minute 1: Problem quality

    1-2 min

    State the problem in one sentence and assess whether it has pain, urgency, or economic relevance. Hint: If the problem is described only as a solution, the idea is not ready for evaluation.

    FacilitatorVC-check note
  2. 2

    Minute 2: Target customer

    1-2 min

    Name the concrete target group and separate user, buyer, and decision maker when they are not the same person. Hint: Broad target groups such as all companies or all developers are warning signals.

    FacilitatorGo/sharpen/park decision
  3. 3

    Minute 3: Current solution

    1-2 min

    Write down how the problem is solved today: existing tools, manual workarounds, internal process, or ignoring it. Hint: Existing competition is not a reason to stop. It often shows demand exists.

    FacilitatorRisk and assumption list
  4. 4

    Minute 4: Differentiation

    1-2 min

    Check why the new solution would be clearly better: simpler, faster, cheaper, more precise, more accessible, or easier to distribute. Hint: A single feature advantage is usually not enough. Look for a clear reason to switch.

    FacilitatorNext validation step
  5. 5

    Minute 5: Market and decision

    1-3 min

    Roughly estimate whether the segment can become large enough, and decide: deepen, sharpen, or park. Hint: The decision must be tied to the strongest unresolved assumption.

    OwnerVC-check note
  6. 6

    Publish artifact

    10 min

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

    OwnerVC-check note
Usable artifact

Session Brief

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

session-brief.md

Session Brief: 5-Minuten VC-Check

Goal

Artifact: VC-check note

Working Question

Is this idea structurally strong enough to deserve a next validation round?

Context

Short idea description, assumed target group, known alternatives or competitors, and rough price assumption if present.

Setup

  • Format: Method session
  • Duration: 5-15 min
  • Mode: Workshop or async
  • Participants: One idea owner, optional critical sparring partner with founder- or investor-perspective. In groups: at most five people, otherwise the timebox weakens.
  • Owner: One idea owner, optional critical sparring partner with founder- or investor-perspective
  • 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 VC-check note. After the session, the artifact should be shareable, reviewable, or reusable.

Input

An empty check table with five rows; timer; a field for decision and next validation step.

Preparation

Set timer for five minutes. Write the idea in one sentence at the top. Prepare five assessment questions below: Problem, customer, current solution, differentiation, market.

Agenda

  1. Minute 1: Problem quality (1-2 min) Owner: Facilitator Action: State the problem in one sentence and assess whether it has pain, urgency, or economic relevance. Hint: If the problem is described only as a solution, the idea is not ready for evaluation. Output: VC-check note

  2. Minute 2: Target customer (1-2 min) Owner: Facilitator Action: Name the concrete target group and separate user, buyer, and decision maker when they are not the same person. Hint: Broad target groups such as all companies or all developers are warning signals. Output: Go/sharpen/park decision

  3. Minute 3: Current solution (1-2 min) Owner: Facilitator Action: Write down how the problem is solved today: existing tools, manual workarounds, internal process, or ignoring it. Hint: Existing competition is not a reason to stop. It often shows demand exists. Output: Risk and assumption list

  4. Minute 4: Differentiation (1-2 min) Owner: Facilitator Action: Check why the new solution would be clearly better: simpler, faster, cheaper, more precise, more accessible, or easier to distribute. Hint: A single feature advantage is usually not enough. Look for a clear reason to switch. Output: Next validation step

  5. Minute 5: Market and decision (1-3 min) Owner: Owner Action: Roughly estimate whether the segment can become large enough, and decide: deepen, sharpen, or park. Hint: The decision must be tied to the strongest unresolved assumption. Output: VC-check note

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: VC-check note

Closeout

  • Update result artifact: VC-check note
  • 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

VC-check note: 5-Minuten VC-Check

Working Question

Is this idea structurally strong enough to deserve a next validation round?

Context

Short idea description, assumed target group, known alternatives or competitors, and rough price assumption if present.

Participants

  • Owner: One idea owner, optional critical sparring partner with founder- or investor-perspective
  • Participants: One idea owner, optional critical sparring partner with founder- or investor-perspective. In groups: at most five people, otherwise the timebox weakens.

Input

An empty check table with five rows; timer; a field for decision and next validation step.

Template

5-Minute VC Check Working Template

Idea in one sentence

For [target customer], we solve [problem] with [new approach], so that [benefit].

Checklist questions

QuestionShort answerSignal
ProblemWhat concrete pain, effort, loss, or risk exists?Green/Yellow/Red
CustomerWho uses it, who buys it, and which budget pays for it?Green/Yellow/Red
Current solutionHow is the problem solved or ignored today?Green/Yellow/Red
DifferentiationWhy would the new approach be clearly better or more accessible?Green/Yellow/Red
MarketCan an initial sub-market be large enough and reachable?Green/Yellow/Red

Triage

  • Decision: Deepen / Sharpen / Park
  • strongest open assumption:
  • biggest risk:
  • most important positive signal:

Next validation step

  • Format: problem interview / smoke test / landing page / concierge test / desk research
  • Target group:
  • Success signal:
  • Owner:
  • Date:

Completion Check

  • VC-check note 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

5-Minute VC Check Working Template

View templateCompact template for evaluating an early business idea through five investor checklist questions and deriving a triage decision.
markdown

five-minute-vc-check-working-template.md

Compact template for evaluating an early business idea through five investor checklist questions and deriving a triage decision.

5-Minute VC Check Working Template

Idea in one sentence

For [target customer], we solve [problem] with [new approach], so that [benefit].

Checklist questions

QuestionShort answerSignal
ProblemWhat concrete pain, effort, loss, or risk exists?Green/Yellow/Red
CustomerWho uses it, who buys it, and which budget pays for it?Green/Yellow/Red
Current solutionHow is the problem solved or ignored today?Green/Yellow/Red
DifferentiationWhy would the new approach be clearly better or more accessible?Green/Yellow/Red
MarketCan an initial sub-market be large enough and reachable?Green/Yellow/Red

Triage

  • Decision: Deepen / Sharpen / Park
  • strongest open assumption:
  • biggest risk:
  • most important positive signal:

Next validation step

  • Format: problem interview / smoke test / landing page / concierge test / desk research
  • Target group:
  • Success signal:
  • Owner:
  • Date:
Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits VC-check note.
  • Keep one version per idea with date, context, and reviewer. Add later assessment as an append-only entry, not by overwriting older conclusions.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.