Lightweight-process maturity check

The diagnostic goal

Use the lightweight-process maturity check to locate the specific conditions behind this question: Is a process absent, appropriately lightweight, or heavier than the problem requires? The working view makes problem, scale trigger, and risk visible so discussion can move from general opinion to a specific action or decision.

When to run it

Run the lightweight-process maturity check before a consequential review or change in operating foundations, when symptoms are visible but the underlying condition is still unclear. Repeat it when the evidence for problem, scale trigger, and risk changes, rather than on a calendar alone.

What it tests

The lightweight-process maturity check is an evidence-based review that keeps healthy, watch, gap, and unknown states visibly distinct. Its core working elements are problem, scale trigger, risk, and current process. Those elements belong together because each changes how the others should be interpreted or acted on.

Diagnostic dimensions

Problem

Record only the context that changes the work, separating verified facts from interpretations and assumptions. Within the lightweight-process maturity check, connect this entry to scale trigger so the relationship can be reviewed rather than inferred.

Scale trigger

Record only the context that changes the work, separating verified facts from interpretations and assumptions. Within the lightweight-process maturity check, connect this entry to risk so the relationship can be reviewed rather than inferred.

Risk

Describe the cause, possible consequence, early warning signal, owner, and proportionate prevention or response. Within the lightweight-process maturity check, connect this entry to current process so the relationship can be reviewed rather than inferred.

Current process

Capture current process only at the level needed to answer: Is a process absent, appropriately lightweight, or heavier than the problem requires? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the lightweight-process maturity check, connect this entry to burden so the relationship can be reviewed rather than inferred.

Burden

Capture burden only at the level needed to answer: Is a process absent, appropriately lightweight, or heavier than the problem requires? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the lightweight-process maturity check, connect this entry to consistency so the relationship can be reviewed rather than inferred.

Consistency

Capture consistency only at the level needed to answer: Is a process absent, appropriately lightweight, or heavier than the problem requires? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the lightweight-process maturity check, connect this entry to failure evidence so the relationship can be reviewed rather than inferred.

Failure evidence

Name the evidence, its date and owner, and any limitation that affects how confidently it can be used. Within the lightweight-process maturity check, connect this entry to next experiment so the relationship can be reviewed rather than inferred.

Next experiment

Capture next experiment only at the level needed to answer: Is a process absent, appropriately lightweight, or heavier than the problem requires? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the lightweight-process maturity check, connect this entry to failure evidence so the relationship can be reviewed rather than inferred.