methodatlas
Session Builder

Plan my session

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

Method session2-4 hWorkshopConflict Cloud

Session: Evaporating Cloud

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

  1. 1

    Fix scope

    10-20 min

    Define trigger, goal, and boundaries of analysis. Capture off-scope topics in a parking lot. Hint: A tight scope produces better results than a complete but diffuse broad approach.

    FacilitatorConflict Cloud
  2. 2

    Collect raw material

    20-40 min

    Bring facts, events, options, constraints, or assumptions into visibility. Hint: Keep facts and interpretations separate. Mark uncertainty explicitly instead of smoothing over unknowns.

    FacilitatorAssumption List
  3. 3

    Build structure

    30-60 min

    Fill the Conflict Cloud step by step, clarify relationships between elements, and expose contradictions. Hint: Do not evaluate too early. First stabilize structure, then draw conclusions.

    FacilitatorBreakthrough Ideas
  4. 4

    Validate and refine

    20-40 min

    Mark gaps, weak assumptions, counterexamples, and critical paths. Check output for comprehensibility. Hint: If nobody can explain the logic in two minutes, the artifact is not ready yet.

    FacilitatorNext Experiments
  5. 5

    Define next steps

    15-20 min

    Document decision, experiment, test, action, or follow-up with owner and date. Hint: A good artifact without next action is knowledge work without impact.

    OwnerConflict Cloud
  6. 6

    Publish artifact

    10 min

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

    OwnerConflict Cloud
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Evaporating Cloud

Goal

Artifact: Conflict Cloud

Working Question

Which conflict does the system maintain, which assumptions reinforce it, and which breakthroughs can resolve it?

Context

Scope, trigger, known facts, relevant constraints, prior options or events, and desired outcome of the workshop.

Setup

  • Format: Method session
  • Duration: 2-4 h
  • Mode: Workshop
  • Participants: Facilitator; subject-matter experts from the affected area; one owner for outcomes and follow-up; a named decider for decisions.
  • Owner: Facilitator
  • 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 Conflict Cloud. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Working board or document for Conflict Cloud; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Preparation

Prepare an empty Conflict Cloud template. Make scope and driving question visible at the top. Mark every assumption as an assumption, not as fact.

Agenda

  1. Fix scope (10-20 min) Owner: Facilitator Action: Define trigger, goal, and boundaries of analysis. Capture off-scope topics in a parking lot. Hint: A tight scope produces better results than a complete but diffuse broad approach. Output: Conflict Cloud

  2. Collect raw material (20-40 min) Owner: Facilitator Action: Bring facts, events, options, constraints, or assumptions into visibility. Hint: Keep facts and interpretations separate. Mark uncertainty explicitly instead of smoothing over unknowns. Output: Assumption List

  3. Build structure (30-60 min) Owner: Facilitator Action: Fill the Conflict Cloud step by step, clarify relationships between elements, and expose contradictions. Hint: Do not evaluate too early. First stabilize structure, then draw conclusions. Output: Breakthrough Ideas

  4. Validate and refine (20-40 min) Owner: Facilitator Action: Mark gaps, weak assumptions, counterexamples, and critical paths. Check output for comprehensibility. Hint: If nobody can explain the logic in two minutes, the artifact is not ready yet. Output: Next Experiments

  5. Define next steps (15-20 min) Owner: Owner Action: Document decision, experiment, test, action, or follow-up with owner and date. Hint: A good artifact without next action is knowledge work without impact. Output: Conflict Cloud

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

Closeout

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

Conflict Cloud: Evaporating Cloud

Working Question

Which conflict does the system maintain, which assumptions reinforce it, and which breakthroughs can resolve it?

Context

Scope, trigger, known facts, relevant constraints, prior options or events, and desired outcome of the workshop.

Participants

  • Owner: Facilitator
  • Participants: Facilitator; subject-matter experts from the affected area; one owner for outcomes and follow-up; a named decider for decisions.

Input

Working board or document for Conflict Cloud; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Template

Evaporating Cloud Working Template

Goal

TOC method for resolving apparent conflicts through needs, assumptions, and breakthrough ideas.

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

  • Conflict Cloud:
  • Assumption List:
  • Breakthrough Ideas:
  • Next Experiments:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Conflict Cloud 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

Evaporating Cloud Working Template

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

evaporating-cloud-working-template.md

Compact working template for Evaporating Cloud with context, input, output artifacts, and next step.

Evaporating Cloud Working Template

Goal

TOC method for resolving apparent conflicts through needs, assumptions, and breakthrough ideas.

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

  • Conflict Cloud:
  • Assumption List:
  • Breakthrough Ideas:
  • Next Experiments:

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 Conflict Cloud.
  • Save artifact with date, scope, and participants. On new evidence, add a new version or a change note to keep decision logic traceable.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet