Define the system and unit of analysis
Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.
Plans operational changes by linking the change, impact, risk, training, documentation, owners and post-implementation monitoring.
Before opening a form, define the question that must be answered. A management tool is useful when it reduces ambiguity, exposes assumptions and makes clear which decision will be made from the evidence produced.
CTL-01Which system components will be affected by the change, and which risks, training, documents, interfaces and measures must be prepared before implementation?
Process tools make boundaries, inputs, outputs, risks and responsibilities visible. This reduces the classic mistake of optimizing one step while moving the problem elsewhere in the flow.
Use them when the challenge crosses functions, depends on handoffs, contains operational risk or requires standardization and clarity about how work actually happens.
A matrix turns criteria into a comparable structure. Before scoring, define scales and the meaning of each axis; otherwise different numbers may represent different interpretations across evaluators.
Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.
Translate abstract concepts into operational definitions, scales, classification rules and data sources. Criteria should exist before the result to reduce retrospective interpretation.
Link each conclusion to data, observations, assumptions and owners. When a score is used, retain its components; when a hypothesis is used, record how it will be tested.
Calibrate when there are multiple evaluators, retain the evidence behind each score and treat the result as decision support — not an automatic replacement for judgment.
When changing an ERP tax field, the matrix identifies impacts on master data, billing, integrations, training and reports. Each impact gets a risk, owner, test evidence, contingency and post-go-live indicator.
The example is intentionally specific. Numbers illustrate the reasoning and are not universal benchmarks: limits, scales and targets must be defined for the process being analyzed.Measures should serve reasoning. Whenever possible combine outcome, process and contextual evidence. For time series, look for patterns and variation rather than only point-in-time before/after comparisons.
Ask whether another person, using the same definitions and evidence, would reach a similar interpretation. If the answer depends heavily on individual judgment, refine the operational definition, scale or data source.
Operational adaptation of recognized methods. Consistency depends on explicit definitions, criteria, evidence and governance.
The matrix does not replace human change management. Low technical impact can still create difficult adoption when roles, incentives or professional identity change.
Define an owner, review frequency, official data source and condition for reopening the decision. Link actions to deadlines and indicators, hypotheses to tests, and risks to treatment and follow-up.
The references below support the methodological family or principle used. Struckel’s digital implementation operationalizes application, documentation and traceability; it does not change the conceptual limits of the original sources.
ISO/TC 176/SC 2. The Process Approach in ISO 9001:2015.
Kotter JP. Leading Change. Harvard Business School Press; 1996.
ISO 31000:2018. Risk management — Guidelines.
Struckel Forms offers a free way to structure this methodology with guided fields, contextual help and print/PDF preparation. Use the tool to organize reasoning; use consulting when the challenge requires design, implementation, facilitation or executive follow-up.