Transition Readiness Assessment

Assess whether conditions are sufficient to cross a threshold or begin a phase transition safely.

Solution archetype #

1096

Problem family

Timing, Transition & Path-Dependence Failure

Problem subfamily

Opportunity Window, Threshold & Readiness Timing

The Diagnostic Story

Symptom: The transition date is driven by a calendar commitment, a political announcement, or a budget deadline — not by evidence that the conditions for stable crossing are present. Hidden dependencies appear late: missing training, inadequate receiving capacity, incomplete documentation, no tested fallback. The system repeatedly starts, pauses, reverses, and tries again because nobody made readiness concrete before crossing.

Pivot: Define readiness criteria tied to transition stability, not approval preference. Measure preconditions before the threshold is crossed, classify gaps with owners and preparation paths, and produce a proceed, delay, condition, or abort decision that a legitimate authority can act on — not merely advisory commentary.

Resolution: Premature, unstable, or symbolic transitions drop because go/no-go decisions are grounded in visible evidence. Missing dependencies surface early enough to address before they become mid-transition crises. Post-transition outcomes feed back into future readiness criteria so the model improves over time.

Reach for this when you hear…

[hospital discharge planning] “The insurance is approved and the bed is needed, but I am not signing discharge until I know there's a home visit scheduled and someone has checked the staircase situation.”

[infrastructure migration] “We can't go live on the new system just because the contract says Monday — the data migration validation has not passed and the fallback procedure is not tested.”

[governance transition] “The election happened but if we transfer authority before the implementing legislation is in force we are handing over a mandate with no legal infrastructure to execute it.”

When This Archetype Applies

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

Diagnostic problem

A system is considering a transition, but the conditions needed for stable crossing may not be present.

What this problem means

The structural problem is premature transition under uncertain conditions. A system is considering movement into a new state, but the conditions required for the new state to hold are not guaranteed. The old state may be uncomfortable or costly, yet the new state may fail if capacity, support, dependency closure, stakeholder readiness, fallback, or evidence is missing.

The central tension is that both movement and delay have costs. Moving too early can damage the transition. Waiting indefinitely can preserve stagnation, waste effort, or miss opportunity. Transition Readiness Assessment converts this tension into an evidence-based sufficiency judgment.

Show the applicability expression

Applicability expression5 distinct conditions

Proposed state transitionandPremature crossing riskandAssessable transition prerequisitesandUncertain distributed prerequisitesandAvailable transition options

Algebraic1∧2∧3∧4∧5

groundedpartly groundedopen

5 conditions, all required.

5Required in every casenumbered 1–5

These hold no matter which pattern applies.

1

Proposed state transition · open

A transition, rollout, migration, discharge, return-to-service, reentry, or phase shift is being considered. more

and — also required

2

Premature crossing risk · open

Premature crossing would create instability, harm, rework, relapse, overload, failure, or loss of trust. more

and — also required

3

Assessable transition prerequisites · grounded

The transition has identifiable preconditions that can be assessed before crossing. more

and — also required

4

Uncertain distributed prerequisites · open

Some preconditions are uncertain, incomplete, unevenly distributed, or dependent on actors outside the focal team. more

and — also required

5

Available transition options · open

There is still time to delay, narrow, stage, prepare, or abort the transition based on evidence. more

Other requirements and context (1)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

• Supporting contextA legitimate decision authority can act on the assessment rather than treating readiness as only advisory commentary. more

Coverage

1 of 5 conditions grounded · 4 open.

Read the methodology · Download the trigger-logic data

Mechanisms / Implementations

• Clinical Discharge Readiness Check: A bedside check of whether a patient is stable and supported enough to move to a lower level of care — judged from clinical evidence rather than a target date, sometimes rehearsed with a trial pass, and confirmed by watching how they do afterward.
• Disaster Reentry Check: A staged protocol that clears people and services to return to a disrupted area only once the utilities, access, and support systems they depend on are confirmed restored and a way to pull back out again still exists.
• Gap Remediation Plan: Turns each unmet readiness criterion into a scheduled task with an owner, a due date, the dependencies it must close, and the retest that will prove it fixed — converting 'not ready' into a route to ready.
• Go / No-Go Meeting: A convened decision event where an accountable authority polls every readiness stakeholder for a go or no-go and converts the assembled findings into one explicit call — proceed, proceed-with-conditions, delay, or abort.
• Launch Readiness Review: Convenes every function that owns a piece of a public launch to confirm the target is defined, all owners are go, and no cross-team dependency is still open before the switch is flipped.
• Migration Readiness Assessment: A pre-stage go/no-go check that a tested fallback exists and every continuity provision is in place, so a cohort commits to moving only when it could still safely turn back.
• Operational Readiness Review: Checks whether the receiving operation can actually run, support, watch, and recover the new state in production — staffing, runbooks, monitoring, and a tested rollback — before it is switched on.
• Phase-Gate Review: A recurring gate between program phases that names the next state, fixes the criteria for entering it, and checks whether current conditions actually clear that bar before work is allowed to advance.
• Preflight Checklist: A fixed, compact list of must-pass conditions run the same way immediately before a repeatable crossing — each item a binary go/no-go against a known failure mode, so nothing routine gets skipped under pressure.
• Readiness Scorecard: Rolls every readiness criterion onto one visible board — each rated, evidence-backed, confidence-tagged, and severity-scored — so a decision-maker sees the whole readiness picture and its worst gaps at a glance.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

• Phase Diagram: Maps system states.
• State and State Transition: Captures system condition and evolution.
• Threshold: Safe vs harmful levels.

Also references 11 related abstractions

• Adaptation: Systems adjust to conditions.
• Boundary: Defines system limits.
• Closure: Ensures operations remain within a set.
• Constraint: Limits possibilities to guide outcomes.
• Controllability: Ability to steer system.
• Cost–Benefit Analysis: Evaluate decisions.
• Feedback: Outputs influence inputs.
• Observability: Infer internal state externally.
• Pipeline: Sequential processing stages.
• Resilience: Absorb shocks and adapt.

▸ Show 1 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Rollout Readiness Assessment · domain variant · recognized

Assess whether a product, service, policy, curriculum, or process is ready to move from pilot or preparation into broader rollout.

Migration Readiness Assessment · domain variant · recognized

Assess whether a system, data set, user population, or operational process is ready to move from one platform, environment, or operating model to another.

Clinical or Care Transition Readiness · domain variant · recognized

Assess whether a person can safely move from one care state, setting, or level of supervision to another.

Reentry Readiness Assessment · domain variant · recognized

Assess whether conditions are sufficient for return to a previously restricted, evacuated, suspended, or disrupted state.

Editorial Notes

Problem Classification

Classification: Timing, Transition & Path-Dependence Failure → Opportunity Window, Threshold & Readiness Timing

Problem kernel: a proposed transition lacks verified crossing and stabilization conditions

Rationale: Earliest causal condition: A system is considering a transition, but the conditions needed for stable crossing may not be present.

Independent corroboration: The earliest necessary condition in the frozen evidence is: A system is considering a transition, but the conditions needed for stable crossing may not be present. That is a opportunity window threshold and readiness timing problem because Preparation and action fail to coincide with a bounded state of receptivity, malleability, advantage, or threshold readiness.

Review outcome: Independent reviewer agreement; high confidence.