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

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:15:10 UTC

Part I — Bound the Operation and Select Coordination Views

OPS.23 - Connect Operational Reasoning — The Operational Mantra

Type: Method pattern Status: Stable Normativity: Normative within the stated operating use.

OPS.23:1 - Problem frame

Use this when individually plausible answers about local work, delivery, capacity, service, money or people’s working conditions do not yet explain what the continuing operation can actually deliver. An assigned task can finish while its recipient still waits. A team can speed up processing while its service promise becomes infeasible. The needed result is a connected operating judgement: what can proceed, what must change, or which missing answer prevents a responsible decision.

The first useful move is to name the result the recipient must be able to use and follow one proposed local action to that result. Where does its contribution become usable, and which other condition must hold? Reuse current answers; pursue a missing connection when it could change the operating choice or the grounds for relying on it. Ordinary prose, a sketch or a current shared account can suffice.

Use a direct OPS Method when it already supplies the whole answer. An isolated capacity calculation, a known permission rule or a settled service decision does not require reconstruction of the whole operation. Use OPS.19 for an identified conflict among simultaneous work; this pattern also applies before such a conflict has been found. It supplies reasoning, not specialist judgements, missing resources or authority.

OPS.23:2 - Problem

Operating decisions are often made from different local accounts. A completion count, a queue view, a resource calendar, a service promise and a cash forecast can each be correct while their combination is impossible or useless. Conversely, requiring a complete enterprise model before any decision delays an adequate local result. The practitioner needs to assemble just the mutually relevant answers and preserve their conditions through a change.

OPS.23:3 - Forces

ForceTension
Local progress and receiving useA finished task can supply a needed intermediate result or merely increase unfinished inventory.
Speed and continuing provisionFaster processing can consume recovery capacity or leave the decisive wait untouched.
Shared judgement and authorityParticipants can expose an incompatibility without being entitled to change each other’s commitments.
Coherence and unnecessary reconstructionThe whole needs compatible answers, but an unchanged sufficient answer should not be rebuilt.
Immediate protection and learning about causesA supported response can protect service while the reason for recurrence remains unresolved.

OPS.23:4 - Solution

Use this mantra to connect the work of a person, team or other contributor to what the operation can deliver. Follow a local action through to the result its recipient can use. The short form is:

Accepted result → route and readiness → limiting conditions → release and feasible order → service, money and human conditions → observed result and changed conditions.

These are connected questions to keep in attention. Their answers constrain one another. Start wherever a missing answer could change the present decision or its grounds, and use adequate answers already available. OPS.Reference:8–OPS.Reference:11 explains the connections with other operating methods.

Relate local work to a result the recipient can use. Identify the operating system, required result, acceptance boundary and commitments through OPS.1 and OPS.3. Follow the work and its required inputs through the relevant workstations or contributors. Locate the local contribution in that route: producing an intermediate item, making later work ready, handling a return or preserving service can affect the whole differently. A completed local task is useful on this account when the receiving work can use its contribution. OPS.11.1 develops the connection between local routes, shared resources and order-level completion. When the route or work unit is itself missing, its :4.2a constructs operating alternatives from the required result and available professional methods; an unavailable method returns to its subject discipline. The judgement can therefore begin before an adequate operating arrangement exists. When the required system or its intended use remains unclear, FPF A.1.STM supplies the connected system-thinking questions; an operating calculation cannot settle that earlier choice by itself.

Find which condition limits the result under the present demand. Work can wait because an input or permission is missing, because usable capacity is insufficient, or because the selected order delays a needed completion. OPS.8 and OPS.9 distinguish these causes; OPS.10 qualifies capacity over the relevant interval. Improving an already non-limiting station can increase intermediate inventory without increasing accepted output. Conversely, protecting the limiting station may require work elsewhere. The target matters: shortening the time to a first accepted result and increasing sustained output can require different changes, as OPS.9:5.4 explains. To identify the constraint, relate the queue or occupied resource to the result being limited.

Choose starts and order from those conditions. Use OPS.2 to select the relevant management view, OPS.8 for release and queue rules, and OPS.10.2 when a deadline needs a feasible schedule. Count waiting from the recipient’s relevant starting event; moving an incomplete item off a board does not remove that delay. Include returning work, setup and recovery where they consume the same capacity. A calculation of total required hours supplies a necessary bound, while precedence and simultaneous resource requirements can still prevent a schedule. Priorities need the decision’s supported consequences and available authority. OPS.14 compares financial consequences on a common basis; its indivisible-job case shows why a value-per-hour ranking need not select the best feasible set. An unknown monetary estimate does not establish that work has no value.

Require the combined promise to be feasible. The whole-combination conditions in OPS.Reference:10 apply to continuing service and the proposed change together. OPS.12 preserves the affected people’s required conditions, OPS.13 relates service commitments to available provision, and OPS.14 checks payments when they fall due. OPS.19 reconciles conflicts that otherwise valid local decisions leave unresolved. PumpWorks in OPS.19:5.1 shows the consequence: two test completions and a possible repeat exhaust the same six rig-hours, so a separately feasible Method trial cannot also use that interval. Qualified relief, incident coverage and funding remain separate conditions even if more rig access can be obtained.

Return observations to the answers they change. OPS.15 keeps the observed result and its population clear; OPS.18 distinguishes containment, correction and evidence about recurrence. If a constraint moves, a return consumes a reserve or an input becomes unavailable, reconsider the starts, commitments and resource choices that relied on the earlier condition. Keep unrelated valid results. A change to the way of working uses OPS.16 with its own trial conditions, including coexistence with continuing service. If the work extends to development for further problems, use FPF C.40.OD to establish its purpose and means. The operating account supplies the conditions that undertaking must meet.

The same reasoning applies at a workplace and across an organization. Within the authority already given, a contributor can revise a local choice from the shared operating facts. A change to a commitment, resource allocation or protected condition outside that authority goes to the party entitled to decide it.

OPS.23:4.1 - Assemble the decision and select its next useful question

Keep the receiving result, proposed action and the conditions on which their connection depends in the same account. For each consequential claim, distinguish an observed fact, a justified forecast, an authorized commitment and an unresolved condition. A promised specialist is not the same as an available specialist; a planned acceptance is not an accepted result. Use OPS.4 and OPS.15 when recovering these facts is the difficulty.

Follow a suspected mismatch in both directions. If a test may finish late, identify the input, resource window or ordering constraint that could explain the delay and the accepted promise that depends on the test. If a promise changes, trace it back to the work and provision it requires. Use the relevant method or its available result to establish whether the promise can stand, what supports that conclusion and whether a change needs a decision from the party responsible.

A current sufficient answer closes the question. Otherwise choose the next inquiry, coordination or permitted operating action by what its result could change about the choice or its grounds. If a fact or decision is still missing, identify the work it limits. Independent work can proceed when its conditions and authority are established.

A plausible mismatch is enough to select this Method. Reliance on a schedule, service promise, causal diagnosis or protected human condition needs the corresponding qualified result.

OPS.23:5 - Archetypal Grounding

OPS.23:5.1 - Four ready packages do not imply four accepted results

Use the constructed PumpWorks conditions in OPS.19:5.1. Four packages are ready; each requires two rig-hours; six hours are available; one possible two-hour repeat must remain protected. The resource account permits two selected packages and that repeat: four hours of initial tests plus two reserved hours. Starting all four would require eight hours before any repeat. Readiness therefore supplies one premise of release, not a sufficient start rule.

Connecting the answers changes more than the count. An incident consumes the change interval and interruption reserve; qualified specialist relief is unavailable. An extension would defeat incident coverage and recovery even if more rig access could be arranged. The qualified financial account supports later completion of the third package, but supplies no disposition for the fourth. The resulting judgement retains two starts, protected repeat capacity and incident response, returns the fourth package’s later disposition as an unanswered question, and keeps the Method trial closed. OPS.19 explains how the people responsible resolve this conflict within the rig, service, financial and staffing constraints.

Suppose additional rig hours are offered while specialist relief is still unavailable. Reopen the rig premise and its affected schedule; retain the independent support restriction. The offer alone does not permit the extension or trial. Conversely, if both support and service conditions later change, recover their actual answers before reusing the earlier refusal.

OPS.23:5.2 - One workplace can need the same connection

A technician has a finished repair and wants to begin the next. Under the stated working conditions, the recipient can use the repair only after an acceptance test, and the test fixture will be free in the afternoon. Preparing the required test input now can advance the accepted result more than beginning another repair. If that preparation is already complete, a permissible independent task can proceed instead. Relate the local choice to the missing contribution and current permissions.

If the recipient cancels the afternoon acceptance window, the technically finished repair remains finished. The service promise and useful next action change. Seek the revised receiving decision instead of reporting the local completion as delivered service or silently making a new promise.

OPS.23:6 - Bias-Annotation

Visible tasks and well-recorded resources can crowd out recipient use, support work and the conditions of less powerful participants. Use available evidence about affected contributions and burdens. Where a participant’s conditions remain unclear, ask the participant or a source able to establish them. Neither a monetary estimate nor the easiest available dashboard is a universal measure of the result.

OPS.23:7 - Conformance Checklist

  • The local action is connected to a result its recipient can use.
  • Ready input, usable capacity, feasible order, permitted action and service agreement remain distinguishable.
  • Shared resources, returning work and protected conditions are included where they change this decision.
  • The account states a supported continuation, a specific question or a justified stop; an unknown is not silently made favorable.
  • A changed premise reopens its dependent answers, while independently sufficient results remain usable.
  • Recognition of a problem is not presented as assurance of a schedule, causal account or service result.

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

Anti-patternRepair
Maximize activity at each workplaceFollow the contribution to the accepted result and the condition currently limiting it.
Replace whole feasibility with a sum of hoursRecover ordering, simultaneous resource needs, support and receiving conditions.
Repeat every analysis after any changeIdentify which premise changed and follow the answers that depend on it.
Recite the mantra as a workflowChoose the current question from available answers and what the answer could change about the decision or its grounds.
Let the most complete account confer authorityReturn commitment changes to those entitled to make them.

OPS.23:9 - Consequences

Participants can explain why a local action helps, why an apparently feasible start remains unavailable and what a changed condition reopens. They can retain adequate partial answers. The cost is recovering consequential relations and obtaining qualified missing answers; the Method earns that cost only when the direct local treatment leaves the operating judgement incomplete.

OPS.23:10 - Architectural Rationale

Assemble and revise the operating judgement from the answers the current decision needs. Use applicable specialist results and obtain a missing one when it matters to the judgement. OPS.19 can resolve an identified conflict. At any scale, readiness, authority to start, local completion and use by the recipient can differ. The short mantra recalls these connections. A claim that learners do better with this form than with another would need a comparison of their learning.

OPS.23:11 - SoTA-Echoing

The serious smaller alternative is direct use of a competent current workflow and its operating rules. The Kanban Guide, May 2025, sections “Why Use Kanban?”, “Defining and Visualizing the Workflow” and “Improving the Workflow”, connects value, workflow definition, active management and improvement. It permits multiple workflow definitions and additions for the local setting. Reuse such an account when it already makes the relevant promise, provision and response clear.

Connect contributions when the current workflow leaves them separate. At PumpWorks, the rig schedule leaves open specialist relief, incident coverage, recovery and the disposition of the remaining packages. Establish what is known about each and reconcile their consequences. OPS.8–OPS.14 and OPS.19 give the conditions for using their flow, scheduling, service and financial results. The case shows what combining the answers adds here. Comparing the two approaches across operations would require evidence from those uses.

Keep the simpler arrangement if it supplies the same judgement with less reconstruction. Reopen this choice when an operating method supplies the missing connection directly, a changed receiving condition invalidates a join, or use shows that maintaining the account costs more than the decisions it improves.

OPS.23:12 - Relations

OPS.1–OPS.15 and their nested Methods supply the relevant operating answers. OPS.19 reconciles actual cross-scale conflicts; OPS.16–OPS.18 address Method change and quality; OPS.21–OPS.22 distinguish aims from performance interpretation. STR.18 connects a changed operating possibility to direction and commitments when that strategic question is live. FPF A.1.STM supplies system-project reasoning and C.40.OD the distinct continuation of development. The Architectural Reference explains the language and its field boundaries; this pattern supplies the operational reasoning Method.

OPS.23:End

OPS.1 - Identify the Operating System, Commitments, and Flow Units

Status: Stable

OPS.1:0 - Use This When

Use this pattern when you want to improve a process, clear a backlog, raise utilization, accelerate flow, or redesign a board but cannot yet name the operation whose result must continue. Typical warning signs are an organization name used as the operating boundary, one ticket called the customer need, a queue column treated as the Work, or a service promise discussed without its parties, conditions, or horizon.

The first useful result is one bounded operating focus. An existing account or a short statement can carry it:

For this decision and horizon, OperatingSystem-X must continue supplying Result-or-Service-Y; current demand and commitments are ...; the decision-bearing subjects and counted units are ... under these identity rules; any boundary, authority, evidence or control question that still affects this decision is ....

That statement is useful before a workflow, target, priority, or policy is chosen. Use this focus in OPS.2 if coordination needs a decision, or in OPS.3 if subject identities or relations need clarification.

Recognition is cheap: enter when a practical decision cannot name its operating System, continuing result, commitments, or tracked unit. Assurance is claim-specific: System identity, commitment, Work, subject identity, authority, evidence, safety, value, and effectiveness use their own governing patterns and specialist Methods before reliance.

Use an established operating boundary when it already answers the decision. When an outside result determines the answer, use the relevant specialist contribution. For example, the question may concern a product or asset change, organization change, a person’s capability, finance, law or safety. Return to the operating focus if the contribution changes its boundary, use or grounds.

OPS.1:0.1 - Working Distinctions

Name used hereMeaning
operating SystemOne actual System whose continuing operation and results are current for the decision. It is not inferred from an organization name, process diagram, product label, software tool, or reporting boundary.
continuing result or serviceThe result, service, or preserved condition the operation must keep supplying to a named receiver under stated conditions. Continuation does not prove value, quality, acceptance, or fulfilment.
demandA request, need, condition, candidate Work claim, arrival, or other input entering the operating decision. Demand is not automatically admitted Work or a commitment.
commitmentA promise or obligation with parties, promised result or service, conditions, horizon, authority, and current status. A due date or priority label alone is not a commitment.
operating subjectThe exact System, item, case subject, material, service relation, account, or other entity whose state or relation can change the operating decision.
flow or case unitA decision-specific counted or tracked unit with an identity rule and receiving use. Treat Work items, cases, physical items, batches, transactions, commitments, and results as different units unless their identity rules and evidence establish that the labels denote the same counted or tracked unit for this use.
operating boundaryThe included subjects, Work, resources, relations, environments, and time horizon needed for this decision, with consequential exclusions and any needed specialist contribution.
control-relevant operating concernA question in which observation, decision, actuation, supervision, feedback or unlike rates can change coordination. It calls for the relevant control account, with a formal structure or view only when that claim is needed.
operating-focus resultThe bounded operating System, continuing result, demand, commitments, subjects and units, with the boundary and grounds needed for the current decision. Include a missing condition or further use when one remains.

OPS.1:1 - Problem Frame

Operations work begins in the middle. Demand has arrived, commitments already exist, cases are open, resources are shared, records disagree, and service must continue while changes are considered. Familiar representations make that situation look simpler than it is. A board foregrounds Work items, an organization chart foregrounds positions, a process map foregrounds recurring order, and a product model foregrounds the engineered object.

Answering the operating question may require several of these representations. A useful starting boundary therefore comes from the continuing result and present decision, then identifies the actual operating System, commitments, subjects, and units needed to decide.

OPS.1:2 - Problem

Without an operating focus, later optimization can improve the representation while degrading the operation. A team can shorten one board column while customer cases age, increase resource utilization while service commitments fail, count ticket closures while the field condition persists, or optimize product-control performance while release and incident-response Work remain blocked.

The failure propagates. Queue, constraint, capacity, quality, service, finance, and Method-improvement decisions inherit the wrong boundary and unit.

OPS.1:3 - Forces

ForceTension
UrgencyA visible backlog invites immediate action, while an incorrect operating boundary makes the action locally efficient and globally harmful.
Familiar namesCompany, team, product, service, platform, and process names help orientation, while none alone identifies the operating System.
Several commitmentsCustomer, safety, provider, release, support, and financial commitments can coexist without one being the universal priority.
CountabilityBoards and logs offer convenient units, while convenience does not establish identity or receiving use.
Continuing serviceThe operation must act with incomplete evidence, while uncertainty does not license invented state or authority.
Bounded entryThe first result must be affordable, while later decisions need enough identity and boundary precision to avoid rework.

OPS.1:4 - Solution

Start with the result that must continue. Identify the operating System, relevant commitments, subjects and units at the boundary the current decision needs.

OPS.1:4.1 - Pattern-Use Unfolding

  1. Name the first user and decision. State who needs the focus, what decision it enables, the relevant horizon, and the first useful result or the condition that prevents it.
  2. Resolve the operating-System boundary. Use the already supported referent when it fits the decision. Where the boundary is unsettled, compare materially different plausible candidates: for example, the whole organization, a service operation, production cell, development operation, hospital function, supply relation, personal operation, product or asset, or coordination software. Use A.1.SCR only when System identity changes the decision; otherwise name the actual subject and leave through its pattern.
  3. State the continuing result or service. Name its receiver, conditions, horizon, and the observation that would show interruption or degradation. Keep value, quality, acceptance, fulfilment, safety, and causal effect as separate claims.
  4. Recover demand and commitments. Distinguish requests and candidate Work from admitted Work. For each decision-bearing commitment, name parties, promised result or service, conditions, horizon, authority, current status and any gap in the evidence.
  5. Name operating subjects. Identify the customers, cases, physical items, release candidates, incidents, transactions, materials, services, accounts, or other subjects whose state or relation changes action.
  6. Define every tracked unit. Derive it from the result and the boundaries at which a contribution can become ready, be assigned or be used. Retain the difference between a customer matter, an operation on it, a processing batch and an accepted result where their events diverge. State the unit’s identity rule, start and finish when it is a Work item, subject/result relation, counted interval, and receiving use. If the unit itself needs a different work boundary or preparation arrangement, use OPS.11.1:4.2a; a count on a board alone does not supply that construction.
  7. Draw the operating boundary. Include only the Work, resources, relations, environments, and time horizon needed by the decision. Name the specialist questions left outside the boundary and when their results matter to the operation. Examples include product design, asset condition, finance, law, safety and capability.
  8. Check the control branch. If observation, decision, actuation, supervision, feedback, or rate separation can change coordination, record the control-relevant operating concern for OPS.2. Do not construct a control view or infer a feedback relation here.
  9. Recover authority and evidence limits. Name who may use the focus for which decision, what evidence supports it, any material uncertainty and any missing fact or authority that limits reliance.
  10. Return the focus and any needed continuation. State the supported operating focus or exact unresolved condition. Explain rejected candidates when a boundary comparison was needed. A sufficient answer can finish here; name a next contribution only when the receiving decision still needs it. For a focus maintained across uses, identify changes that would require revision. When a field changes, check the known views, accounts, policies and decisions that relied on it; explain which need rechecking or a return and which remain usable. Communicate that disposition in the account used by the affected participants.

