Method guideOperations

Change Analysis

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

ComplexityMedium

Time45-120 min

Participants2-6

FormatWorkshop + async

MaturityEstablished

Plan Change Analysis

Prerequisite

What needs to be finished first

Complete firstClear boundary

Choose the event and a genuinely comparable incident-free reference with the same boundary and similar conditions.

Without a boundary, cases, periods, or variables become mixed.

Complete firstEvidence access

Event situation, comparable incident-free reference, change matrix, time and source evidence, cause log

Missing sources remain visible as uncertainty.

Preparation

What needs to be ready before start

Materials

Event situation, comparable incident-free reference, change matrix, time and source evidence, cause log

People / roles

Investigation lead · people from reference and event periods · process/system experts · action owners

Pre-read

Choose the event and a genuinely comparable incident-free reference with the same boundary and similar conditions.

Time needed

90–180 minutes after securing the timeline; add evidence validation.

Setup

Prepare a workspace with Compare · Changes · Sequence · Effect · Conclude; separate example from live data.

Core question

The one question this method answers

Which evidenced change distinguishes the event from a comparable incident-free situation, and what effect did it have?

Flow

Phases with goal, actions, output and pitfall

Change analysis compares conditions before and after an observed shift. The comparison produces testable hypotheses about which change may have caused the effect.

Change Analysis · working structure

Fictional example

Fictional values show the actual method fields.

Change Analysis · working structure
Category	Reference	Event	Difference	Time	Effect	Evidence	Status
ProcessAdd evidence and rationale.	No batch during peak	Batch starts 09:08	New parallel workload	09:08	Pool rises to 95%; checkout timeouts	Scheduler and pool log	Causal trigger
ControlAdd evidence and rationale.	Batch metric visible	Metric removed	Alert blind spot	Dashboard release 13 May	Batch use triggers no alert	Dashboard version	Contributing control gap
PeopleAdd evidence and rationale.	Same team	Same team	No difference	Unchanged	No observable effect	Roster	Not causal

1. Reference
Process
No batch during peak
Control
Batch metric visible
People
Same team
2. Event
Process
Batch starts 09:08
Control
Metric removed
People
Same team
3. Difference
Process
New parallel workload
Control
Alert blind spot
People
No difference
4. Time
Process
09:08
Control
Dashboard release 13 May
People
Unchanged
5. Effect
Process
Pool rises to 95%; checkout timeouts
Control
Batch use triggers no alert
People
No observable effect
6. Evidence
Process
Scheduler and pool log
Control
Dashboard version
People
Roster
7. Status
Process
Causal trigger
Control
Contributing control gap
People
Not causal

All values are fictional.

Reference · original teaching example

1
Compare
Comparison pair
Goal
Comparison pair: Test event and incident-free reference for equivalent service, boundary, and conditions.
Inputs for this step
- Choose the event and a genuinely comparable incident-free reference with the same boundary and similar conditions.
- Event situation, comparable incident-free reference, change matrix, time and source evidence, cause log
Actions
- Test event and incident-free reference for equivalent service, boundary, and conditions.
Output
Comparison pair
Test event and incident-free reference for equivalent service, boundary, and conditions.
Quality check
Are reference and event comparable apart from changes under investigation?
Pitfall
A quiet weekday is compared with the Saturday peak. Choose a reference with similar demand, configuration, and mode, or mark differences.
Timing: 20–30 minutes
2
Changes
Change register
Goal
Change register: Capture differences across people, equipment, procedures, controls, and environment.
Inputs for this step
- Comparison pair
Actions
- Capture differences across people, equipment, procedures, controls, and environment.
Output
Change register
Capture differences across people, equipment, procedures, controls, and environment.
Quality check
Is every difference concrete and labelled with time or version?
Pitfall
Only the most visible technical change is collected. Review every category, including planned, gradual, and external changes.
Timing: 30–45 minutes
3
Sequence
Evidence-backed chronology
Goal
Evidence-backed chronology: Check whether each change was effective before the event; document source and uncertainty.
Inputs for this step
- Change register
Actions
- Check whether each change was effective before the event; document source and uncertainty.
Output
Evidence-backed chronology
Check whether each change was effective before the event; document source and uncertainty.
Quality check
Did the change precede the effect, and is activation evidenced?
Pitfall
Commit time is equated with production effect. Evidence deployment, activation, and observation times separately.
Timing: 20–35 minutes
4
Effect
Effect assessment
Goal
Effect assessment: Test mechanism and magnitude of each relevant change; distinguish trigger from exposed latent weakness.
Inputs for this step
- Evidence-backed chronology
Actions
- Test mechanism and magnitude of each relevant change; distinguish trigger from exposed latent weakness.
Output
Effect assessment
Test mechanism and magnitude of each relevant change; distinguish trigger from exposed latent weakness.
Quality check
Is effect supported by a mechanism and counter-comparison?
Pitfall
The latest change is declared the sole root cause. Assess trigger and existing control gap separately and test against reference data.
Timing: 30–50 minutes
5
Conclude
Cause and action path
Goal
Cause and action path: Move evidenced causal changes and system weaknesses into further causal analysis or actions.
Inputs for this step
- Effect assessment
Actions
- Move evidenced causal changes and system weaknesses into further causal analysis or actions.
Output
Cause and action path
Move evidenced causal changes and system weaknesses into further causal analysis or actions.
Quality check
Were non-causal differences rejected and actions linked to evidenced effect?
Pitfall
Every identified difference creates an action. Carry forward only changes with evidenced mechanisms; retain others as open hypotheses.
Timing: 20–35 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Change Analysis · What Changed?Compare normal state and problem case, evaluate differences, and derive testable causes

Form

Change analysis matrix with reference, event state, difference, time, effect, evidence, and causal status.

Versioning / ownership

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

Tool alternatives

Reference-versus-event matrix
Timeline and change records
Cause and action log

change-analysis-working-template.md

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

Change Analysis: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 90–180 minutes after securing the timeline; add evidence validation.

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

Preparation for this scope

Method setup

Materials: Event situation, comparable incident-free reference, change matrix, time and source evidence, cause log
Roles: Investigation lead · people from reference and event periods · process/system experts · action owners
Advance information: Choose the event and a genuinely comparable incident-free reference with the same boundary and similar conditions.
Overall time needed: 90–180 minutes after securing the timeline; add evidence validation.
Setup: Prepare a workspace with Compare · Changes · Sequence · Effect · Conclude; separate example from live data.

Prepare for the work steps

Compare: Comparison pair

Choose the event and a genuinely comparable incident-free reference with the same boundary and similar conditions.
Event situation, comparable incident-free reference, change matrix, time and source evidence, cause log

Changes: Change register

Comparison pair

Sequence: Evidence-backed chronology

Change register

Effect: Effect assessment

Evidence-backed chronology

Conclude: Cause and action path

Effect assessment

Change Analysis · working structure

Category	Reference	Event	Difference	Time	Effect	Evidence	Status
Process
Control
People

Process: Add evidence and rationale.
Control: Add evidence and rationale.
People: Add evidence and rationale.

The blank worksheet contains prompts only.

Reference · original teaching example

Compare: Comparison pair

Expected artifact: Comparison pair

Test event and incident-free reference for equivalent service, boundary, and conditions.

Entry:

...

Are reference and event comparable apart from changes under investigation?

Changes: Change register

Expected artifact: Change register

Capture differences across people, equipment, procedures, controls, and environment.

Entry:

...

Is every difference concrete and labelled with time or version?

Sequence: Evidence-backed chronology

Expected artifact: Evidence-backed chronology

Check whether each change was effective before the event; document source and uncertainty.

Entry:

...

Did the change precede the effect, and is activation evidenced?

Effect: Effect assessment

Expected artifact: Effect assessment

Test mechanism and magnitude of each relevant change; distinguish trigger from exposed latent weakness.

Entry:

...

Is effect supported by a mechanism and counter-comparison?

Conclude: Cause and action path

Expected artifact: Cause and action path

Move evidenced causal changes and system weaknesses into further causal analysis or actions.

Entry:

...

Were non-causal differences rejected and actions linked to evidenced effect?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/change-analysis/run-sheet

Example output

Concrete filled scenario, fictional example

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

change-analysis-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Change Analysis · working structure

Category	Reference	Event	Difference	Time	Effect	Evidence	Status
Process	No batch during peak	Batch starts 09:08	New parallel workload	09:08	Pool rises to 95%; checkout timeouts	Scheduler and pool log	Causal trigger
Control	Batch metric visible	Metric removed	Alert blind spot	Dashboard release 13 May	Batch use triggers no alert	Dashboard version	Contributing control gap
People	Same team	Same team	No difference	Unchanged	No observable effect	Roster	Not causal

Pitfalls

Recognize symptoms and steer against them

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

Comparison pairA quiet weekday is compared with the Saturday peak.View in phase
Change registerOnly the most visible technical change is collected.View in phase
Evidence-backed chronologyCommit time is equated with production effect.View in phase
Effect assessmentThe latest change is declared the sole root cause.View in phase
Cause and action pathEvery identified difference creates an action.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Compare: Are reference and event comparable apart from changes under investigation?

Stop Changes: Is every difference concrete and labelled with time or version?

Stop Sequence: Did the change precede the effect, and is activation evidenced?

Stop Effect: Is effect supported by a mechanism and counter-comparison?

Stop Conclude: Were non-causal differences rejected and actions linked to evidenced effect?

Where to go next?

Operations

Root Cause Analysis

Further investigates the confirmed differences with a full root cause analysis.

Operations

Kepner-Tregoe

Bundles the found differences into a structured problem and decision analysis.

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 profile More methods

Change Analysis · working structure

1. Reference

2. Event

3. Difference

4. Time

5. Effect

6. Evidence

7. Status

Comparison pair

Change register

Evidence-backed chronology

Effect assessment

Cause and action path

change-analysis-working-template.md

Change Analysis: Worksheet

Question

Desired outcome

Scope

Preparation for this scope

Method setup

Prepare for the work steps

Compare: Comparison pair

Changes: Change register

Sequence: Evidence-backed chronology

Effect: Effect assessment

Conclude: Cause and action path

Change Analysis · working structure

Compare: Comparison pair

Changes: Change register

Sequence: Evidence-backed chronology

Effect: Effect assessment

Conclude: Cause and action path

Open questions and next steps

change-analysis-beispiel.md

Fictional teaching example: Change Analysis · working structure

Comparison pair

Change register

Evidence-backed chronology

Effect assessment

Cause and action path

Where to go next?

Finished the method guide?