methodatlas
Session Builder

Plan my session

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

Method session5-20 min sprint, optionally 2-4 sprints in sequenceWorkshop or asyncIdeenpool

Session: Rapid Ideation

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

  1. 1

    0-3 min: Setup and prompt

    3 min

    Read prompt. Communicate rule: quantity over quality, no discussion, one idea per sticky. Set timer to chosen sprint duration. Hint: If participants ask clarification questions, clarify briefly, then start hard. Longer pre-discussion destroys the speed effect of the method.

    FacilitatorIdeenpool
  2. 2

    3-10 min: Sprint 1

    5-7 min

    Silent phase. Each person writes as many ideas as possible on stickies. Facilitator enforces absolute discussion ban. Keep timer visible. Hint: Anyone thinking too long writes something banal. Banality is part of the lever because it tires the inner critic. Originality often comes after the banal.

    FacilitatorRoh-Shortlist
  3. 3

    10-13 min: Short sharing

    3 min

    Round-robin: read one favorite idea, without discussion. Others note spontaneous follow-on ideas on their own stickies. No but allowed. Hint: Sharing is a trigger for Sprint 2, not an evaluation round. Facilitator interrupts every evaluation immediately.

    FacilitatorCluster
  4. 4

    13-20 min: Sprint 2 and clustering

    5-7 min

    Optional Sprint 2 with slightly varied prompt (for example "how would a competitor do it"). Then build clusters, consolidate duplicates, mark top 5-10. Hint: If Sprint 2 does not create more ideas, stop and move to evaluation. Three sprints are rarely better than two with smart prompt variation.

    OwnerIdeenpool
  5. 5

    Publish artifact

    10 min

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

    OwnerIdeenpool
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Rapid Ideation

Goal

Artifact: Ideenpool

Working Question

What range of ideas does the team generate in a hard timebox when every evaluation is deliberately suppressed?

Context

Prompt or challenge as one sentence; optionally two backup prompts for follow-up sprints; definition of how clustering or evaluation will happen; estimate group energy level.

Setup

  • Format: Method session
  • Duration: 5-20 min sprint, optionally 2-4 sprints in sequence
  • Mode: Workshop or async
  • Participants: One facilitator who keeps timer, suppresses discussion and switches prompts if needed; one to twenty participants; optionally one scribe for consolidation at the end.
  • Owner: One facilitator who keeps timer, suppresses discussion and switches prompts if needed
  • 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 Ideenpool. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or board with large free area; stickies or sticky tool; very visible timer (buzzer helps); markers; clearly formulated prompt as card.

Preparation

Prompt visible at top. Empty area for stickies. Timer set to 3-7 min per sprint. State rule: no evaluation, no discussion, quantity over quality. One idea per sticky.

Agenda

  1. 0-3 min: Setup and prompt (3 min) Owner: Facilitator Action: Read prompt. Communicate rule: quantity over quality, no discussion, one idea per sticky. Set timer to chosen sprint duration. Hint: If participants ask clarification questions, clarify briefly, then start hard. Longer pre-discussion destroys the speed effect of the method. Output: Ideenpool

  2. 3-10 min: Sprint 1 (5-7 min) Owner: Facilitator Action: Silent phase. Each person writes as many ideas as possible on stickies. Facilitator enforces absolute discussion ban. Keep timer visible. Hint: Anyone thinking too long writes something banal. Banality is part of the lever because it tires the inner critic. Originality often comes after the banal. Output: Roh-Shortlist

  3. 10-13 min: Short sharing (3 min) Owner: Facilitator Action: Round-robin: read one favorite idea, without discussion. Others note spontaneous follow-on ideas on their own stickies. No but allowed. Hint: Sharing is a trigger for Sprint 2, not an evaluation round. Facilitator interrupts every evaluation immediately. Output: Cluster

  4. 13-20 min: Sprint 2 and clustering (5-7 min) Owner: Owner Action: Optional Sprint 2 with slightly varied prompt (for example "how would a competitor do it"). Then build clusters, consolidate duplicates, mark top 5-10. Hint: If Sprint 2 does not create more ideas, stop and move to evaluation. Three sprints are rarely better than two with smart prompt variation. Output: Ideenpool

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

Closeout

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

Ideenpool: Rapid Ideation

Working Question

What range of ideas does the team generate in a hard timebox when every evaluation is deliberately suppressed?

Context

Prompt or challenge as one sentence; optionally two backup prompts for follow-up sprints; definition of how clustering or evaluation will happen; estimate group energy level.

Participants

  • Owner: One facilitator who keeps timer, suppresses discussion and switches prompts if needed
  • Participants: One facilitator who keeps timer, suppresses discussion and switches prompts if needed; one to twenty participants; optionally one scribe for consolidation at the end.

Input

Whiteboard or board with large free area; stickies or sticky tool; very visible timer (buzzer helps); markers; clearly formulated prompt as card.

Template

Rapid Ideation Working Template

Goal

Time-boxed idea generation that deliberately favors volume and pace over quality.

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

  • Idea pool:
  • Rough shortlist:
  • Clusters:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Completion Check

  • Ideenpool 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

Rapid Ideation Working Template

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

rapid-ideation-working-template.md

Compact working template for Rapid Ideation with context, input, output artifacts, and next step.

Rapid Ideation Working Template

Goal

Time-boxed idea generation that deliberately favors volume and pace over quality.

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

  • Idea pool:
  • Rough shortlist:
  • Clusters:

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 Ideenpool.
  • Date, prompt and participant count in header. Separate section or color code per sprint. Shortlist as separate artifact with reference to sprint the idea came from.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet