methodatlas
Method guideSystems Thinking

Behavior Over Time Graph

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityLow
Time20-45 min
Participants1-10
FormatWorkshop + async
MaturityEstablished
Plan Behavior Over Time Graph
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Set one influenceable variable, unit, and time span; prepare data sources and known events.

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

BOTG axes, data or explicitly estimated points, event notes, uncertainty markers, and hypothesis log

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

BOTG axes, data or explicitly estimated points, event notes, uncertainty markers, and hypothesis log

People / roles

Facilitator · people with system experience · data owner · decision owner

Pre-read

Set one influenceable variable, unit, and time span; prepare data sources and known events.

Time needed

45–90 minutes for one to three variables; validate data beforehand if needed.

Setup

Prepare a workspace with Variable · Curve · Events · Pattern · Hypotheses; separate example from live data.

03

Core question

The one question this method answers

How does one clearly defined variable change over a relevant period, and what might explain turning points?

04

Flow

Phases with goal, actions, output and pitfall

A behavior-over-time graph makes the course of a selected variable visible across a relevant period. Turning points, peaks, plateaus, and drops provide a basis for examining influencing events or interventions.

Behavior Over Time Graph · working structure

Fictional example

Fictional values show the actual method fields.

Behavior Over Time Graph · working structure
VariableUnitPeriodData pointsPatternTurning pointEvidenceHypothesis
p80 waiting timeAdd evidence and rationale.MinutesJan–Jun14, 15, 17, gap, 18, 11Rise then downward stepMay: −7 minutesDashboard; April missingSlot cap or new warehouse crew
Warehouse callsAdd evidence and rationale.Calls/SaturdayJan–Jun21, 22, 25, 24, 23, 24High plateauNo turning pointPhone logInventory currency remains bottleneck

  1. 1. Unit

    p80 waiting time
    Minutes
    Warehouse calls
    Calls/Saturday

  2. 2. Period

    p80 waiting time
    Jan–Jun
    Warehouse calls
    Jan–Jun

  3. 3. Data points

    p80 waiting time
    14, 15, 17, gap, 18, 11
    Warehouse calls
    21, 22, 25, 24, 23, 24

  4. 4. Pattern

    p80 waiting time
    Rise then downward step
    Warehouse calls
    High plateau

  5. 5. Turning point

    p80 waiting time
    May: −7 minutes
    Warehouse calls
    No turning point

  6. 6. Evidence

    p80 waiting time
    Dashboard; April missing
    Warehouse calls
    Phone log

  7. 7. Hypothesis

    p80 waiting time
    Slot cap or new warehouse crew
    Warehouse calls
    Inventory currency remains bottleneck

All values are fictional.

Reference · original teaching example

  1. 1

    Variable

    Labelled axes

    Goal

    Labelled axes: Set the variable, unit, system boundary, and a sufficiently long time axis.

    Inputs for this step

    • Set one influenceable variable, unit, and time span; prepare data sources and known events.
    • BOTG axes, data or explicitly estimated points, event notes, uncertainty markers, and hypothesis log

    Actions

    • Set the variable, unit, system boundary, and a sufficiently long time axis.

    Output

    Labelled axes

    Set the variable, unit, system boundary, and a sufficiently long time axis.

    Quality check

    Are variable, unit, and period explicit without mixing measures in one curve?

    Pitfall

    The Y-axis only says quality and combines several measures. Choose one observable variable with unit and boundary.

    Timing: 10–15 minutes

  2. 2

    Curve

    Evidence-backed curve

    Goal

    Evidence-backed curve: Plot data points or clearly marked estimates and connect them into a trajectory.

    Inputs for this step

    • Labelled axes

    Actions

    • Plot data points or clearly marked estimates and connect them into a trajectory.

    Output

    Evidence-backed curve

    Plot data points or clearly marked estimates and connect them into a trajectory.

    Quality check

    Can actual data, gaps, and estimates be distinguished?

    Pitfall

    A smooth desired curve is drawn without data points. Cite sources, mark estimates, and leave data gaps open.

    Timing: 10–20 minutes

  3. 3

    Events

    Event annotations

    Goal

    Event annotations: Annotate events at their time on the curve without already declaring them causes.

    Inputs for this step

    • Evidence-backed curve

    Actions

    • Annotate events at their time on the curve without already declaring them causes.

    Output

    Event annotations

    Annotate events at their time on the curve without already declaring them causes.

    Quality check

    Are event and timing evidenced and separated from causal claims?

    Pitfall

    Every event near a turning point is treated as causal. Record time and event first; test causality separately.

    Timing: 10–15 minutes

  4. 4

    Pattern

    Pattern description

    Goal

    Pattern description: Describe slope, delay, plateau, oscillation, and turning points; compare perspectives.

    Inputs for this step

    • Event annotations

    Actions

    • Describe slope, delay, plateau, oscillation, and turning points; compare perspectives.

    Output

    Pattern description

    Describe slope, delay, plateau, oscillation, and turning points; compare perspectives.

    Quality check

    Does the pattern describe the trajectory without mixing explanation and judgment?

    Pitfall

    The group jumps from one event directly to a solution. Name shape, direction, pace, and turning point first.

    Timing: 10–20 minutes

  5. 5

    Hypotheses

    Test plan

    Goal

    Test plan: Form several explanations for relevant turning points and specify needed evidence.

    Inputs for this step

    • Pattern description

    Actions

    • Form several explanations for relevant turning points and specify needed evidence.

    Output

    Test plan

    Form several explanations for relevant turning points and specify needed evidence.

    Quality check

    Does each hypothesis have a distinguishing signal and next data source?

    Pitfall

    One plausible story is recorded as the conclusion. Add an alternative and a signal that discriminates between explanations.

    Timing: 10–20 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Behavior over Time · System-TrendVerlauf, Ereignisse und Hypothesen sichtbar machen, bevor Ursachen diskutiert werden
Behavior over Time GraphDie Skizze zeigt eine qualitative Kurve über Zeit, markierte Ereignisse, typische Muster und Hypothesen zur Systemdynamik.Vom aktuellen Zustand zum VerlaufsmusterEine relevante Variable wird über Zeit skizziert, Ereignisse werden markiert und als Systemhypothesen gelesen.hochniedrigStartheuteZeitWert / VerhaltenEreignisRedesignInterventionTemplatesAnstiegProblem eskaliertPlateauSystem stabilisiertKnickHebel wirkt verzögertHypothesenUrsache?Verzögerung?Hebelpunkt?
Form

Annotated behavior-over-time graph with axes, curve, evidence, turning points, and testable explanatory hypotheses.

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • BOTG surface with labelled axes
  • Data and event sources
  • Turning-point hypothesis log

behavior-over-time-graph-working-template.md

Set subject, evidence, roles, flow, and review.

Behavior Over Time Graph: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 45–90 minutes for one to three variables; validate data beforehand if needed.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: BOTG axes, data or explicitly estimated points, event notes, uncertainty markers, and hypothesis log
  • Roles: Facilitator · people with system experience · data owner · decision owner
  • Advance information: Set one influenceable variable, unit, and time span; prepare data sources and known events.
  • Overall time needed: 45–90 minutes for one to three variables; validate data beforehand if needed.
  • Setup: Prepare a workspace with Variable · Curve · Events · Pattern · Hypotheses; separate example from live data.

Prepare for the work steps

Variable: Labelled axes

  • Set one influenceable variable, unit, and time span; prepare data sources and known events.
  • BOTG axes, data or explicitly estimated points, event notes, uncertainty markers, and hypothesis log

Curve: Evidence-backed curve

  • Labelled axes

Events: Event annotations

  • Evidence-backed curve

Pattern: Pattern description

  • Event annotations

Hypotheses: Test plan

  • Pattern description

Behavior Over Time Graph · working structure

VariableUnitPeriodData pointsPatternTurning pointEvidenceHypothesis
p80 waiting time
Warehouse calls
  • p80 waiting time: Add evidence and rationale.
  • Warehouse calls: Add evidence and rationale.

The blank worksheet contains prompts only.

Reference · original teaching example

Variable: Labelled axes

Expected artifact: Labelled axes

Set the variable, unit, system boundary, and a sufficiently long time axis.

Entry:

...

  • Are variable, unit, and period explicit without mixing measures in one curve?

Curve: Evidence-backed curve

Expected artifact: Evidence-backed curve

Plot data points or clearly marked estimates and connect them into a trajectory.

Entry:

...

  • Can actual data, gaps, and estimates be distinguished?

Events: Event annotations

Expected artifact: Event annotations

Annotate events at their time on the curve without already declaring them causes.

Entry:

...

  • Are event and timing evidenced and separated from causal claims?

Pattern: Pattern description

Expected artifact: Pattern description

Describe slope, delay, plateau, oscillation, and turning points; compare perspectives.

Entry:

...

  • Does the pattern describe the trajectory without mixing explanation and judgment?

Hypotheses: Test plan

Expected artifact: Test plan

Form several explanations for relevant turning points and specify needed evidence.

Entry:

...

  • Does each hypothesis have a distinguishing signal and next data source?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/behavior-over-time-graph/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

behavior-over-time-graph-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Behavior Over Time Graph · working structure

VariableUnitPeriodData pointsPatternTurning pointEvidenceHypothesis
p80 waiting timeMinutesJan–Jun14, 15, 17, gap, 18, 11Rise then downward stepMay: −7 minutesDashboard; April missingSlot cap or new warehouse crew
Warehouse callsCalls/SaturdayJan–Jun21, 22, 25, 24, 23, 24High plateauNo turning pointPhone logInventory currency remains bottleneck
07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Labelled axesThe Y-axis only says quality and combines several measures.View in phase
  2. Evidence-backed curveA smooth desired curve is drawn without data points.View in phase
  3. Event annotationsEvery event near a turning point is treated as causal.View in phase
  4. Pattern descriptionThe group jumps from one event directly to a solution.View in phase
  5. Test planOne plausible story is recorded as the conclusion.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Variable: Are variable, unit, and period explicit without mixing measures in one curve?
Stop Curve: Can actual data, gaps, and estimates be distinguished?
Stop Events: Are event and timing evidenced and separated from causal claims?
Stop Pattern: Does the pattern describe the trajectory without mixing explanation and judgment?
Stop Hypotheses: Does each hypothesis have a distinguishing signal and next data source?

Method after Systems Thinking Community. The method comes from systems thinking, system dynamics, or adjacent organizational practice. Curated with 1 sources.

Sources: Behavior Over Time Graph

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Iceberg Model method illustration showing its working structure
Systems Thinking
Iceberg Model

Looks for the structural causes behind a notable turning point.

A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys

Traces a specific turning point with a cause chain down to the root cause.

View in playbookUnderstand a Systemic Problem and Find LeverageMove from a recurring symptom to the underlying system structure and a concrete leverage point.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods