Skip to content

Improvising Reference Progression

01.030.031.020.100 v20260810.001

Purpose and Transition

The Improvising Reference Progression illustrates the transition from M0 Conceptualized to M1 Improvised.

It describes common ways in which a governed concept is placed into actual or sufficiently representative operation so that initial experience, situational knowledge, operating Practices, Player Proficiencies, enabling conditions, exceptions, and evidence can emerge.

Reference Posture

This Reference Progression is illustrative and non-exhaustive. It is not a universal checklist or complete prescription. Applicable requirements must be established through registered Progression Patterns and a subject-specific Progression Application.

Typical Transition Conditions

Advancement may be justified where:

  • the subject is sufficiently defined but has not operated;
  • assumptions require exposure to real operating conditions;
  • accountable Players need practical experience before standardization is possible;
  • a minimum viable Capability or Competency expression can be exercised safely;
  • the expected value and risks justify bounded experimentation;
  • continued conceptual refinement without operating evidence would create delay or false confidence.

Value Realization Pillar Relationships

Role Illustrative Pillars Rationale
Primary Players Pillar, Practices Pillar, Projects Pillar Initial operation depends on accountable Players, emergent Practices, and governed work that places the concept into use.
Contributing Platforms Pillar, Products Pillar, Partners Pillar Enabling foundations, usable propositions, and counterparties may be necessary to create a representative operating context.
Affected All six Pillars Initial operation may change roles, dependencies, Products, Platforms, Practices, Partner relationships, and governed work.
Evidence-producing Players Pillar, Practices Pillar, Projects Pillar, Products Pillar Observed execution, decisions, exceptions, use, and outputs provide the principal evidence that the subject operates.

Illustrative Priority Outcomes and Effects

Possible Priority Outcomes

  • Capability Optimization;
  • Competency Optimization;
  • Confidence Optimization;

Possible Contributing or Protected Effects

  • Control Optimization;
  • Continuity Optimization;
  • Compliance Optimization;
  • Cost Optimization;
  • Capacity Optimization;
  • Contribution Optimization.

The Progression should preserve safety, compliance, continuity, and controlled exposure where experimentation could create material harm.

Illustrative Plays and Efforts

  • Bound the First Operating Context. Define where, for whom, and under what constraints the subject will initially operate.
  • Assign Initial Accountability. Identify who owns the outcome, decisions, evidence, and adjustment.
  • Establish the Minimum Viable Practice. Define the least operating discipline necessary for purposeful and safe execution.
  • Enable the Initial Players. Provide the minimum Proficiencies, authority, access, information, and support needed to act.
  • Exercise in Representative Conditions. Perform the work in actual or sufficiently representative circumstances.
  • Capture Operating Evidence. Record decisions, actions, outputs, exceptions, outcomes, and limitations.
  • Convert Exceptions into Learning. Use encountered variation to refine the concept and expose future normalization requirements.
  • Review Value and Risk. Test whether continued establishment remains fit-for-value.

Illustrative Practices and Proficiencies

Possible Practices include bounded experimentation, decision logging, exception capture, initial risk control, learning review, and value-hypothesis testing.

Possible Proficiencies include situational judgment, initial work performance, exception handling, evidence capture, risk recognition, and adaptation based on operating feedback.

These are illustrative. The required Practices and Proficiencies depend on the maturity subject and operating context.

Enabling Conditions

Common enabling conditions may include:

  • explicit scope and value rationale;
  • accountable sponsorship and decision rights;
  • minimum viable Players and Proficiencies;
  • safe operating boundaries and controls;
  • sufficient Platform and Product availability;
  • access to representative data and information;
  • Partner participation where the operating context crosses organizational boundaries;
  • a Project, Initiative, pilot, or other governed work object where appropriate;
  • a defined evidence and learning cadence.

Illustrative Evidence

  • observed performance in operating or representative conditions;
  • actual decisions, transactions, outputs, or service events;
  • evidence of accountable Player participation;
  • use or consumption by an intended Consumer where applicable;
  • captured exceptions, workarounds, and learning;
  • evidence that the subject exists in operation rather than only in design;
  • evidence that material risks and constraints were governed proportionately.

Characteristic Value Enablement

  • converts assumptions into operating knowledge;
  • reveals real dependencies and constraints;
  • develops initial Player Proficiencies;
  • enables earlier learning and adaptation;
  • reduces prolonged analysis without evidence;
  • creates the evidence basis required for future Normalizing.

Characteristic Value Risk

  • uncontrolled experimentation;
  • overreliance on one expert or early adopter;
  • premature scaling of an unstable subject;
  • mistaking a demonstration for sustained operation;
  • local success that does not represent the declared scope;
  • failure to capture learning;
  • sunk-cost continuation after the value hypothesis weakens.

Boundary Conditions and False Positives

The following do not independently establish M1 Improvised:

  • approving a concept or business case;
  • completing a design or architecture;
  • configuring a Platform without operating the Capability;
  • running a scripted demonstration that avoids representative conditions;
  • assigning roles without observed performance;
  • completing training without demonstrated Proficiency;
  • producing isolated outputs without accountable and repeatable operating activity.
  • Minimum Viable Operating Context;
  • Initial Accountability Establishment;
  • Operating Evidence Capture;
  • Bounded Experimentation;
  • Exception-to-Learning Conversion;
  • Minimum Viable Control;
  • Value Hypothesis Revalidation.

Limitations

The Improvising Progression establishes operating evidence. It does not establish repeatability, standardization, economic justification, scalability, or realized value. Those claims require separate evidence and, where appropriate, later Progressions.