Part IX — Improve Methods, Control Quality, Reconcile Work, and Continue Practice

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

OPS.16:0 - Use This When

Use this Method when repeated delay, rework, blockage, burden, quality failure, or a changed condition makes one operating way current for an evidence-bearing change decision. Enter through one of two branches: an operating Method already admitted as U.Method, or a provisionally identified reusable way carried only by a source-traceable A.3.1.MR candidate-account episteme.

The first useful result preserves that starting status. For an admitted Method, it names the exact Method and relied-on version or U.MethodDescription, the operating use, proposed change, bounded trial question, evidence status and decision that the evidence can change. Before admission, it names the candidate reusable way only through its source-traceable account, real rivals, gaps and explicit absence of U.Method and U.MethodDescription status. A distinguishing question is included only when it changes the receiving use. The account can support an identity test, revision, comparison, stop or selected further observation without an automatic future-study commitment.

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 ME.11-ME.16 when the specialist question is trial design, coherence, fit, worth, lineage, introduction, or revision without the receiving Operations decision.

Recognition is noticing that a recurring operating difficulty challenges a way of working rather than only one case. Assurance preserves exact Method or candidate-account status, source support, use limits, needed authority and the bounded return. A claimed trial additionally needs its prospective plan, independently admitted actual Work, typed observations and qualified evidence. A favorable episode, new board field or rollout supplies none of those by itself.

OPS.16:1 - Problem frame

Operating Methods need revision when demand, services, constraints, technologies, participants, or protection conditions change. Local evidence can make that revision practical, but only if the team can tell what was intended, what was actually done, which Method was enacted, what changed, and which decision the observations support.

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.

The Operations question is narrower and more actionable: given an admitted Method or a status-preserved candidate account, what bounded operating decision is justified by the actual trial Work and qualified consequences 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, the difficulty is sharper. The candidate account may be strong enough to guide a distinguishing observation, but it is still an episteme about a possible reusable way. Calling the candidate enacted, adopted, or branched would decide its identity before the required A.3.1 work.

OPS.16:3 - Forces

OPS.16:4 - Solution

Build one status-preserving evidence chain from the operating question to the supported decision. In the pre-admission branch, a current account revision, retention, comparison or stop can finish under A.3.1.MR without another question, trial plan or performed trial. If a trial is selected, state the change hypothesis and alternatives, establish its actual conditions, keep planned and actual Work distinct, type observations and qualify their reach through the current owners. Return only the decision supported by the evidence and actual authority.

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. Then select the branch from evidence already available; the desired outcome does not select it.

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. Independently apply A.3.1 to admit a Method and A.3.2 to classify a separate description episteme. If those results are unavailable, retain the candidate branch.

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

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. Name the observation that could defeat the hypothesis and the decision it would change.

Use OPS.11.1 when the question requires reconstructing the current and proposed networks of transformations, resources and enabling conditions. 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 when serious candidates must be recovered or compared. Consume an OPS.19 result only when its cross-scale decision changes feasible trial Work or a protected trial condition. A trial need not compare every named alternative; it must preserve the alternatives that can still change the receiving decision.

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.

Obtain ordinary access, support and work allocations from their existing providers under the current arrangements. 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. Unchanged job titles do not make a proposed arrangement effective. 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 - Write a prospective trial WorkPlan

Plan the smallest trial whose observations can change the receiving decision. 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 the plan prospective and identify the interval during which its premises must remain current.

A compact plan can use these positions:

This is a writing aid rather than a new trial object. A.15.2 governs the WorkPlan. The plan is neither performed Work nor evidence that the candidate whole or changed Method was enacted.

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

After the trial interval, identify only Work that actually occurred. For each Work occurrence, recover the actual performer, temporal extent, containing System, enacted admitted Methods, and departures under A.15.1. 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

Separate every observation that can change the decision. Do not combine them into a single improvement score.

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

Ask only the specialist questions that the receiving decision needs. Current ME.11 supplies representative and discriminating trial evidence; ME.12 examines coherence; ME.13 examines situational fit or transfer; ME.14 examines practical worth; ME.15 maintains Method lineage and variant claims; and ME.16 separates target, introduction strategy, actual Work, observations, and bounded revision. Reuse their current results instead of recreating them inside Operations.

Use A.10 for evidence reliance, C.16 for measurement validity, and C.27.TA for the temporal window. 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 favorable occurrence automatically establishes none of coherence, transfer, practical worth, sustained effectiveness, or causality.

Increase assurance effort only where it can change the decision. 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 the current, revised, branched, stopped, and still-uncertain alternatives that remain feasible. 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 result cannot make an infeasible alternative 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.

For either branch, return the exact operating use, supported evidence, unsupported stronger use, 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.

What changes in practice: the team stops saying “we tried the new process and it worked.” It preserves Method or candidate-account status and source limits, finishes a supported current account, and separates a selected trial’s plan, actual Work and observations. Service and authority limits remain binding in every branch.

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 two-package trial begins as a WorkPlan. It 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.

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.

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 a reusable readiness way for transferring a patient case between clinical areas. The provisionally distinguished way is carried by candidate account ED-Handover-Readiness-CA1. The account retains two serious explanations: missing readiness information may cause avoidable repeat work, while changing clinical priority or diagnostic uncertainty may explain the same delay. It names the missing identity evidence and the observation that could distinguish those accounts. No U.Method or U.MethodDescription has been admitted.

A bounded WorkPlan proposes observing two handover intervals under current staffing and safety conditions. It names the intended information check, qualified participants, privacy protection, stop, and the later identity decision. When actual clinical and coordination Work occurs, it is admitted separately. Only independently admitted triage, clinical-assessment, and handover Methods may be recorded as enacted. The candidate whole and its account are not enacted.

Suppose one repeated clarification follows missing readiness information while another follows a new clinical finding despite complete information. The first observation supports part of ED-Handover-Readiness-CA1; the second preserves the rival and shows that one fixed readiness rule cannot explain every delay. Patient, clinical case, WorkPlan, actual Work, information observations, safety conditions, and clinical decisions remain separate.

The current return is a revised candidate account with the rival and missing identity evidence retained. That revision is complete; it is not adopt or branch. If the later receiving decision needs Method identification, further discrimination may be needed before the separate A.3.1 test; select the inquiry only when its obtainable contribution warrants its whole burden. An unavailable observation leaves the identity claim unsupported without erasing the current account. Medical 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 actual 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

OPS.16:7 - Conformance Checklist

• The operating System, use, difficulty, receiving decision, decision maker, horizon, and protected conditions are explicit.
• The starting branch names either an exact admitted U.Method and relied-on version or U.MethodDescription, or an exact A.3.1.MR candidate account with source support, real rivals, 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 and decision-changing observation preserve every Method or candidate status; a supported current candidate account does not create that trial.
• The 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.
• A selected trial’s WorkPlan names intended tasks, proposed performers, expected admitted constituent Methods, supports, observations, burdens, protections, stops, hand-back and later use without claiming actual Work.
• Every actual Work occurrence has actual performers, enacted admitted Methods, extent, containing System, departures, and direct results. 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.
• The result claims no organization-wide adoption, cultural selection or retention, causal superiority, new capability, or authority outside its boundary.

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

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 that can change an operating start, branch, or stop. 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

An operating improvement is a decision about a way of working under actual service conditions. Its evidence becomes usable only when the object under change, performed Work, direct observations, and receiving authority remain identifiable.

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 practice question is how to turn evidence about one way of operating into a bounded Method-change decision. The selected line combines current Method Engineering’s trial-to-revision route with FPF identity, Work, evidence, time, measurement, causality, and choice governors, then adds Operations service consequences and authority. It deliberately requires more identity and evidence bookkeeping than a generic improvement loop, but limits that effort to distinctions that can change a start, branch, stop, or stronger claim.

OPS.16:12 - Relations

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. None changes a Method’s or candidate’s status by adjacency.

OPS.10–OPS.13 supply the needed resource, schedule, human-condition and service contributions; OPS.19 supplies a cross-scale decision when it changes feasible trial Work or protected conditions. 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 ME.11-ME.16 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; it creates no second generic trial object or replacement specialist test.

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. One local decision supplies no cultural continuation claim.

OPS.16:End

OPS.17 - Compare and Refresh Operations Methods

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, or how a service responds to failures.

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, where it fails and what result an alternative must improve. 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. Comparing their operating moves makes that question answerable before the team commits to a school or tool.

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

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, what people 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. Select only the row needed by the operating question.

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.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 that could change the decision: 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 only where it can change the choice. If every proposed option depends on the same unresolved mandatory staffing condition, obtain that missing result before refining their service scores.

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. Locate the failed claim before replacing the whole repertoire. A change in customer acceptance can affect a service forecast while leaving readiness checks useful.

Use ME.15 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 ME.7 for the status of a proposed whole and ME.14 for its practical worth. Maintaining an account or choosing a repertoire supplies no additional Method admission, compatibility, empirical fit or transfer evidence, or permission for operating use.

When an unresolved operating effect could change the decision, 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. ME.11 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:

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.

The resulting instruction for the next window is concrete: 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.