Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:15:20 UTC

OPS.16 - Decide Whether and How to Change an Operating Method

Status: Stable

OPS.16:0 - Use This When

Use this Method when delay, rework, recurring failure, burden or a changed condition raises a question about continuing or changing a way of operating. Identify whether the way is already admitted as U.Method or is provisionally identified through a source-traceable A.3.1.MR candidate account.

For an admitted Method, identify the Method and the version or U.MethodDescription relied on, its operating use, any proposed change, and the decision the available evidence supports. For a candidate, identify the proposed reusable way through its source-traceable account, with its live rivals, gaps and use limits. Neither a U.Method nor a U.MethodDescription has yet been established for that candidate. Existing grounds may suffice to revise, compare or retain the account, or to stop. Consider another observation or trial when its attainable contribution to the decision or its grounds justifies the work.

Use OPS.17 when the current question is which operating Method or candidate from a repertoire deserves comparison. Use OPS.18 when existing evidence already calls for one quality or reliability control response. Use OPS.19 when simultaneous Work across cases or scales must first establish a feasible trial and protected conditions. Use current A.3.1.WT–A.3.1.MV, C.11.MV and A.3.1.MI when the specialist question is trial design, coherence, fit, worth, lineage, introduction, or revision without the receiving Operations decision.

Recognition concerns a recurring way of working rather than only one case. Assurance establishes the selected status branch and the evidence for its bounded decision. Existing Work observations can supply that evidence when their subject and conditions fit. A newly performed trial needs a prospective plan; claims about actual Work need independent occurrence support and observations qualified for their use.

OPS.16:1 - Problem frame

Review an operating Method when changes in demand, services, constraints, technology, participants or protection conditions could affect its use. Use the evidence that bears on the proposed revision. Where performance matters, distinguish the Work supported by observations from what a prior plan, if available, shows was intended.

Improvement language often collapses those distinctions. A proposed way is named as a new version before its reusable semantics have been admitted. A trial schedule is reported as completed Work. A tool output is treated as the operating result. One successful case becomes proof of effectiveness or transfer. The resulting decision can widen an unsupported practice or discard a useful incumbent for the wrong reason.

Given an admitted Method or a status-preserved candidate account, what bounded operating decision is justified by the Work observations and other qualified grounds now available?

OPS.16:2 - Problem

An operating team needs to improve one way of working without turning local learning into an uncontrolled change. The team must preserve service, reliability, human recovery, permission, and other protected conditions while obtaining evidence that can distinguish current, revised, branched, stopped, and still-uncertain alternatives.

The evidence rarely arrives as one result. Actual Work can show that a readiness rule was followed, while service evidence remains too short to establish reliability, fit elsewhere is unknown, burden is only partly observed, and a changed provider invalidates a description. Combining these observations into one improvement score hides the decision boundary.

Before Method admission, a candidate account can guide a distinguishing observation while its reusable-way identity remains unsettled. Preserve that uncertainty instead of reporting Method adoption.

OPS.16:3 - Forces

ForcePractical tension
learning and continuityA trial must expose a useful difference while the continuing operation still needs service, recovery, safety, and support.
status and actionPractitioners need to act on a promising way, while a candidate account cannot be treated as an admitted Method.
plan and occurrenceA prospective plan specifies intended trial Work; existing observations and any available prior plan must be recovered without inventing what was intended or performed.
local evidence and wider useOne bounded trial can settle a local choice while leaving transfer, general reliability, practical worth, and causality unresolved.
change and lineageA reusable semantic change can require a Method variant, while a changed tool, description, support, or departure may leave Method identity unchanged.
speed and assuranceA small trial can reduce delay, but it must stop if the required authority is missing or a protection condition no longer holds.
one decision and many observationsService, flow, human condition, finance, burden, side effects, and missing evidence can all matter without becoming one score.

OPS.16:4 - Solution

Preserve the distinction between an admitted Method and a candidate account from the initial question through the conclusion. Either branch can finish on sufficient current evidence. Under A.3.1.MR a candidate account may be revised, retained, compared or set aside. If the remaining question warrants a trial, state the change hypothesis and alternatives, establish the operating conditions and plan the Work. For existing observations and new ones, distinguish intended from performed Work, identify what was observed and establish its evidential reach. Make a decision within the authority and grounds available, or state what limits it.

OPS.16:4.1 - Fix the operating question and status branch

Name the operating System, Work family or service, current difficulty, receiving decision, decision maker, horizon, and protected conditions. Use the available identity and admission evidence to select the applicable branch.

Starting branchRequired identityFirst decision-facing statement
admitted MethodExact U.Method, exact relied-on Method version or separately classified U.MethodDescription, current operating use, maintained claim, and evidence windowDoes the evidence support continuing the present use, adopting, revising, branching or stopping, or making a further observation?
pre-admission candidateExact A.3.1.MR candidate-account episteme for the provisionally distinguished reusable way, source support, any live rivals and gaps, use limits and explicit non-admission; a distinguishing question only when it changes useWhich identity-test, account-revision, comparison, stop or selected further-observation result can this basis support?

A candidate label such as “v2”, a checklist, a repeated local habit, or a repository entry does not move the second row into the first. When admission is needed, apply A.3.1 to the reusable way and A.3.2 to any separate description episteme. Use established results where available. A way without an established admission remains in the candidate branch.

Start with the existing improvement account. A competent PDSA record may already distinguish prediction, proposed test, actual observations, adaptation and later implementation. Reuse it. For the branch selected above, reuse any established identity and status; supply the missing Method or candidate-account distinctions needed by the receiving decision. Qualify a stronger evidence claim only when the decision uses it. Include the cost of maintaining these distinctions, obtaining support and displacing service in the comparison. If existing observations may settle the decision, recover the occurrences, their conditions and any prior plan available, then use :4.5–4.9 to judge their reach. Evidence of performance can suffice even when the prior intention is unknown. Use :4.3–4.4 to arrange new trial Work only for a remaining question whose obtainable answer warrants that work.

OPS.16:4.2 - State a bounded change hypothesis and alternatives

When a change is being examined, write the hypothesis in operating terms: for the named use and interval, changing the specified action or condition is expected to alter a named operating result without violating stated protections. Identify observations that could support or challenge the hypothesis, and how they would affect the decision or the grounds for it.

Use OPS.11.1 when the question requires reconstructing the current and proposed networks of transformations, resources and enabling conditions. Its :4.2a constructs alternative arrangements from a required result and their professional contributions when the proposed way has not yet been supplied. Compare that construction before treating a named change as the only trial candidate. State which operation, input, output, release rule, resource assignment or receiving commitment changes. Preserve the distinction between changing the operating route, changing the reusable way described, and establishing changed relations or capabilities in the organization. A change in one does not establish the other two.

Keep materially different, status-preserved alternatives in view:

  • continue the current admitted Method or current observed practice for its supported use;
  • use a revised admitted Method where its identity and description are already established;
  • retain or test a candidate account without calling it a Method;
  • branch an admitted Method by a real applicability or semantic difference;
  • stop the proposed change or seek another observation.

Use OPS.17 if serious candidates still need to be found or compared. Use an OPS.19 result when it establishes or changes the feasible trial Work or a protected condition. In a trial, preserve the alternatives whose differences matter to the receiving choice or its grounds.

OPS.16:4.3 - Establish the conditions for running the trial

Recover the service, reliability, human-condition, access, permission, support, recovery, and resource conditions on which the trial relies. State the basis, interval and responsible party for each condition. Use existing resource, schedule and service results from OPS.10–OPS.13 or OPS.19 where they establish the required arrangement. Count existing assignments, trial work, learning and support against the same actual resources.

Use access, support and work allocations already provided under current arrangements. Obtain any missing contribution from its provider. Use an organization-change result when the proposal needs to change the contribution, responsibility or authority arrangement itself, rather than use it for another case. Granting already-permitted tool access can be an administration service; transferring responsibility for accepting a result needs the corresponding organizational and professional decisions. Use a sufficient authorized result directly; OCE supplies design or coordination where that question remains unresolved, and OCE.11 coordinates the organization change with continuing service when needed. Obtain any missing capability or practice support from its appropriate development or introduction method.

A conditional WorkPlan can name a missing arrangement and the decision needed to establish it. Before starting the dependent trial Work, confirm that its allocation, permitted overlap, service protection, support, recovery and hand-back conditions hold for the required interval. A prospective plan does not establish their availability. If a condition is missing, keep the affected trial Work closed, as an OPS.19 decision may require, and state what can still proceed.

OPS.16:4.4 - Plan new trial Work when needed

For a selected new trial, plan Work whose attainable contribution to the question justifies its burden. If a smaller trial would provide a sufficient answer, use it. Name intended tasks, proposed performers, admitted constituent Methods expected to be enacted, supports, protected conditions, observations, burdens, stop rules, hand-back and later receiving uses. Keep this WorkPlan prospective and identify the interval during which its premises must remain current. Existing Work is examined from its actual evidence and any plan available for it; do not write a retrospective intention as though it preceded the Work.

A compact plan can use these positions:

PositionWhat to state
status-preserved subjectExact admitted Method and relied-on description, or exact candidate account and its missing admission basis
operating questionCurrent use, proposed change, comparison, decision maker, and observation needed to decide or support the choice
intended WorkTasks, proposed performers, expected admitted constituent Methods, containing System, and temporal window
conditions and stopsAuthority, permission, support, service, recovery, human protection, fallback, and hand-back
observationsDirect subjects, measures or descriptions, collection point, burden, and later receiving use
returnSupported decision branches, limits on stronger uses, and any still-needed observation or revision condition

A.15.2 governs this prospective WorkPlan; section 4.5 establishes what actually occurred.

OPS.16:4.5 - Establish actual Work and direct results separately

For existing observations or after a new trial interval, identify only Work that actually occurred. For each Work occurrence, recover the actual performer, temporal extent, containing System and enacted admitted Methods under A.15.1; identify a departure only against an established plan or applicable rule. Identify each direct result through its relevant domain owner. Keep later service Work, recovery Work, observation Work and decision Work as separate wholes where their identities require it.

Never record the candidate reusable way or its candidate account as enacted. In the pre-admission branch, actual Work may enact independently admitted constituent Methods and may supply observations relevant to the candidate account. It does not enact the candidate whole.

A completed task also does not prove a Method change. A changed board, prompt, tool, description, support arrangement, or local departure changes Method identity only when reusable Method semantics change under A.3.1. Keep the changed object and direct relation instead when they do not.

OPS.16:4.6 - Type observations by subject and receiving use

Keep the subject and evidential reach of each material observation visible in the decision.

Observation positionDirect subject and useUnsupported stronger reading to avoid
operating resultThe named Work or operating System result for the selected intervalThe changed Method caused a general improvement.
service or reliabilityEligible service events, accepted results, loss, recovery, or reliability conditionOne completed case establishes broad reliability.
human conditionAffected participants, exposure, recovery, load, or supportReported completion means burden was acceptable.
queue or constraintWaiting, eligibility, admission, resource use, blockage, or displacement on its own populationLocal utilization proves total-flow gain.
financial consequenceIncremental payment, receipt, cost, contribution, or horizon-specific consequenceA favorable accounting value authorizes the change.
side effectA separately identified beneficial or harmful consequenceAn observed side effect explains the whole result.
burdenTime, attention, coordination, training, observation, or apparatus requiredSmall trial effort proves affordable sustained use.
missing evidenceThe absent observation, affected decision, and next way to obtain or stopAbsence may be filled by a nearby proxy.
Method or description claimThe exact reusable semantic or description claim that observations support or contradictEvery tool, wording, support, or local-use change creates a Method variant.

Use OPS.15 when the observation population or event correspondence is not yet trustworthy. Use OPS.18 when the evidence calls for a quality or reliability control decision. Those results retain their own subjects and authority.

OPS.16:4.7 - Qualify the evidence through its current owners

Use applicable specialist results and obtain a missing contribution when the decision needs it. A.3.1.WT explains how to use matching observations of Work or design a representative trial that distinguishes alternatives. Use A.3.1.CC for coherence, A.3.1.FT for situational fit or transfer, C.11.MV for practical worth, A.3.1.MV for Method lineage and variant claims, and A.3.1.MI to distinguish the target, introduction strategy, actual Work, observations and bounded revision.

Use A.10 when the source-to-use account remains implicit or must remain replayable. Use C.16 for measurement validity and C.27.TA for the temporal window needed by the receiving decision. Use C.27 when the receiving use requires a temporal-claim adequacy check, and the C.28 causal-use result when the decision relies on a causal claim. Return temporal order, association or direct occurrence evidence at its supported strength, keeping the limits needed by the decision in the existing operating return. A broader claim about coherence, transfer, worth, sustained effectiveness or causality needs evidence for that claim.

Increase assurance effort when its attainable contribution to a consequential choice or condition of use justifies the effort. The extra identity and evidence distinctions are worthwhile when they prevent an unsupported start, branch, or stop. If a simpler observation settles the same bounded choice under the same protections, use it and leave stronger claims unresolved.

OPS.16:4.8 - Compare alternatives under authority and protected conditions

Compare feasible options for continuing, revising, branching or stopping under the same operating use, interval, result definition and protected conditions. Carry uncertainty as an interval, scenario or missing claim. When different operating uses matter, compare the options within each use and identify which options remain non-dominated there. Keep an unresolved comparison visible if the missing information could change which variant is retained.

Identify the Agent authorized to make the local operating decision and the predicate, scope, and basis of that authority. Clinical, safety, release, financial, employment, security, and other specialist decisions remain with their owners. Expertise, sponsorship, assignment, access, and a tool recommendation do not transfer authority.

A favorable trial result applies within the conditions that made the trial feasible. Stop or narrow the trial when permission, qualified support, fallback, recovery, evidence validity, or another protected condition is absent.

OPS.16:4.9 - Return a status-preserving operating decision

Use the branch selected in section 4.1.

BranchPermitted returnRequired boundary
admitted Methodcontinue the established use, adopt, revise, branch, stop, or further observationBind the decision to the exact admitted Method and relied-on version or description, named operating use, conditions, evidence window, and authority.
pre-admission candidatecontinue to the separate A.3.1 identity test; revise or retain competing candidate accounts; stop; or seek further observationKeep the candidate reusable way inside its candidate-account episteme. Return no Method adoption, Method branch, or U.MethodDescription claim.

For either branch, return the exact operating use, supporting evidence, any material limits on stronger uses, protected conditions, decision maker and relevant repertoire, lineage or reopen consequence. Include a next observation only for a selected further inquiry; a completed candidate-account revision or stop needs none. When the decision consumes a returned value from a governed operation application, A.6.1 binds that exact value and C.2.1 identifies its separate result episteme. Do not turn it into a generic Work result or produced entity. Keep the decision and any Method-lineage update separate from trial Work.

An adopt or branch return makes an admitted Method available only for the named operating use and conditions. It does not establish organization-wide adoption, cultural selection or retention, causal superiority, a new capability, or authorization elsewhere. Send a result to OPS.20 only as an admitted local Method variant with its exact relied-on description and bounded evidence, or as a status-preserved candidate-account or observed-practice variation.

OPS.16:4.10 - Keep the return short enough to decide from

A useful return lets the responsible practitioner answer four questions quickly: which admitted Method or candidate account was considered; which available sources support the result and, if a trial is claimed, what actual Work and observations occurred; what current account or decision is supported; and what remains unsupported or reopens the decision. Attach detailed evidence through its owning account rather than restating it.

The team can finish a supported candidate account or make a bounded operating decision. Service and authority conditions continue to govern its use.

OPS.16:5 - Archetypal Grounding

OPS.16:5.1 - PumpWorks branches an admitted package-admission Method

This constructed case continues the PumpWorks control-service operation. The incumbent package-admission Method is admitted PW-TestAdmission-v1. A source-traceable A.3.1.MR candidate-account episteme proposed adding current package readiness, required permission, qualified support, a downstream acceptance path, and a stop on new starts when incident margin is consumed. Before this trial, its EntityOfConcern was independently admitted as PW-TestAdmission-v2 : U.Method. Separate episteme PW-TestAdmission-Description-e2 : U.MethodDescription passed A.3.2 and is the exact description relied on here. The candidate account, admitted Method, and MethodDescription remain different objects.

The local hypothesis is that v2 will reduce avoidable setup and unsupported starts for the named control-service package family without damaging incident response or protected recovery. The alternatives are retain v1 for the whole family, use v2 for the named family, branch by an applicability condition, stop the change, or obtain further evidence. The control-service operations lead holds the local package-admission authority; safety and field-release decisions remain with their existing holders.

The prior OPS.19 result keeps the trial closed while incident coverage, recovery, support, permission or feasible rig use is absent. In the later trial interval, the service and resource owners confirm permitted overlap, retained incident coverage, manual fallback, a qualified support window, the stop on new starts and hand-back. Those conditions make a two-package trial feasible. The earlier plan could describe them while they were still unavailable; it could not authorize an unsupported start.

The WorkPlan for the two-package trial names two intended package-admission decisions, proposed coordinators, v2 as the admitted Method expected to be enacted, support and fallback, the service and recovery protections, the readiness and permission observations, the burden to record, and the stop. In the constructed later week, Coordinator-C17 performs PW-Admission-A-1 from 09:10 to 09:18 and Coordinator-C22 performs PW-Admission-B-1 from 10:05 to 10:12, both inside PumpWorks-ControlServiceOps. Each is separately admitted Work and enacts admitted v2.

Actual occurrenceWork and direct resultDecision-relevant observation
package A admissionIn PW-Admission-A-1, Coordinator-C17 confirms readiness and current permission and admits the package. Separate admitted test Work PW-Test-A-1 later completes and returns its accepted test result.The readiness and permission branch is usable for this occurrence; the package result does not by itself establish why it succeeded.
package B admissionIn PW-Admission-B-1, Coordinator-C22 finds that the permission basis is not current and holds the package. No test Work starts and no test result exists for this package.The explicit hold prevents an unsupported start while preserving the package as pending demand.
continuing serviceIncident coverage, manual fallback, and protected recovery remain available through the trial interval and hand-back.The trial stayed within its supplied conditions; broader reliability remains untested.
burden and descriptionThe account retains the additional readiness and permission checks, support use, departures, and exact description edition separately.The bounded burden is visible; sustained affordability and description adequacy outside this use remain open.

The observations support the readiness and permission branch for these two decisions. They do not establish transfer to another service, causal superiority over v1, general reliability, or practical worth across a broader horizon. The operating decision can rely on the actual occurrences, available service protection and observed hold. If a later decision asks whether v2 causes fewer unsupported starts than v1, these observations do not supply the needed C.28 comparison and inference basis. Return that causal-support gap while preserving the independently supported branch decision.

The selected return is branch. Retain admitted PW-TestAdmission-v2 under PW-TestAdmission-Description-e2 for the named control-service package family and the supplied support and service conditions. Keep admitted v1 for an unaffected family whose current facts still fit. Before widening the v2 branch, require a discriminating observation under provider unavailability. Record the authorized operating decision, Method-lineage update, and repertoire return separately from the trial Work. Reopen when permission, provider support, incident margin, package family, relied-on description, or the next discriminating observation changes.

Compare this same return with competent PDSA. A PDSA team can predict fewer unsupported starts, conduct the two bounded tests, observe A’s usable result and B’s proper hold, preserve service and adapt before wider implementation. Those are shared contributions. OPS.16 adds a useful result only for the receiving question that PDSA’s ordinary local report might leave open: which admitted reusable way and exact description may another package family rely on, and which family stays on v1? If that report already records the same identity, applicability, conditions and evidence limits, it is sufficient. The lineage and repertoire return then reuse it. Their ongoing maintenance and any extra qualifying observation must earn their cost.

OPS.16:5.2 - A hospital keeps a proposed readiness way pre-admission

A public-hospital emergency-flow team observes repeated handover clarification and proposes an information-checking way for transfers between clinical areas. Candidate account ED-Handover-Readiness-CA1 describes the proposed operations: recover the information required by the applicable qualified handover conditions, compare the available case information with those requirements, and refer a missing item or changed clinical condition to its qualified owner before the corresponding coordination decision. The clinical requirements and decision authority are supplied inputs. Brief delay notes leave unclear whether repeated clarification followed missing information or a new clinical finding despite complete information. The account leaves its applicability to changing clinical conditions unresolved. No U.Method or U.MethodDescription has been admitted.

To resolve that applicability question, suppose the team selects observation of two handover intervals under current staffing and safety conditions. Its bounded WorkPlan names the information to compare, qualified participants, privacy protection, stop and the candidate-account revision the evidence can change. When actual clinical and coordination Work occurs, it is admitted separately. Record as enacted only the independently admitted Methods used in those occurrences, such as triage, clinical assessment or handover. The proposed whole retains its candidate status.

Suppose the first record shows a required information item absent before clarification, while the second shows a new clinical finding after the required information was complete. These observations support distinct applicability returns in ED-Handover-Readiness-CA1: seek the missing information in the first condition and return the changed clinical condition to its qualified owner for the needed decision in the second. Completing the information check cannot establish readiness that still depends on that decision. Patient, clinical case, WorkPlan, actual Work, information observations, safety conditions and clinical decisions remain separate.

The current result is a revised candidate account with the proposed operations, their qualified clinical inputs and the newly distinguished applicability condition. That revision can finish the receiving question while retaining candidate status. If another use requires Method identification, compare the account with A.3.1 and name the particular missing identity condition before selecting further inquiry. Clinical priority, consent, privacy, safety, staffing and worker-health decisions remain with their qualified owners.

OPS.16:5.3 - An AI-assisted software operation stops at a provider boundary

A software operations group has independently admitted AI-ReleasePrep-v3 : U.Method for one release-preparation family. Exact AI-ReleasePrep-Description-e4 : U.MethodDescription states the human review, evidence capture, security check, fallback, and release-authority boundary. A prompt repository, model endpoint, and usage counter are supporting Systems or records; none is the Method or proof of enactment.

The trial WorkPlan compares the current human preparation route with admitted v3 for a small set of eligible low-risk changes. It names the proposed human reviewers, the admitted Method expected to be enacted, model and provider condition, security and software-assurance checks, fallback, review burden, evidence window, and a stop if the provider or model condition changes. Actual release-preparation and review Work is admitted separately. Model calls, traces, generated text, test results, security observations, human decisions, and release authorization retain their own subjects.

For eligible cases under the qualified provider and model condition, the observations can support a bounded adopt or branch decision if human review, assurance, service, and burden conditions remain current. If the provider changes the model to an unqualified edition during the interval, the existing evidence no longer supports that branch. The team stops AI-assisted starts for the changed condition and uses the named fallback while qualification is unresolved.

The return preserves the admitted Method and its exact description while narrowing its applicable branch. It establishes neither model capability in general, causal superiority, release authority for the tool, nor transfer to high-risk changes. Security, software assurance, model capability, employment, and release decisions remain with their owners.

OPS.16:6 - Bias-Annotation

Recurring biasLikely driftWorking repair
novelty and solution biasThe proposed change is named as a Method version before identity is established.Begin from the admitted-Method or candidate-account branch and preserve it through the return.
success-story biasOne completed or favorable case becomes proof of effectiveness, fit, or worth.Type the direct observations and state the limits material to the proposed use.
plan-completion biasA scheduled trial or configured tool is reported as performed Work.Keep WorkPlan, actual Work, supporting Systems, and direct results separate.
survivorship biasHeld, stopped, failed, or missing-evidence cases disappear from the trial account.Account for each eligible case, its result or disposition, and the reason where the intended result was not obtained.
measurement availability biasA visible cycle-time or usage measure becomes the improvement objective.Start from the operating decision and qualify the measure’s subject and use.
rollout biasPublication, training, access, or local use becomes organization-wide adoption.Limit the return to the named operating use; use OPS.20 only for a separate population-level cultural question.
tool-change biasA prompt, board field, model, or support change is called a new Method.Apply the reusable-semantics identity test and retain the actual changed object otherwise.

OPS.16:7 - Conformance Checklist

  • The operating System, use, difficulty, receiving decision, decision maker, horizon, and protected conditions are explicit.
  • The starting branch names either an exact admitted U.Method and relied-on version or U.MethodDescription, or an exact A.3.1.MR candidate account with source support, any live rivals and gaps, and explicit non-admission. A distinguishing question is required only when it changes the receiving use.
  • For a selected trial, the bounded hypothesis, current alternative, material change or branch, stop condition and expected observation are clear, including what the observation can establish for the decision. The plan identifies the status of each Method or candidate.
  • A selected new trial uses applicable resource and service results; OCE.11 is selected for coexistence around an organization change. Conditions needed for the trial hold when its dependent Work starts; a conditional plan preserves any remaining gap.
  • New trial Work has a prospective WorkPlan naming intended tasks, proposed performers, expected admitted constituent Methods, supports, observations, burdens, protections, stops, hand-back and later use. Existing evidence retains any available prior plan without inventing intention or occurrence.
  • Every actual Work occurrence has supported actual performers, enacted admitted Methods, extent, containing System and direct results; any claimed departure has an established comparison basis. No candidate whole or candidate account is enacted.
  • Operating, service or reliability, human-condition, queue or constraint, financial, side-effect, burden, missing-evidence, and Method or description observations retain their direct subjects and uses.
  • Coherence, fit or transfer, worth, evidence reliance, measurement validity, temporal window, and causal reach are qualified only where the receiving decision needs them and through their current owners.
  • Alternatives use the same operating basis, preserve protected conditions, carry uncertainty, and remain within named authority.
  • The return uses the permitted branch vocabulary, exact use, evidence window and limits, and relevant repertoire, lineage and reopen consequences. A next observation belongs only to a selected further inquiry, not to every completed account revision or stop.
  • A board, prompt, tool, description, support, or local departure changes Method identity only when reusable Method semantics changed under A.3.1.
  • Any proposed wider use has its own cultural, causal, capability or authority basis; the local decision is not that basis.

OPS.16:8 - Common Anti-Patterns and How to Avoid Them

MisuseWorking repair
“We trialled candidate v2, so the team enacted it.”Keep the reusable way in its candidate account; record only actual Work and independently admitted constituent Methods as enacted.
“The rollout finished, therefore the new Method is adopted.”Separate introduction Work, later operating Work, local decision, and any population-level cultural claim.
“The package passed, so the Method works.”Retain the package result, service conditions, comparison, evidence window, and unsupported causal or transfer claim.
“The dashboard improved after the change.”Recover the observation population, covarying conditions, validity window, and decision that the value can support.
“The new tool created a new Method.”Test whether reusable inputs, operations, applicability, or result semantics changed; otherwise record the tool or description change directly.
“The trial must continue because learning is valuable.”Stop when protection, authority, evidence validity, or a worthwhile contribution to the decision or its grounds is unavailable.
“One standard branch should replace every local variant.”For each material operating use, compare the variants that can serve it. Give the grounds for retaining each branch or identify the unresolved comparison.
“No adverse event occurred, so reliability is established.”State the exposure and observation window; keep broader reliability unresolved.

OPS.16:9 - Consequences

Practitioners can improve an operating Method without losing track of what was planned, performed, observed, or decided. The two status branches let teams learn from a candidate reusable way before admission while preventing candidate language from becoming an enactment or adoption claim.

The method adds explicit identity, evidence, and authority work. That effort is concentrated on distinctions needed to justify continuing, starting, branching or stopping. Some useful trials end with further observation, a revised candidate account, or a narrower branch rather than a general improvement claim.

A bounded decision also preserves later learning. Lineage, repertoire, service evidence, and an OPS.20 cultural question can receive the exact result they need without inheriting a stronger claim.

OPS.16:10 - Rationale

The decision concerns whether to change a way of working under the relevant service conditions. Establish its subject, the grounds the choice depends on and the available authority. A comparison of descriptions can establish a conflict. A claim about performance needs evidence of the Work and result in question.

The status split prevents circular proof: a candidate is not admitted because a plan calls it a Method, and actual Work is not said to enact a candidate whose identity remains unsettled. The typed observation and specialist-return steps prevent one favorable outcome from silently supplying coherence, fit, worth, reliability, or causality.

Local decisions remain valuable even when stronger claims are open. A branch that works for one package family under one support condition can improve operation now while preserving the evidence needed to reconsider transfer or cultural continuation later.

OPS.16:11 - SoTA-Echoing

The question is what to change in a reusable way of operating, and what the evidence actually supports. Plan–Do–Study–Act (PDSA) provides a comparison for the worked case. The Institute for Healthcare Improvement’s testing guidance includes predictions, small tests, actual observations, unexpected effects, refinement and tests under varied conditions. Its implementation guidance distinguishes learning from a change from making it a lasting part of work. OPS adopts these contributions.

At the PumpWorks decision in section 5.1, both arrangements can retain A’s successful use, value B’s refusal to start without current permission, protect service and withhold a broader implementation claim. The residual OPS contribution arises when another service must recover the exact reusable way, distinguish its description from a changed tool or local adjustment, and decide which applicability branch it may use. Sections 4.1 and 4.5–4.9 connect that receiving decision to Method Engineering and FPF’s identity, occurrence, measurement and evidence distinctions. A candidate account can also finish with a supported revision or comparison without inventing a trial or asserting Method admission.

The whole added burden includes recovering Method identity, relating observations to the claims actually consumed, maintaining description and lineage, informing later users, and any specialist qualification or additional observation required by a stronger claim. Those tasks can exceed the cost of the local improvement test. Include the distinctions needed for a branch, stop, receiving claim or later use. Where PDSA is in use, an existing record may already preserve those grounds or need only the missing distinction.

Method Engineering’s trial, coherence, fit, worth, lineage and introduction contributions remain the direct suppliers. FPF A.3.1.MR, A.3.1, A.3.2, A.15.1, A.15.2, A.10, C.16, C.27.TA, C.28 and C.11 qualify the corresponding identity, Work, evidence and comparison questions; they do not set the operation’s service consequence or authority. An operating allocation can supply trial conditions without an organization change; OCE.11 is used when changed organizational relations require coexistence with continuing service.

For rapid feedback, DORA’s continuous integration, continuous delivery and risk-sensitive approval guidance supplies software contributions. The SRE error-budget example supplies a reliability stop. Zampetti et al., “Continuous Integration and Delivery Practices for Cyber-Physical Systems” (2022), provides transfer limits from heterogeneous pipelines. In §§4.3–4.8, choose feedback timing, automation and independent assurance to suit the service, available support and applicable protection conditions. Reopen when a changed family, observation window, candidate identity, support condition or capable incumbent changes the reuse decision or its total cost.

OPS.16:12 - Relations

Introduction and later-use support are supplied by FPF A.3.1.MI. Its result keeps the target practice, introduction strategy and support distinct.

OPS.15 supplies a decision-specific account when observations, populations, or event relations are not yet trustworthy. OPS.17 supplies status-preserved admitted Methods, repertoire claims, or candidate-account alternatives. OPS.18 supplies quality or reliability evidence and its control result.

OPS.10–OPS.13 supply the needed resource, schedule, human-condition and service contributions; OPS.19 supplies a cross-scale decision when trial feasibility or protection depends on its result. OCE.11 supplies coexistence around an organization change. Use each result within its supported scope and confirm the conditions needed for execution; a prospective arrangement remains conditional.

Current A.3.1.WT–A.3.1.MV, C.11.MV and A.3.1.MI govern representative trial evidence, coherence, fit or transfer, worth, lineage, introduction, observation, and bounded revision. A.3.1.MR, A.3.1, A.3.2, A.3.4, A.15.2, A.15.1, A.6.1, C.2.1, A.10, C.16, C.27.TA, C.27, C.28, C.11, and E.23 retain their direct identity, Work, result, evidence, choice, and improvement questions. This pattern composes their results for one Operations decision.

OPS.20 may receive an admitted local Method variant with its exact relied-on description and bounded evidence, or a status-preserved candidate-account or observed-practice variation. It independently supports the practitioner population, cultural predicate and bounded continuation decision. A new intervention or later observation is required only for the claim or selected work that needs it, with its own authority and evidence. A claim that the practice continued across a population needs evidence of that continuation.

OPS.16:End

Referenced in the corpus

52 literal mentions in other sections. Read their context to establish the relation.