# Graph the behavior before explaining the cause

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Graph the behavior before explaining the cause

ID: MHC-D-RESEARCH-0342 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/graph-the-behavior-before-explaining-the-cause

Before explaining the curve, draw the curve.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A team is arguing about why a recurring problem happens while nobody has made the pattern over time visible.

### Avoid when

- The selected metric, sampling and time window can distort the story; a behavior-over-time graph is evidence organization, not proof of causation.

### Explanation

Choose the behavior that matters and sketch or plot how it changed over a meaningful time window. Mark important events or regime changes, then tell the factual story the shape supports before proposing causes. Add a second variable only when the comparison helps the question. The graph is a shared observation surface, not a causal verdict.

### Steps

1. Name the behavior precisely enough to measure or estimate consistently.
2. Choose a time window that includes the pattern you are trying to understand.
3. Plot the behavior and annotate important events without drawing causal arrows yet.
4. Describe the visible pattern before proposing structures or explanations.
5. Change the window or add a comparison when the first graph could hide a different story.

### Example

Plot queue age across several release cycles before deciding that one slow week proves a permanent capacity problem.

### Check

Different people can point to the same visible change over time even if they still disagree about why it happened.

### Limits

- The selected metric, sampling and time window can distort the story; a behavior-over-time graph is evidence organization, not proof of causation.

### Evidence and sources

- supports: The Waters Center presents behavior-over-time graphs as a tool for showing patterns and trends and for making assumptions about a system visible through the story of the graph. — RS-D295223796F1E7D5. A graph makes a pattern inspectable but does not establish the cause of the pattern or guarantee that the chosen time window is representative. (Tools Course #1: Behavior-Over-Time Graphs)
- RS-D295223796F1E7D5: Tools of Systems Thinking Courses — https://thinkingtoolsstudio.waterscenterst.org/courses/tools

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/move-from-the-event-down-the-systems-iceberg