Use an existing workflow or service account when it already identifies the needed result, receiver, promise and return. Add a missing distinction when it could change the decision or the grounds for a conclusion the recipient needs. A short statement can supply it.

OPS.1:4.2 - Carry the Result

Use the current account when it preserves the needed content below. Maintain a record when later reliance, coordination or a governing requirement needs it; a one-time answer can be stated directly.

Result positionContent for the receiving use
use boundaryFirst user, decision, horizon, the result that suffices or the condition limiting the answer.
operating-System boundarySupported System or subject-pattern return; decisive identity and boundary facts, with alternatives and their disposition when comparison was needed.
continuing result or serviceReceiver, result or preserved condition, operating conditions, interruption observation, and any value, quality, safety or acceptance claim that remains open.
demand and commitmentsDemand classes; commitment parties, contents, conditions, horizons, authority, status and any gaps in their evidence.
subjects and unitsIdentified subjects, unit identity rules, Work-item start/finish where relevant, subject/result relations, and receiving uses.
boundary and returnsIncluded Work, resources, relations, environments, horizon, exclusions, and specialist results needed.
control concernThe relevant observation, actuation, supervision, feedback, or rate question, when it changes coordination.
continuationMissing contribution and next useful method, if any; revision conditions for a focus that will be maintained or reused.
downstream effectWhen a focus field changes, which known consumers need rechecking or a return and which remain usable, with the reason needed by their users.

OPS.1:4.3 - What Changes in Practice

The practitioner stops treating “the process”, backlog, service label, or reporting unit as self-evident. Every later view, queue, capacity measure, or intervention must refer to one operating System, a continuing result, explicit commitments, and units whose identity and use are known. A missing boundary or commitment becomes a useful blocker before a policy change accumulates cost.

OPS.1:5 - Archetypal Grounding — PumpWorks Continuing Control Service

PumpWorks must continue weekly evidenced controller releases while field incidents, provider changes, test-rig access, safety questions, and service commitments coexist.

CandidateDisposition for this decision
PumpWorks companyToo broad; corporate, financial, and legal questions remain specialist returns.
controller productAn engineered product and possible plant/controller participant, not the operation coordinating its continuing service.
field installationA product-use and service subject whose state matters, not the whole release-and-incident operation.
board and issue trackerRepresentations and records used by the operation; neither acts as the operating System.
PumpWorks-ControlServiceOpsSelected operating System because its continuing Work coordinates evidenced releases, incident response, provider change, rig access, and service commitments.

The continuing results are usable evidenced releases and truthful incident/service responses, not card movement or software deployment alone. Current demand includes ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, and test-rig requests. They are not one unit kind.

The weekly release commitment names the product/service receivers, required evidence, release horizon, release authority, and hold conditions. Incident response has different parties and horizons. Provider access and safety review have their own commitments and authority. Identify the terms of each commitment before deciding which work can proceed.

The operating subjects include the release candidate, field installation, incident case, safety question, provider change, rig booking, evidence results, and service relation. A release-candidate Work item may be counted for one workflow; the incident case and field pump remain separately identified. The selected boundary excludes product redesign, safety acceptance, corporate finance, and provider-contract decisions except as named returns.

Unlike rates make a control concern current: sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change can affect the release decision. Use OPS.2 to determine which of these timing and control relations matter for the release decision. A conclusion about stability or safety needs its own engineering grounds.

Reopen the focus if the operation’s continuing result changes, field-service Work makes another System the decision bearer, a commitment’s parties or authority change, or the current units cannot preserve subject identity across the next decision.

Suppose ProviderChange-P8 becomes a separately authorized provider-transition operation rather than Work inside PumpWorks-ControlServiceOps. Recheck the OPS.2 migration-project view and the OPS.4 provider-access and authority claims because they consumed that boundary. Keep the release-validation process view and the FieldIncident-I73 case account usable while their subjects, commitments, and relations remain unchanged. Return provider-contract authority to its specialist owner. The focus record carries these three dispositions instead of discarding every downstream result.

OPS.1:6 - Bias-Annotation

Recurring biasLikely driftRepair
process-name bias“The release process” becomes the operating System.Start from the continuing result. Use a supported System boundary, or compare plausible candidates when their differences matter to this decision.
organization-boundary biasA department or company name fixes the operation.Recover the Work and relations that make the bounded operation relevant.
ticket-as-subject biasThe record becomes the customer, product, incident, or commitment.Name the represented subject and the record relation separately.
commitment-by-date biasA due date or service target is treated as an obtaining promise or authority.Recover parties, content, conditions, horizon, status, and authority.
unit-of-value biasEvery counted item is called value or flow.State identity and receiving use; use the source-local term only within its boundary.
controller-name biasA controller product makes every operating question a control question.Enter the control branch only when control relations or rates change coordination.

OPS.1:7 - Conformance Checklist

  • The opening names a first user, operating decision, horizon, and useful stop.
  • The operating System has a supported boundary; materially different plausible candidates are resolved when they affect the choice, or the result returns to the appropriate subject pattern.
  • The continuing result or service names its receiver and conditions without declaring value, quality, safety, acceptance, or fulfilment by wording.
  • Demand, commitments, admitted Work, subjects, records, and units remain distinct.
  • Every decision-bearing commitment names parties, content, conditions, horizon, authority, status, and evidence limits.
  • Every counted or tracked unit has an identity rule and receiving use.
  • The boundary names included Work and relations, consequential exclusions, any needed specialist results and any evidence or authority gaps.
  • A control concern is recorded only when it can change the decision; no diagram or controller label establishes it.
  • Any still-needed contribution is explicit; a maintained or reused focus states the changes that would require revision.
  • A changed focus is checked against known uses of the changed field, and affected participants can recover the needed revision or continued use.

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

Anti-patternRepair
“Optimize the whole value stream.”Name the operating System, receiver, result, subjects, and exact selected transformation-flow structure before optimizing.
“The backlog is demand.”Distinguish external demand, candidate Work claims, admitted Work, deferred demand, and records.
“One ticket equals one customer outcome.”Recover the customer or service subject, case, Work items, results, and record relations.
“All urgent items have commitments.”Recover the actual promise or obligation and its authority; urgency and queue rank are separate.
“The board is our operating model.”Treat the board as a representation; select the operation and decision before choosing views.
“The controller is the operation.”Keep the engineered controller, controlled plant, service operation, control structure, and operating account distinct.

OPS.1:9 - Consequences

Using this focus gives later work identified subjects, commitments, units and return conditions before an improvement is selected. It also exposes when the useful next result belongs to product engineering, organization change, maintenance, finance, safety, law, capability development, or another specialist practice.

The cost is early boundary and identity work. Some urgent requests stop because no one can support the operating System, commitment, unit, authority, or evidence claim.

OPS.1:10 - Rationale

Continuing operation is coordinated through actual Systems, Work, relations, commitments, and results. A board, process description, metric, or school can help only after its subject and use are fixed. Beginning from the continuing result and decision makes the boundary small enough to use while preserving the distinctions later queue, constraint, capacity, quality, service, and improvement decisions consume.

OPS.1:11 - SoTA-Echoing

The decision is where to place the operating boundary before changing coordination. A capable incumbent is an explicit Definition of Workflow with meaningful start and finish, receiving stakeholders, policies, service expectations and flow observations. The Kanban Guide 2025.5 supplies that bounded construction. TameFlow’s preparation and commitment discussions add the recipient’s useful package and the distinction between an option and committed work. OPS adopts those contributions rather than replacing them with a new preliminary form.

Compare the same PumpWorks decision. A well-maintained release workflow can already identify its validation work, completion criteria, WIP and promised delivery. If that is the decision’s whole reach, reuse it as the operating focus. If the question is whether the service can release R42 while continuing incident I73, however, finishing validation and restoring the field installation are different results. A single workflow may deliberately exclude the field receiver, the safety decision and provider-access commitments. Sections 4.1–4.2 add only the missing relation to those subjects and the participant who can answer it. The gain is a changed boundary and return: a completed lab package can be available while field restoration or release permission remains unresolved. If the release workflow already represents these relations, use it directly.

For another use, consider a competent travel-office workflow whose finished item is an issued ticket. The receiver now needs arrival before a site-access window. OPS.1 asks whether the current promise is ticket issuance or a usable travel arrangement, and who supplies the access and timing conditions. The result may remain a bounded travel service with a returned access question, rather than expanding its responsibility to the success of the whole visit. If the existing workflow already captures that receiving use and return, nothing must be added.

Establishing a missing relation between a subject and a commitment can take work with the receiver. Count that work and any later maintenance that continued use requires. Compare the cost with what the distinction can change about admission, continuation, a promise, an intervention or the grounds for a conclusion the recipient needs. Use the existing workflow directly when it already supplies those grounds.

FPF’s A.1.SCR, A.6.REL, C.2.1 and A.10 govern System recognition, relations, accounts and evidence. The historical DEMO distinction between production and coordination helps identify commitments and participants. Choose the operating boundary for the decision and establish local authority from the applicable arrangements. The PumpWorks and travel-office examples show when a missing relation changes the useful boundary. A comparison of effectiveness needs evidence from use of the alternatives. Reconsider your choice when it omits a relation that matters or when the existing workflow can supply the same answer at lower total cost.

OPS.1:12 - Relations

  • A.1.SCR governs conditional System recognition; OPS.1 consumes that result and adds the operating continuation, commitment, subject, and unit boundary.
  • A.6.REL and direct subject patterns govern obtaining relations. C.2.1 governs persisted claim-bearing accounts; a focus statement creates neither relation nor world state.
  • OPS.2 consumes the operating System, commitments, subjects, units, decision questions, and any control-relevant concern. OPS.3 consumes subject candidates, commitments, evidence questions, and identity gaps.
  • OPS.5 later consumes the eligible demand and current commitments for admission; OPS.15, OPS.17, and OPS.19 later consume the operating scope for account, repertoire, and simultaneous-Work decisions.
  • Product engineering, OCE, Maintenance, HCD, finance, governance, administration, safety, law, medicine, and other specialists retain their subjects, Methods, evidence, and authority.

OPS.1:End

OPS.2 - Select Work-Management Views and Coordination Methods

Status: Stable

OPS.2:0 - Use This When

Use this pattern when the same continuing Work is being called a project, process, case, workflow, queue, programme, or control loop and that choice changes coordination. Enter when one view hides a decision that another exposes: a process map may not show a permissible next action for an exceptional case, a project plan hides recurring service, a case file hides aggregate load, a queue hides commitments and subject state, or a loop diagram hides the operating account.

Choose the view and coordination method that answer the current question. For example:

For decision D about subjects S at grain G, use view V and coordination Method M under conditions C. If another view must be used with it, specify how their subjects correspond, which commitments and handoffs connect them, which rules apply and when to stop.

You may select one view or several compatible views, or keep the current arrangement when the existing coordination already answers the question.

A disagreement about how to coordinate the Work or a question the current view cannot answer gives a reason to use this method. Establish the structures, relations, performed Work, plans, control claims, authority, safety or evidence on which the selected decision relies through their applicable FPF or specialist methods.

Do not use OPS.2 to classify Work into a universal natural kind, infer performed Work from a plan, select a structure by diagram appearance, or prescribe one lifecycle. If the question concerns only the identity of an already selected structure, mathematical lens, or architecture view, use A.22, C.29, or C.30.LCA directly.

OPS.2:0.1 - Working Distinctions

Name used hereMeaning
WorkActual dated activity under its governing FPF pattern, including the enacted Method. Intended activity belongs to a plan or proposal. A management view describes or coordinates Work; it does not create another Work occurrence.
viewpoint questionThe question a view must answer for a named user and decision, such as dates and allocation, repeatability, changing subject state, aggregate waiting, or feedback and rate separation.
Work-management modeThe selected use of one or more descriptions and coordination Methods for the current Work and questions. The same Work can be coordinated through different views and Methods.
project viewA description emphasizing a time-bounded undertaking, commitments, intended results, decisions, dates, WorkPlan content, allocation, dependencies, and closure conditions.
programme viewA description coordinating several projects or change commitments and their dependencies or intended contributions. Claims about a containing System, a benefit or decision authority need their own grounds.
process viewA description emphasizing a recurring Method, inputs, results, repeated order or constraints, and control points. It does not prove that every occurrence follows the description.
case viewA description organized around a changing subject, current facts, commitments, discretionary or constrained next Work, exceptions, and closure conditions. The case is not its file.
queueing viewA description of eligible items, membership, order or service relation, waiting, arrival, departure, resource demand, and policy for one receiving question. The queue is not a board column.
control-structure viewA current FPF description of one selected control structure and its actual observation, actuation, reference, supervision, feedback, and rate-relevant relations. Use it when the decision depends on identifying that structure and its relations.
coordination MethodA reusable way of coordinating the Work under stated conditions. A view can expose what the Method needs without being that Method.
mixed-mode decisionAn explicit co-use account stating subject correspondence, scope and grain, commitments, handoff or coexistence conditions, decision rules, conflicts, and stops among unlike views and Methods.

OPS.2:1 - Problem Frame

Project, process, and case management are often offered as competing descriptions of reality. Operations practice then chooses a tool or school and lets its default object model decide what exists. Yet one release operation can have a project for platform migration, a recurring process for validation, cases for field incidents, a queue for a scarce test rig, and a control view for observation and intervention at unlike rates.

These views are useful when they supply information needed by the receiving decision. Select each for the question it can answer. Where a decision uses more than one view, identify the subjects and relations that correspond across them.

OPS.2:2 - Problem

Using one view for questions it cannot answer loses information. A process-only account can force evolving cases through a route whose next Work depends on new facts. A case-only account can hide repeatable validation and shared capacity. A project-only account can treat continuing service as a temporary deliverable. A queue-only account can optimize waiting while breaking a commitment. A control-only account can turn observation and actuation into a complete management Method.

The opposite failure is an ungoverned hybrid: every tool and view is kept, but subjects, grains, states, and decisions disagree. Participants spend more effort reconciling records than coordinating Work.

OPS.2:3 - Forces

ForceTension
Familiar methodsTeams can act quickly with a known project or process Method, while familiarity can hide the wrong question.
Several truthsUnlike views can all be useful, while their subjects and state claims may conflict.
Runtime discretionSome Work can be planned, while new facts require case-responsive continuation.
Aggregate coordinationIndividual cases need attention, while shared queues and resources require a population view.
Control languageFeedback and rate distinctions can change coordination, while a loop diagram can overclaim stability, safety, or authority.
AffordabilityA full multi-model account is expensive, while one view may omit the next decision.

OPS.2:4 - Solution

Select views and coordination Methods from the operating questions they must answer. Preserve Work identity across views, select actual structures independently, and combine views when their distinct information can change the decision or what supports it.

OPS.2:4.1 - Pattern-Use Unfolding

  1. Recover the operating input. Start from the OPS.1 operating System, continuing result, commitments, subjects, units, horizon, and decision. Stop if the mode question is only a label preference.
  2. List the viewpoint questions. Name each user, decision, subject, grain, horizon and any information still needed. Separate planning, recurring execution, case continuation, aggregate waiting/capacity, and control questions.
  3. Identify relevant view candidates. Use a sufficient current selection directly. For an open choice, compare the incumbent with plausible alternatives, including a simpler view where it can answer the question. Candidate views include project or programme, process, case, queueing and control-structure views.
  4. Compare fit to the current Work. Examine the conditions that distinguish the serious candidates: for example, predictability, recurrence, subject identity, decision latency, runtime discretion, plannability, shared-resource coupling, exception frequency, evidence refresh or authority. Reuse an adequate existing selection when its grounds still hold.
  5. Select the coordination Method separately. Recover the actual rule or reusable way currently used: what fact permits a start or continuation, who applies it, what it orders, what evidence it needs and when it stops. Use OPS.17:4.1–OPS.17:4.4 when a real alternative or combination must be chosen. Compare the incumbent with that alternative at the same operating decision and include application and maintenance effort. Retain the incumbent when adequate. A notation, board, model or view alone is not this rule.
  6. Qualify a selected structure when needed. Use A.22 when the decision needs a claim about a selected transformation-flow, queue/resource-dependency, commitment, event, case-state, control or other structure. Preserve its actual constituents and relations. A mathematical graph or diagram represents that subject under its own correspondence conditions.
  7. Use the control branch conditionally. When coordination or the grounds for its decision depend on observation, decision, influence or their timing, use C.43 to recover the actual participants, information, choice, realization and return. That ordinary account can suffice. Use A.22 and C.30.LCA when a selected control structure and view are needed; use B.2.5 only for an obtaining two-sided supervisor relation and C.27.TA, C.27 or A.3.3 for the exact rate, temporal or dynamics claim. Stop without a control account when the decision and its grounds are independent of these relations.
  8. When views must work together, relate them. State the shared subjects, relevant grain and horizon, state and evidence correspondence, governing commitments, receiving decisions, handoff and update rules. If Methods coexist, settle which rule governs a disputed permission, ordering, resource or stop decision; retain the other rule where its conditions still hold. Use the existing OPS.17:4.4 composition result where current. An unresolved conflict returns to its authority; a “hybrid” label does not settle it.
  9. Examine a consequential change when its handling is unresolved. For a new or changed rule or an uncertain correspondence, change an input the rule uses and apply the resulting permitted action or stop. Identify unaffected subwork: a new fact may retire one exception without changing the recurring procedure, case identity or every view. Reuse a current qualifying replay or operating observation when it already answers this question; communicate what the next participant can still rely on.
  10. Return the selection. State the views and coordination Methods to use, the grounds for a material rejection, and any unresolved correspondence or needed input. A sufficient existing selection can finish the decision. Identify revision conditions when the selection will be maintained or reused.

OPS.2:4.2 - Carry the Result

Use the current coordination account when adequate. The following content is needed only for the questions and combinations selected above; retain it in a record when the receiving use or governing requirement needs one.

Result positionContent for the receiving use
use boundaryUsers, decisions, subjects, grains, horizons, and useful stop.
viewpoint questionsThe planning, recurrence, case-state, aggregate waiting/capacity, control, or other questions that remain current.
candidate viewsA sufficient existing selection, or the incumbent and plausible alternatives considered. Give the reasons for the choice, any material rejection and any evidence still missing.
coordination MethodsThe coordination Methods in use or proposed, their conditions, costs, evidence, authority and stopping rules.
selected structuresExact actual structures and direct relations relied on, plus representation and mathematical-lens boundaries.
mixed-mode correspondencesSubjects, grains, commitments, state correspondence, handoffs or conditions of coexistence, update and decision rules, any conflicts and stopping conditions.
control branchActual information, choice, influence and return needed by the operating question; a selected control view and qualified relation, rate or dynamics claims when that stronger use is needed, or the precise missing result.
continuationAny still-needed subject or state-account input; revision conditions for a maintained or reused selection.

OPS.2:4.3 - What Changes in Practice

Choose descriptions and coordination Methods for the decision, then relate those used together through their subjects and commitments. A view can be added, narrowed, or retired without retyping the Work or rebuilding every other view.

OPS.2:5 - Archetypal Grounding — PumpWorks Mixed Operating Views

OPS.2:5.1 - Identify the useful views

PumpWorks-ControlServiceOps coordinates several unlike questions:

Current questionUseful viewBoundary
How should FieldIncident-I73 continue after new field evidence?Case view over the field installation, incident state, commitments, evidence, authority, and permissible next Work.The ticket is a record; safety and product decisions retain their owners.
How is release evidence repeatedly produced and checked?Process view of the recurring validation Method and its input/result relations.A process description does not establish that an occurrence happened or conformed.
How is a time-bounded provider-platform migration coordinated?Project and, when several projects are coordinated, programme views of commitments, WorkPlan content, decisions, allocations, and closure.The plan is not performed Work, adoption, or benefit.
How is scarce rig access coordinated across eligible requests?Queueing view over request membership, order/service relation, waiting, resource access, and policy.Establish request membership, service order, and resource access for this queueing view; a board column alone does not establish them.
Which observations and interventions matter at unlike rates?Conditional control-structure views for the product-side plant/controller/observer/supervisor relations and the operating-supervision relation.FPF owns the generic structures and rate claims; the diagram is neither the account nor the Operations Method.

The views preserve correspondences to ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, the test rig, commitments, evidence results, and decisions. The incident case can request a validation-process occurrence; that occurrence can consume rig capacity; its evidence can inform the weekly release decision; a platform-migration project can change provider access. None of these relations makes the views one structure.

The product-control structure has FieldPumpInstallation-P4 as plant, FieldTelemetryObserver-O4, DeployedController-C17, and FieldModeSupervisor-S1 only where their direct relations obtain. The operating-supervision structure has ReleaseSupervisorTeam-S2 receive operating-state reports and return release, hold, rollback, or permitted-mode constraints to the operating System. The timing claims remain separate: sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change. Select the timing or control relations needed for this coordination decision. Establish feedback closure, stability, safety or authority separately when the decision relies on such a claim.

OPS.2:5.2 - Choose and combine actual coordination rules

In a constructed 09:00–11:00 window, PumpWorks permits at most two active engineering work packages under its existing staffing and recovery policy. T8 is already running. Incident diagnosis I73-D and the older provider-preparation package P8-P are both ready and permitted; both would need engineer E18. I73 has a field-contact window closing at 11:00, while P8-P can wait until the afternoon without violating a promise. The recurring T8 validation procedure is adequate and remains unchanged.

The incumbent rule starts the oldest ready package when a slot and performer are free. Its virtue is predictable order with little coordination. The incident rule allows a ready package to precede that order when a named response window would otherwise be lost, provided the incident lead authorizes the exception, the resource owner confirms it, displaced work remains feasible and the active limit is respected. These are supplied local rules, not universal properties of either a case view or Kanban.

Using OPS.17:4.2–OPS.17:4.4, the coordinator compares the two rules at this decision. Starting the noninterruptible two-hour P8-P would remove E18 from the incident’s remaining evidence-and-response interval. The exception instead starts I73-D, defers P8-P to an authorized afternoon review and leaves T8 running. Preserving the field-contact window costs one confirmation and a follow-up on the deferred package. Under the combined rules, readiness and permission govern eligibility, the incident exception governs order among eligible packages, the two-package limit still governs starts, and validation controls its own safe completion. No extra active slot is created.

At 09:50 the field contact becomes unavailable. The exception no longer justifies reserving E18 for live verification. The incident remains a case with a partial diagnostic result, but the live continuation returns for access and permission. T8’s completed evidence and the independently permitted T9 validation remain usable; the coordinator reconsiders ready demand without reopening every view. OPS.5:5.1, OPS.6:5.1 and OPS.7:5.1 develop the admission, observation and commitment decisions for this same constructed matter. They can also be used independently.

Keep the existing validation process where its rule fits. Add the case, queue or commitment relation when it changes the decision or the grounds for relying on it.

