Phase Specific Intervention

Use different interventions in different phases because each regime responds differently.

Version

v1 · 2026-08-24 · History

Solution archetype #

753

Problem family

Adaptation, Variation & Context Misfit

Problem subfamily

Heterogeneous Case & Pathway Misfit

Essence

Phase-Specific Intervention is the pattern of changing the intervention because the system is in a different phase. It starts from the premise that a system may look like one object while behaving like several different systems over time: launch is not maturity, acute crisis is not recovery, early learning is not expert performance, and ecological establishment is not succession. The archetype asks: what phase are we in, why does that phase respond differently, what action fits this phase, and when must the response change?

The core move is not merely to draw a phase diagram. The core move is to bind phase diagnosis to action selection, contraindications, handoffs, and feedback.

Compression statement

When a system's response changes by phase, tailor interventions to the current phase rather than applying one uniform policy.

Canonical formula: phase_classifier + phase_condition_model + action_by_phase + contraindication_map + transition_indicator + handoff_rule + feedback_monitor → phase-matched intervention with lower wrong-phase harm

When This Archetype Applies

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

Diagnostic problem

An intervention effective in one phase is ineffective or harmful in another phase, but the system is being treated as if one uniform action applies across all phases.

What this problem means

The structural problem is phase mismatch. Actors apply one rule across a system whose behavior changes by phase. The result may be premature escalation, delayed support, stale emergency mode, advanced practices imposed before prerequisites exist, or late-stage maintenance applied during early experimentation.

The deeper tension is that systems need coordination and consistency, but phase-sensitive systems also need differentiated action. Too much uniformity produces wrong-phase interventions; too much differentiation produces complexity, unfairness, and fragmentation.

Applicability expression4 distinct conditions

Distinct system phasesandPhase-varying causal structureandHarmful uniform interventionandApproaching phase boundary

Algebraic1∧2∧3∧4

groundedpartly groundedopen

4 conditions, all required.

4Required in every casenumbered 1–4

These hold no matter which pattern applies.

1

Distinct system phases · grounded

The system has distinguishable lifecycle, hazard, crisis, disease, developmental, or maturity phases. more

primeEvent Lifecycle Phases— Decomposing a hazard-bearing event into pre-event, event, and post-event regimes and treating each phase, not the event, as the primary unit of intervention design.

and — also required

2

Phase-varying causal structure · grounded

Causal conditions, risks, constraints, sensitivities, levers, or stakeholder needs change materially by phase. more

primeEvent Lifecycle Phases— Decomposing a hazard-bearing event into pre-event, event, and post-event regimes and treating each phase, not the event, as the primary unit of intervention design.

and — also required

3

Harmful uniform intervention · grounded

One uniform intervention would mistime, over-treat, under-treat, destabilize, or delegitimize at least one phase. more

primeEvent Lifecycle Phases— Decomposing a hazard-bearing event into pre-event, event, and post-event regimes and treating each phase, not the event, as the primary unit of intervention design.

and — also required

4

Approaching phase boundary · open

The system may be approaching a phase boundary where action rules must change. more

Other requirements and context (3)

Why these sit outside the expression

Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.

Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.

Deployment constraint — it constrains how the intervention must be deployed, not the situation that calls for it.

• Solution feasibilityThere is enough observability to classify the current phase or at least reason about phase uncertainty. more

• Application gateActors must decide what to do now, not only how to represent the phase diagram or state model. more

• Deployment constraintThe intervention needs to preserve continuity across phase transitions while changing enough to fit the new phase. more

Coverage

3 of 4 conditions grounded · 1 open.

Read the methodology · Download the trigger-logic data

When to Use This Archetype

Use this archetype when a uniform response is creating wrong-time or wrong-phase harm. It is especially relevant when phases have different objectives, sensitivities, available levers, stakeholder needs, or transition risks. It works best when the system can classify its current phase with enough confidence, monitor when that classification changes, and explain why different phases deserve different interventions.

It is useful in clinical staging, incident response, product lifecycle management, organizational maturity, ecological restoration, public-policy rollout, education, and behavior-change support. In each case, the same generic action may be helpful in one phase and damaging in another.

Structural Problem

The structural problem is phase mismatch. Actors apply one rule across a system whose behavior changes by phase. The result may be premature escalation, delayed support, stale emergency mode, advanced practices imposed before prerequisites exist, or late-stage maintenance applied during early experimentation.

The deeper tension is that systems need coordination and consistency, but phase-sensitive systems also need differentiated action. Too much uniformity produces wrong-phase interventions; too much differentiation produces complexity, unfairness, and fragmentation.

Intervention Logic

The intervention begins by defining phases only where phase differences change action. It then builds a causal phase condition model, classifies the current phase, maps actions and contraindications by phase, monitors transition indicators, and updates the response when the system enters a new phase.

A strong implementation also defines handoff rules. When a crisis moves from containment to recovery, or a product moves from growth to maturity, authority, communication, resources, and success criteria often need to change. Feedback then revises both the phase classification and the action map.

Key Components

Phase-Specific Intervention treats a system as something whose behavior shifts over its life, then binds diagnosis of the current phase to a different choice of action. The Phase Classifier decides which phase the system is in right now, but classification alone is cosmetic without a causal account; the Phase Condition Model explains why each phase responds differently, so the labels carry real action consequences. Action by Phase maps those phases to the supports, constraints, and communication that fit, while the Phase Contraindication Map names what is useful in one phase but harmful, premature, or illegitimate in another. Together these four components turn a phase model into a working intervention rule rather than a description.

The remaining components govern how the rule moves through time and how it survives uncertainty. The Transition Boundary Indicator watches for evidence that the system is crossing into another phase and the action set should change, and the Phase Handoff Rule governs how authority, resources, and procedures move cleanly across that boundary so continuity is preserved. The Adaptation Rule handles ambiguous or mixed-phase cases without forcing rigid categorization, and the Exception Review Path provides a route for cases that fall outside the standard model. The Phase Feedback Monitor checks whether the current phase-matched intervention is actually working and whether the phase classification still holds, while the Phase Transition Memory accumulates lessons across repeated transitions so the action map, contraindications, and indicators improve with experience.

Component	Description
Phase Classifier ↗	Determines which phase, stage, regime, or operating state the system is currently in before action is selected.
Phase Condition Model ↗	Explains why the system responds differently by phase, so phase labels are causally meaningful rather than cosmetic.
Action by Phase ↗	Maps each recognized phase to appropriate actions, supports, constraints, and communication rules.
Phase Contraindication Map ↗	Identifies actions that are useful in one phase but harmful, premature, or illegitimate in another.
Transition Boundary Indicator ↗	Tracks signs that the system is crossing into another phase and the action set should change.
Phase Handoff Rule ↗	Defines how authority, responsibility, resources, or procedures move between phase-specific responses.
Adaptation Rule ↗	Handles uncertainty, mixed phases, and contested phase diagnosis without forcing rigid categorization.
Phase Feedback Monitor ↗	Tests whether the current phase-specific intervention is working and whether the phase classification remains valid.
Exception Review Path ↗	Allows review or override when a case does not fit the normal phase model.
Phase Transition Memory ↗	Captures what worked across phases so future phase rules can improve.

Common Mechanisms

Mechanisms implement the archetype; they are not the archetype itself. A clinical staging protocol, crisis playbook, lifecycle policy, or maturity model becomes an implementation of Phase-Specific Intervention only when it connects phase diagnosis to different actions, contraindications, handoffs, monitoring, and revision.

Common mechanism families include lifecycle-stage policies, disease-stage treatment protocols, incident phase playbooks, product lifecycle strategies, market regime strategies, ecological phase management, education scaffolding by stage, maturity model guidance, escalation/de-escalation matrices, and stage-specific communication plans.

10 documented mechanisms across 6 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Assessment, Review & Assurance · 1 mechanism

• Maturity Model Guidance — Implements the archetype by tying recommended practices to capability maturity stages rather than recommending the same practice to every organization.

Communication, Facilitation & Learning · 1 mechanism

• Education Scaffolding by Stage — Implements the archetype by matching supports, prompts, autonomy, feedback, and challenge level to the learner or cohort stage.

Control, Automation & Runtime · 2 mechanisms

• Ecological Phase Management — Implements the archetype by changing restoration, protection, disturbance, harvesting, invasive control, or monitoring actions according to ecological succession or regime phase.
• Market Regime Strategy — Implements the archetype by selecting different risk, pricing, liquidity, hedging, or operating strategies under expansion, contraction, stress, recovery, or shock phases.

Protocol, Workflow & Routine · 2 mechanisms

• Disease-Stage Treatment Protocol — Implements the archetype when diagnosis, treatment intensity, contraindications, monitoring, or follow-up differ across disease stage or recovery phase.
• Incident Phase Playbook — Implements the archetype by using different response modes for detection, containment, stabilization, recovery, communication, postmortem, and prevention phases.

Representation, Specification & Plan · 1 mechanism

• Stage-Specific Communication Plan — Implements the archetype by matching message content, audience, timing, tone, and disclosure level to the current phase of a project, crisis, treatment, negotiation, or rollout.

Rule, Policy & Commitment · 3 mechanisms

• Escalation/De-escalation Matrix — Maps the current severity or phase to a graded response tier, with explicit thresholds for escalating up and de-escalating down and defined ownership at each level.
• Lifecycle-Stage Policy — Implements phase-specific intervention by assigning different policies, supports, constraints, or review duties to startup, growth, maturity, decline, renewal, or sunset stages.
• Product Lifecycle Strategy — Implements the archetype by changing investment, marketing, reliability, migration, pricing, support, and retirement actions according to product lifecycle phase.

Parameter / Tuning Dimensions

Important tuning dimensions include phase granularity, classification confidence, phase transition thresholds, response intensity by phase, degree of local adaptation, handoff timing, exception authority, review cadence, and tolerance for mixed-phase segmentation. Too few phases create mismatch; too many phases create bureaucracy and coordination failure.

Invariants to Preserve

The intervention should preserve actionable phase definitions, transparent criteria, reviewability, phase-appropriate support, continuity across handoffs, feedback-driven revision, and protection against unfair gatekeeping. Phase labels should remain tools for better intervention, not status labels or permanent identities.

Target Outcomes

The target outcomes are fewer wrong-phase interventions, better timing of support or constraint, clearer handoffs, reduced over-treatment and under-treatment, more accountable stage-based decisions, and improved learning across repeated phase transitions.

Tradeoffs

The main tradeoff is fit versus simplicity. Phase-specific rules improve intervention fit but increase operational complexity. Precision can become brittleness when classification is uncertain. Segmentation can improve fairness when groups are truly in different phases, but it can also produce opaque or inequitable treatment if criteria are poor.

Failure Modes

Common failure modes include wrong-phase classification, stage-label bureaucracy, premature escalation or de-escalation, stale playbooks, over-fragmentation, aggregate phase mismatch, and gatekeeping by phase label. These failures are mitigated by clear criteria, contraindication maps, feedback monitors, transition indicators, exception review, and equity checks.

Neighbor Distinctions

This archetype is distinct from Regime Map Navigation, which builds and navigates the map of operating regimes. Phase-Specific Intervention uses a phase diagnosis to choose the right action. It is distinct from Transition Readiness Assessment, which decides whether conditions are sufficient to cross a threshold. It is distinct from Controlled Phase Transition, which deliberately moves the system between phases. It is distinct from Therapeutic Window Management, which manages safe ranges of intensity, and from Stratified Treatment, which usually differentiates response by stable subgroup characteristics rather than changing phase.

Cross-Domain Examples

In clinical care, treatment changes across acute, stabilization, rehabilitation, and maintenance phases. In incident response, detection, containment, recovery, and learning require different actions. In product management, launch, growth, maturity, and sunset require different investment and communication. In ecological restoration, intervention changes across colonization, establishment, succession, and disturbance recovery. In education, support changes as learners move from novice dependence to independent performance.

Non-Examples

A phase diagram that does not alter decisions is not this archetype. A readiness checklist that only says proceed or delay is not this archetype unless it also maps actions by current phase. A universal safety rule that must apply identically in every phase is not this archetype. A maturity label used mainly for ranking, stigma, or exclusion is misuse, not Phase-Specific Intervention.

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.
• Stratification: Layered separation of a system.
• Therapeutic Window: Optimal input range.

Also references 7 related abstractions

• Adaptation: Systems adjust to conditions.
• Boundary: Defines system limits.
• Contextual Mode Switching: Adapt communication.
• Feedback: Outputs influence inputs.
• Observability: Infer internal state externally.
• State and State Transition: Captures system condition and evolution.
• Threshold: Safe vs harmful levels.

Variants

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

Lifecycle Phase Intervention · temporal variant · recognized

Tailor interventions to predictable lifecycle phases such as launch, growth, maturity, decline, renewal, or sunset.

• Distinct from parent: This variant emphasizes lifecycle timing, while the parent includes any phase-dependent response, including crisis, clinical, ecological, and market phases.
• Use when: The system progresses through recognizable lifecycle phases; The appropriate support, constraint, investment, or communication changes as the lifecycle phase changes; The main risk is applying early-stage or late-stage actions at the wrong time.
• Typical domains: product management, organizational development, education, public programs
• Common mechanisms: lifecycle stage policy, product lifecycle strategy, maturity model guidance

Crisis Phase Response · temporal variant · recognized

Use different interventions in detection, escalation, containment, stabilization, recovery, and learning phases of a crisis.

• Distinct from parent: This variant focuses on crisis time structure and operational handoff rather than all phase-dependent systems.
• Use when: The system is moving through a crisis or incident with changing objectives; Actions appropriate in active containment would be harmful in recovery or learning phases; Authority, communication, or resource allocation must shift as the crisis phase changes.
• Typical domains: incident response, public health, organizational crisis, cybersecurity
• Common mechanisms: incident phase playbook, escalation deescalation matrix, stage specific communication plan

Capability Maturity Intervention · implementation variant · recognized

Recommend different practices according to capability maturity rather than prescribing advanced practices to immature systems.

• Distinct from parent: It is a readiness- and maturity-oriented variant of phase-specific intervention.
• Use when: Organizations, learners, teams, or infrastructures have different capability stages; Advanced interventions fail when prerequisites are absent; A development path should sequence practices without treating every case as identical.
• Typical domains: organizational change, security programs, learning design, operations maturity
• Common mechanisms: maturity model guidance, education scaffolding by stage

Mixed-Phase Targeting · scale variant · likely subtype

Apply different phase-specific interventions to subgroups or regions that occupy different phases simultaneously.

• Distinct from parent: The parent may assume a single current phase; this variant explicitly manages simultaneous phase heterogeneity.
• Use when: The aggregate system hides phase differences among subgroups, regions, cohorts, assets, or cases; A uniform policy would over-treat one subgroup and under-treat another; Segmentation can be done without unacceptable complexity or inequity.
• Typical domains: public health, market operations, education, ecological restoration
• Common mechanisms: market regime strategy, ecological phase management, stage specific communication plan
• Evidence: US6007869A; Selective microwave heating of solid phase relative to gas; Microwave selective heating review

Observe Now Correct At Safe Transition · temporal variant · recognized

Record irreversible drift in the state where it becomes observable, but apply the compensating adjustment only during the next unloaded transition.

• Distinct from parent: The transition is not gated by readiness; rather, observation occurs when drift is visible and correction is deferred to the next safe unloaded window. This is a phase-separated intervention architecture with stale-observation and residual-load failures.
• Use when: Progressive lining wear changes clutch clearance, but adjusting during the loaded operating state risks unintended movement or false compensation.
• Evidence (strong independent recurrence confirmed): US5560463A; In-process tool-wear monitoring and offset compensation; CNC tool offsets applied between cuts

Removable Ballast / Permanent Guided Mobility · reversible state configuration variant · recognized

Convert between stable and mobile states by making operating ballast removable while keeping guided mobility in the permanent base.

• Distinct from parent: Phase-Specific Intervention owns changing the intervention by operating phase. The child assigns ballast to the stable-service phase and keeps mobility hardware in the permanent base for the relocation phase, with omitted reballasting and loaded-motion failures that current lifecycle and crisis variants do not preserve.
• Use when: A large shade needs heavy ballast for wind stability in use, but that same mass makes repositioning laborious.
• Evidence (strong independent recurrence confirmed): US10813425B2; Spalding portable basketball system manual; Spalding hoops buying guide

Near names: State-Specific Response, Stage-Specific Policy, Regime-Specific Action, Phase-Matched Response, Stage-of-Change Matching.

Editorial Notes

Problem Classification

Classification: Adaptation, Variation & Context Misfit → Heterogeneous Case & Pathway Misfit

Problem kernel: uniform intervention ignores phase-specific response regimes

Rationale: System phases differ materially in behavior, vulnerability, leverage, and treatment response, yet one uniform intervention treats them as interchangeable and becomes ineffective or harmful in some regimes. Opportunity timing concerns acting inside one bounded readiness window; this record requires distinct routes across multiple phases rather than merely choosing the correct moment for one action.

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

Why this classification prevailed: Heterogeneous-pathway misfit concerns different interventions required across regimes; opportunity timing concerns one action missing a bounded state of receptivity, advantage, or readiness.

Review outcome: Adjudicated after independent review; high confidence.