Skip to content

Normalizing Reference Progression

01.030.031.020.110 v20260810.001

Change Log

Purpose and Transition

The Normalizing Reference Progression illustrates the transition from M1 Improvised to M2 Normalized.

It describes common ways in which experience-dependent execution is converted into a defined, transferable, consistently applied, and governable operating baseline.

Reference Posture

This Reference Progression is illustrative and non-exhaustive. It does not define every Practice, Proficiency, control, evidence source, or exit criterion required for every subject. Registered Progression Patterns and a subject-specific Progression Application control the actual prescription.

Typical Transition Conditions

Advancement may be justified where:

  • outcomes depend materially on tacit knowledge or named experts;
  • work is repeatedly reinvented or performed inconsistently;
  • onboarding and succession are difficult;
  • quality and evidence vary by Player or occurrence;
  • basic accountability, terminology, controls, or exception handling are unclear;
  • the value at stake justifies greater repeatability and transferability.

Value Realization Pillar Relationships

Role Illustrative Pillars Rationale
Primary Practices Pillar, Players Pillar Normalization establishes common Practices and required Proficiencies that reduce dependence on individual improvisation.
Contributing Platforms Pillar, Products Pillar, Projects Pillar, Partners Pillar Tools, services, governed change, and counterparties may enable or constrain the standard baseline.
Affected All six Pillars Standardization may change roles, controls, interfaces, services, data, and Partner obligations.
Evidence-producing Practices Pillar, Players Pillar, Platforms Pillar, Products Pillar Observed adherence, comparable outputs, Proficiency demonstrations, telemetry, and service evidence support designation.

Illustrative Priority Outcomes and Effects

Possible Priority Outcomes

Possible Contributing or Protected Effects

  • Compliance Optimization;
  • Capacity Optimization;
  • Cost Optimization;
  • Confidence Optimization;
  • Contribution Optimization;

Normalization should protect justified flexibility and avoid codifying waste or obsolete work.

Illustrative Plays and Efforts

  • Define the Operating Boundary. Establish the scope within which a common baseline is required.
  • Observe the Effective Current Practice. Identify how successful work is actually performed before prescribing it.
  • Establish Controlled Terminology. Define the concepts, outputs, roles, and evidence consistently.
  • Define the Standard Practice. Document proportionate policies, processes, procedures, protocols, methods, and controls.
  • Define Required Proficiencies. State what Players must demonstrate to perform the standard Practice.
  • Establish Exception Governance. Distinguish authorized adaptation from unmanaged variation.
  • Institutionalize Knowledge Transfer. Establish onboarding, reference, coaching, and succession mechanisms.
  • Establish Baseline Evidence. Define minimum measures, records, and validation responsibilities.
  • Verify Consistent Application. Confirm that documented and actual operation align across the declared scope.

Illustrative Practices and Proficiencies

Possible Practices include standard-work definition, controlled documentation, role and decision-right definition, exception management, onboarding, knowledge transfer, baseline measurement, and periodic conformance review.

Possible Proficiencies include execution of the standard Practice, exception recognition, evidence production, knowledge transfer, coaching, and adaptation within governed boundaries.

Enabling Conditions

Common enabling conditions may include:

  • accountable ownership;
  • stable enough operating patterns to define a baseline;
  • access to effective practitioners and operating evidence;
  • proportionate documentation and knowledge Platforms;
  • common data definitions and basic authoritative sources;
  • training, coaching, and Proficiency demonstration mechanisms;
  • controls and escalation paths;
  • Projects or Initiatives to establish the baseline where material;
  • Partner alignment where the standard crosses organizational boundaries.

Illustrative Evidence

  • observed use of the standard Practice;
  • comparable outputs across Players, teams, or periods;
  • documented and governed exceptions;
  • demonstrated required Proficiencies;
  • repeatable onboarding and knowledge transfer;
  • defined accountability and decision rights;
  • baseline performance, quality, continuity, and control evidence;
  • alignment between documented and actual operation.

Characteristic Value Enablement

  • repeatability and transferability;
  • reduced key-person dependency;
  • improved continuity and succession;
  • clearer accountability;
  • faster onboarding;
  • comparable evidence;
  • baseline assurance;
  • a stable foundation for Rationalizing.

Characteristic Value Risk

  • standardizing waste or obsolete work;
  • excessive documentation and procedural burden;
  • superficial compliance;
  • rigidity that suppresses justified judgment;
  • hidden exceptions beneath formal standards;
  • false assurance where actual and documented Practices diverge;
  • premature standardization before sufficient operating learning exists.

Boundary Conditions and False Positives

The following do not independently establish M2 Normalized:

  • documentation that is not used;
  • training completion without demonstrated Proficiency;
  • a workflow tool configured without operating adoption;
  • a policy published without accountability and evidence;
  • isolated team consistency while the declared scope remains materially variable;
  • standardization that cannot be transferred or sustained;
  • a checklist completed without representative operating evidence.
  • Standard Practice Establishment;
  • Controlled Vocabulary Establishment;
  • Required Proficiency Definition;
  • Exception Governance;
  • Knowledge Transfer and Onboarding;
  • Baseline Evidence Establishment;
  • Documentation-to-Operation Alignment;
  • Minimum Control Baseline.

Limitations

Normalized maturity establishes a common baseline. It does not prove that the baseline is simplified, economically optimal, integrated, or valuable. Duplication and incoherence may remain and are addressed through the Rationalizing Progression where justified.