Reopen the mode decision when a new subject cannot be related across views, a plan repeatedly fails after new facts, queue policy changes a commitment, a control relation becomes decisive, or maintaining one view costs more than the decision value it supplies.

OPS.2:6 - Bias-Annotation

Recurring biasLikely driftRepair
one-true-kind biasWork is declared inherently project, process, or case.Recover the question, subject, and selected view; preserve Work identity.
tool ontology biasThe tracker schema decides which objects and states exist.Identify subjects and relations first; treat the schema as representation.
hybrid-label bias“Hybrid” hides missing correspondences and decision rules.State subject/grain mappings, commitments, coexistence, conflicts, and stops.
process-normality biasExceptions are forced back into the designed route.Use a case view when new facts change permissible next Work.
project-temporariness biasContinuing operation is treated as a project deliverable.Keep the time-bounded change view separate from ongoing service Work.
loop-as-method biasA feedback diagram becomes the whole Operations Method.Use the conditional FPF control branch and retain the operating decision separately.

OPS.2:7 - Conformance Checklist

  • The decision begins with an OPS.1 operating focus and exact viewpoint questions.
  • Work identity is preserved across every selected view.
  • Project, programme, process, case, queueing, and control are selected for questions rather than declared natural Work kinds.
  • Coordination Methods, views, actual structures, diagrams, and tools remain distinct.
  • Selection uses the conditions that distinguish the serious candidates and reuses an adequate current answer.
  • Every mixed-mode use states subject and grain correspondence, commitments, coexistence or handoff, update and decision rules, any conflicts and stopping conditions.
  • The control branch names actual participants and direct relations only where they obtain and returns rate/dynamics claims to their FPF owners.
  • A changed case or cross-view probe can expose a failed selection or correspondence.
  • Any material rejection, unresolved gap or needed continuation is explained. A selection maintained or reused includes the conditions for revision.

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

Anti-patternRepair
“Everything is a process.”Identify changing subjects and ask whether discretionary or constrained case continuation is needed.
“Every initiative is a project.”Separate time-bounded change commitments from recurring and continuing operation.
“Case management means no process.”Retain reusable Methods and recurring subwork while letting subject state govern permissible next Work.
“Put all work in one queue.”Name eligibility, service/resource relation, commitment effects, and the subjects that must remain separate.
“Use one integrated model.”Preserve non-isomorphic views and relate only the claims the decision consumes.
“The loop proves control.”Recover actual relations and use direct rate, dynamics, evidence, safety, and assurance patterns.

OPS.2:9 - Consequences

The operation can combine familiar practices while preserving the subjects and results each one addresses. Missing correspondences, duplicated state, disagreements between records, stale mappings and the cost of maintaining them can then affect which views to retain.

The cost is maintaining subject and state correspondence where several views are genuinely useful. Some integrations are rejected because the views answer no different question or cannot preserve identity and commitments reliably.

OPS.2:10 - Rationale

A view earns its place when it supplies information needed for a decision or for a warranted conclusion about it. Project, process, case, queueing, and control descriptions foreground unlike structures, times, and questions. Treating them as views preserves their strengths and avoids a false taxonomy of Work. Explicit mixed-mode rules then make coexistence testable without requiring one universal model.

OPS.2:11 - SoTA-Echoing

The question is how to coordinate evolving case work with recurring procedures and shared resources. A strong alternative already integrates them. CMMN 1.1, §4.1 and §5.4.9 supports runtime case planning, procedural subwork and authorized planning roles. An adaptive project arrangement can likewise revise its plan when facts change. Both can already support coordination that changes with the case.

At PumpWorks, such an arrangement can retain T8’s procedure while a case manager selects incident diagnosis. If its case file, resource policy and decision rights also settle the shared E18 allocation and preserve the field-contact window, use it unchanged. OPS adds no gain by displaying the same decision in more tools. The remaining question arises when the case manager’s chosen action, the queue’s oldest-ready rule and the resource owner’s active limit produce incompatible starts. Sections 4.1.5 and 4.1.8 connect to OPS.17 to recover and compose the actual rules; section 5.2 makes the incident exception govern order without overriding eligibility or increasing the limit. The changed contact condition retires that exception while recurring validation survives.

This synthesis costs rule recovery, agreement on the one disputed decision, mapping of the shared subject and evidence, and maintenance of that correspondence. It can be more expensive than using a capable integrated case model, especially when one owner already maintains all relevant policies. Its conditional gain is avoiding an unsupported cross-view action when those policies were separately governed. Stop adding views when they cannot change the decision or its grounds. Retire a duplicate view when its continued use no longer warrants the cost of keeping it in agreement.

CMMN shows how planned and discretionary work can coexist. The DCR tradition supplies explicit conditions and responses. For the operating case, use applicable domain evidence and establish any required external authority from the arrangements or decisions that grant it. The Kanban Guide supplies the bounded flow-policy contribution. FPF C.43 supplies the ordinary control account; A.22, C.29, C.30.LCA and the applicable temporal patterns govern selected structures, mathematical representations and stronger control claims. Reopen when the integrated incumbent already settles the same conflicts more simply, or a new case defeats a relied-on composition rule.

OPS.2:12 - Relations

  • OPS.1 supplies the operating System, continuing result, commitments, subjects, units, horizon, and any control concern relevant to the decision.
  • C.43 supplies the ordinary control account. A.22 governs selected structures; C.29 governs mathematical-lens use; C.30.LCA, B.2.5, C.27.TA, C.27 and A.3.3 govern the corresponding view, supervisor, rate, temporal and dynamics claims when needed.
  • OPS.3 receives selected subjects, grains, view correspondences, direct-relation questions, and representation gaps. OPS.4 receives the selected participant views and their state-correspondence obligations.
  • OPS.5 later consumes the selected coordination form for admission. OPS.6 later consumes case-state and continuation needs. OPS.8–OPS.11 can use the selected views to answer queue, constraint, capacity and interacting-structure questions.
  • Project Management, case management, BPM, Kanban, SRE, and other practices offer candidate coordination Methods. Select a particular Method using its applicability conditions and evidence.

OPS.2:End