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 under the same operating use, interval, result definition and protected conditions. Carry uncertainty as an interval, scenario or missing claim. When different operating uses matter, compare the options within each use and identify which options remain non-dominated there. Keep an unresolved comparison visible if the missing information could change which variant is retained.
Identify the Agent authorized to make the local operating decision and the predicate, scope, and basis of that authority. Clinical, safety, release, financial, employment, security, and other specialist decisions remain with their owners. Expertise, sponsorship, assignment, access, and a tool recommendation do not transfer authority.
A favorable trial result applies within the conditions that made the trial feasible. Stop or narrow the trial when permission, qualified support, fallback, recovery, evidence validity, or another protected condition is absent.
OPS.16:4.9 - Return a status-preserving operating decision
Use the branch selected in section 4.1.
| 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.