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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:00:05 UTC

OCE.16:0.1 - Working Distinctions

Name used hereMeaning
separately managed changeA proposed or actual organization change with its own subject, intended result, status, scope, owner, evidence, and next decision. Separation does not imply independence.
organizational conditionA contribution, assignment, authority, permission, access path, provider or support relation, information return, acceptance route, participation condition, capability condition, or other organization relation or condition that a change may alter.
consequential dependencyA claim that alteration of one named condition can change another change’s exact action or decision within a stated window. It is not proved by temporal overlap, a diagram, or a participant’s interpretation alone.
participant accountA bounded report from a participant or affected System about an action, demand, consequence, or condition. Use it to locate a possible dependency, then test the claimed contradiction against current evidence and recover decision authority separately.
qualified cross-change questionOrdinary decision-support content naming the changes, altered condition, consumer action or decision, window, participants, evidence and claim status, direct Method, result owner, and any missing input.
direct MethodA Method whose result answers the qualified question within its stated applicability. For example, ME.6 compares ways of using Methods together; an appointment requires the applicable assignment Method and actual authority.
per-change returnA readable application of already-governed direct results to every affected change. It adds no second choice or authorization.
direct exitA stop in OCE.16 because no consequential consumer exists, the dependency is unsupported, or the direct answer and its per-change consequences are already available.

Different project, process, case, architecture, Method, organization, and operating descriptions remain different. OCE.16 asks whether one change alters a condition another actually uses; it does not force unlike subjects into one view or one programme.