They understand or agree; why does the needed work still not follow?
Use this entry when an unclear or disputed proposal, apparent understanding or agreement leaves the next contribution uncertain. A buyer may understand an offer yet have good reasons to decline it. An operator may agree with a change yet lack an input, permission, time or a way to perform the required action. Find the question that matters to the participants, then choose a contribution that answers it and can be used in the receiving work.
Start with what happened and what each participant needs, including people affected by the proposed intervention. The initiator’s desired change is a proposal to examine. Understanding can support a decision; agreement can support a commitment. Neither settles whether the proposed means are justified or whether the work can be performed. A response that changes or declines the proposal can be more useful than assent.
The first useful answer can be a supported comparison, a revised proposal, an informed refusal, a feasible next action or a stated condition preventing dependent work. A successful explanation or trial can remain useful while a launch is deferred. The purchase and internal-change cases below develop these distinctions through the same reporting difficulty.
If the needed method and its conditions are already clear, use it directly. Open only a question whose answer can change the work. When the question has become which of several complete available ways to choose, how to perform the selected way or how to improve recurring assistance decisions, continue with Make an available contribution work in the whole task.
Recover the question and develop the reasons
Recover a recent or representative episode before choosing how to intervene. Establish who did what, what resulted and which work used or lacked that result. Keep an observation such as a late report distinct from an explanation such as repeated entry causing the delay. “We dislike this system” is a complaint; “we need a checked report before allocating the next shift” names a desired result. Whether to pursue it through a new system remains a decision. Recover a missing participant or concern when it could change that decision.
Follow a claimed consequence to the affected work and person. If repeated entry is said to waste a shift, ask which extra operations it causes, what evidence supports that connection and what would make it false. Distinguish the same loss reported by two participants from two separate losses. PSD.11 develops the comparison when consequences, uncertainty and value differences decide among alternatives. Keep an unknown consequence visible instead of entering zero or an invented value in the comparison. When both alternatives are feasible but their consequences for different people point in different directions, use PSD.11’s qualitative-network construction: recover the intermediate relationships and their grounds, carry each alternative through the same network, and ask the affected people or qualified sources to judge unresolved transitions. Its library-service case distinguishes a supported trade-off from an unknown effect, tests a proposed combination backward and forward, and revises only the consequences that depend on a new observation. Understanding a provision or checking its availability does not supply that comparison.
Let the recipient explain why a change would matter and where its value would stop. Their account may expose a relationship they have not understood, a premise they reject or an interest the proposal neglected. Use a relevant example, source, demonstration or repaired explanation for the question it answers. A request to repeat the preferred conclusion would conceal these differences. Understanding a claim and agreeing with it remain different results.
Prepare information already obtainable without burdening the recipient, and choose a form in which the relationship can be examined. A diagram can expose dependencies; a written account can give colleagues time to compare alternatives; dialogue can locate a misunderstanding. Ask for the recipient’s interpretation and questions. Attend to emotional context, likely consequences and the conditions for attention, while keeping those conditions separate from the grounds for the claim. Leave a usable account of the reasoning, limits and unresolved question for the recipient’s later discussion or work. A prompted response establishes what the recipient could do with that support.
When a commercial invitation is the missing contribution, MKT.3 connects the promise a recipient can reasonably infer, an appropriate contact, an attainable response and the work that receives it. Interpret the reply under its stated conditions. Attention, silence or acceptance of a meeting leaves demand and consent to further actions unsettled. Ordinary requested communication can proceed directly.
Change the contribution when the decision question changes. Once a buyer has accepted a reason to change, amplifying dissatisfaction again does not supply criteria for comparing offers. Once an option is preferred, another general demonstration may leave its implementation risk untouched. If implementation fails because a promised input did not arrive, renewed selling does not deliver it. Use the supported answer already obtained and work on the remaining comparison, condition or contribution. Return to the earlier reason only when new information defeats it.
These questions can be pursued in conversation, asynchronously or by several participants. A demonstration may clarify an explanation while exposing a new concern; colleagues may compare options while a data owner examines permission. Connect the answers required by the chosen action before relying on them; they need not arise in one order.
Examine the proposed means and affected concerns
Name the purpose stated by the participant responsible for the receiving work. A supervisor may need a checked report to allocate work, while a supplier proposes obtaining named error histories to prepare it. Ask which part of the proposed action supplies the needed result and which part creates the objection. If a hidden motive is suspected, retain it as a hypothesis with its grounds. Agreement or disagreement alone does not establish it.
Use D.1 when the value basis needs recovery. Identify who may gain or lose, what consequence matters to each side, and why. Attribute the premise to a person’s statement, an applicable agreement or a representative whose remit includes that question. For an absent participant, say how the concern is represented. If that basis is unknown and could change the choice, obtain it or leave the proposal conditional. Representation for one decision does not supply assent to every use.
Distinguish the decisions and who may make each one. Permission to retrieve records can differ from permission to disclose them or use them in an employment decision. A purchaser’s agreement to a trial does not establish the data owner’s contribution, another person’s consent or authority over a decision outside the purchaser’s remit. Apparent assent under pressure and the absence of an objection leave those questions open.
When claims conflict, D.3 makes the sides and tension inspectable. State which proposed action prevents both concerns from being met as expressed. Then use D.4 to compare means that could meet the receiving need: for example, a narrower disclosure, a different provider or retaining the existing arrangement. Compare the same alternatives under each side’s attributed values, constraints and uncertainty. Include the work displaced and the burden of obtaining further information. Keep disagreement about consequences separate from disagreement about which consequences or duties should govern.
For this decision, an available option that is no worse under each retained value account and better under at least one can remove the need to trade those values. That supports a recommendation for those concerns and conditions. When different value accounts favour different options, state the proposed priority or compromise and the residual concern. Missing permission or an unresolved value premise may instead require inquiry, a narrower proposal, deferral or refusal. A recommendation still needs the named decision and the contributions that make it possible.
State what is being declined and which obligations remain. A buyer can decline a proposed purchase. An employee’s reasoned objection can reveal a defect in an assigned task or its means; it does not itself cancel every reporting obligation. Identify who can revise the task, permission or work allocation and what arrangement applies meanwhile. An organization’s authority to assign work does not establish voluntary agreement or resolve the objection to its means.
Use this reasoning for the conflict that can change the action. An ordinary requested explanation or an adequately supported permissible action needs no new ethics dossier. D.2 helps recognise a concern when that is the missing question; D.5 addresses a separate ethical-assurance claim. Recognising a concern, judging a proposed use and obtaining permission are different results.
Examine a disputed basis for requiring work
Use this when participants understand the requested work but disagree about why one of them may require it of another. A broken tool can prevent permissible work. A clear request can exceed the requester’s authority. A history of unfulfilled undertakings can undermine reliance on a new one. Ask which ground the person is giving: another explanation of the work’s value will not by itself repair any of these conditions. More than one question may need an answer.
For a disputed requirement, make the claimed ground explicit: under which arrangement may this person require that person to perform this action, for this purpose and in these conditions? Obtain the provision or other basis being relied on and the facts that make it applicable. First establish whether the arrangement recognises those roles and includes this kind of work. Then check whether these people occupy the relevant roles for this act, whether the utterance is a requirement or advice, and whether its scope and time are covered. Where requirements conflict for this action, establish which applicable precedence rule or independently authorized decision can settle that conflict. The critical questions for arguments from deontic authority develop this separation between an authority relationship and a particular directive. Use the questions that can change the present answer.
Ask the participants to identify the disputed connection. They may disagree about a fact, the provision’s meaning, its application here, or whether the arrangement should be changed. Bring the relevant text and facts into the discussion. An uncertain domain interpretation may need a qualified contribution through A.15.9; listing authority questions does not supply that expertise. If the applicable provision excludes the requested action, explain that limit to the requester and develop a narrower request when it would still serve the work. If it applies but its consequences are contested, use the preceding comparison of means and affected concerns to develop a proposed revision. State who may decide that revision and what act would make it effective. Discussing its merits and changing the arrangement are different results.
A claim that work was already owed needs the same attention. Recover the actual undertaking, assignment or other instituting basis and the rule under which it created this person’s duty. A.2.8:4.4–4.5 explains why a role description or a record of a claimed obligation is insufficient on its own. If that basis is unknown, leave the duty claim unresolved: uncertainty establishes neither the duty nor its absence. Preserve independently established obligations whose conditions still hold.
Return the answer to the work. Name what can now be requested, decided or performed, the person who may make a needed decision, and any condition still preventing it. When authority or the applicable rule remains unresolved, choose only a continuation supported independently of that disputed premise, or defer the dependent action. Use applicable safety and interim-work rules when delay itself has consequences. A participant may end voluntary discussion without accepting the proposal; any established obligation needs its own permitted revision or release. If agreement cannot be reached, retain the precise disagreement and the basis needed to reconsider it. A claimed title, persistence or apparent assent under pressure supplies no missing decision authority.
This change of subject is informed by Dietz and Mulder’s Enterprise Ontology, §§8.2.1 and 8.2.6: participants can question the norms of their interaction, and an attempted revision can leave an earlier commitment unchanged. Enterprise Design Fundamentals, §6.2.6, also distinguishes disputes about the requested product from disputes about rightness or sincerity. The applicable arrangement supplies the particular authority and revision conditions; these distinctions do not impose one transaction protocol on every conversation.
Reporting: a claimed extension of authority
Use the reporting agreement developed in the purchase case below: the operations manager may release specified current-entry fields for the trial, while named error histories retain their separate protection. Now suppose a manager says, “I am responsible for reporting, so send the supplier the named histories.” The worker accepts the need for a checked handover but disputes that conclusion. Ask which provision extends this manager’s reporting authority to that disclosure. Under the stated agreement, responsibility for reporting does not supply the missing extension.
The current-entry extract remains an available proposal: the operations manager can authorize the listed fields, the provider can prepare them, and the supervisor can allocate work from confirmed information while the data owner retains the correction trace. Their decisions and contributions are still needed. The worker’s objection does not cancel the established reporting duty, and the supervisor’s need does not authorize the broader export. This answer returns to the trial arrangement rather than requiring agreement about every value at stake.
Change the premise. The manager says that a later amendment authorized the export. Obtain the amendment, establish who could make it effective, and check its purpose, people, fields and period. A verified applicable amendment changes the permission question; compare the changed use and affected concerns before selecting the continuation. If the amendment cannot be established, its claimed extension remains unresolved. Continue the earlier limited handover only while its own authority, resources and receiving conditions still hold. If the dispute concerns who may amend the agreement, return that exact question through the agreement’s decision procedure; an office name alone does not settle it. A proposal to adopt an amendment is not evidence that it already took effect.
An asserted earlier undertaking
Suppose a purchaser tells a service team, “You already promised today’s extract.” The only available message is a draft offer marked as awaiting the service owner’s approval. In this constructed arrangement, only that owner can commit the team, and an approved work order specifying the delivery institutes its duty. The draft does not establish that duty. Other communications may exist, so neither the purchaser’s assertion nor the missing approval settles whether a commitment was made. Ask for the approved order or another basis recognized by the arrangement.
While that question is open, do not plan the dependent report as though the asserted delivery were established. The separately authorized internal extract may still support the handover if it can arrive in time; otherwise return the missing input and timing to the person responsible for the reporting arrangement. This preserves useful work without declaring either that the service team owes the delivery or that it is released from an obligation.
Now an approved order covering this team, extract and day is found. The duty’s basis is established, but the team reports unavailable capacity. The question becomes restoration or a permitted change to delivery. Under the case’s rule, a capacity shortage does not cancel the order; revising the delivery time requires the service owner’s and purchaser’s agreement. Proposing a delay does not yet revise the order; if agreement fails, its duty remains while the delivery problem and its consequences still need handling. Use MKT.7 to address an owed service contribution and its consequences; the purchase case below follows a missing input through the reporting work. Confirmation of a duty is not confirmation that the extract will arrive.
An ordinary request outside the offer
In a constructed pizzeria case, the offer covers food and the restaurant has made no undertaking to obtain footwear. A customer asks the waiter to buy sandals and claims that being a customer entitles them to that service. Clarifying the offer identifies the unsupported extension: the customer may ask, but this arrangement gives no footwear obligation. The waiter can decline without persuading the customer to prefer a narrower offer. Help finding a shop is optional. If both already understand this boundary, a brief answer suffices.
A separate concierge offer changes the inquiry. Read its actual scope and any undertaking made under it; neither the word customer nor the restaurant setting decides the result. If an authorized concierge promise has already created a duty, use the preceding undertaking-and-revision reasoning. The initial freedom to decline a service cannot establish release from that later duty.
Find the contribution that is still missing
Name the participants and what each must obtain or do. In a reporting-system purchase, the buyer needs a justified choice, the data owner controls retrieval, the operations manager decides the permitted release, an operator needs to prepare a checked report and the receiving supervisor uses it to allocate work. These participants can understand the same proposal while making different decisions. One person’s willingness does not supply another person’s authority, available time or contribution.
Inspect the answer already available for the receiving question. Check its subject, conditions and permitted use. A qualified trial result may already answer whether an operator can perform a particular check with a checklist and supplied data. Retain that answer even if it does not establish independent performance or coverage of every shift.
When another practice governs a needed result or its qualification, A.15.9 explains how to reuse an adequate answer or request a bounded contribution. Compare the expected value of a new answer for the receiving decision with the total work of formulating the request, preparing and interpreting the answer, and with the delay and work displaced. Request it only when obtaining it is preferable to using the current answer, narrowing the action, deferring or stopping. State the receiving question, subject, conditions, interval and limit of use. The supplier keeps its method and professional judgement; the receiver keeps the decision that consumes the answer. An adequate available answer closes the present question.
For a result already obtained, RESULT-TO-NEXT-MOVE helps identify which downstream question is current. Calling a trial “learning” leaves open what was learned, by whom and under what conditions. Name what the trial produced and under which conditions before selecting reliance, comparison, another inquiry or use.
Select the contribution from the difficulty:
- The proposed relationship is unclear. EXD.4 uses the recipient’s account to locate and repair the explanation. The useful result is an explanation whose relevant relationship the recipient can recover and question. Agreement and later performance remain separate questions.
- The relationship is understood but a premise, consequence or proposal is disputed. PSD.7 preserves the participants’ reasons and material dissent; PSD.11 compares consequences for the affected people under stated conditions. For a purchase, MKT.4 connects this inquiry to the buyer’s next choice, the complete customer work and a feasible trial or acquisition. A corrected judgement or an informed refusal can finish the inquiry.
- Participation in an organizational change remains difficult. OCE.10 examines a concrete episode and explanations that would require different responses. An objection, conflicting assignment, missing authority, burden or unavailable support can require changing the proposal or arrangement. Establish the unresolved human contribution before choosing development.
- Recognition, selection or performance may be limiting the work. HCD.1 identifies the contribution required by later work and its permitted tools and help. HCD.3 distinguishes the limitations that would change the response. The person may need to recognise an occasion, select an action, interpret an input, coordinate help or perform the action. With a suitable task, method, criterion and feedback provider, HCD.9 develops the selected contribution through an attempt, usable feedback, correction and retry.
- A required condition or another participant’s contribution is unavailable. Address the owner of the permission, allocation, tool, input or work under its applicable rules. Reuse a sufficient existing decision. Apply A.15.9 when a bounded result from another practice is missing or needs qualification. ECO.4 helps form missing commitments whose conditions must hold together. OCE.11 coordinates change work with continuing service when setup, learning, support or recovery compete with existing commitments.
These are examples of contributions selected by the difficulty, not a complete catalogue or required sequence. A person who performs adequately with permitted help may already meet the work’s need. Independence becomes a development target when the receiving work requires it. Missing data or permission can stop a capable person’s work without changing that capability.
Connect the returned result to its use
For each connection, say what result the receiver needs, what contribution supplies it and which conditions must hold. State what the explanation or demonstration leaves untested. A buyer’s corrected explanation gives colleagues a proposition they can examine; the group still makes its own comparison and authorised commitment. A practice retry can show a corrected action with stated assistance; a launch still needs that assistance to be allowed and available. A provider’s commitment backed by access and capacity can establish a support arrangement; delivery must then make the promised input available, and the receiver must use it. Observe what was produced and how it was used before concluding that the promised result was obtained. Keep observed improvement, its causal explanation and a claim of acquired capability distinct.
Distinguish actions that make up the work of preparing a handover report from work and conditions that enable that preparation. Checking entries and recording unresolved items are parts of the report-preparation work. The report is the result used by the next supervisor. Granting access is separate work that supplies an enabling condition; a purchase decision can precede the preparation. B.1.5.EW, currently a Candidate, develops this distinction when the relation to encompassing work needs recovery. The reporting rule and the evidence of what was performed still come from the reporting practice.
The ordinary branch of A.22.CGUS makes available, blocked and unknown continuations explicit. E.18.3:4.0 helps identify what changes, the situations being connected and the continuation that depends on the change. Distinguish what is required to start, what must remain available during the work and what the receiving work consumes. Check shared people and time as well as the feasibility of each contribution separately. Keep an unverified prerequisite unresolved until evidence supports it; obtain further information when its effect on a worthwhile next action warrants the burden.
Availability does not by itself choose between several complete ways to obtain one result. Use a direct domain comparison when it already answers that question. If proposed alternatives are fragments such as “use local staff” and “obtain a service”, C.38 develops comparable ways with the same receiving result, use and acceptance basis. Include the permissions, inputs, execution, checking, support and burdens that could change the choice; keep proposed or unknown conditions visible. C.11 then supports a choice, retained tie, rejection of the set or worthwhile further inquiry. A sufficient existing set of alternatives can go directly to that choice.
If no adequately explained way is available, C.39, currently a Draft, offers guidance for recovering a relevant practice’s operations and constructing the missing connection on the receiving material. Its explained candidate still needs the domain support required for the intended use. A known operation blocked only by missing permission returns to the permission owner.
Purchase case: agreement survives the loss of support
An organisation is considering an integrated reporting system for three shifts after a failed handover. An operator wants to avoid repeated entry; the next shift needs a timely, usable report; the purchaser must justify the whole cost; and the data owner controls access. These are constructed teaching conditions. The attempts and changes below are stipulated to explain the decisions.
Begin with the consequences of the reported difficulty. Which handover is delayed? What must the next shift do without the report? Who reconciles inconsistent entries, and which losses actually follow from repeated entry? Check those relations before counting benefits. The buyer can then explain why a timely, checked report would matter: it could let the next supervisor allocate work from agreed information and reduce manual reconciliation. This supplies an expressed reason for change that colleagues can examine.
Once the buyer accepts this reason for change, establish what would distinguish an adequate option: report fitness, whole cost, correction of disputed entries and support across shifts. Compare the proposed system with retaining the present arrangement, repairing the handover without that purchase or obtaining a reporting service. Include the complete work and consequences for the affected participants. A demonstration can show what the system produces from an approved sample, what remains manual and what depends on integration or help. If the buyer understands the proposal but judges its value insufficient, obtain the reason and reconsider the proposal or end the purchase inquiry. Teaching the buyer to repeat a preferred answer would not resolve that disagreement.
Revise the proposed data use before arranging the trial
Suppose the supplier proposes exporting the last week’s named operator-error histories to the purchaser, receiving supervisor and supplier. The data owner permits internal retrieval, and one operator appears to agree in a manager’s presence. Before treating that as a usable trial arrangement, recover the purpose and the authority for each proposed use.
For this constructed case, the receiving supervisor states the purpose: allocate the next shift’s work from the current report entries. That use needs entry identifiers, confirmed status and unresolved flags. It does not need an operator-error history. The data owner can retain the internal source trace so that a disputed entry can be investigated and corrected.
A written reporting agreement protects correction of erroneous attributions and limits person-linked error information to its agreed uses. The affected employees are the operators on all three shifts, including those absent from the discussion. Their elected representative has authority to negotiate this reporting protocol and states their concern: a routine handover trial must not expose named past errors to the supplier or turn them into employment assessments. This remit supplies a premise for the protocol comparison. It is neither each employee’s personal assent nor authority to waive unrelated protections. The supervisor states the corresponding work priorities: a timely checked handover and a retained route for correcting an entry.
The agreement authorizes the data owner to retrieve records internally. It authorizes the operations manager to release the listed current-entry fields to the supervisor and trial supplier for one window. A separate employment use requires its own purpose and decision by the designated personnel authority under the applicable arrangements; none is supplied in this case. Retrieval permission and the operator’s apparent assent do not authorize the proposed disclosure of histories.
The reporting need and the objection can therefore be separated. A checked handover remains valuable, but the supplier’s proposed means carries information beyond its receiving use and breaches the stated protection. Compare three alternatives:
| Proposed means | What the receiving work obtains | Consequence under the stated agreement and concerns |
|---|---|---|
| Export the last week’s named error histories to the purchaser, supervisor and supplier | The export includes information beyond the current allocation need and reveals absent operators’ attributed errors. | This disclosure is outside the agreement and conflicts with the represented concern. Internal retrieval permission does not make it available for this use. |
| Release the approved current-entry fields and retain the source trace with the data owner | The supervisor receives confirmed status and unresolved flags; the data owner retains investigation and correction of disputed entries. | The case stipulates that the owner can provide this correction route and the operations manager can authorize the limited release. The proposal meets the reporting need within the agreement. |
| Defer the trial and keep the existing reporting arrangement | Existing reporting obligations continue and no new disclosure occurs; the useful trial result is postponed. | Deferral remains possible. Under the included concerns and the supervisor’s preference for an adequate report now, it has no advantage over the feasible limited-release proposal. |
Recommend the limited extract on that basis. The operations manager must still decide the release and the provider must prepare it. The recommendation establishes neither that disclosure occurred nor that everyone agrees. It relies on the named receiving need, the agreement, the representative’s remit and the available correction route.
If the representative’s remit or the agreement’s application to these employees is unknown, obtain that premise or defer; do not fill it with assumed agreement. If allocation needs an omitted identity, recover that receiving requirement and compare a suitably bounded disclosure with its value and permission grounds. A separate investigation that lets each operator inspect and correct the last week’s attributed records may need the named records for its authorized investigator. That changes the receiver, purpose and permitted use. It can justify a named-history option under those premises, not the original export to the supplier. Calling that export “customer success” changes none of these relations.
Carry the chosen conditions into the trial and launch
If the limited extract resolves the data-use objection, the next question is whether the proposed arrangement can supply a checked handover in the required window. General enthusiasm for the system does not answer that implementation question. Reuse the buyer’s reasons and the ethical comparison; arrange a trial that can resolve the remaining uncertainty.
A useful next commitment might be a permitted representative sample and a bounded joint trial at an agreed time. Obtain the buyer’s, data owner’s and operations manager’s decisions within their respective authority. Make the needed contributors and resources available, name the question the trial can change and retain a negative or inconclusive result. A conclusion that the expected gain does not warrant the trial is a valid stop. A pleasant promise to meet again supplies none of those prerequisites.
Suppose operator N performs the daytime trial with a consultant’s help. The consultant obtains the permitted data extract. The supported conclusion is that N, using the approved checklist and supplied data, reconciled the entries, marked the unresolved item for the data owner’s decision and prepared this checked report, which the receiving supervisor uses to allocate this window’s work from the confirmed information. The unresolved item remains outside decisions that depend on its resolution. The trial does not establish every operator’s independent performance across three shifts or the system’s causal effect.
The buyer still wants the system, but the consultant will be unavailable at launch and no other permitted extraction arrangement exists. The missing result is an input for report production. Return to the data owner and service provider: can an authorised person or service supply the extract in the required window? Retain sufficient permissions or allocations that still apply. The trial’s one-window release does not authorize launch data; obtain the decision needed for that use. Obtain a missing cross-practice answer through A.15.9 when needed; use ECO.4 for an unresolved provider commitment. If arranging or trying the replacement competes with continuing reporting service, OCE.11 establishes the allowed overlap, support and recovery. N’s supported performance remains useful.
Suppose an authorised replacement needs ten minutes to deliver the extract in a twenty-minute handover window. Now add another required, non-overlapping fifteen-minute assignment in the same window. The combined twenty-five minutes cannot fit, although each assignment is feasible alone. Change the allocation with its responsible owner, obtain another qualified contributor, revise the timing or defer launch. The buyer’s decision and N’s described contribution survive. One supported window still does not establish coverage of all three shifts.
If the consultant was instead doing reconciliation that N must now perform, the unresolved question changes. HCD.1 specifies the contribution N must make, and HCD.3 tests what limits it before practice or continued specialist help is selected. If support was already owed and fails to arrive, MKT.7 governs recovery of that contribution and its consequences; restoration does not depend on another purchase.
MKT.6 connects implementation to representative use, actual assistance and revision when conditions change. Operators and support providers contribute their knowledge to the plan. Arrange with those responsible for assignments to allocate or reserve the required operator and support time, and obtain the required access from its owners. Account for work displaced by those allocations and observe the receiving reporting work before concluding that the implementation is useful. Early enthusiasm or one assisted success leaves those questions open. A feasible pause, narrower use or useful ending can be the result.
Internal-change case: distinguish choosing the action from performing it
A process owner proposes changing the handover rule without buying a new system. The proposed rule requires an evidence-based check before releasing the report, with unresolved entries identified for the next supervisor who allocates work. Before interpreting operator P’s continued use of the old routine, establish which contribution is disputed or missing.
Prepare the decision with the people whose judgement matters
The owner wants advice from a former operations colleague outside the organization. Ask what this adviser needs to understand and arrange a permitted sample, without disclosing the protected operator histories. Using OCE.12:4.3.3, explain how the proposed handover would work and ask which consequence concerns them. The adviser suspects that the checklist creates a second reporting obligation. Their experience gives a reason to examine that claim; it supplies neither authority over P’s work nor a decision for the owner.
Trace one handover with P and the receiving supervisor. In this constructed case the needed preparation and checking take twenty minutes, while copying the status into another tracker takes five more. The available handover interval is twenty minutes. Another explanation of the benefit leaves that five-minute shortage unresolved. The participants inspect the second view’s use and find no separate receiving need. Its responsible owner can retire it. They propose keeping the existing report, putting the selected questions beside the source entries and giving the supervisor its confirmed status and unresolved questions. If a separate consumer needs the copied view, obtain a way to supply that contribution before counting its removal as a saving.
The revised arrangement fits the twenty-minute operator interval; any setup and assistance need their own allocation. The owner can now discuss the proposed work and its consequences with the relevant participants. Decisions about actual capability, resources and authority are needed to establish feasibility. Bargaining over who receives a title before the work is understood would leave that question unanswered. A valid disadvantage can require a different proposal, and an adviser or participant can remain unconvinced. Use OCE.12:4.3.1 when conflicting contributions need an agreement; use OCE.11 when preparation, learning or help competes with continuing service.
Suppose P directly raises a concern that named mistakes might be reused for punishment. The process owner states the need for a checked handover. In this constructed case, the same reporting agreement protects correction and limits use of the records, and the employee representative’s protocol remit covers the affected shifts. A handover containing current-entry status, with the source trace retained by its owner, can serve the reporting use within those protections.
The process owner can choose an allowed cue and allocate checking time; the operations manager controls the limited report release. Neither obtains authority for a separate employment use from P’s assent. If a manager threatens unrelated consequences to obtain agreement, recover the objection through a channel where it can be examined. Suppose this agreement provides a protected route for P to raise the data-use concern through the representative. Use that route to establish what P contests and bring the disputed use to the operations manager, retaining any issue outside the representative’s remit. The response may expose a defect in the proposal or leave a supported assignment in force; apparent assent under that pressure does not decide which.
If P disputes a use the agreement does not settle, or the representative’s remit is unknown, obtain the missing decision basis instead of diagnosing a human limitation. If the protected conditions and required service cannot both be met, describe the conflict and return it to whoever can revise the relevant arrangement. State the reporting obligation and allowed interim work while that question remains unresolved.
Make the agreed start visible and obtain the first result
Suppose the reporting use and protection above are settled and the responsible participants accept the revised arrangement. The process owner allocates the twenty-minute operator interval, the operations manager permits the limited report release, and a capable colleague has separate time to help. One person organizes this first use; the next supervisor remains responsible for the receiving allocation decision. Their shared brief identifies the accepted report, allowed cue and help, source access, timing and response to an unresolved entry. The relevant participants hear or read one another’s confirmed contributions. An absent shift receives the same decision and returns any condition needed for its handover. A launch meeting is useful only insofar as it supplies that shared understanding; it does not supply an unanswered agreement.
Use CHK.3 to put the questions at the handover while the entries can still be checked and a negative answer can change the report. The questions and criteria come from the reporting work; the aid keeps attention on them. The first assisted use examines the actual interaction and receiving report, including an unresolved case. Keep the assistance visible when interpreting its result.
Now P understands the purpose and agrees to the change, yet continues the former routine. The owner supplies the reporting rule and a representative task; tools, access and time are initially available. Calling this a habit is a hypothesis about the difficulty.
Use HCD.3 to examine the alternatives that change the next action. Does P recognise the occasion for the check, select it, perform it when selected and combine it with the rest of handover? Suppose an attempt follows the old routine, while a comparable attempt with a prompt to consider which check applies produces the required check and report. The prompt supplies a selection cue, not the answer. This supports performance with that cue in those conditions. The cue may also prime or teach; the comparison alone establishes neither a durable habit mechanism nor independent recognition.
If the cue is acceptable in ordinary work, retain it and check its use and burden. The useful result can be supported performance. If the work requires recognition without the cue, specify that contribution as the development target. With a qualified task, criterion and feedback provider, use HCD.9 to arrange practice. Ask P to identify the occasion and select the check; the provider gives feedback on a consequential miss. P uses that feedback to correct the selection and tries again on a suitable task. Test the required recognition under the intended conditions before relying on it. If P cannot perform the check even when it is selected, return to the missing explanation, action or domain rule instead of practising selection alone.
Now keep the successful supported performance and withdraw access required to check the source entries. Stop the dependent report check and return to the data owner. More explanation of the change’s purpose does not restore access. Permitted practice on a sample or other independent preparation may continue when its own conditions hold. Restore the affected access condition before using the live source.
If access returns and the earlier extract remains valid for this reporting window, resume checking with it. A fresh delivery is needed only when the retained input no longer answers the current reporting use. Neither continuation requires repeating the purchase discussion or treating P’s earlier performance as lost.
A different observation could redirect the work again. If the required check cannot coexist with the handover burden, change the work arrangement or timing with its owner. If P disputes the rule after understanding its consequences, return to that disagreement through PSD.7 rather than prescribing more practice. If the proposed change no longer serves the receiving work, revise or end it.
For one agreed handover window, the process owner may authorise continued use of the existing reporting tools with the approved selection cue and remains responsible for that temporary arrangement. It is available only if cue-assisted checking is permitted, P has the required access and reserved checking time, and the next supervisor receives the checked report when needed. Keep unresolved entries explicit; the receiving supervisor must be able to make the allocation decisions required for that window from the confirmed information without relying on those unresolved entries. Where the reporting rules permit this restricted use and the supervisor accepts its consequences, the arrangement preserves a useful handover while keeping the remaining uncertainty out of the dependent allocation decisions. Reconsider it at the end of the agreed window. If these conditions cannot be met, revise the proposed arrangement or stop the dependent report release.
In the constructed first handover, P uses the permitted cue, checks the entries against the available sources, and gives the report with one unresolved entry to the supervisor. The reporting rule permits allocating the other confirmed work independently. The supervisor verifies that restriction, makes those allocations and returns the unresolved entry through the agreed response. This receiving action is the useful first return. A completed list alone would not establish it. CHK.3’s ordinary later-use question remains when the arrangement will continue; one assisted success leaves other shifts and independent performance untested.
Change a premise after agreement but before a later start. A maintenance planner now identifies a real decision that depended on the retired tracker. The earlier assumption of no receiving need is false for that use. Ask which information the planner needs and whether access to the existing report can supply it with suitable interpretation and timing. If it can, obtain that arrangement and the affected parties’ response. If the extra five-minute task remains necessary, the twenty-minute window is insufficient: obtain a feasible allocation, change the promised scope or defer the affected start. Communicate the revised decision to those relying on it. Repeating the launch announcement or dismissing this as resistance would leave a contribution missing. Keep earlier valid explanation, checking evidence and unrelated commitments within their existing conditions.
A working mantra and the continuations it leaves open
To recall the broader choice of contribution:
Recover the present question → develop reasons and affected concerns → compare the proposed means and choose, revise or decline → arrange the contribution and its conditions → produce a result and use it → reconsider what changed.
These phrases recall questions developed above. A participant can enter at the question already open, retain an adequate answer, or stop with a reasoned refusal. A meeting may explain and inquire at the same time; permission work and preparation can overlap. The reminder neither makes agreement the desired result of every inquiry nor supplies a universal order of persuasion, learning and work.
For the purchase case’s missing-input question, select the narrower teaching walkthrough:
Missing input → feasible authorised provision → input available for use → checked report → report used by the receiving shift.
The phrases name conditions or results of different participants’ work. The purchase decision and the operator’s supported contribution are retained in this walkthrough. The provider makes the input available; the operator checks the entries and produces the checked report; the next shift’s supervisor judges its fitness and uses it to allocate work. A feasible arrangement still needs delivery; a delivered input still needs the reporting work.
The same walkthrough can be recalled through questions or through operations:
| Connection being explained | Through the problem and question | Through the solution and operation |
|---|---|---|
| The required input can become available in this window. | Who can supply it with permission and jointly available time? | Obtain the needed permission and allocation from their owners. Resolve a missing commitment through ECO.4, or a conflict between change and continuing service through OCE.11, when that is the live question. |
| The arranged contribution supplies an input fit for use. | Has the required extract arrived, and is its use permitted? | The provider delivers it; check that the received input and access meet the reporting use. |
| The entries become a checked report. | What prevents the required check under the permitted help, tools and time? | Perform the reporting method, retaining supported human contributions and making unresolved items explicit. |
| The receiving shift obtains a useful contribution. | Does the report supply what this shift needs to allocate work? | The supervisor judges fitness, uses the report and observes the receiving result. |
A mantra is a working reminder that can link the applicable patterns and their contributions. Its question form and its operation form can recall the same connections. Use it to find the unresolved question and resume the explanation; its order does not prescribe every participant’s work. This ordinary reminder does not require a formal CGUS model.
Retain the continuations omitted by the selected walkthrough:
- If the buyer has accepted a reason to change but cannot distinguish offers, open the comparison question. If a new purpose, affected concern, representation basis or permission changes the data-use judgement, reopen the data-use comparison without discarding an unrelated supported performance.
- If permission is lost before delivery or twenty-five minutes of required work are assigned to the twenty-minute window, reopen the permission or allocation question. Preserve the purchase decision and supported human contribution; defer the launch when no feasible repair is available.
- If source access is withdrawn after the extract arrives, stop the dependent check. Once access is restored, a still-valid extract lets checking resume directly. Return to provision and delivery only when a fresh input is needed.
- If the operator’s contribution is the unresolved part, begin with the internal-change question. A permitted cue can remain; independent recognition needs development only when the receiving work requires it.
- Independent preparation, practice or provision can overlap when their own inputs and shared resources permit. Check their joint conditions again before the receiving use.
These returns explain why a single sequence of persuasion, purchase, training and use can choose the wrong work. The missing contribution may be access or delivery while understanding and capability remain adequate. Conversely, an available input does not settle a human contribution that has not yet been demonstrated under the required conditions.
A customer or learner journey can describe these possible interactions from the participant’s perspective. A plan selects contributors, actions and times; an observed history says what actually occurred. This walkthrough represents one proposed connection within the cases and leaves other shifts, purchase alternatives and long-term learning outside it. Return to those questions when their conditions can change the next action.
The two cases share a way to select and connect contributions; their domain work remains distinct. Requiring unaided recognition changes the internal case’s development and evidence needs, without changing the buyer’s acquisition decision. Losing a seller’s promised support changes restoration and resource arrangements, without making internal change a sale. A shared access condition can affect both, and each receiving use must then be reconsidered.
For advertising, detailed sales or customer-learning work, continue in the Marketing DPF. Organization design and wider participation or leadership questions remain in Organization Change Engineering; development-programme design and transfer evidence remain in Human Capability Development. This explanation develops the connection for the purchase and internal-change situations rather than a complete rhetoric or persuasion technique.
Stop when the current receiving question has an adequate answer, including a warranted refusal or deferral. Reopen the affected result or continuation when its source, required capability, permission, support, shared capacity or use changes. Preserve other warranted results and obtain only the contribution now needed.