Library / Organization Change Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:45:04 UTC

OCE.2:4.1 - Pattern-Use Unfolding

  1. Bound the recovery use. State the organization, intended contribution, receiving decision and horizon. Select a result or preserved condition whose current production or use can change that decision. Begin with an available episode, including an unsuccessful attempt; extend the sample only where another condition could change the account.
  2. Reconstruct the episode from permitted sources. Follow the result from the receiving use back to its contributors, then forward through the actual use and any exception return. Use the source-to-claim moves below. Ask participants to show what they used, supplied or decided on that occasion; retain their explanation and the supporting or conflicting trace separately.
  3. Identify Work at its supported precision. For a relied-on Work claim, recover the performers’ A.13 basis and the A.15.1 occurrence basis. Keep plans, routine descriptions, schedules and reports distinct from the occurrences they describe. When the basis is incomplete, preserve the observations and name the unresolved occurrence claim. Use B.1.5.EW:4.1–4.5 when the connection between a constituent action and the receiving whole is unclear; it helps explain what that action performs, supplies or supports.
  4. Recover the decision-bearing relations. Use A.22:4–4.1 to select the structures needed by this question and A.6.REL or the direct relation governor to keep each predicate and its participants explicit. Recover supplied results, information use, material transfer, decisions, service provision, access and coordination as the episode requires. A carrier such as a ticket can supply evidence for several different relations.
  5. Check the institutional basis where it matters. For a position, obtain the establishment and continuation basis under OCE.5; otherwise retain only the supported description, contribution, eligibility and holder claims. Use A.2.1 for obtaining assignments. Establish authority, responsibility and resource access separately, with their scope, window and basis. Ask the participant or owner who can supply the missing evidence; hierarchy or a budget entry cannot settle another relation’s claim.
  6. Match formal and observed claims. Compare the same action or relation, participants, conditions and time window. Resolve an apparent difference by inspecting its basis, or retain the contradiction and competing explanations. The account distinguishes agree, contradict, unknown and changed-window; the worked procedure below explains their use.
  7. Return a bounded account or a specific gap. Include omitted participants or burdens that can change the decision, the supported result path and its uncertainty. Use OCE.10:4.1–4.3 for a consequential participation gap, including its participant explanation and discriminating contrast. Stop when the account supports the receiving use or exposes the precise missing contribution. Reopen the affected claim when a new occurrence, source edition, participant account, provider condition, authority decision or service result defeats it.
OCE.2:4.1.1 - Turn an episode into a result path

Choose the episode from the receiving question. For a delayed acceptance decision, begin with the evidence that acceptance needed; for an unreliable service return, begin with the result the service user could or could not use. A conveniently documented meeting is a useful starting point only if it connects to that result. An ordinary completed episode can expose the usual path. A relevant exception, failed attempt or other contrast can expose a condition concealed by success. Neither is a statistical sample of the whole organization merely because it is concrete.

Put the permitted materials beside one another: the applicable rule or commitment; the result and its revisions; traces of request, supply, use and decision; and accounts from the people who performed or received the contribution. Ask ordinary questions: What did you need at this moment? What did you receive? What did you actually do with it? What happened when it was missing or unusable? Whom did you ask next? Ask the next consequential supplier or receiver to inspect that part of the account. This follows a result across a real boundary without requiring interviews with everyone.

Construct a short path in verbs, for example: Electrical supplied a compatibility report; Integration used it to challenge a package claim; Electrical returned a corrected result; Safety accepted the evidence; the release director decided release. Follow both the normal route and the exception that changes the decision. If a contribution serves two receiving uses, keep their different conditions visible. Use B.1.5.EW to settle whether an observed action is part of the encompassing performance or supplies separate support; temporal order alone does not settle that connection.

For each consequential link, inspect what the evidence establishes. A repository entry can establish that a version was present; it does not by itself show who interpreted it or whether a receiver used it. A decision record can show an issued result; the effective rule or delegation supplies its authority basis. A participant can explain an undocumented action; another trace or participant may corroborate, qualify or dispute that account. Write the supported claim at this stage, including a reported but uncorroborated action when that is all that is available. Keep a missing link visible instead of completing the expected route from the procedure manual.

OCE.2:4.1.2 - Match claims and resolve only consequential differences

Translate the relevant formal statement into the same concrete question as the observation. “Software owns the package” may concern package assembly, while “Electrical supplied the evidence” concerns the source of one input. Both can hold. Ask which action, result, participants and conditions each sentence names before marking contradiction. A policy that applied before a temporary delegation and an observation after it form a changed-window pair until the effective window is recovered.

When two claims really concern the same case and predicate, inspect the source closest to the disputed fact and an account from a participant affected by it. A newer chart is not automatically stronger than a dated transaction; an event log is not automatically stronger than the rule defining authority. Record which claim changes and why. If the source supports supply but receiving use is unobserved, that use remains unknown. If an applicable rule requires a prior acceptance and the inspected release record precedes the acceptance, retain a contradict pair at that scope; separately investigate its explanation and consequences.

Keep alternatives when they imply different repairs. A late return may result from unavailable rig access, a missing request, an unrecognized obligation or an incomplete log. Look for the smallest available contrast that can distinguish the live alternatives, such as the request and access state in another comparable episode. Use OCE.10 for the participation branch and the direct service or resource owner for the corresponding condition. A majority of interviewees agreeing does not remove contrary evidence, and a disagreement need not prevent an account that honestly preserves it.

OCE.2:4.1.3 - Stop in proportion to the decision

Ask which unresolved claim could reverse the next decision or make its use unsupported. Obtain another permitted observation only when it can change that decision, its warranted claim or its conditions enough to justify retrieval, participant effort and delay; use C.11.DUA when that appraisal is itself difficult. A sufficient existing result can end the inquiry. If neither rival explanation changes the current concept boundary, carry both into OCE.3 and stop. If a missing authority basis prevents an intervention, stop that intervention while preserving the account and permitted design work.

The result can be a few linked claims with a stated missing path. It need not be a census, a complete model, agreement among all participants or an admitted Work occurrence for every observation. Protect personal and commercially sensitive material according to the actual permission and professional conditions. If a source cannot be used, retain the resulting evidence limit; do not fill it with an inference from an unrelated case.