Part IX — Improve Methods, Control Quality, Reconcile Work, and Continue Practice
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
| Force | Practical tension |
|---|---|
| learning and continuity | A trial must expose a useful difference while the continuing operation still needs service, recovery, safety, and support. |
| status and action | Practitioners need to act on a promising way, while a candidate account cannot be treated as an admitted Method. |
| plan and occurrence | A 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 use | One bounded trial can settle a local choice while leaving transfer, general reliability, practical worth, and causality unresolved. |
| change and lineage | A reusable semantic change can require a Method variant, while a changed tool, description, support, or departure may leave Method identity unchanged. |
| speed and assurance | A 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 observations | Service, 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 branch | Required identity | First decision-facing statement |
|---|---|---|
| admitted Method | Exact U.Method, exact relied-on Method version or separately classified U.MethodDescription, current operating use, maintained claim, and evidence window | Does the evidence support continuing the present use, adopting, revising, branching or stopping, or making a further observation? |
| pre-admission candidate | Exact 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 use | Which 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:
| Position | What to state |
|---|---|
| status-preserved subject | Exact admitted Method and relied-on description, or exact candidate account and its missing admission basis |
| operating question | Current use, proposed change, comparison, decision maker, and observation needed to decide or support the choice |
| intended Work | Tasks, proposed performers, expected admitted constituent Methods, containing System, and temporal window |
| conditions and stops | Authority, permission, support, service, recovery, human protection, fallback, and hand-back |
| observations | Direct subjects, measures or descriptions, collection point, burden, and later receiving use |
| return | Supported 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 position | Direct subject and use | Unsupported stronger reading to avoid |
|---|---|---|
| operating result | The named Work or operating System result for the selected interval | The changed Method caused a general improvement. |
| service or reliability | Eligible service events, accepted results, loss, recovery, or reliability condition | One completed case establishes broad reliability. |
| human condition | Affected participants, exposure, recovery, load, or support | Reported completion means burden was acceptable. |
| queue or constraint | Waiting, eligibility, admission, resource use, blockage, or displacement on its own population | Local utilization proves total-flow gain. |
| financial consequence | Incremental payment, receipt, cost, contribution, or horizon-specific consequence | A favorable accounting value authorizes the change. |
| side effect | A separately identified beneficial or harmful consequence | An observed side effect explains the whole result. |
| burden | Time, attention, coordination, training, observation, or apparatus required | Small trial effort proves affordable sustained use. |
| missing evidence | The absent observation, affected decision, and next way to obtain or stop | Absence may be filled by a nearby proxy. |
| Method or description claim | The exact reusable semantic or description claim that observations support or contradict | Every 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. Identify any remaining uncertainty that affects the comparison. Use the same operating use, interval, result definition, and protected conditions. Carry uncertainty as an explicit interval, scenario, or missing claim. Preserve alternatives that remain non-dominated for materially different uses or conditions.
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.
| Branch | Permitted return | Required boundary |
|---|---|---|
| admitted Method | continue the established use, adopt, revise, branch, stop, or further observation | Bind the decision to the exact admitted Method and relied-on version or description, named operating use, conditions, evidence window, and authority. |
| pre-admission candidate | continue to the separate A.3.1 identity test; revise or retain competing candidate accounts; stop; or seek further observation | Keep 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 occurrence | Work and direct result | Decision-relevant observation |
|---|---|---|
| package A admission | In 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 admission | In 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 service | Incident 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 description | The 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 bias | Likely drift | Working repair |
|---|---|---|
| novelty and solution bias | The 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 bias | One 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 bias | A scheduled trial or configured tool is reported as performed Work. | Keep WorkPlan, actual Work, supporting Systems, and direct results separate. |
| survivorship bias | Held, 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 bias | A visible cycle-time or usage measure becomes the improvement objective. | Start from the operating decision and qualify the measure’s subject and use. |
| rollout bias | Publication, 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 bias | A 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.Methodand relied-on version orU.MethodDescription, or an exactA.3.1.MRcandidate 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
WorkPlannaming 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
| Misuse | Working 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.” | Retain non-dominated variants for materially different uses and conditions. |
| “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
OPS.17 - Compare and Refresh Operations Methods
Status: Stable
OPS.17:1 - Problem frame
Use this when the current way of running an operation repeatedly misses its purpose, a changed condition defeats one of its assumptions, or a serious alternative could improve a live operating decision. You may need to choose how ready work enters a queue, how an exceptional case continues, how a service responds to failures, or how repeated support develops usable knowledge.
Start with that decision and one family of Work: the actual work people and other systems perform to produce the operating result. Recover what the present method does and what would justify retaining or changing it for this use. The first useful result is a small repertoire of operating methods with their applicable uses, evidence, costs and reasons to reconsider them. A repertoire is a maintained selection of ways of working, with enough guidance to choose among them.
Operations management is the wider practice. This pattern governs the choice and maintenance of reusable operating methods within it. If an existing method already fits the situation and its conditions still hold, use it for the current decision. Replacing a display, repairing a tool or resolving one unusual case may need only that bounded action. A present comparison or traceable candidate account can be complete while a stronger operating-effect claim remains unsupported. Developing or testing that claim is separate work, selected only when its attainable contribution is worth the whole burden.
A PumpWorks board contains twelve matters, yet only four test packages are ready for the rig. Buying more rig time, restricting work in progress and repairing readiness can all sound like remedies. Their value depends on why work waits. Compare the moves and identify any remaining question about the cause of the wait before choosing a response.
OPS.17:2 - Problem
A named approach often bundles useful operations with assumptions about demand, resources, evidence and the purpose of the organization. Adopting the bundle can import an unsuitable objective or omit a condition that made its source example work. A local success also gives weak grounds for general use if the team cannot recover what was actually changed.
A catalogue creates a different difficulty: it preserves names but leaves every practitioner to reconstruct applicability. The needed knowledge is what each method lets the operation do, what it requires, and what observable change would defeat the claim.
OPS.17:3 - Forces
| Force | Practical tension |
|---|---|
| reuse and fit | A known method saves invention, while local demand, authority or capability can invalidate its assumptions. |
| improvement and adoption cost | A stronger response can consume training, observation and coordination effort that a simpler adequate response avoids. |
| local gain and operating result | Faster preparation can move unfinished work to acceptance or consume incident cover elsewhere. |
| comparison and preference | Several feasible methods can remain worthwhile for different service, burden and financial consequences. |
| consistency and exception | A stable work policy helps coordination; a justified urgent exception can require explicit displacement and recovery. |
OPS.17:4 - Solution
OPS.17:4.1 - Frame the choice in operating terms
Name the Work family, the result served, the receiving decision and its horizon. Describe the current method through a recent representative case: what triggered action, what inputs and resources were used, which participants acted and what they did, what result was accepted and where work or information waited. Use existing evidence first.
State the consequential discrepancy. “The board has twelve cards” is an observation. “Four ready packages cannot receive their required two-hour rig visits before Friday” names a service problem. If the mechanism is unresolved, state how that uncertainty affects the current choice. OPS.9 helps with a disputed constraint; OPS.15 helps when the existing account cannot make the distinction.
Keep current practice and the least costly adequate response in the comparison. A corrected readiness check may be enough when a wholesale planning change offers no further decision-relevant benefit.
OPS.17:4.2 - Recover candidate operations from their sources
Read each candidate at the level that could actually be reused. Recover its input, sequence or conditional rules, first useful result, required capability and support, evidence for the claimed effect, and conditions for stopping or changing its use. Retain the source and its relevant version or date when that changes the meaning.
For example, an explicit limit on started work requires a start/end definition and a policy for reaching the limit. A rule protecting a scarce resource requires evidence of the resource’s limiting role for the named demand and horizon. A case method requires conditions under which a practitioner may choose or change the next action. These are different claims even when one tool presents them together.
The following repertoire supplies starting comparisons. Use the rows that address the operating question. If none supplies the needed result, recover or construct the missing contribution through C.39 rather than selecting the nearest school name. OPS.11.1:4.2a can construct a different operating arrangement using adequate methods already available; a new reusable operation retains its candidate status until its own basis is established.
| Operating question | Candidate move | Evidence and limit that change its use |
|---|---|---|
| Too much work starts while eligible work waits | Define readiness, control work in progress and pull new work when the stated capacity is available, using the Kanban line. | Recover item boundaries, actual waiting and the start policy. A limit must protect the receiving service; its value is not inferred from the number of board cards. |
| A particular resource or dependency limits the result | Protect its useful time and feed it appropriately, using bounded moves from the Theory of Constraints (TOC) and TameFlow. | Establish the current limiting mechanism. Historical average utilization alone can miss starvation or short peak overloads. |
| New information changes an admitted case | Choose or revise the next action under case conditions, using CMMN case planning or declarative condition/response rules. | Recover prerequisites, pending obligations and practitioner discretion. A recurring subprocedure can remain fixed inside the case. |
| A customer-relevant service objective is missed | Relate eligible service events, observed loss and an authorized response through a service-level objective (SLO) and an error-budget policy that connects permitted loss to action. | Check event coverage and response timing. An aggregate can hide a severe short incident or an affected customer group. |
| Repeated production results change or a lot needs disposition | Use statistical monitoring for variation, or an acceptance plan for the particular lot. | The population, sampling basis and decision differ. A monitoring signal does not supply a lot-disposition decision. |
| More output appears financially worthwhile | Compare contribution per scarce resource under a suitable model, and compare actual incremental payments and receipts over the decision horizon. | Recover demand, variable costs, displacement, acceptance and timing. Coupled constraints and indivisible jobs can defeat a simple ranking. |
| Extra service consumes human recovery or attention | Remove avoidable demand, redesign the work pattern or provide qualified coverage before relying on individual coping. | Recover affected groups and supplied protection conditions. Use OPS.12 to choose the intervention. |
| Repeated support consumes expertise while useful answers are missed or remain inadequate | Compare direct use of a sufficient answer with KCS knowledge development within service work; use :4.2.1 for the source operations and receiving returns. | Distinguish the service interaction, applicable knowledge and receiving outcome. Supply qualified correction and maintenance; use patterns can justify a service-change question without proving its cause. |
A source’s example is evidence for what it demonstrates. Treat a proposed combination as a candidate whose compatibility and fit still need examination. A tool’s changed version is a reason to inspect its effect on the method, rather than sufficient evidence of a new Method variant.
OPS.17:4.2.1 - Choose how service work develops usable knowledge
Repeated requests can consume expert time even when useful answers already exist. They can also expose an answer whose conditions are unclear, a missing professional solution, or a costly workaround worth removing. Start with a representative receiving case and distinguish these possibilities before commissioning more articles, training or a new knowledge platform. The first useful result is a choice of what to reuse or change, with the professional contribution and support it needs.
Knowledge-Centered Success (KCS, formerly Knowledge-Centered Service) is a candidate when the service needs to develop shared working knowledge through its use. The Consortium for Service Innovation’s complete practices guide explains the professional practice: knowledge is reused and improved during service work, while analysis across uses changes content, workflow or the underlying service. An adequate manual, direct source or competent provider remains a serious alternative. Use it directly when it supplies the required result; a single unfamiliar case need not justify a continuing knowledge programme.
For a selected KCS use, obtain the particular operation from the following treatments and bring its result back to the operating choice. A practitioner familiar with the operation can reuse it; a performer new to it needs access to the explanation and any support required to perform it competently.
- Connect the request to a usable answer. Use Structured Workflow Integration and Track Reuse to retain the requester’s circumstances, find and judge existing knowledge, and associate the interaction with the knowledge actually used and what is known about its outcome. Professional diagnosis or investigation supplies an absent answer. Return the supported resolution, or the precise unresolved question and the qualified contribution needed next. A maintained external source can remain the answer rather than being copied into another authority.
- Make the reusable contribution discriminating and correctable. When material needs development, use selective creation to distinguish useful contextual capture from another article. The simple template and article-structure treatment explain how the question, environment and resolution support later discrimination, while requester-specific details stay in the interaction record under its access and retention rules. Use Article State for the separate confidence, audience and governance decisions. Reuse is Review connects actual application to correction by a capable contributor; opening or citing an article alone supplies no such judgement.
- Choose the receiving improvement. Use Knowledge Optimization when recurring uses can change which content, access, workflow or product problem deserves action. Preserve materially different conditions behind similar requests. Return the supported discrepancy and affected uses to the responsible practice; a recurring symptom motivates investigation without establishing its cause.
These returns determine which further contribution to obtain. For a sound answer that is hard to recover or maintain, use the relevant Knowledge-Corpus Access Engineering (KCAE) method: KCAE.MEMORY retains permitted episodes and conditional connections; KCAE.CHANGE maintains editions and affected derived results; KCAE.EVAL examines the usefulness of the access arrangement. A missing domain answer needs its professional supplier. Use OPS.22 when service observations need interpretation or an authorized response. Return a proposed reusable operating-method change to OPS.16. CB.14 is useful when a community actually wants to develop and maintain a joint repertoire.
Include the work that makes the chosen arrangement sustainable. Diagnosis, content correction and analysis across cases need suitable competence, time, permission and a receiving decision maker. The full KCS guide develops content standards, proficiency and coaching, and continuing organizational support; check which of those conditions are already available and what must still be provided. Use Roles and Proficiency for the rights model and its competency conditions. Content Health Indicators and Process Alignment Review distinguish article-standard checks from observations of case handling. Coaching for Success and Structuring Coaching Sessions explain how to arrange the coach’s contribution, the practitioner’s work and follow-up. Obtain missing support, revise the service promise or retain the simpler adequate arrangement. Compare the burden on contributors and recipients as well as the sponsor’s expected saving. New material can also be warranted before failure, when a forthcoming change and its professional evidence create a useful receiving question.
An agent can perform any of these contributions within its actual qualified capability and granted scope. If automation removes the capable observation that previously corrected an answer, arrange an adequate replacement for that contribution. It may be an agent check, suitable independent assessment, receiving-outcome evidence or qualified human work, according to the claim at issue. For tool integration and interrupted self-service, use the guide’s Technology Integration to preserve the context needed by the next performer. The changed division must still supply the service result and the knowledge correction on which future use relies.
OPS.17:4.3 - Compare feasible ways of working
First exclude options that violate a supplied protection, authority limit or necessary operating condition. For the remaining options, compare the consequences material to the choice or its grounds: accepted service, resource demand, delay, quality, human burden, financial effect and the effort to introduce and sustain the method.
Use the same Work family, horizon and result definition for each option. Carry uncertainty as an interval, scenario or unresolved claim suitable for the use. Separate an observed result from a forecast or causal explanation. A method that worked in one team may still be a useful candidate elsewhere; the evidence for that receiving use must remain visible.
An option is dominated when another feasible option is at least as good on all consequential comparison characteristics and better on at least one, under the stated comparison. Keep non-dominated options when the preference remains unresolved. The authorized decision maker can choose among them by an explicit priority or justified trade-off. For example, earlier service may justify a higher payment; a weighted score cannot make a breached recovery condition acceptable.
Increase comparison effort when its attainable contribution warrants the burden. If every option needs the same staffing condition, a conditional comparison can show what the options would deliver. Establish that condition before relying on any option as executable; detailed scores can wait if they would add little.
OPS.17:4.4 - Compose compatible moves and state the usable result
Several moves can serve one operation. Readiness-based admission can coexist with case discretion and a reliability stop rule. Check the shared subject and the points at which one rule changes another rule’s permission, priority, resource use or stopping condition.
Resolve a consequential conflict before using the combination. An urgent incident may override a WIP policy under an existing service authority. The exception needs the displaced work, remaining protected conditions and recovery action to be clear. A general “urgent” label cannot supply those facts.
Return the selected use and the actual level of support: an applicable established method, a conditional alternative, a traceable candidate account with an unresolved operating claim, or an unsuitable use with its reason. On the available basis, the repertoire can retain current practice, keep or revise a candidate account, or reject a proposed use. Preserve the gap needed by a later stronger use in that same return. Keep any selected first action, its conditions and evidence limits, burden and reason to reopen close to the consequential choice. An existing operating note or method description can hold this result; maintaining a second catalogue adds value only if someone uses it to choose work.
OPS.17:4.5 - Refresh the affected method claim
Reconsider a method when a relied-on condition changes, its operating result deteriorates, or a credible alternative changes the comparison. Identify which claim or use the change affects. Reassess that part of the repertoire. A change in customer acceptance can affect a service forecast while leaving readiness checks useful.
Use A.3.1.MV when the reusable semantics change: inputs, operations, applicability or result may define a Method variant. Keep changes to the description, supporting tool and one local departure distinguishable. Preserve evidence only for the claims and conditions it still supports. A combination of previously admitted methods needs its own evidence where their interaction changes the claimed result.
Use the available qualified evidence, estimates and judgement to complete the comparison needed by the decision maker, or to document the proposed method’s origins and unresolved claims. Retain the adequate incumbent or bounded candidate account with its actual gap when no further inquiry can make a worthwhile attainable contribution. Use B.1.5.CM for the status of a proposed whole and C.11.MV for its practical worth. For admission, compatibility, fit, transfer or permission for operating use, retain the separate grounds the claim requires.
When an unresolved operating effect matters to the decision or its grounds, compare the attainable contribution of a new trial question or evidence acquisition with its whole burden: design, performance, interpretation, delay and displaced operating Work. Select it only when that contribution is obtainable and worth the burden. For a selected trial, return the effect to observe, protected conditions, authority, stop and comparison basis. When the question concerns competing explanations, include the observation that could distinguish them. A.3.1.WT can guide that trial. The repertoire choice itself establishes neither that the candidate was performed nor that it improved service.
OPS.17:5 - Archetypal Grounding
OPS.17:5.1 - PumpWorks chooses what to change
This constructed case concerns the engineering test service, PumpWorks-ControlServiceOps. Its board includes release candidate R42, incident I73, safety question S19 and provider change P8. They are unlike matters requiring different actions. Four packages are ready for testing and need eight rig-hours.
A historical forty-hour rig log contains twenty execution hours, four setup hours, four unavailable hours and twelve hours with no eligible job. The next service window has six usable rig-hours. The team compares three responses:
| Response | What the evidence supports | Result of the comparison |
|---|---|---|
| Extend the rig window immediately | The four ready packages exceed the current window; more usable time could help this peak. Historical idle time does not remove that fact. | Keep a capacity alternative for OPS.10 and OPS.13, conditional on actual access, qualified cover, rework and the service horizon. |
| Admit only test-ready packages to the rig queue and make the next eligible package visible | The board count mixes unlike matters; the log also shows lost opportunities when no eligible package was available. | Select the existing readiness criteria for queue admission and make readiness timestamps available for the next operating review. |
| Treat the rig as the persistent constraint and impose a new protective buffer | The supplied log does not settle whether readiness failures, peak demand or rig access limits accepted service over the relevant horizon. | Return the constraint question to OPS.9 before choosing the buffer policy. |
The result combines a usable admission move with an unresolved capacity choice. It does not erase the four-package peak. Readiness and rig-access evidence answer different parts of the problem, so both remain in the repertoire.
For the next window, use the established readiness criteria to populate the test queue; compare the six-hour plan with any authorized extension using OPS.13; reopen constraint protection if matched demand, readiness and rig-use histories show the rig consistently limiting accepted service. S19’s field-release decision remains with the authorized safety and release practitioners. A permission for laboratory testing has the scope supplied by those practitioners.
OPS.17:5.2 - A hospital continues an evolving discharge case
In a constructed hospital service, a standard checklist works for the recurring discharge subprocedure, but a newly discovered home-support need changes one patient’s case. Repeating the checklist cannot decide the next action. The practitioner compares a fixed sequence with conditional case planning.
The local care plan requires a qualified clinical decision and confirmation of necessary home support before discharge. The selected case rule allows the responsible practitioner to coordinate the required assessment and home support in the order the situation permits, while keeping both conditions visible. A change in support can reopen planning. The standard medication-check subprocedure remains applicable when the case reaches it.
This is a method comparison about continuing the case. The clinical judgment and the patient’s actual readiness come from their own qualified work. The case account supplies the conditions and the evidence needed by the operating decision.
OPS.17:5.3 - Faster AI drafting changes the constraint
Suppose an assisted drafting service generates twenty candidates per day while qualified readers can accept six. A tool update raises generation to sixty; the acceptance capability stays at six. The old rule of keeping every generator busy now adds unaccepted drafts to the queue; reviewing more of them would add reader work.
Compare a controlled generation rate, extra qualified acceptance capacity, and a changed acceptance method. Limiting starts to the demonstrated acceptance capacity can be a current operating response. The other two choices need capability, burden and quality evidence. OPS.12 checks the transferred reading burden, OPS.13 qualifies the service commitment and OPS.18 supplies the acceptance and reliability conditions.
The repertoire refresh concerns the claim that more generation improves accepted throughput. A.3.1.MV distinguishes a changed generation method from a support-only update. That distinction preserves what existing evidence still supports without assuming that either kind of update improves the whole service.
OPS.17:5.4 - A current comparison and a later worthwhile trial
For a later PumpWorks decision, admitted Method R continues to meet the package-admission requirements for the same permitted use. Proposed N combines its readiness check with a different sequencing rule. The sources and proposed interaction are traceable, but whether N preserves the permission-expiry hold while reducing repeat checks remains unsupported. No rig slot or trial permission is available before the decision window. The operating note retains R for current use and N as a candidate account with that precise gap. This completes the current comparison and lineage return.
Later, twenty-four planned package admissions make the repeated checking burden consequential. N now has a credible estimated saving of ten to fifteen minutes per admission, but preservation of the permission-expiry hold is still uncertain. A comparison of R and N on representative ordinary and expired-permission inputs can change the choice. A rig slot, qualified people and the appropriate trial permission are available. Design, performance, interpretation and return together need three of five available hours and displace no required operating Work; the estimated four to six hours saved across the planned admissions can justify the three-hour inquiry, given its ability to check the required hold.
The team selects the bounded comparison, with the permission-expiry hold as a required result and a stop if supplied support or permission ceases. R remains selected pending the result. The trial permission does not supply Method admission or authority for normal service use. Any later fit, transfer or causal claim still needs evidence adequate for that claim.
OPS.17:5.5 - An incident exception that does not repeal the start limit
Use the constructed PumpWorks choice in OPS.2:5.2. Recover the two rules before combining their labels. The normal rule chooses the oldest ready package; the incident rule changes order only when a supported response window would otherwise be lost. Both still require current readiness, permission, an available performer and room under the active-work limit.
At 09:00, T8 occupies one of two slots. I73-D can use the other with E18, while older P8-P can wait until its authorized afternoon review. The incident lead approves the exception and the resource owner confirms the displacement. The combination therefore starts I73-D without interrupting T8 or creating a third slot. If both slots were already occupied, the exception alone would not authorize another start: a safe, permitted completion or stop and a new capacity decision would be needed. Merely moving a suspended card out of sight would not free a still-occupied resource.
At 09:50, unavailable field contact removes the ground for reserving E18 for live verification. Keep the readiness and WIP rules, close only the unsupported exception and reconsider the eligible work. The combination costs the exception decision and its expiry check; when ordinary ready order already preserves the response window, keep that cheaper rule.
OPS.17:5.6 - Repeated support changes the knowledge and then the service
Consider a constructed service helping project teams import records into a shared platform. A qualified specialist has established that, for platform version P4 with a particular permission setting, duplicated rows on screen are a display problem: the stored records remain unique, and the documented view refresh restores the display. The current manual calls this a stale view. Users search for duplicate imports and often miss it. A different P5 import format has produced a similar report, but its mechanism and remedy remain unresolved. The current routine sends requests to specialists and batches manual updates at month end; it leaves later responders repeating already completed distinctions.
The service lead compares four moves for the next month: retain the current manual and expert response; improve access to the known answer; use KCS to maintain answers through subsequent service work; or change the platform. Bulk article production would not distinguish the two configurations. Immediate platform replacement would assume a wider cause and benefit than the supplied evidence establishes.
For P4, the specialist first checks the requester’s environment against the supported conditions. The answer can remain in the maintained manual. A discoverable entry associates the user’s duplicate-row wording with that answer and its P4 permission condition. Its resolution states the applicable refresh and the expected result: one displayed row for each stored record. The service interaction retains which edition was used and whether that result occurred. The reusable entry need not include the team’s private project data. This small access correction is enough for a familiar matching case.
The P5 request changes the selection. Similar wording does not make the P4 answer applicable. Preserve the new environment and unresolved question, and obtain the appropriate platform investigation. The known P4 resolution stays usable. The service responders can apply the KCS workflow, and their case-handling allocation includes capturing relevant context and linking the answer used. The lead selects that workflow for continuing support so that developing answers and their conditions become available during service work, instead of waiting for the monthly manual revision. The full source techniques in :4.2.1 supply that work. The choice provides a way of handling the gap, not a newly established P5 remedy.
The service already has a small, allocated maintenance interval that can supply the P4 access correction. Proposed weekly analysis across cases needs additional qualified time, while current response commitments occupy the remaining specialist capacity. The lead keeps the useful local correction and obtains a separate contribution or changes the relevant commitment before promising recurring analysis. Expected future savings cannot supply that missing hour.
Suppose later observations show that matching P4 users obtain the right answer but still incur substantial effort repeating the workaround. The next comparison concerns removing that burden through a platform change, changing the service offer, or retaining the workaround at its actual cost. The product owner needs the affected conditions and receiving burden; the engineer must supply the causal explanation and proposed remedy. OPS.22 interprets the supported service result, and OPS.16 is used if the selected response changes a reusable operating method. Better article retrieval remains useful, but it no longer answers the whole improvement question.
Now change the performer. A corporate agent configuration is qualified to distinguish the supported P4 condition, use the current answer, perform the permitted refresh and check the resulting display. It can replace the corresponding human service performance. P5 remains outside that qualified use until a suitable answer and performer are available. The replacement also needs to preserve error detection: if the agent merely repeats the article while never noticing a failed result, the previous specialist’s corrective contribution has been lost. Obtain an adequate outcome check or other qualified assessment for that gap; human approval is needed only where the particular judgement or authority requires it. If a qualified agent obtains an answer without using an article, preserve the actual basis rather than inventing an article-use event.
After the change, assisted contacts fall from 40 to 12 per interval and the system records 30 agent interactions. The difference is 28 contacts; it does not establish 28 avoided issues or attribute the change to the agent. One issue may span several interactions, and a failed answer may never return as a ticket. The KCS self-service measurement treatment helps recover the relevant issue population, observed outcomes and unobserved part. Bring that bounded account to OPS.22 and compare the receiving effort and service mix as well as contact counts. KCAE.EVAL can examine the access contribution within that whole comparison.
A later policy change forbids the old refresh for one protected class of records. The responsible policy authority supplies the effective rule. The service revises the affected answer and uses KCAE.CHANGE to remove or mark stale dependent current advice. Historical correctness of the P4 diagnosis remains different from permission to act now. A recipient’s personal assistant must likewise obtain its own permitted access and action scope; the corporate agent’s grant does not travel with a copied answer.
When a person wants to learn the diagnosis, use HCD to arrange the needed learning. A claim that the person has acquired the capability needs evidence from their own performance. If independent practitioners instead want to establish a novel shared method, CB.14 can organize that joint undertaking and its professional contributors; the frequency of support questions cannot establish the new method. These changed purposes preserve the useful service-knowledge contribution while changing what else must be obtained.
OPS.17:6 - Bias-Annotation
People who have invested in a school or tool can find its benefits easier to see than its operating costs. Include current practice and a simpler adequate response, and establish where the proposed gain would create additional work. Use measurements that cover that burden or obtain an affected practitioner’s account where the burden is known through their experience.
Available telemetry also favors measurable activity over accepted service. Inspect omitted work, blocked cases and receiving practitioners’ effort before choosing comparison characteristics. The repertoire can remain small when those observations identify the only live choice.
OPS.17:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The choice has a working purpose. | The Work family, receiving decision, discrepancy and horizon can be recovered. |
| Candidate content is actionable. | Inputs, operating moves, first result, needed capability/support and source limits are clear. |
| The comparison preserves feasibility and preference. | Protected conditions are checked before trade-offs; consequential differences and unresolved preferences remain visible. |
| Composition is usable. | Shared conditions, exceptions, displacement and stops are compatible for the selected use. |
| The returned claim has appropriate support. | Supported uses, current candidate accounts, actual evidence gaps and any selected worthwhile attainable trial are distinguished. |
| Refresh can be directed. | A changed condition can be traced to the affected method claim and its receiving decision. |
OPS.17:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Choose a school from a general maturity score. | Compare its actual moves against the current service problem at comparable adoption effort. |
| Protect the apparently busiest resource. | Establish which mechanism limits the named accepted result and horizon before choosing the protection. |
| Add an expedite lane while claiming an unchanged WIP policy. | State the exception authority, displaced work and recovery, and requalify the combined policy. |
| Keep evidence attached to a method name after its conditions change. | Reassess the affected applicability or effect claim and retain unaffected evidence. |
| Call a promising combination proven because its components are familiar. | Examine the available interaction evidence and keep the unproved claim as a gap in the current candidate account. Obtain more operating evidence only when its attainable contribution is worth the whole burden for the receiving decision. |
OPS.17:9 - Consequences
Practitioners can reuse a bounded operating move without importing a whole school’s objective or record system. The repertoire also makes changed conditions easier to address: the team can revise one admission rule or acceptance assumption while retaining useful neighboring methods.
The comparison takes effort, and some effect claims remain uncertain until local use. Maintaining only decision-relevant alternatives and finishing the supported comparison limits that cost. Further inquiry is selected for the contribution it can make at its full cost. Broader comparative effectiveness remains an empirical question.
OPS.17:10 - Rationale
Method-level comparison preserves the connection between a working problem and the action intended to change it. It is especially useful where several traditions overlap in vocabulary but act on different objects: a ready queue, a case, a scarce resource, a service-event population or a cash consequence.
The separate feasibility and preference steps preserve non-negotiable conditions while allowing a real choice among useful alternatives. Review then follows the affected claim, making evidence reuse possible without treating the method as timeless.
OPS.17:11 - SoTA-Echoing
The practice question is how to select and maintain operating methods when demand, constraints and evidence change. The cases combine work control, case continuation and evidence for the receiving decision where their conditions fit. Selecting the contributions separately preserves the ready-queue move, peak-capacity question, case discretion and acceptance bottleneck that whole-school adoption can obscure.
| Source contribution | Adopted or adapted move and serious alternative | Change in this pattern and limit |
|---|---|---|
| The Kanban Guide 2025.5 | Adopt explicit workflow boundaries, WIP control and elapsed-time evidence; compare with an unrestricted start policy. | Sections 4.2–4.4 require the item boundary and the consequence protected by a limit. The guide’s knowledge-work metric set is not imposed on every method. |
| Steve Tendon’s The Book of TameFlow (2022), pp. 25–27, 135 and 142, and Donald Reinertsen’s The Principles of Product Development Flow (2009), chapters 2–9 | Adapt constraint protection and cost-of-delay questions; compare with maximizing each resource’s utilization. | The PumpWorks comparison needs a diagnosed limiting mechanism and an actual service horizon. These are historical mechanisms; their age or continued use does not establish superiority. |
| CMMN 1.1 and the DCR condition/response line | Adopt explicit case conditions and permitted discretion where a fixed sequence cannot cover the evolving facts. | The hospital case preserves obligatory conditions while allowing a different next action. A notation does not supply clinical authority or evidence. |
| SRE service objectives, NIST process monitoring and lot acceptance | Select evidence by the operating question; compare with one aggregate quality dashboard. | Section 4.2 distinguishes service loss, recurring variation and lot disposition, with OPS.18 as the receiving control method. |
| ACCA relevant-cost comparison and throughput accounting | Retain constrained-resource contribution and incremental cash as different comparisons; compare with a general local-efficiency ranking. | Section 4.3 preserves horizon, actual costs and accepted demand. OPS.14 develops the financial consequence; statutory or investment uses need their own methods. |
| NIOSH’s hierarchy of controls for Total Worker Health | Prefer removal or redesign of harmful conditions to relying first on individual coping. | Feasibility and the OPS.12 receiving result preserve affected groups and supplied protections. |
| Consortium for Service Innovation, Knowledge-Centered Success practices guide, titled 2027, and its edition explanation | Use knowledge development within service work when an adequate manual or direct provider no longer supplies the needed continuing result. Compare access correction, knowledge correction and a change to the service. | Section 4.2.1 directs the professional execution to the complete source treatments; :5.6 develops the operating selection and returns under changed conditions. The guidance specifies professional practice. An estimate of local benefit needs evidence from the particular service. |
These sources contribute different strengths: formal rules, practitioner guidance, technical models and worked financial reasoning. The repertoire preserves those evidence limits. Reopen a selected claim when a better-supported competing move, changed source meaning or changed operating condition affects the choice.
OPS.17:12 - Relations
OPS.5, OPS.6, OPS.8 and OPS.9 supply the concrete admission, continuation, queue and constraint questions for which a repertoire entry can be selected. OPS.12–OPS.15 and OPS.18 supply human-condition, service, financial, account and control results needed by particular comparisons. Their use follows the live question.
For the service-knowledge choice, the KCS treatments linked in :4.2.1 supply the professional operations. The Knowledge-Corpus Access Engineering framework supplies KCAE.MEMORY, KCAE.CHANGE and KCAE.EVAL for retaining useful episodes, maintaining current knowledge and assessing the access arrangement. OPS.22 receives the service interpretation; CB.14 and HCD receive a joint repertoire or human-learning question when that is the intended result.
A.3.1.MV guides maintenance of Method variants and the evidence they can reuse. A.3.1.WT supplies a trial method for a selected worthwhile and attainable local comparison; A.3.1.FT and C.11.MV address fit and worth where those judgments are required. The full operating-Method-change question of OPS.16 and cultural continuation question of OPS.20 remain distinct from maintaining this repertoire.
Use FPF A.3.1 for a Method, A.3.2 for its description and A.15.1 for performed Work when the comparison relies on those claims. C.16 and G.5 support meaningful comparison characteristics and selection among alternatives. A.11.OP limits additional collection or apparatus to what contributes to the decision, needed assurance or recovery.
OPS.17:End
OPS.18 - Control Operating Quality and Reliability
Status: Stable
OPS.18:1 - Problem frame
Use this when an operating result may no longer meet its requirement, observed service failures exceed the agreed allowance, a recurring process changes, a lot needs acceptance or an incident raises a containment, recovery or recurrence-prevention question.
Begin with the result at risk, the affected population or configuration and the applicable requirement. Use evidence suited to the question. State what it establishes, including any scope or uncertainty. If a response is needed, identify the available action, authority and conditions, or what prevents a decision.
This pattern governs operating decisions about quality and reliability. A monitoring account is one input. A qualified product requirement, clinical decision, statistical method or engineering acceptance result may be another. If the question is only how to define and reconcile observations, use OPS.15. If a current response policy and adequate evidence already settle the action, apply them directly.
For example, twelve nonconforming items in a sample can trigger investigation under a process-monitoring rule. A lot-disposition decision still needs its own acceptance basis. Likewise, exhausting a software service’s error budget can pause discretionary changes while urgent restoration continues under the responsible authority.
OPS.18:2 - Problem
Different quality questions are often compressed into one status: the process looks stable, the customer objective was met, the lot passed or the service is restored. Each statement needs different evidence and supports a different action.
A dashboard can therefore look satisfactory while the actual service remains impaired. The opposite failure reacts to every fluctuation as a process change, consuming effort and destabilizing work without a suitable monitoring basis.
OPS.18:3 - Forces
| Force | Practical tension |
|---|---|
| prompt response and false signals | Earlier detection can help containment while unsuitable thresholds create unnecessary interventions. |
| stability and acceptability | A stable process can repeatedly produce results that fail the requirement. |
| aggregate service and local consequence | A good average can hide an affected customer group or a short severe incident. |
| restoration and causal understanding | Service may be recoverable before the cause is fully established, while recurrence prevention still needs investigation. |
| continuity and protected conditions | Urgent recovery work requires the capability, authority and protections of its actual operation. |
OPS.18:4 - Solution
OPS.18:4.1 - Recover the result, requirement and available action
State the operating result at risk: conforming output, correct responses, timely service, availability or restored operation. Recover the relevant population, configuration, period, requirement and consequence of failure. Name the authority for continuation, containment, acceptance and restart where those decisions differ.
Use the actual requirement. A product specification, an agreed service objective and a statistical control limit answer different questions. A control limit describes variation under its model. A requirement states what the result must satisfy. Recover each from its appropriate basis.
If a known violation already calls for a protective action, take that action under the current authority and pursue any diagnosis or recovery result still required. A broad data analysis is unnecessary before a response already required by the observed condition.
OPS.18:4.2 - Select the evidence branch
| Current question | Evidence method | First operating use |
|---|---|---|
| Has a recurring process changed from its established behavior? | A suitable statistical monitor with a qualified baseline, sampling rule and response policy. | Continue observation or investigate and contain the affected process/result. |
| Is event-based service meeting its objective? | Definitions of good and eligible events, observation coverage, reporting window and permitted loss. | Report the result against the objective. When a response is needed, apply the authorized policy or identify the missing decision. |
| Should a particular lot or result be accepted? | Its qualified acceptance plan, defect definitions, sampling basis and relevant risks. | Accept, reject, segregate, rework or obtain the missing acceptance result. |
| Can an impaired service be restored or restarted? | Evidence of the failure, containment or repair, and the required restart conditions. | Restore service when its conditions hold under the appropriate authority. Continue an investigation if the remaining question requires it. |
| What prevention does an incident or near miss need? | Reconstructed events, material explanations and sufficient support for feasible protective measures. | Select and verify prevention under :4.4, retaining the limits on the causal conclusion. |
Use the branches whose results affect the response or the grounds for relying on it. A monitoring signal, lot acceptance and authorization to restart each need evidence for that particular conclusion.
For recurring variation, check that the observations are comparable, the baseline is appropriate and the model fits the data. Changing sample size, seasonality, clustering, rare events or dependence can change the required monitor. When a simple chart is inadequate, use an applicable qualified design, develop one within your competence or obtain specialist help. Establish the defect or result definition, sampling, grouping, time order, baseline, plausible dependence or drift, costs of false and missed signals, and the latest useful response. A usable design identifies its population and model, detection and false-signal performance at specified changes, observation burden, and the rule the operator can execute.
For an event-based service, define the good and eligible events at the service boundary that matters to the recipient. Check omitted events, important subgroups and observation delay. A fast failure can require a timely alert before an end-of-window aggregate is available.
For acceptance, recover the lot or item, what counts as a defect, the sampling/inspection method, and the consequences of accepting unacceptable output or rejecting acceptable output. Obtain the qualified plan where it is missing. An operating practitioner can use a supplied plan without deriving its statistical design anew.
OPS.18:4.3 - Interpret the observation within its evidence limits
Calculate the selected quantity from its declared population. Use OPS.15 when event identity, coverage, time or missing observations need repair. Preserve any consequential uncertainty in the control decision.
A process-monitoring signal supports the action specified by its policy; it does not identify the cause by itself. An observation within the limits can still violate a product requirement. A capability claim needs the relevant stable-process and specification basis.
An error budget expresses permitted service loss for a stated objective and population. Compare observed loss with that allowance, then apply the authorized policy. Protected safety, human or clinical conditions remain applicable regardless of budget remaining.
A sample acceptance result supports the named lot decision under its plan and risks. It does not establish that every item conforms, that the process is stable or that a known failure mechanism has been corrected.
OPS.18:4.4 - Carry out containment or recovery and preserve continuing service
Select an action within the available authority: continue with observation, segregate affected output, pause a risky change, adjust admission, restore a known workable configuration, rework a lot or request the needed professional decision. State the affected scope and any service that must continue.
Establish that the required capability, access and human protections are in place. Obtain any missing contribution before starting work that relies on it. Use OPS.12 and OPS.13 if recovery competes with existing service or relies on extra cover. An urgent label can identify priority; the actual assignment and authority determine who may act.
Where containment restores service before the cause is known, state what remains unresolved. Enter the following inquiry when prevention still needs an explanation. Extending a correction to new operating conditions requires support for its protective effect there; a stronger causal claim needs evidence for that claim. Reuse sufficient existing results, and apply a qualified correction directly when they settle the action.
- Reconstruct the incident. Recover the failed result and requirement, affected occurrences and configurations, sequence, effects and containment already performed. Use sources that cover the events in question, such as observations, permitted records or participants’ accounts. Seek a missing contribution when the reconstruction needs it. Distinguish observations from inferred links and identify missing facts that could matter to prevention.
- Develop the material explanations. Follow contributing conditions beyond the immediate symptom, allowing several interacting conditions or rival accounts. Use B.5.2 when plausible explanations still need to be developed. For a disputed link, identify the existing observation, established mechanism or attainable test that could support or challenge it. C.28 helps qualify the causal conclusion; domain knowledge and evidence must supply the links in this incident.
- Choose supported prevention. Compare retaining adequate protection, a narrow configuration or access correction, a change to the reusable way of working and a larger redesign where these are credible alternatives. Assess future exposure and avoidable consequences together with the full effort, delay, displaced service and other burden of each change. C.11 governs the choice; use C.11.CRC when the contribution of a finite change to the present arrangement needs that comparison. Zero loss in a near miss does not remove the exposed future consequence.
- Assign and verify the chosen change. If a change is selected, name who will deliver it, the required result and its completion conditions. A recurring operating Method change belongs to OPS.16; choosing among ways to retain in an operating repertoire belongs to OPS.17. A local configuration, access or maintenance correction can finish as that correction. Verify completion separately from the restart conditions and later recurrence observations in :4.5.
Require sufficient support for the proposed protection under the relevant explanations that remain plausible. If they all support the same available correction, choosing a final causal account is unnecessary for that prevention decision. Retain the unresolved explanation wherever it limits a claim or later use. Obtain another observation when it can change the prevention, its permissibility or burden, or what the evidence warrants saying. If the worth or feasibility of that inquiry is itself unsettled, use C.11.DUA. Applicable protection and evidence requirements continue to govern the action.
OPS.18:4.5 - Verify restart and choose the next observation
Recover the condition under which service, normal production or discretionary change may resume. Use current evidence that establishes the required condition, or obtain the missing result. Depending on the condition, the basis can be applicable test evidence, a confirmed working configuration, restored service behavior, qualified acceptance or another required result.
Check the observation’s scope and time. A restarted process, a new reporting period or an empty incident queue is not itself evidence that the defect was corrected. Preserve residual uncertainty and a response if the condition fails again.
Choose follow-up from the consequence and detection need. Large isolated departures, small persistent drift and rapid incidents may need different observation rules. Retain enough evidence for the continuing decision, and end collection when its result no longer serves a decision, required operating claim, assurance or recovery.
Return the supported quality or reliability conclusion, its evidence and the affected population or configuration. If an operating response is required, state the action, its authority and any restart or monitoring conditions. The existing account or display can carry the result.
OPS.18:5 - Archetypal Grounding
OPS.18:5.1 - A process signal calls for containment and investigation
In this constructed recurring inspection operation, the supplied stable reference proportion of nonconforming items is p₀ = 0.02. Samples contain n = 200 independent, comparable items under the stated binomial basis. The local monitoring policy uses a three-standard-deviation p-chart rule and calls for segregation of the affected output and investigation when the upper limit is exceeded.
The upper limit is p₀ + 3√(p₀(1 − p₀)/n) = 0.02 + 3√(0.02 × 0.98 / 200), approximately 0.0497, or 4.97%. The corresponding lower value is negative and is truncated to zero.
The next sample contains twelve nonconforming items: 12 / 200 = 0.06, or 6%. This exceeds the specified upper limit. The practitioner applies the policy’s containment and investigation response and identifies the sampled output, source process and current configuration.
The arithmetic establishes the signal under that rule. It does not identify why the items failed, determine another lot’s disposition or show that the process is capable of meeting a product specification. The three-standard-deviation calculation defines the limit for this rule; it does not supply an exact confidence or false-alarm probability. With this low reference rate, a claim about false-alarm or missed-detection probability needs an appropriately qualified binomial or other statistical design.
Suppose the investigation finds a changed setup condition. Returning to the earlier setup and obtaining the required process and output evidence can support restart under the responsible authority. A single subsequent point below the limit is insufficient to establish every one of those claims. A persistent smaller shift may call for a monitor such as an exponentially weighted moving average (EWMA), which retains information from successive observations, if its detection properties fit the need.
Change the sampling premise. The 200 inspected items now come as fifty groups of four, sharing one setup within each group. In this constructed return, the qualified statistical supplier establishes a bounded model for the defect being monitored: all four items in a group share its conforming/nonconforming state; different sampled groups are independent; the stable reference probability is 0.02 per group. The sample’s twelve defects occupy three groups. The count is therefore 3 of 50 independent group outcomes, not 12 of 200 independent item outcomes. The original 4.97% limit is inapplicable. With this model, its apparent trigger would correspond to at least three defective groups, with a baseline false-signal probability of about 7.84% per sample.
The operating owner needs to protect this finite campaign and decide whether a recurring-shift monitor adds a useful further result. The current product rule already holds any known defective group’s output. The supplier is asked to compare early detection with the available inspection and response time, including a persistent rise from 2% to 6% defective groups. It returns these two explicit candidate rules under the stated independent-group model and fixed baseline:
| Candidate monitoring rule | Baseline false-signal probability | Detection probability if the group rate is 6% throughout the tested observations | Delay and use |
|---|---|---|---|
| Investigate at five or more defective groups in one fixed sample of 50. | approximately 0.321% per sample | approximately 17.94% per sample | Available after that sample; often misses this small persistent shift. |
| Investigate at ten or more in one prespecified, nonoverlapping block of four such samples, 200 different groups in total. | approximately 0.748% per block | approximately 76.57% per block | Uses four rounds of evidence; it does not provide an earlier warning. |
These exact-binomial tail calculations are a constructed statistical return, conditional on the supplied model; they are not lifetime false-alarm guarantees. Repeated blocks create repeated opportunities to signal. They do not authorize changing the baseline after seeing unfavorable observations or treating overlapping blocks as independent.
Suppose the next four rounds contain three defective groups each. No individual sample triggers the first rule; twelve of 200 groups triggers the second at the fourth round. The authorized response is a wider process investigation and containment at the supported scope. Each known defective group was held when found under the independent product rule; waiting for the fourth-round monitoring result cannot authorize its release. Unaffected output still uses its own acceptance basis.
Include the whole price and reuse observations already obtained. In this finite campaign each round’s fifty groups are all its output. A qualified full screen costs forty staff-minutes per round, 160 over four rounds, and fits the service window. That adequate product-protection rule applies with or without a process monitor; the monitoring rule does not replace it. Its observations already supply the group outcomes, so do not charge for a second sample. The monitor adds two minutes per round for group/time reconciliation, 120 once for qualification/setup and twenty for the wider investigation in the supplied signal trace: 148 additional minutes, or 308 including inspection, apart from protective handling common to both alternatives. Retain direct protection alone for this one-off use when no continuing exposure or other decision needs the separate recurring-shift answer. Where that answer is useful, compare its expected contribution with these added costs, actual signal workload and missed-loss consequences. The full screen protects this output without itself establishing the process-change claim. If action is needed before four rounds, request a qualified sequential design; the ordinary normal-data EWMA limits cannot simply be pasted onto these rare grouped counts. Correlation between groups, a changed defect mechanism or an unrepresentative baseline reopens this statistical return without canceling already supported containment.
OPS.18:5.2 - Service loss exceeds the agreed budget
In a constructed software service, the objective is 99.9% successful requests over the defined window. The account includes 1,000,000 eligible requests, with success and eligibility measured at the service boundary relevant to users. The allowance is:
- 1,000,000 × (1 − 0.999) = 1,000 unsuccessful requests;
- observed unsuccessful requests = 1,500;
- budget consumed = 1,500 / 1,000 = 150%.
The observed success proportion is 99.85%. The service has exceeded the stated allowance by 500 unsuccessful requests.
Its previously authorized local policy pauses discretionary feature releases when the budget is exceeded, permits the specified urgent recovery and security work, and requires investigation of the affected service. The practitioner applies that policy, names the eligible population and affected service, and directs the authorized recovery work. Another service needs its own objective and permitted response.
A total of 1,500 also needs timely interpretation. If most failures occurred in the last few minutes or affected one important user group, the aggregate alone can understate the current incident. Inspect the relevant time and group breakdown if it could change the containment or the scope supported by the evidence.
Now suppose a calendar boundary starts a new reporting window while the failing request path remains impaired. The operation still lacks restoration evidence. Later, the recovery team restores a known working configuration, verifies the previously failing user path and obtains the live observations required by the agreed restart criteria. The responsible service owner can then decide whether to resume discretionary changes. Keep any unresolved causal or recurrence question visible.
The responsible owner uses budget consumption in the stated service policy. Independent safety and acceptance conditions still apply, and recovery work requires a qualified, authorized performer for each action.
OPS.18:5.3 - The lot decision uses its own plan
A separate constructed supplier lot arrives after the process signal above. The supplied product-acceptance plan defines the lot, defects, sampling and disposition authority. For this illustration, it specifies a random sample of fifty items and acceptance only if at most one is nonconforming. Its qualification for the actual product and producer/consumer risks belongs to the supplied plan.
The sample contains two nonconforming items. The acceptance practitioner rejects or segregates the lot as the plan requires and obtains the prescribed rework or supplier response. Even if a process chart for that producer has no current signal, the lot fails this stated acceptance rule.
If the lot had passed, the result would support its disposition under the plan’s risks. It would not settle the earlier process investigation. If the plan or its risk qualification is missing for the actual use, obtain that result before relying on this sample rule; these illustrative numbers do not provide a general acceptance plan.
OPS.18:5.4 - Human service and AI assistance need their actual result
In a hospital operation, the due-request account can show missed service times while clinical priority changes the permissible response. The operating coordinator uses qualified clinical decisions and the current service authority to choose additional cover, rescheduling or another permitted intervention. A low average waiting time cannot clear an individual case whose required condition is unmet.
After an intervention, the coordinator observes the affected service and support work under the selected continuation conditions. A clinical outcome or health-effect claim requires its own evidence. OPS.12 helps preserve human conditions when recovery work adds demand.
In an assisted production service, a monitor may show fewer detected defects after a model change while the current sample excludes difficult requests. Recover that population before interpreting the improvement. Continue or contain the affected use according to the requirement and policy for accepted outputs.
A changed model can also alter the relevant failure modes. Qualification of the current acceptance method, actual accepted results and any affected customer promises may therefore need reconsideration. A passed sample from the earlier version is reusable only for the claims and conditions it still supports.
OPS.18:5.5 - An unresolved cause need not delay a supported correction
In this constructed print-shop incident, the customer approved proof P2, but the booklets reproduce P1. Records and participant accounts establish that the operator followed the work card containing P1; P2 was unavailable at the station, and the admission check asked only whether a proof was attached. The quality rule requires the affected order to be held.
Trace how P1 reached the station and why P2 was unavailable. Two explanations remain plausible: the preparer copied the earlier attachment, or the station received it from a stale synchronized folder. The records do not distinguish those paths. Both leave the same exposed condition: production can start without checking the proof against the customer’s approved edition.
For this case, a qualified proof-control procedure is available for both paths: retrieve the approved proof through the authorized source, check its edition at the station and require first-article acceptance before releasing the order. The responsible production manager has authority and the necessary staff and access to apply it; its effort fits the continuing service commitments.
The manager applies that correction. Staff verify that P2 is available, perform the edition check and obtain the required first-article acceptance for restart. Selecting between the copying and synchronization explanations is not a prerequisite to this adequately supported response. Their difference would become relevant if, for example, a proposed automatic retrieval change protected only one path; that proposal would need the missing discrimination or a protection covering both.
OPS.16 addresses any resulting decision to change the recurring operating Method; OPS.17 is needed only for a repertoire choice among competing ways. Completion of the proof-control change is observed separately from recurrence over the later orders and exposure that the prevention claim covers. A clean first article does not establish a long-term recurrence rate.
If the edition check catches P1 before printing, no booklets are spoiled: the check has protected this order. Whether further change is needed depends on the remaining exposure and available protection.
OPS.18:6 - Bias-Annotation
Visible control limits can look authoritative even when their model or baseline does not fit the operation. Keep the required product or service result beside the monitoring claim and inspect the assumptions before extending its use.
A recent repair can also encourage early closure. Verify restored service at the affected scope, and distinguish that result from identification of the cause and evidence about recurrence.
OPS.18:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The requested result is clear. | Its requirement, population or configuration and consequence are recoverable. If a response is needed, so is its authority or the remaining gap. |
| The evidence method answers that question. | Monitoring, service-objective, acceptance, recovery and prevention uses retain their distinct bases. |
| The observation is interpretable. | Baseline, sample or event population, coverage, time, model and uncertainty fit the claim. |
| Any selected action follows the applicable rule. | Continuation, containment, acceptance, restoration or Method change uses the actual policy and protected conditions. |
| Any restart is supported. | Evidence or a qualified result establishes the required condition at the relevant scope and time. A reporting reset alone cannot support restart. |
| Remaining work is directed. | Unresolved cause, recurrence risk, missing professional result or changed method assumption has a concrete receiving use. |
| Prevention has sufficient support. | Further discrimination is sought when its attainable result matters to prevention, permissibility, burden or a required conclusion; a common adequately supported correction can proceed with the remaining explanation explicit. |
OPS.18:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Treat statistical stability as product conformity. | Compare output with its requirement and obtain the applicable capability or acceptance result. |
| Use a chart signal as proof of a specific cause. | Contain as required. Pursue a causal investigation when its result is needed. |
| Let an error budget authorize every kind of loss. | Preserve independent safety, human, clinical and acceptance conditions. |
| Accept a lot because the process chart looks normal. | Apply the lot’s qualified acceptance plan and risks. |
| Resume normal work when the reporting window resets. | Verify the actual restart conditions and use the applicable continuation authority, obtaining a decision when the conditions require one. |
| Reuse an old monitor after the population or failure modes change. | Requalify the affected observation and detection method for the new use. |
OPS.18:9 - Consequences
The practitioner can connect quality and reliability evidence to a concrete operating response. The action remains scoped to the affected output, service or configuration, while necessary service can continue under its own conditions.
Monitoring and acceptance can incur false alarms, missed failures, inspection cost or delayed service. Recovery can restore operation while leaving a cause unresolved. Selecting the method and evidence by consequence makes these trade-offs visible for the operating question.
OPS.18:10 - Rationale
Monitoring, acceptance, restoration and prevention regulate different moves. Selecting the evidence from the current decision preserves the meaning of a statistical limit, a product requirement, a service objective and a supported protective change.
The separation between containment, restored service and causal knowledge also supports proportionate action. A practitioner can act on sufficient operating evidence while obtaining the stronger result needed for prevention, wider use or a more consequential commitment.
OPS.18:11 - SoTA-Echoing
Select quality and reliability evidence for the question being answered. A monitoring rule signals observations that meet its criterion under the stated model, a service indicator measures the agreed outcome, and acceptance and restart each require their own criteria. These distinctions determine what follows in the worked cases.
| Source and practice question | Selected move and alternative | Operative contribution and limit |
|---|---|---|
| NIST proportions control charts and process stability | Use a monitor suited to recurring variation, instead of reacting to every raw fluctuation. | Sections 4.2–4.3 and 5.1 preserve baseline, population and model. The original three-sigma signal and the changed group-count return answer different sampling conditions; exact tail risks are stated only for the latter’s supplied model. |
| NIST EWMA guidance | Consider a memory-bearing monitor when persistent small shifts matter more than one large point. | Sections 4.5 and 5.1 retain detection delay and assumptions as reasons to change the method. NIST’s ordinary EWMA limits assume independent data and their tabulated design assumes normality; grouped rare-event monitoring needs a qualified design, not merely the chart name. |
| NIST process capability and acceptance sampling | Select specification/capability or lot-disposition evidence for that question, instead of reusing a monitoring verdict. | Sections 4.2–4.3 and 5.3 keep the lot, defect and producer/consumer risk basis separate. |
| SRE service objectives, error-budget policy and alerting on SLOs | Relate user-relevant observed loss to an agreed action and timely detection, instead of using infrastructure availability alone. | The service case adopts the loss calculation and policy relation. Local targets, exceptions, authority and restart evidence are supplied for the actual service. |
| Ries, The Lean Startup (2011), chapter 11; Lean Enterprise Institute, Five Whys; Google SRE, Postmortem Culture (2016) | Recover contributing conditions and assign supported prevention, instead of stopping at the first symptom or treating a question count as causal proof. | Sections 4.4 and 5.5 adapt incident reconstruction, knowledgeable participation, countermeasure selection and follow-up. The historical accounts and practice guidance do not prove a particular causal chain or a recurrence reduction; those claims need their own evidence. |
The NIST handbook provides standing technical models. The SRE Workbook supplies software-service guidance and a dated 2018 policy example.
For an individual known failure, immediate qualified containment can be the stronger response than developing a new statistical monitor. For recurring uncertain behavior, a designed monitor can reduce reactive disturbance and improve timely detection. Reopen the selected method when the population, baseline, loss consequence, detection need or authorized policy changes.
OPS.18:12 - Relations
OPS.15 helps construct the observation account when its subjects, coverage or definitions are unresolved. OPS.4 guides shared attention to qualified operating state. OPS.5–OPS.7 guide admission, continuation and attention to aging work when those actions depend on the control result.
Use OPS.12 for human conditions and OPS.13 for service commitments and resource choices affected by containment or recovery. OPS.14 helps compare consequential operating and financial alternatives. OPS.16 evaluates a change to an operating Method; OPS.17 compares and refreshes the repertoire of ways available for operating work.
B.5.2 helps develop rival explanations of the incident; C.28 qualifies their causal support. C.11 and C.11.CRC support the choice and whole-burden comparison of preventive changes. C.11.DUA enters only when the contribution or feasibility of a requested inquiry remains in question.
FPF C.16 governs the measures and statistical assumptions relied on, and A.10 preserves evidence reach. A.11.OP limits additional monitoring or records to their decision, assurance or recovery contribution. Use the qualified acceptance, protection or restoration result for the domain. Obtain it from the appropriate source when it is missing.
OPS.18:End
OPS.19 - Reconcile Simultaneous Operating Work Across Cases and Scales
Status: Stable
OPS.19:0 - Use This When
Use this Method when several kinds of operating Work are present together and a locally sensible choice can harm another case or service, worsen an operating result, or move a result into a horizon where its consequence changes. Typical moments include keeping a busy resource utilized while incident coverage is thinning, completing one case sooner by moving delay to a shared acceptance queue, or starting improvement Work while current commitments and human recovery still need protection.
The first useful result is a short cross-scale operating account and decision. It names the local choice, the simultaneous Work and relations on which it depends, the conflicting results and measures on their own subjects, feasible alternatives, authority and protection conditions, the selected reconfiguration or bounded continuation, and the condition that reopens the decision. It may instead return one exact unresolved conflict when a necessary result or authority is missing.
Start here only when the decision genuinely crosses subjects, operating scopes, or time horizons. Use OPS.8 for one queue-policy question, OPS.9 for one current-constraint question, OPS.10 for one capacity-and-service comparison, and OPS.11 for one interacting-structure coordination question that those patterns can settle directly. Use current C.32.MWA.PP when the primary question is comparison of Method or candidate-account co-use rather than reconfiguration of continuing operating Work. Use OPS.16 when the current object is one operating Method change, and OPS.20 when the current claim concerns continuation or change of enacted practice in a practitioner population.
OPS.19:1 - Problem frame
Continuing operation brings several Work wholes and decision structures together. Customer or patient cases progress while shifts provide service, queues and constraints are coordinated, incidents or recovery Work consume margin, financial-control Work changes the feasible horizon, and Method-improvement Work may be planned or performed. These wholes can overlap without becoming parts of one master process.
A local measure sees only its own subject and scale. Rig utilization can rise while case completion, cash timing, incident resilience, or participant recovery worsens. Faster case admission can overload inspection or release. A change programme can meet its milestone while the continuing service loses a protected condition.
Here scale means the subject, operating scope, or time horizon on which a result is claimed. It does not imply a universal hierarchy of team, department, organization, or enterprise levels. Select the scales and relations needed to make or justify the current operating choice.
OPS.19:2 - Problem
Operations teams often receive several correct local accounts that recommend incompatible actions. A queue report says start now, a capacity account retains a recovery reserve, a service account says hold, a financial comparison favors deferral, and an improvement plan needs the same specialist. Combining the numbers into one dashboard does not reconcile their subjects, horizons, evidence, or authority.
An exhaustive enterprise model can describe many structures while leaving the practitioner unable to decide what to start, hold, reconfigure, or return. The practical need is a bounded decision that preserves each material result, exposes moved burden, and stops when an indispensable premise is missing.
OPS.19:3 - Forces
| Force | Practical tension |
|---|---|
| local action and wider consequence | A narrow choice is easy to execute, while its delay, risk, cash need, or burden may appear elsewhere. |
| immediate completion and retained resilience | Starting additional Work can consume recovery, incident or acceptance margin needed later. |
| unlike results and one decision | Service, cash, quality, human recovery, throughput, and evidence can all matter without one defensible common score. |
| simultaneous Work and sequence | Some Work has real order; other Work overlaps or remains a separate whole. One sequence can hide the conflict. |
| coordination and distributed authority | One operating decision needs several inputs, while clinical, safety, financial, service, and employment authority do not merge. |
| enough structure and timely action | Omitting a material relation makes the choice unsafe; mapping every relation delays the useful result. |
| current evidence and changing conditions | A previously justified decision can lose its basis when access, demand, commitments, support, or the evidence window changes. |
OPS.19:4 - Solution
Start with the local choice and the simultaneous Work it affects. Reuse an account that identifies the relevant relations, protection conditions and consequences across cases or horizons. If it leaves a consequential gap, establish the missing relation or identify the limit it creates. Use existing arrangements where adequate, construct a missing alternative when needed and compare materially different arrangements. Return a reconfiguration, a bounded continuation or the unresolved conflict within the available authority.
OPS.19:4.1 - Fix the operating question and exposed local choice
Name the operating System, the useful result or service that must continue, the receiving decision, the current horizon, and the exact local choice that exposed the conflict. State the local measure or reason supporting that choice and the consequence that could defeat it.
Examples are: start a third package to keep a rig utilized; release more cases into a diagnostic queue; extend a shift to clear backlog; defer inspection to protect a shipping date; or open a Method trial while incident coverage is reduced.
Reuse a current OPS.1 operating focus and OPS.3 subject account when they are available. If the subject, commitment, or decision cannot be identified, return that missing basis before comparing alternatives. If the local method already justifies the choice and no material consequence elsewhere remains to be reconciled, use its result and stop.
OPS.19:4.2 - Recover the simultaneous Work without forcing one whole
Identify the actual or intended Work whose relations matter to the decision. Check case Work, shift or continuing-service Work, queue or constraint coordination, incident and recovery Work, financial-control Work, and Method-improvement Work where they affect the choice, its grounds or its conditions of use.
For actual Work, preserve each independently supported Work whole and identify any supported parts or episodes separately. Record precedence, succession, or overlap only as relations among the identified Work. For intended Work, keep the WorkPlan and its conditions distinct from performed Work. Shared performers, timestamps, resources, labels, or diagrams do not establish parthood.
An admission–processing–inspection–delivery order can be real for one case while service coordination and improvement Work overlap it as separate wholes. Record both facts.
OPS.19:4.3 - Select the structures on which the choice depends
Select only the subjects, Work, Methods, resources, commitments, accounts, authority relations, and descriptions on which the choice or its conditions depend. Recover the exact obtaining relation or supported claim used from each structure.
Keep every process diagram, board, event log, financial model, and dashboard separate from what it represents. State what the representation preserves, what it omits, and which current decision uses it. Use C.32.MWA when the question needs several practice structures with different relations. Use its architecture evidence in the operating decision within the applicable authority.
Inspect a capable existing integrated account before assembling another. It may already preserve subjects, participants, production and coordination, resource calendars, promises and evidence. Reuse its supported results and establish any missing relation needed to compare, qualify or justify the choice. Count the cost of keeping that addition current, including specialist returns.
A compact working account can use these positions:
| Position | What to record |
|---|---|
| local choice | the proposed start, hold, sequence, allocation, or policy and the local reason for it |
| simultaneous Work | the independently identified Work wholes and only the part, order, episode, or overlap relations used by the choice |
| structures used in the decision | the cases, queues, constraints, resources, commitments, accounts, authority and descriptions whose relations matter to the choice or its conditions |
| conflicting results | each result or measure with its subject, scale, horizon, evidence, and protected condition |
| alternatives | materially different feasible arrangements, including bounded continuation and a truthful stop |
| return | authorized decision or exact unresolved conflict, together with its conditions and reopen trigger |
OPS.19:4.4 - Keep results and measures on their own subjects
State each decision-relevant result on the subject and scale it actually concerns. Case completion, total flow, service, current-constraint protection, resilience, cash, participant recovery, quality, and improvement evidence do not become one result because they appear on the same dashboard.
For every relied-on measure or claim, name its subject, scheme or interpretation, time window, evidence basis, and receiving use. Distinguish a direct observation from an association, contribution claim, forecast, or causal claim. Keep an unavailable result as a gap rather than filling it with a nearby proxy.
Use OPS.12 for human-condition evidence, OPS.14 for operating and financial consequences, OPS.15 for a decision-specific account, and OPS.18 for a quality or reliability control decision when their questions are current. Their results constrain this choice; they retain their own subjects and authority.
OPS.19:4.5 - Construct materially different operating alternatives
Compare the materially different arrangements already available, including the present arrangement and its limits. If they leave a material need, condition or conflict unresolved, try changing an allocation, sequence, start condition or service boundary to construct a practicable alternative. Check the resources, commitments, authority and protections it needs. Compare continuation, deferment, a hold or stopping where they have different consequences. If no feasible alternative can be found, state what excludes the options or which condition remains open.
For every alternative, expose where it moves delay, burden, evidence risk, cash need, service exposure, quality risk, or recovery cost. Ask which participant or operating scope receives that moved consequence and whether the required condition or authority is current there.
Preserve protected conditions before seeking a local gain. An alternative that requires unavailable access, unsupported overtime, missing clinical authority, consumed incident margin, or evidence from the wrong configuration is not yet feasible. Return the exact missing result instead of treating the alternative as available.
OPS.19:4.6 - Apply authority, commitment, evidence, and currentness conditions
Identify which operating policies can change within current authority and which decisions belong to another holder. Recover commitments, permissions, protection conditions, evidence windows, and stop rules that the selected alternative relies on.
Use C.11 for the bounded choice when the chooser, option set, rule, evidence, and authority are present. A coordination proposal, model optimum, or majority preference does not supply missing authority. A clinical, safety, legal, financial, employment, or release result remains with its professional owner.
When a required result is unavailable, decide only what can proceed without it and return the blocked remainder. Name the missing input and the decision that depends on it.
OPS.19:4.7 - Return the cross-scale operating decision
Return one of three useful results:
- Cross-scale reconfiguration. Change which Work starts or is held, or change allocation, sequence, support, or another operating relation so the material results can coexist under current authority and conditions.
- Bounded continuation. Keep the current arrangement for a named scope and interval when its consequences and protections justify doing so. A proposed change may consume a protected reserve or offer no justified improvement.
- Exact unresolved conflict. Name the incompatible results, missing evidence or authority, what can still proceed, and the result that must return before the decision can close.
Record the supported outcome, its conditions, preserved results and what would reopen it. Identify any deferred demand and who is responsible for a remaining decision. Do not infer implementation, later effectiveness, a changed Method, or cultural continuation from the decision.
Send the result to OPS.16 when trial feasibility or a protected trial condition relies on it. Send it to OPS.20 only as a candidate practice variation or consequence; that Method independently supports its population, predicate and continuation decision. Any selected intervention, needed authority or claimed later observation keeps its own basis.
OPS.19:4.8 - Keep the result short enough to use
The practitioner should be able to state the conflict, alternatives, decision, and reopen condition in a brief account. Add structural detail only when it changes feasibility, consequence, authority, or evidence reach.
Recognition is the ability to spot when a local operating choice is exporting harm or consuming another scope’s protected condition. Assurance requires supported Work and relation claims, qualified consequences, current authority, and explicit evidence limits.
The operator can identify the consequences across cases or horizons, compare feasible arrangements under their protections and return the authorized action or unresolved conflict.
OPS.19:5 - Archetypal Grounding
OPS.19:5.1 - PumpWorks: preserve incident coverage and recovery
In this constructed continuation of the PumpWorks control-service case, four ready test packages require two rig-hours each. Six rig-hours are currently available, and the retained adverse scenario includes one immediate two-hour repeat. A field incident consumes the change interval and two hours previously available from specialist E27 while exhausting the interruption reserve. No qualified relief is available for an extension.
The local utilization proposal would start all four ready packages and requires eight rig-hours. Preserving the retained two-hour repeat would require ten rig-hours, so an eight-hour plan silently displaces that repeat. The current financial comparison says only that qualified deferral of the third package is worth 700 more within the stated two-month horizon than immediate completion, while the service account protects incident coverage and E27’s recovery. No current priority, acceptance-window, or financial premise decides the fourth package.
| Decision-bearing item | Supported current fact | Conflict exposed |
|---|---|---|
| package cases and test Work | four ready packages, two rig-hours each, plus one retained two-hour repeat | two selected packages can complete and the repeat can remain reserved inside six hours; the third has a qualified deferral premise, while the fourth has no supported later disposition yet |
| incident and service Work | the incident consumes the change interval and interruption reserve | an extension removes protected response and recovery margin |
| rig and specialist resource use | the rig can appear locally available while qualified specialist support is not | rig utilization alone overstates feasible Work |
| financial consequence | qualified deferral of the third package is worth 700 more in the stated horizon | immediate completion is locally visible but financially worse under the current premises |
| proposed Method trial | its support, permission, service, and recovery conditions are not yet current | starting the trial would convert missing conditions into unsupported Work |
Compare a capable bounded integrated arrangement: its transaction account identifies the package request, promise, result and receiver; its schedule distinguishes test, incident and coordination Work, the six rig-hours, specialist E27 and the repeat reserve. The schedule fits two two-hour packages and reserves two more hours for a possible repeat. If the same arrangement also carries the third package’s qualified financial horizon and later agreement, the unresolved fourth-package disposition and E27’s recovery protection, reuse its complete return.
Where only the resource schedule is current, the needed addition is those exact receiving constraints. The available agreements and the current staffing result confirm the third package’s supported deferral and the absence of qualified specialist relief; the fourth package remains unresolved. These facts defeat an extension and keep the Method trial closed. Mapping them to the schedule costs source consultation, horizon checking and later refresh. That cost is warranted here because the proposed extension would consume a protected condition.
OPS.19 returns a bounded cross-scale reconfiguration: preserve incident coverage and E27’s recovery; complete the two selected packages and reserve the possible two-hour repeat inside six rig-hours; defer the third package to its qualified later slot; hold the fourth package’s start and return its later disposition as unresolved because no qualified priority, acceptance-window, or financial premise selects it; and keep the Method trial closed until service recovery, support, permission, and trial conditions are current. Reopen if qualified relief and access become available, the financial horizon or acceptance premise changes, a qualified fourth-package disposition basis returns, or the incident or service result changes.
This result does not decide the later Method change. It supplies OPS.16 only with the feasible trial boundary and protected conditions.
OPS.19:5.2 - Public-hospital emergency flow: bed occupancy is not the whole decision
A public-hospital emergency function can have a locally attractive bed-occupancy or diagnostic-throughput proposal while patient priority, diagnostic queues, room constraints, shift coverage, clinician recovery, and safety conditions recommend a different action. Use the applicable clinical and staffing judgments for those conditions.
The practitioner identifies the patient cases, current clinical decisions, queue and room relations, service commitments, staffing and recovery conditions, and the exact authority needed for the proposed change. A bounded result can reconfigure admissions or support only where those inputs permit it. If clinical priority, consent, safety, or staffing authority is missing, the result is the exact blocked decision and what can continue safely, not a utilization-driven substitute.
OPS.19:5.3 - AI-assisted software operation: generation rate is not release capacity
An AI-assisted software operation can raise candidate-change or ticket-completion counts while incident recovery, human review, test and assurance Work, release queues, provider or compute limits, and deployment authority remain unchanged. Model calls, tool episodes, candidate artifacts, accepted changes, release results, and user service are different subjects.
The practitioner compares the locally faster generation arrangement with alternatives that limit admission to acceptance capacity, reserve incident and recovery margin, or hold Work when provider or evidence conditions are stale. A cross-scale decision may reduce starts, reserve a compatible test environment, and return an unresolved release or assurance result. It does not infer model capability, accepted software, cultural adoption, or better service from more generated artifacts.
OPS.19:6 - Bias-Annotation
| Bias | Likely drift | Countermeasure |
|---|---|---|
| utilization bias | Busy resources are treated as the operating result. | State the useful service, case, cash, resilience, quality, and recovery consequences that can defeat utilization. |
| scale collapse | Case, shift, service, operating-System, and improvement results are added or averaged as though they share one subject. | Keep subject, scope, horizon, scheme, and evidence with every claim. |
| sequence bias | All simultaneous Work is forced into one process order. | Preserve independently grounded Work wholes and their actual order, episode, part, or overlap relations. |
| dashboard realism | A visible measure or diagram is treated as the obtaining operation. | Recover the represented subjects, relations, omissions, and receiving use. |
| scalarization bias | Unlike consequences are compressed into one ungrounded score. | Compare them through the applicable decision rule and protected conditions. |
| authority aggregation | One coordinator appears able to grant clinical, safety, financial, employment, and release decisions. | Name the actual decision holder and return missing authority. |
| action bias | Starting something is preferred to a bounded hold or unresolved result. | Keep defer, hold, stop, and exact missing return as legitimate alternatives. |
OPS.19:7 - Conformance Checklist
- Is the operating System, useful result, receiving decision, horizon, and exposed local choice clear?
- Are the simultaneous Work wholes and only their supported part, episode, order, or overlap relations identified?
- Are actual Work, intended Work, Methods, subjects, structures, descriptions, and records kept distinct?
- Does every selected structure or relation affect the choice, its conditions or its grounds?
- Are results and measures stated on their own subjects, scales, horizons, schemes, and evidence bases?
- Do the alternatives differ materially and expose moved delay, burden, evidence risk, cash, service exposure, quality risk, or recovery cost?
- Are protected conditions, commitments, authority, and currentness checked before an alternative is called feasible?
- Does the return clearly state reconfiguration, bounded continuation, or exact unresolved conflict?
- Are downstream Method-trial and cultural questions left to
OPS.16andOPS.20under their own entry conditions? - Can the receiving practitioner state the supported action or unresolved conflict, its scope and what would reopen it?
To recognize the situation, identify the material conflict and the operating scopes it connects. Assurance requires the obtaining relations, evidence reach, protection conditions, and authority used by the selected decision.
OPS.19:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| Maximize the visible resource. | Local utilization consumes service, recovery, cash, or acceptance margin elsewhere. | Compare the resource choice with every material protected result and moved burden. |
| Treat a shared timeline as proof that distinct Work wholes are parts or successive steps of one process. | Overlap and separate Work identities are lost behind unsupported succession or part relations. | Recover each Work identity and the exact temporal or part relation actually used. |
| Balance everything in one score. | Unlike subjects, horizons, and uncertainties disappear behind weights. | Keep each consequence explicit and apply a grounded decision rule. |
| Let the dashboard define the situation. | Records and representations replace the operation and its missing facts. | Recover subjects, evidence, omissions, and current relations before relying on the display. |
| Build an exhaustive enterprise map when a smaller account already settles the choice. | Unneeded modeling work delays the useful result. | Use the structures needed to compare or justify the choice and its conditions. |
| Treat a feasible model as authorization. | Another holder’s permission or professional judgment is bypassed. | Obtain or return the exact authority-bearing result. |
| Call the reconfiguration a Method improvement. | One operating allocation decision silently changes Method identity. | Open OPS.16 only when reusable Method semantics and a bounded evidence question are current. |
| Call one successful continuation cultural adoption. | Local use becomes an unsupported population claim. | Use OPS.20 for the independently supported population and cultural predicate. Current grounds can suffice; new intervention and later evidence are conditional on the claim or selected work. |
OPS.19:9 - Consequences
The operation gains a decision that can preserve current cases, service, resilience, cash, human recovery, quality, and improvement conditions without pretending they are one measure. A bounded hold or exact missing return becomes an actionable result rather than evidence of weak coordination.
The cost is explicit recovery of several subjects, relations, evidence windows, and authority conditions. Some decisions remain partial. This cost is proportionate when a relation can materially change the choice or establish the grounds for relying on it. Leave other detail with its source.
OPS.19:10 - Rationale
Simultaneous operating Work creates a domain decision beyond generic several-structure synthesis. C.32.MWA can produce the architecture evidence, but it does not select the operating reconfiguration, apply Operations commitments and protected conditions, or return the service, cash, quality, recovery, and authority consequences.
The Method also remains distinct from OPS.11. Interacting-structure coordination can settle one concrete coupling, while OPS.19 opens when several otherwise valid operating results conflict across subjects, scopes, or horizons and must be reconciled in one authorized Operations decision.
OPS.19:11 - SoTA-Echoing
The decision is how to reconcile simultaneous work whose service, resource, financial and human results can disagree. A serious alternative is a bounded integrated operating arrangement. DEMO distinguishes models from modeled subjects and permits a selected Scope of Interest: see the primary 2024 chapter summaries for EE Model Theory and DEMO Methodology. Its historical production/coordination and commitment distinctions are useful inputs.
The competent comparator in section 5.1 is a constructed arrangement using those distinctions together with a supplied resource schedule and domain policies. It retains separate work and parties, protects the possible repeat and reaches the same six-hour allocation. OPS adopts its results. The residual question is whether the qualified financial horizon, receiving agreement and specialist recovery condition are actually connected to the proposed extension. Sections 4.2–4.8 add only a missing consequence or authority relation and return an actionable bounded reconfiguration. If the incumbent already carries all of them, use it as the operating account.
The integrated material, information and financial model of Perez et al. (2023) is another serious source line for coupled decisions. The worked case uses the supplied resource schedule and domain policies. A more detailed model can be worth its data and maintenance cost when resource interactions repeatedly change the schedule; it is not necessary for the simple arithmetic in this case. C.32.MWA supplies general structure selection and synthesis, while the operation retains its actual allocation, service obligations and authority.
The full incremental burden of the OPS synthesis is recovering missing owner results, aligning their subjects and horizons, checking that one benefit has not displaced another protected use, and maintaining the resulting correspondence. It can lose to a mature integrated practice that already does this. TameFlow’s distinct operational, financial, informational and human concerns and the historical constraint-accounting sources help expose moved burdens. Reopen when a newly established relation affects the choice or the conditions that justify it, a source assumption ceases to fit, or a simpler incumbent preserves the same commitments, protections and truthful unresolved remainder at lower total effort.
OPS.19:12 - Relations
- Receives from:
OPS.1andOPS.3for the operating System, commitments, subjects, cases, resources, records, and relation candidates; reidentify any subject or boundary whose current facts no longer support the earlier result. - Receives from:
OPS.11,OPS.12,OPS.15, andOPS.17for interacting-structure evidence, human-condition consequences, a decision-specific account, and applicable status-preserved Method or repertoire claims. An absent or stale result stays an exact gap. - Coordinates with:
OPS.8–OPS.10,OPS.13,OPS.14, andOPS.18when queue, constraint, capacity, commitment, operating-financial, quality, or reliability results affect the choice or its grounds; each pattern retains its own subject and result. - Uses: current
C.32.MWAfor general several-structure architecture evidence,C.11for a bounded choice when its conditions obtain, and the current FPF Work, structure, evidence, measurement, temporal, causal-use, and representation owners for the exact claims relied on here. None supplies the Operations reconfiguration or its domain authority. - Provides to:
OPS.16when the trial’s feasibility or protected conditions depend on the cross-scale result. The receiving trial independently establishes its subject status, evidence, alternatives, authority, and available return. - Provides to:
OPS.20only as a candidate practice variation or operating consequence. The cultural Method independently supports its bounded population, predicate and continuation decision; an intervention, needed authority or claimed later observation has its own basis. - Does not replace: clinical, safety, legal, financial, employment, software-assurance, release, product, organization, capability, or cultural decisions owned by their direct practices.
OPS.19:End
OPS.20 - Deliberately Continue and Change Operations Culture
Status: Stable
OPS.20:0 - Use This When
Use this Method when you need to establish whether an operating practice persisted or changed across a particular practitioner population, or decide how to support its continuation or change. Typical signs are that a method’s author or coach will leave, two shifts use the same carrier differently, an operating rule is visible but not followed independently, or a local improvement must survive handover without becoming a compulsory rollout.
The first useful result is an account of what continued, changed or remains unknown within the stated population and period. Identify the Operations Management Discipline or smaller practice, operating setting, relevant interval and the admitted Method or candidate or observed practice at issue. Give the cultural claim, its participants, applicability, test and evidence. Use an existing predicate when it fits. If a decision is requested, give the supported continuation, revision, branch, replacement, stop or remaining uncertainty. Pursue a new observation or intervention when its attainable contribution warrants the burden.
Use OPS.16 for a local Method-change decision, including trial Work when that decision needs it. Use OPS.17 to compare or refresh a repertoire of operating Methods. Use OPS.19 when simultaneous Work across cases or scales must first be reconciled. A publication, training event, tool rollout, local project decision, or one successful service episode stays with its direct owner unless a bounded population relation is also current.
Here Operations culture is ordinary practice wording for how the named population generates, transmits, recognizes, selects, remembers, retains, changes, or loses Operations practice. Identify the participants in the relation being claimed.
Recognition concerns continuation across practitioners. Assurance supports the selected population claim, with its status, participants and interval. A new intervention additionally needs feasible authorized work; a later-result claim needs later observations. Sufficient current grounds can finish the account without another experiment.
OPS.20:1 - Problem frame
Operations depend on practices that cross shifts, sites, providers, and generations of practitioners. Readiness checks, incident stops, acceptance rules, recovery routines, and case-specific judgment can disappear when one experienced person leaves, or persist only as a card that no longer guides actual Work.
Visible activity can overstate continuity. Handover attendance establishes participation in that event; receiving enactment requires evidence of the receiver’s operating Work under the conditions intended for that use. Keep support that belongs to the practice. Independence from a coach, retention after a specified interval or support change, and a causal service effect are stronger claims with their own evidence needs. A carrier or usage count may help locate those observations.
Which relation concerning the practice does the evidence support in this population and period? What might explain the observed successes or failures? If a decision is requested, determine what continuation or change is justified. A further observation or intervention earns its place through its attainable contribution to the required claim or decision.
OPS.20:2 - Problem
A team wants useful operating practice to continue and harmful or stale practice to change. It often responds with training, publication, a required field or a tool rollout because those actions are visible and easy to count. To determine what changed, identify the relation actually claimed, its participants and applicability, and apply its test to the available evidence.
Collapsing the practice, its description and the population claim also hides what remains unknown. A local successful use may be established while selection by another shift or retention after support ends is unresolved. Obtain a further observation when its attainable contribution to the receiving use warrants the effort.
Intervention adds a further boundary. An Operations lead may be permitted to change one handover or local carrier without authority over another shift, professional practice, employment condition, safety decision, or wider field. The proposed intervention, performed Work, changed subject, later cultural observation, and later operating consequence must therefore remain separately inspectable.
OPS.20:3 - Forces
| Force | Practical tension |
|---|---|
| continuity and change | Stable practice supports reliable handover, while stale practice can preserve yesterday’s assumptions. |
| carrier and enactment | Cards, descriptions, repositories, rules and training make practice recoverable, while enactment under the intended conditions still needs evidence of use. |
| local use and population claim | One practitioner can use a Method correctly, while the relation claimed for a population needs its own participants and evidence. |
| speed and retention | Receiving enactment can be observed soon, while retention and loss need later intervals. |
| explanation and action | A visible failure invites immediate retraining, while access, recognition, authority, applicability, or Method fit may explain it better. |
| service and cultural evidence | Service, reliability, flow, toil, adoption, and human-condition consequences matter, while they are not the cultural predicate. |
| authority and participation | A local Agent can alter an assigned carrier or handover, while wider professional or organizational change may remain outside its authority. |
| common language and status | School and community names help practitioners orient, while labels do not establish Method identity, enactment, or population adoption. |
OPS.20:4 - Solution
Bound the practice, practitioner population and period. Preserve the status of the practice and establish what the evidence supports about the cultural relation. Distinguish the relation from its description, supporting observations and operating consequences. If a continuation or change is requested, compare the credible options and explanations that matter to it. Propose a course to the decision holder or decide under the authority granted for the task. Carry out the decision when implementation is part of the task, preserving the required service protections. A new observation or intervention must justify its design, effort, delay and displaced work through the contribution it can make to the question.
OPS.20:4.1 - Bound the practice, population, and status branch
Name the current Operations Management Discipline result when it is available. Otherwise name the smaller practice and population under C.36 and keep the Discipline claim unresolved. State the operating System or service, place, period, qualification window, and the people or other actual participants meant by transmitting, receiving, recognizing, selecting, remembering, retaining, generating, or losing.
Then preserve the input status:
| Starting branch | Required input | Claim still missing |
|---|---|---|
| admitted Method | Exact admitted local U.Method variant, exact relied-on version or separately classified U.MethodDescription, and bounded evidence for the operating use | The practitioner population and cultural predicate remain independently supported claims. Any intervention, needed authority, or claimed later observation has its own basis. |
| candidate or observed practice | Exact candidate account or source-described practice variation, its status, actual claim-bearing materials, and independently supported Work facts | The account can support an observation about receiving use. Admission as a Method, classification of a MethodDescription and enactment of that Method each require their own grounds. |
An OPS.16 return may supply either row exactly. An OPS.17 repertoire may supply current alternatives and lineage claims. An OPS.19 result may supply a candidate variation or consequence when its cross-scale decision matters. None supplies the cultural claim by adjacency.
OPS.20:4.2 - Select one value and one testable cultural predicate
Choose the relation needed to answer the question about the population or support the requested decision. Recover its value, participants and applicability, then apply the existing predicate’s test. If no suitable predicate expresses the needed relation, develop its meaning and a discriminating positive and failed case before relying on it. The examples below illustrate these distinctions.
| Predicate family | Operations question | Example positive and discriminating negative |
|---|---|---|
| generation | Did the named practitioners originate a distinguishable operating variation during the stated interval? | A source-traceable variation and its generating Work are recoverable; the negative is a relabelled carrier with no changed practice claim. |
| receiving enactment or another transmission relation | Does the receiver perform eligible Work using the admitted Method or the observed practice within its stated scope under the intended conditions of support? | An eligible case is handled under the rule and stop with the permitted help; the negative is a completed handover followed by an unsupported start. Test without the source practitioner or coach only when the later use requires that independence. |
| recognition | Does the named population identify the practice or result as the one meant by the local term in applicable cases? | Practitioners distinguish the practice from its serious rival; the negative is agreement on the label with incompatible case judgments. |
| selection | Does a named selecting participant or population choose the value under an explicit applicability rule? | Actual eligible decisions designate and use the selected value; the negative is a mandatory field with no corresponding Work. |
| memory | Can the population or its identified memory arrangement recover the value and its applicability at the named interval? | Practitioners recover the current rule and stop from identified carriers; the negative is an archive entry that directs a stale or unsupported action. |
| retention | Does the same predicate remain supported after the stated interval under the conditions being claimed? | Positive cases recur under those conditions; a failed case no longer meets the predicate. A claim of retention after support ends specifically needs observations after that change. |
| loss | Has a previously supported relation ceased for the named participants and interval? | Eligible cases now fail the earlier predicate under otherwise applicable conditions; the negative is only a missing carrier record with no observation of practice. |
Use an existing adoption or incident account when it identifies the eligible cases, observations of receiving use and interval relevant to the question. Where assistance matters, distinguish support available from the assistance actually used. Add a distinction when it could affect the cultural claim, its limits or a decision to continue, extend or withdraw support. Include the added observation and maintenance burden.
Use the lightest truthful claim. Apply A.6.RCD only when a reusable or local compound predicate is needed; open A.6.REL occurrence identity only when a later use must distinguish relation occurrences. State a missing cultural result where it limits the requested claim or decision.
OPS.20:4.3 - Separate the practice, carriers, Work, claims, and consequences
Recover what each observation establishes for the selected predicate:
| Subject or evidence | Required meaning for this use |
|---|---|
| admitted Method or candidate account | The exact admitted reusable way, or a source-traceable account of the provisionally distinguished way with non-admission explicit. |
| description episteme and carrier | What the separate description says, and which carrier makes it available to which participant and when. Method, description and carrier retain their different identities. |
| publication or training Work | What was actually delivered or performed and who participated. |
| operating Work | What the receiving practitioners actually did, with admitted enacted Methods where supported and the relevant performance evidence. |
| local decision or rule | What an authorized chooser selected, for which use and participants. |
| cultural claim episteme | The separately stated proposition about the value, population, relation and interval. |
| operating consequence | The service, reliability, burden or other outcome for its own subject and interval. |
For the primary predicate, identify the relation claimed in practice, the episteme that states the claim and the evidence relied on. Preserve unknown where a required observation is absent. Publication, training and local rule selection can support their own rows without establishing receiving enactment or later retention. A later observation does not create an earlier occurrence or prove that the intervention caused the change.
OPS.20:4.4 - Identify the participants and arrangements on which the claim or decision depends
Name the carriers, Systems, Work occurrences, decision rules, forums, assignments, permissions, authority relations, support arrangements, and selected structures needed to establish the claim, compare live explanations or carry out a selected intervention. State which participant can act through each and which condition it changes.
Do not bundle a card, board, handover, coach, rule, repository, and practice into one cultural mechanism. A carrier can improve access, a forum can supply recognition Work, an assignment can locate responsibility, and an authority predicate can permit a change; their effects and evidence differ.
Use A.22 only when the organization of identified constituents and their relations matters to the claim or decision. Use C.30 only for a current architecture question. A compact plain account is enough when the intervention depends on one carrier or one Work occurrence.
OPS.20:4.5 - Compare explanations that matter to the claim or decision
Retain credible non-equivalent explanations whose different consequences could change the continuation or warranted claim. Do not invent another explanation to fill a fixed count. Common rivals include:
- the carrier and visible rule are sufficient under the intended support conditions;
- case replay, coaching, local authority, or a forum is needed for unfamiliar cases;
- practitioners cannot recognize applicability even though they can recover the content;
- required support or permission is absent;
- the Method no longer fits the changed operating condition.
For a needed comparison, state the consequences that differ and what an attainable observation could settle. Use sufficient current observations when they answer the receiving question. Select a new contrast only if its contribution warrants its whole cost, delay, practitioner burden and displaced service, including the effort of designing it; use C.11.DUA when that demand needs appraisal. Use B.5 and B.5.2 for a needed durable hypothesis account, C.27 for temporal adequacy, A.3.3 for a state-space and transition-law claim, and C.28 for causal reliance.
If the observations cannot distinguish the explanations, retain unknown for that explanatory question. An independently supported current continuation or local response can finish while the explanation remains unresolved. If a contrast is unavailable, state which claim remains open and what the other evidence still supports.
OPS.20:4.6 - Compare alternatives and bound the intended action
When the current arrangement leaves a receiving operation unavailable, use C.36.MC:4.5–4.6 to obtain the missing contribution. Start with the result the recipient needs, available inputs and intended support. Trace the operations and their conditions to the needed result using available explanations and observations. If a reason or operation remains missing, establish it through further observation or obtain it from a qualified source or practitioner. Compare the receiving condition with the demonstrated one, preserve the dependencies that still apply and change the affected operation, allocation or support. Follow that alternative back to its required inputs, participants and resources and forward to the receiving result.
If the recipient needs a capability change, use the development or technical method appropriate to that holder. Identify what the recipient needs for this operation. An existing source, procedure, retained state or tool can supply a missing input. Performance feedback may improve the operation of a service or support a person learning it. For human learning, provide the explanation, practice, feedback and variation the learner needs. Establish the time and support needed for the selected change. A familiar operation may need only a reminder. Keep a precise gap or restrict the offered use when the needed provider is unavailable.
When choosing a continuation or change, compare the alternatives that remain serious for the named population:
- retain the current carrier and selection arrangement;
- change one carrier, handover, forum, rule, or selection arrangement;
- branch the arrangement for a population, setting, case, or condition;
- replace the current means;
- stop or revert the intervention;
- preserve a relevant
unknown, selecting a discriminating observation only when it is useful and obtainable.
For the intended continuation or change where authorization is required, name the decision-making Agent and its assignment, permission, or authority predicate, participants, scope, positive basis, and protected conditions. A factual account creates no intervention to authorize. A selected change also states reversible exposure and its intended operating consequence. Expertise, sponsorship, attendance, tool ownership, assignment, permission, and authority are not interchangeable.
Keep service stops, safety, recovery, privacy, consent, security, release authority, employment conditions, and professional judgments with their current owners. A missing authority or protection returns an exact stop or narrower branch; it does not justify a broader rollout.
OPS.20:4.7 - Keep a selected change and its observed results distinct
When the task includes performing a selected change, use the direct Method under its actual authority and protections. Keep the following claims separate, using only those made by the result. A recommendation can finish as a warranted proposal; a claimed performed test or later cultural result cannot finish without its actual Work and observations.
| Claim | Basis when claimed |
|---|---|
| proposed intervention | Intended changed subject or relation, supported contribution, scope, needed authority, protection and stop; a later observation only for the selected inquiry or claim that needs it |
| intervention Work | Actual performers, enacted admitted Methods, history, interval, containing System, used Systems, any supported departures, and direct result |
| actual changed subject | The card, rule, handover, assignment, forum, carrier, or other subject that actually changed |
| later cultural observation | The same testable predicate applied to named participants at the named later interval |
| later operating consequence | Service, reliability, flow, toil, adoption, human condition, burden, non-use, rejection, or another direct result for its own subject |
An intervention can be performed without changing the intended subject. A changed subject can be followed by no change in the cultural predicate. A positive cultural observation can coexist with a poor operating consequence. Use the evidence and qualified judgment needed for each claim separately.
OPS.20:4.8 - Return the cultural account and any requested decision
State what the evidence supports about the selected practice and relation for the named participants, setting, period and qualification window. Identify its status and limits. If a decision is requested, return continue, revise, branch, replace, stop, a retained set or unknown, with the grounds, authority and protections needed for that outcome.
Include the following where they bear on the result:
- the available positive, negative, inapplicable, unknown, or missing-information observations, including later observations when a later claim is made;
- any serious alternatives and explanations still live;
- separate service, reliability, flow, toil, adoption, or human-condition consequences;
- population, authority, time, transfer, and causal limits;
- what change would warrant revisiting the conclusion and, for a selected inquiry, the next attainable observation.
Return a contradicted admitted-Method or lineage claim to its specific maintained result under OPS.16 or A.3.1.MV. When the receiving use warrants keeping a new reusable difference, send its changed operation or relation, origin, intended use and evidence limits to A.3.1.MV as a status-preserved candidate; the parent need not be false. Return repertoire implications to OPS.17. Return candidate or source material to its candidate account or source claim. Population spread alone changes none of those objects.
OPS.20:4.9 - Keep the first account small
A compact account states the bounded practice and population, subject status, selected cultural claim, applicable test, evidence and conclusion, including a continuation decision if requested. Keep the uncertainty, limits, operating consequences and grounds needed by its recipient. Develop new predicate cases, explanations, intervention details or later observations only when the current claim or selected work needs them.
An Operations lead can document how a practice continued, retain a supported bounded practice, repair a particular gap, or stop an unsupported branch without counting publication, attendance, fields or tool use as adoption. A selected worthwhile test still distinguishes its actual Work and results from unknown transmission, selection, retention or causality.
OPS.20:5 - Archetypal Grounding
OPS.20:5.1 - PumpWorks tests receiving enactment across two shifts
This constructed case continues the PumpWorks control-service operation. The bounded practitioner population is the coordinators of the named PW-Early and PW-Late shifts during the next six weeks. The admitted input is PW-TestAdmission-v2 : U.Method under exact PW-TestAdmission-Description-e2 : U.MethodDescription and the bounded OPS.16 evidence. That evidence includes one correct admission, one truthful hold for missing permission, preserved service conditions during the trial, and a branch decision. It establishes no population relation.
The value under test is the admitted package-admission Method for eligible control-service packages. The primary predicate is receiving enactment: after the initial author is absent, a shift coordinator independently applies v2 to an eligible package, records a truthful hold when a required condition is absent, and preserves the service stop. The discriminating negative is a completed handover followed by an unsupported start. Apply the claim distinctions in section 4.3: handover participation and a successful package result cannot substitute for independent receiving use.
For this decision, the existing handover account identifies the admitted v2 and exact description, the card and board support, performed replay and package decisions. It distinguishes supported receiving-enactment claims from open questions for the two shifts and six-week window, with the available observations linked to the claims they support. Service results remain separately qualified.
Two explanations remain live:
H-PW-1: the readiness card plus board field is sufficient for independent receiving enactment; it predicts correct unfamiliar as well as familiar decisions after access and handover.H-PW-2: replay of an incident or provider-handover case plus current local authority is needed for unfamiliar cases; it predicts correct familiar decisions but a false start or escalation failure when the unfamiliar case has not been replayed.
The control-service operations lead is the decision-making Agent for a bounded intervention. In this constructed case, current predicate PW-Handover-Change-Authority-1 permits the lead to add one case replay to the existing PW-Early handover for this six-week probe. It permits no change to field-release, safety, staffing, employment, or the PW-Late handover. Incident coverage, manual fallback, protected recovery, required permission, qualified support, and the stop on unsupported starts remain protected. The change is reversible by removing the added replay after the probe.
The selected intervention adds one familiar-case replay to PW-Early’s existing handover. The proposal, performed replay Work, revised handover content, and later package decisions are recorded separately. During the later interval, two coordinators independently apply v2 correctly in familiar eligible cases. A third coordinator starts a provider-unavailability case without the required support, satisfying the discriminating negative. The unsupported start is a failed receiving-enactment observation, not an authorized relaxation of the stop.
These observations do not isolate the card, board field, replay, authority reminder, practitioner background, or case familiarity as the cause. They also do not establish six-week retention: the observation window is still open. Service results from the three packages remain separate, and no favorable package outcome repairs the failed predicate.
Return revise for the unsupported provider-unavailability branch and retain the observed familiar-use contribution of the card-plus-replay arrangement for the named PW-Early coordinators. Keep the failed case, PW-Late, and longer retention distinct. Suppose another comparison would displace needed service without improving the grounds for continued use in the familiar cases. That bounded continue needs no new replay or causal explanation. The failed unsupported start remains failed and supplies no permission to repeat it.
Now suppose the next receiving use requires the provider-unavailability decision to be made independently. The current evidence does not support that extension. Select a provider-unavailability decision replay only if a qualified facilitator, participants, protected interval, and current permission for that additional replay are available and its attainable result justifies the effort of deciding whether the extension is supported. Permission for the trial does not authorize the extension. No unsupported operational start is part of that probe. The proposal completes the decision to test; a claimed tested extension still needs its actual result and independent later use. If the trial is unavailable or not worthwhile, withhold that extension while preserving the supported familiar branch. Reopen the affected result when the Method, description, population, authority, protection or receiving condition changes.
A capable adaptive SRE approach would also investigate the unsupported provider start, listen to the receiving coordinators and retain the useful familiar branch rather than mandate wider rollout. OPS adds the explicit receiving-enactment predicate only if the existing adoption account cannot distinguish the two supported familiar decisions from the failed unfamiliar decision, the unobserved Late shift and unobserved retention. If it already can, it suffices. Maintaining that distinction costs eligible-case observation, follow-up and communication; a further provider replay adds design, facilitation and displaced-service cost.
OPS.20:5.2 - A hospital keeps the cultural claim on the candidate branch
A public-hospital emergency-flow team carries proposed information-checking way ED-Handover-Readiness-CA1 from OPS.16:5.2 through its A.3.1.MR candidate account. Its operations compare available information with qualified handover requirements and return missing information or changed clinical conditions to their responsible owners. Method admission remains unestablished. The bounded population is the licensed transfer coordinators for one named emergency unit and shift over four weeks; the receiving-use conclusion applies to those coordinators and that interval.
The value being examined is the practice described by the candidate account, and the primary predicate is its receiving use under the stated support conditions, without a Method-culture claim. A positive case is an eligible transfer in which a coordinator performs the described information comparison and preserves the required return when information is missing or a clinical condition has changed. A negative case is a completed mandatory field followed by transfer Work with no recoverable check. The candidate account, checklist, field, training Work, actual clinical Work, patient case and population claim remain separate.
The support question is whether the checklist and field make those operations recoverable under the intended receiving conditions, or whether the coordinators also need qualified case discussion to recognize when the information check must return to clinical judgement. Retain a bounded receiving-use account when existing eligible-case evidence supports it. Select a comparison of ordinary handover and qualified case replay when its attainable contribution to the claim or decision justifies the licensed participation, support and time it needs. Any intervention stops until current clinical and administrative authority permits it and preserves consent, privacy, safety, staffing, worker health and medical priority.
The return can be a qualified continuation, a revision of the candidate account, or unknown for the unsupported population relation. It establishes neither Method admission nor clinical effectiveness. Return observations to the account and to a separate A.3.1 identity question only when that question is needed; clinical decisions and protections remain with their qualified owners.
OPS.20:5.3 - An AI-assisted software operation separates tool use from selection
A software operations group has admitted AI-ReleasePrep-v3 : U.Method and exact AI-ReleasePrep-Description-e4 : U.MethodDescription for one low-risk release-preparation family. A prompt repository, model endpoint, tool rollout, and usage counter are carriers, Systems, or records. They do not show that the on-call population selects or enacts v3.
The group bounds two named on-call rotations and one release interval. It tests one selection predicate: for an eligible low-risk change under the qualified provider and model condition, the responsible human practitioner selects v3 only when its human review, evidence capture, security check, fallback, and release-authority conditions are current. The negative is a logged tool invocation followed by release preparation that omits one required condition.
Credible rivals are that description plus repository access is sufficient, or that a case replay and explicit recognition of the provider/model qualification boundary are needed. Existing eligible-case observations can support a bounded current selection account under the unchanged qualified provider condition. Select a reversible provider-change replay for one rotation when its attainable result can materially improve the decision or its grounds at a cost justified by the use, with the participants, facilitator and protected time available, under current release and training authority. Actual handover, release-preparation, review, security and release Work remain separate, as do model calls, generated text, traces, test results, decisions and service consequences.
If the provider or model changes to an unqualified edition, the current branch stops and the named fallback applies. The result can retain one population-specific selection claim while returning the changed-provider branch as unknown or stop. Security, software assurance, model capability, release, employment, and governance consequences remain with their owners; usage count and one successful release establish none of them.
OPS.20:6 - Bias-Annotation
| Recurring bias | Likely drift | Working repair |
|---|---|---|
| rollout bias | Publication, training completion, access or a configured tool becomes population adoption. | Apply the needed population predicate to actual receiving use; develop a new predicate only when the existing one cannot express the claim. |
| label and school bias | A familiar community name, such as SRE or Kanban, substitutes for the practice being continued. | Recover the actual Method or candidate and the population claim needed here. |
| carrier bias | A maintained carrier is taken as evidence that the practice continues. | Recover receiving Work and the population predicate separately from access. |
| mandate bias | A required field or policy is read as selection and enactment by every practitioner. | Test actual eligible decisions and retain unsupported, copied, or bypassed cases. |
| organization-as-agent bias | “The organization adopted” hides selecting, receiving, and authorizing participants. | Bound the population and name the capable participant for each predicate and action. |
| success-story bias | A favorable service result proves transmission, retention, and causality. | Observe the cultural predicate and operating consequence separately; use C.28 only for causal reliance. |
| intervention bias | Performing training or changing a carrier is reported as successful cultural change. | Separate proposal, Work, changed subject, later predicate, and later consequence. |
| maturity bias | Several missing relations are averaged into an adoption stage. | Return supported predicates and explicit gaps, including unknown. |
OPS.20:7 - Conformance Checklist
- The Operations Management Discipline result or smaller practice boundary, operating System or service, setting, place, period, and qualification window are explicit.
- The practitioner population identifies the participants meant by transmitting, receiving, recognizing, selecting, remembering, retaining, generating, or losing.
- The input is either an exact admitted Method plus relied-on description and bounded evidence, or an exact status-preserved candidate or observed-practice account with no Method, MethodDescription, or enactment inflation.
- The selected value and cultural predicate have recoverable participants, applicability and a test. A new predicate has the positive and failed cases needed to distinguish its meaning.
- A missing cultural result is explicit when it limits the requested conclusion or decision. Support and independence conditions match the claim actually made.
- The account distinguishes the relation claimed in practice, the episteme stating it and the observations at the named intervals on which it relies.
- Each observation is used for the subject and claim it supports in section 4.3.
- A selected structure or architecture is opened when the claim or decision depends on how its constituents are organized.
- The account retains the credible explanations and uncertainty that affect the claim or decision. A new inquiry has an attainable contribution worth its whole burden, including design effort, and feasible participants, capability, access, resources, window and authorization.
- The intended action’s needed Agent, assignment, permission or authority predicate, participants, scope, positive basis and protected conditions are named. A selected intervention also bounds reversible exposure; a current account creates no new change to authorize.
- Where the account concerns an intervention, it distinguishes what was proposed, what Work occurred, what changed and what later evidence shows about the practice and its operating consequences.
- Operating consequences retain their own subjects; cultural and causal conclusions have the separate evidence they require.
-
The return states the supported cultural conclusion, its limits and any material gap or condition for reconsideration. For a decision it also states
continue,revise,branch,replace,stop, a retained set orunknown, with its grounds and material alternatives. A next observation appears only for a selected worthwhile inquiry; stronger later claims keep their own actual evidence.
OPS.20:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| “Everyone attended, so the Method was transmitted.” | Observe eligible receiving Work under its intended support conditions; require independence only for a use that needs it. |
| “The field is mandatory, so the population selected the practice.” | Test whether actual eligible decisions designate and use the value rather than merely complete the field. |
| “The repository has stable editions, so the culture retained the Method.” | Apply the retention predicate to the named practitioners, interval and support conditions; repository persistence and retained practice have different evidence. |
| “The service improved, so the intervention changed culture.” | Keep service evidence, cultural observation, and any causal claim separate. |
| “The school is popular, so its Method fits this operation.” | Use the school as a dated source or alternative and compare the exact operating move and conditions. |
| “The operations lead owns the process and may change every shift.” | Recover the actual assignment, permission, or authority predicate and its scope. |
| “One failed unfamiliar case means the practice should be replaced.” | Compare carrier, recognition, support, authority, and Method-fit explanations before choosing revise, branch, replace, or stop. |
| “No long study exists, so no local cultural claim can be made.” | Make the smallest bounded claim supported by current observations and state the limits on prevalence, causality and retention that remain on those grounds. |
OPS.20:9 - Consequences
Operations practitioners can deliberately continue or change practice without treating every rollout signal as culture. A testable predicate, bounded population and current evidence can establish what continued and support any decision now required; a new discriminating observation is selected when it can improve that use enough to warrant its feasible work.
The method also preserves useful local knowledge. A card, replay, field, forum, or authority reminder can remain in the retained set for the use it supports even when another shift, unfamiliar case, long-term retention, or causal explanation remains unknown.
The work takes time to identify the practice and obtain evidence that covers the claim. Retention and loss can require longer intervals, and separate service or human consequences may need specialist Work. Neither a current account nor an unavailable future observation authorizes an unsupported population change.
OPS.20:10 - Rationale
Cultural continuation concerns identified values and participants. Relating the claim to its applicable test and actual cases helps determine whether the next action should change access, recognition, support, authority, applicability or the Method itself.
Credible explanations can affect what the evidence establishes and whether a change would help. Carrier sufficiency and replay-plus-authority dependence can call for different observations, but distinguishing them is not required for every bounded continuation. A small reversible probe is selected when its attainable contribution warrants its burden, without claiming control of the whole practice or unsupported causality.
Keeping the Method, description, carrier, Work, claim, evidence, and consequence separate also preserves the earlier Operations results. OPS.16 can remain a valid local Method decision while OPS.20 finds that receiving enactment failed in one population. A population observation can inform the repertoire without silently rewriting Method identity or service authority.
OPS.20:11 - SoTA-Echoing
The question is how to continue a useful operating practice among its receiving practitioners, and when to change its support or scope. Adaptive SRE practice provides a comparison in the PumpWorks case. Google’s organizational-change account, especially “Common Tooling Adoption in SRE” describes attention to differing receiving needs, changes in staffing and support when an arrangement failed, migration cost and voluntary uptake. It also permits specialized solutions where a common one does not fit. These are practitioner case observations, not universal causal estimates.
Apply that capable approach to PumpWorks. It can keep the familiar practice, investigate the unsupported provider start, improve receiving support and avoid extending an arrangement whose local value does not justify migration. OPS adopts those moves. Its residual contribution is a more exact decision claim when “adoption” leaves the matter ambiguous: which practitioners independently enact which admitted practice in which eligible cases and interval, and which failed observation defeats the proposed extension? Sections 4.2–4.3 and 5.1 distinguish receiving enactment from participation, institutional selection, carrier availability and longer retention. Two correct familiar decisions and one failed unfamiliar decision support the bounded familiar branch, not both shifts or six-week retention.
This distinction changes the return only when the incumbent adoption account lacks it. If that account already separates eligible use, failed cases, population and interval, reuse it without a parallel cultural register. The full extra burden otherwise includes recovering the exact practice, observing relevant later decisions, retaining failures, communicating use limits and maintaining them when practitioners or support change. A new replay also needs case design, facilitation, permission and protected service time. Continued observation can cost more than the decision it might improve; section 4.5 permits a supported current decision to finish and selects further inquiry only for a worthwhile attainable contribution.
Current C.36 supplies cultural-relation distinctions and C.36.MC supplies their Method Engineering use. OPS adapts them to operating authority, service protection and repertoire consequences. The SRE postmortem-culture account provides a complementary account of learning from failure and making follow-up work actionable; it supplies neither proof of a population relation nor the cause of PumpWorks’ failed case. The directly cited primary accounts are the source returns for these contributions; publication or institutional endorsement of any description is not evidence of its enactment.
Reopen when a new eligible failure, changed support, authority, population or interval changes the bounded return; when evidence warrants or defeats the proposed extension; or when a capable incumbent preserves these decisions at lower total burden.
OPS.20:12 - Relations
C.20 supplies a Discipline result when one is needed. C.36 governs generation, transmission, recognition, selection, memory, retention, loss and intervention distinctions. C.36.MC supplies the admitted-Method and candidate branches, predicate use, receiving explanation and adaptation, human and technical support, authorization and bounded return. Its :4.5–4.6 develops the missing receiving contribution when recognition of a gap is not yet enough. OPS.20 retains the Operations practitioner population, operating input, authority, service and reliability conditions, consequences and repertoire return.
OPS.16 can supply the admitted-Method or candidate/observed-practice input with its existing status and evidence. OPS.17 can supply repertoire alternatives and lineage claims; OPS.19 can supply a practice variation or operating consequence. Use OPS.20 to establish the receiving population claim and, when requested, decide what to continue or change. Obtain intervention authority and later observations for the work or claim that needs them.
OPS.12, OPS.13, OPS.14, OPS.15, and OPS.18 retain human-condition, service, financial, account, quality, and reliability questions when the cultural account or decision relies on those consequences. An actual OCE.11 result may supply obtaining simultaneous-Work conditions; a plan or possible-future arrangement does not.
A.3.1 and A.3.2 govern Method and MethodDescription status. A.13 and A.15.1 govern actual performers and Work. A.6.RCD and conditionally A.6.REL govern the bounded relation claim and occurrence identity. A.10, C.16, C.27, and C.28 retain evidence, measurement, time, and causal questions. B.5 and B.5.2 govern durable hypotheses and consequences. C.11.DUA appraises a questionable inquiry demand, including design and whole burden; C.11 governs an already formed bounded choice. A.22 and C.30 apply when the required cultural claim or decision depends on the organization of the selected constituents and relations.