methodatlas
Session Builder

Plan my session

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

Async work run24 to 72 hasynchronousSimulationsmodell

Session: System Dynamics Simulation

The plan distributes preparation, review, and outcome work across an asynchronous work run. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Async work run with 1-5 Modellierende, Stakeholder asynchron. 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 Simulationsmodell. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Prepare brief

    15-30 min

    Prepare the working question, input, target artifact, and review deadline for System Dynamics Simulation. Link relevant data, sources, and existing artifacts.

    OwnerSession brief
  2. 2

    Work asynchronously

    24 to 72 h

    Participants work through the method along the template. Focus: add contributions directly to the artifact, mark assumptions, and link evidence.

    ParticipantsSimulationsmodell
  3. 3

    Consolidate review

    20-30 min

    Cluster comments, contradictions, and open questions. Sort unclear points into decisions, risks, or follow-ups.

    FacilitatorReview notes
  4. 4

    Finalize artifact

    15-30 min

    Create the integrated version, set status, and schedule the next review or decision point.

    OwnerSzenarienberichte
  5. 5

    Publish artifact

    10 min

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

    OwnerSimulationsmodell
Usable artifact

Session Brief

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

session-brief.md

Session Brief: System Dynamics Simulation

Goal

Artifact: Simulationsmodell

Working Question

Which dynamic effects and policy levers become visible when qualitative structure is calculated as quantitative model across the time horizon?

Context

Question and time horizon; CLD and stock-and-flow sketch; available historical data for calibration; known policy options; accepted uncertainty range; reporting format.

Setup

  • Format: Async work run
  • Duration: 24 to 72 h
  • Mode: asynchronous
  • Participants: One modeler with system dynamics experience (lead); one to two domain experts for rates and assumptions; one data owner for initial and validation data; one stakeholder or client for scenario selection and interpretation.
  • Owner: One modeler with system dynamics experience (lead)
  • 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 Simulationsmodell. After the session, the artifact should be shareable, reviewable, or reusable.

Input

System dynamics tool (Vensim, Stella, Simantics System Dynamics, AnyLogic, BPTK-Py); data sources for initial values and rates; version control (Git, model files plus scripts); spreadsheet for data preparation.

Preparation

Model folder in repo with /model, /data, /scenarios, /docs. Tool installed and licensed. Calibration dataset imported. Question and time horizon visible in model documentation.

Agenda

  1. Prepare brief (15-30 min) Owner: Owner Action: Prepare the working question, input, target artifact, and review deadline for System Dynamics Simulation. Link relevant data, sources, and existing artifacts. Output: Session brief

  2. Work asynchronously (24 to 72 h) Owner: Participants Action: Participants work through the method along the template. Focus: add contributions directly to the artifact, mark assumptions, and link evidence. Output: Simulationsmodell

  3. Consolidate review (20-30 min) Owner: Facilitator Action: Cluster comments, contradictions, and open questions. Sort unclear points into decisions, risks, or follow-ups. Output: Review notes

  4. Finalize artifact (15-30 min) Owner: Owner Action: Create the integrated version, set status, and schedule the next review or decision point. Output: Szenarienberichte

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

Closeout

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

Simulationsmodell: System Dynamics Simulation

Working Question

Which dynamic effects and policy levers become visible when qualitative structure is calculated as quantitative model across the time horizon?

Context

Question and time horizon; CLD and stock-and-flow sketch; available historical data for calibration; known policy options; accepted uncertainty range; reporting format.

Participants

  • Owner: One modeler with system dynamics experience (lead)
  • Participants: One modeler with system dynamics experience (lead); one to two domain experts for rates and assumptions; one data owner for initial and validation data; one stakeholder or client for scenario selection and interpretation.

Input

System dynamics tool (Vensim, Stella, Simantics System Dynamics, AnyLogic, BPTK-Py); data sources for initial values and rates; version control (Git, model files plus scripts); spreadsheet for data preparation.

Template

System Dynamics Simulation Working Template

Goal

Quantitative simulation model built from stocks, flows, and feedback loops.

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

  • Simulation model:
  • Scenario reports:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Completion Check

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

System Dynamics Simulation Working Template

View templateCompact working template for System Dynamics Simulation with context, input, output artifacts, and next step.
markdown

system-dynamics-simulation-working-template.md

Compact working template for System Dynamics Simulation with context, input, output artifacts, and next step.

System Dynamics Simulation Working Template

Goal

Quantitative simulation model built from stocks, flows, and feedback loops.

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

  • Simulation model:
  • Scenario reports:

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 Simulationsmodell.
  • Model with SemVer in Git repo. Structural changes documented per major release. Data snapshots dated, not overwritten. Scenario files as separate files with description.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet