OPS.9 - Diagnose and Treat the Current Operating Constraint

OPS.9:0 - Use This When

Use this Method when an operation is not producing its accepted result as required and someone proposes to remove a bottleneck, increase capacity, automate a step or accelerate a team. The question is which relation currently limits completion, and what treatment the evidence supports.

The first useful result is a bounded constraint account: the lost result and observation window, relevant observations, a candidate explanation and a serious rival, discriminating support or an exact probe request, and a treatment or hold decision. It can conclude that the proposed resource addition is unsupported while specifying a useful readiness or measurement action.

Use OPS.8 when a queue policy can be repaired without settling a wider constraint claim. Use OPS.10 when the immediate question is a load/capacity/service comparison with an already adequate causal basis. A safety, clinical, engineering or financial diagnosis remains with the qualified practice that supplies it.

OPS.9:1 - Problem frame

A queue can be long because service capacity is scarce, inputs arrive in bursts, prerequisites are incomplete, acceptance is delayed, or earlier defects return as rework. Several of these mechanisms can obtain together. A resource may be idle for much of a week and still constrain a short critical window.

Here a current constraint is a supported limiting relation for one operating result under a stated arrangement and horizon. It can concern usable capacity, readiness, sequence, quality, access, a decision or another condition. It is not a permanent label attached to the busiest person or machine.

OPS.9:2 - Problem

Local speed and utilization are easy to observe. The causal relation to accepted operating results is harder. An improvement can halve touch time while leaving completion unchanged because work still waits for acceptance, a complementary input or another resource.

The opposite error demands a complete causal model before making any useful decision. A small feasibility bound, a discriminating observation or a reversible probe can sometimes rule out a proposed treatment at much lower effort.

OPS.9:3 - Forces

Force	Practical tension
urgent treatment and adequate diagnosis	Delay can be costly, but the wrong treatment consumes resources and can move congestion elsewhere.
one focal constraint and distributed delay	Focusing effort helps, while several short waits or alternating regimes can defeat one-resource explanations.
local measures and accepted results	Touch time, busy time and queue length can change without changing what the operation delivers.
useful probes and protected conditions	A probe can discriminate explanations only while preserving the relevant professional, acceptance and comparison conditions.
learning and migration	A useful treatment changes the arrangement; its success can make the former constraint cease to be current.

OPS.9:4 - Solution

OPS.9:4.1 - Fix the result and the shortfall

Name the operating result, its accepted unit, demand or commitment being compared, relevant subjects, horizon and acceptance criteria. Reuse current OPS.1–OPS.4 inputs where they fit. Distinguish accepted demand, service attempts and accepted results; a failed test or reopened case can consume capacity without adding a result.

State the shortfall in terms that can change a decision: fewer accepted results, unacceptable time to result, missed qualified service conditions, or another explicit operating consequence. Preserve the result definition and case mix in later comparisons. A changed definition reopens the account rather than silently improving the metric.

OPS.9:4.2 - Reconstruct where completion is lost

Follow representative matters through the relevant services and joins. Recover entry, eligibility, start, completion, return and acceptance events. Distinguish processing, setup, starvation, blocking, unavailability and rework only where they can explain the shortfall.

Use the event sequence and the resource calendar together. A snapshot identifies a population at one time; it does not explain a week of waiting. A utilization average can hide a critical peak. Record uncertainty and missing events before calculating a causal-looking rate.

If the result is delayed by many small waits, inspect cadence, handoff and decision timing across the path rather than forcing one scarce-resource answer.

OPS.9:4.3 - State a mechanism and a rival

Express the candidate explanation as a relation: “Under this demand and access pattern, the final test cannot process the required eligible load before the horizon,” or “Late prerequisite delivery leaves the booked rig without eligible packages.”

Name an alternative that could produce the same observation and change treatment. Examples are insufficient usable rig time versus incomplete kits; scarce acceptance effort versus evidence repeatedly missing at acceptance; or slow processing versus arrivals concentrated near the deadline.

Give each explanation an expected observation and a possible defeater. If both predict the same data, the present observation cannot choose between them. Do not rename a queue “the constraint” to close that gap.

OPS.9:4.4 - Obtain the least burdensome discriminating basis

Select the basis appropriate to the claim and decision:

A resource/precedence bound can establish infeasibility under explicit demand, capability, calendar and acceptance assumptions. Show a feasible schedule as well when claiming that a proposed treatment makes the result achievable.
Event-history replay can reveal starvation, blocking, rework and timing relations. Its observational explanation remains limited by event quality and unobserved conditions.
A bounded field probe changes one consequential mechanism under the applicable professional Method and permission. State the comparison cases or windows, preserved conditions, interference, expected observations and stopping rule.
A specialist causal or scheduling analysis is warranted when uncertainty, confounding or coupled behavior can reverse a consequential decision and the simpler basis cannot resolve it.

For a probe, keep the same accepted-result criteria and record demand, mix, resource availability and consequential conditions. Shared queues or common providers can affect nominal comparison cases too. Use an appropriate time-blocked, matched or other justified comparison; a convenient before/after label does not remove interference or confounding.

Current FPF C.16 governs the measurement chain and C.28 governs what causal use the basis supports. The operation still has to supply the actual measurement or probe, the professional premises and its observations.

OPS.9:4.5 - Compare treatments from the current arrangement

Compare the incumbent with a finite change that acts on the supported mechanism. Candidate treatments include protecting usable constraint time, changing release or dispatch, completing prerequisites earlier, reducing avoidable setup or rework, obtaining capacity, or changing a domain Method.

Account for implementation effort, transition loss, displaced work, downstream congestion, affected commitments and reversibility. Use C.11.CRC for the finite comparison and C.11 for the choice when several admissible alternatives remain. Resource acquisition is not preferred merely because it is easy to count.

A treatment is supported only to the scope of the evidence. A deterministic scenario can show feasibility; it does not establish actual field effectiveness. A probe can support a bounded effect without showing that the same treatment remains useful under another demand regime.

OPS.9:4.6 - Return the decision and remeasure

Return the result definition and window, observations, supported explanation or unresolved rival, basis and limits, selected treatment or probe/hold decision, authority, affected decisions and the next observation that can change the conclusion.

After a treatment, inspect the accepted result and the actual load, waiting, quality and resource consequences. Reopen when demand, mix, eligibility, access, acceptance, recovery or a coupled structure changes. Do not keep “improving the bottleneck” after the relation that justified the label has disappeared.

OPS.9:5 - Archetypal Grounding

OPS.9:5.1 - PumpWorks: readiness or rig capacity?

PumpWorks coordinates weekly evidenced releases. In the constructed history, five eight-hour rig-access windows contain 20 test hours, 4 setup hours, 4 unavailable hours and 12 hours with no eligible job. Twelve matters appear on local boards at the final snapshot, but only four ready test packages require eight rig-hours.

A proposal to buy more rig time cites the twelve cards. The practitioner identifies the claimed result—accepted evidence-complete releases—and distinguishes it from test attempts and ready packages. The history supports a late-readiness explanation, but it does not rule out insufficient rig time in a later peak window.

The initial account is:

Element	Bounded result
observed loss	twelve open hours without an eligible job; accepted-release shortfall still requires its own event and acceptance account
candidate explanation	prerequisite delivery misses usable rig windows
serious rival	eligible demand exceeds usable rig time in the relevant deadline windows
discriminating next observation	timestamp package eligibility, usable rig slots, starts, results, returns and final acceptance for the same release population
bounded probe	where engineering and test permissions allow, prepare the next-test inputs earlier for a comparable class; preserve test/acceptance criteria and record mix, access and shared-resource effects
present decision	do not infer a rig-capacity treatment from card count; operate the supported ready-queue policy and obtain the missing discriminatory basis

If earlier readiness reduces starvation but accepted releases remain unchanged, that result does not establish completion improvement. Inspect acceptance waiting, rework and the next consequential coupling. If usable access is then reduced by ProviderChange-P8, re-evaluate the capacity explanation under the new window.

This is a completed diagnostic/probe decision. It is not a claim that the constructed probe has been performed or that late readiness has already been established as the sole cause.

OPS.9:5.2 - A narrow capacity treatment with a feasible witness

A different constructed service must finish five ready jobs within twelve hours. All upstream inputs are complete. Each job requires two hours of final verification and then ten minutes of certification; the certificate service has reserved slots after each possible verification completion. Acceptance requires both results, with no failures or rework in this stated scenario.

The verifier is available for eight hours. Verification completions occur at hours 2, 4, 6 and 8, so no more than four jobs can be accepted. Extra upstream processing capacity cannot change that bound: the five inputs are already ready.

The resource owner can supply two additional verifier-hours within the same twelve-hour horizon. With that change, the fifth verification completes at hour 10 and certification at hour 10 plus ten minutes. The comparison therefore returns a feasible five-job treatment candidate under the stated conditions. Its selection still uses the supplied resource cost, permission and protected consequences.

If certification availability later falls to two reserved slots, the old verifier treatment no longer supports five accepted jobs. The same result definition now exposes another limiting relation. Adding further verifier time cannot repair that missing certification capacity.

OPS.9:5.3 - Faster automation without more accepted cases

An operation automates a repeatable step and halves its touch time, but the same accepted-case rate remains. The practitioner keeps the accepted-case criteria, mix and observation window fixed and inspects waiting and returns at acceptance.

If cases repeatedly lack the evidence the acceptor needs, “hire more acceptors” and “complete evidence before presenting the case” are distinct treatments. The next result is the smallest justified comparison that separates those explanations. A model score or automation benchmark does not settle it.

OPS.9:6 - Bias-Annotation

Bias	How it misdirects treatment	Countermeasure
busy-resource attribution	High utilization becomes the causal explanation.	Relate usable capacity and timing to the accepted-result shortfall.
queue-length attribution	Visible waiting is treated as sufficient proof of the constraint.	Test eligibility, arrivals, returns and a serious rival.
preferred-solution bias	Automation, hiring or acquisition is selected before diagnosis.	State a defeater and compare a treatment that acts on another plausible mechanism.
before/after confidence	Coincident changes are attributed to the intervention.	Preserve comparison conditions and account for interference and confounding.
permanent-bottleneck identity	Attention remains on a resource after conditions change.	Remeasure the current limiting relation and accepted result.

OPS.9:7 - Conformance Checklist

Is the accepted result and shortfall fixed for the relevant population and horizon?
Do observations distinguish the mechanisms that could change treatment?
Is there a serious rival with a discriminatory observation or defeater?
Does the selected bound, replay, probe or specialist analysis support the claim actually made?
Does the treatment act on that mechanism and include consequential interactions and transition costs?
Can participants act on the treatment, hold or exact probe request and recognize when it must reopen?

These questions recognize an inspectable diagnosis and decision. Assurance depends on the actual observation quality, comparison validity, professional premises and authority; a complete account is not itself causal evidence.

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

Anti-pattern	Failure	Repair
Every operation has one permanently named bottleneck.	Distributed delay and changing regimes are excluded before observation.	State the result-relative limiting relation and allow unresolved or multiple mechanisms.
A fast local step proves whole-operation improvement.	Acceptance, joins and rework may dominate the result.	Preserve the accepted unit and inspect the whole relevant path.
A capacity ratio is a feasible schedule.	Precedence, access and simultaneous-resource conditions can defeat it.	Supply the timed witness or retain an infeasibility bound only.
A generic causal checklist replaces the field probe.	No actual admissible change or observation is specified.	Name the professional Method, changed action, comparison and stop.
A successful treatment remains the answer forever.	The arrangement and limiting relation have changed.	Reopen the account after the material change.

OPS.9:9 - Consequences

Effort can be directed to a mechanism that affects accepted results. An exact “not yet justified” treatment decision can prevent waste while leaving a cheap useful policy or probe available.

The cost is some additional measurement and comparison discipline. The appropriate depth depends on the consequence of error: a reversible readiness trial and a major capacity acquisition need not carry the same evidence burden.

OPS.9:10 - Rationale

A constraint claim connects an arrangement to an operating result. Its meaning therefore depends on demand, acceptance, time and complementary resources. A resource label cannot retain that meaning when those conditions change.

Diagnosis and treatment belong together, but they are different conclusions. Keeping the rival and evidence limit visible permits action at the smallest justified scope without turning either caution or urgency into a universal rule.

OPS.9:11 - SoTA-Echoing

Practice question and selected line	Serious alternative, trade-off and pattern change	Source roles, limits and reopen condition
What should be treated when local speed does not improve accepted output? Adapt result-relative diagnosis followed by mechanism-specific treatment.	Constraint-focused improvement is useful, but a forced single-resource answer can miss many waits or incomplete inputs. Sections 4.1–4.3 and 5.1/5.3 preserve the accepted result and require a serious rival. The extra event discrimination is worthwhile when it can reverse treatment.	Tendon, The Book of TameFlow (2022), constraint and complete-kit reasoning, is a mechanism candidate. Reinertsen, The Principles of Product Development Flow (2009), E8’s accumulated small waits, is the action-changing rival. Neither proves the current case’s cause. Reopen for a different waiting mechanism or demand regime.
How much evidence is enough before acting? Adapt the least burdensome bound, replay or admissible probe that can distinguish the live alternatives.	Pure utilization ranking is cheaper but cannot support the causal move; a complete optimizer or experiment is unnecessarily costly for some bounded decisions. Sections 4.4–4.6 and 5.2 separate infeasibility, feasible scenario and actual effect.	Current FPF C.16 and C.28 supply measurement and causal-use discipline; C.11.CRC supplies finite comparison. The professional operational data, probe and authority remain case inputs. Reopen when confounding, interference or consequence makes the selected basis insufficient.
Should the former constraint keep receiving improvement effort? Adopt remeasurement of the accepted result and current arrangement after change.	A fixed improvement programme can keep optimizing a relation that no longer limits completion. Section 4.6 and the changed certification case make migration observable at modest extra comparison effort.	The constraint-refocusing line in Tendon and the changing-information reasoning in Reinertsen are compatible mechanism candidates, not guarantees of improvement. Reopen if the result, acceptance conditions or connected resources change.

OPS.9:12 - Relations

OPS.1–OPS.4 supply matching operating focus, subject identities and current observations. OPS.8 supplies relevant queue, readiness and buffer policy; OPS.10 supplies usable-capacity and service comparisons; OPS.11 exposes couplings that can sustain or move a limiting relation.

OPS.5–OPS.7 consume supported operating-policy consequences under their own admission, continuation, priority and commitment authority. A domain Method change returns to its owner. OPS.16 is available for the separate local operating-Method-improvement question but is not a prerequisite for diagnosing the current constraint.

Current FPF C.16, C.27.TA/C.27, C.28, C.11.CRC and C.11 govern measurement, temporal and causal claims, finite contribution and choice. They do not supply a clinical, engineering, safety, labor or financial diagnosis merely by being cited.