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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:40:10 UTC

OCE.15:4.1 - Pattern-Use Unfolding

  1. Name the receiving OCE result. State organization, contribution, OCE question, receiver, horizon, decision authority, and stop. Do not begin from a framework name.
  2. Choose the branch. State whether the need is repertoire repair, domain candidate construction/adaptation, or both. Name the result that each branch must return.
  3. Recover current items and functions. Identify admitted Methods, candidate accounts, observed routines, intervention or implementation-strategy contributions, process models, determinant accounts, evaluation frames, support, and actual Work. Preserve status and function.
  4. Qualify source contributions. Record source and edition, population and setting, claim used, measures, evidence design, reported limits, and the OCE decision that the source can change.
  5. Record decision-sensitive situation facts and changes. Name the Systems, relations, conditions, histories, resources, authority, technology, institutions, populations, and continuing Work that matter. Record observed or anticipated changes and the reassessment trigger.
  6. State reusable semantics and relevant mechanisms. Describe entry conditions, operations or contributions, dependencies, stops, results, and allowed variation. Explain the mechanism when its distinction changes the proposed Method or its use, retaining whether the explanation is a hypothesis or an evidence-supported claim. For example, inability to perform a contribution and lack of access can require different repairs. Select other human or organizational conditions only when they change the receiving result; use the source frameworks to investigate that question rather than completing a fixed factor list.
  7. Recover capability, support, authority, and protection. State who must be capable, assigned, permitted, and authorized; needed tools, data, forums, providers, time, resources; and affected Systems needing representation or specialist protection.
  8. Preserve several Work viewpoints. Project views foreground commitments, dates, resources, and decision slots; process views recurring contributions and controls; case views changing evidence, exceptions, and next decisions. Use these views to describe the same Work; identify the reusable Method separately.
  9. Compare individual items before bundles. Ask which item can contribute to the receiving result. For a bundle, state contribution relations, overlap, interactions, combined burden, contradictory assumptions, and stops.
  10. Complete the repertoire branch. Return the smallest qualified set, visible gaps, selection or probe, and refresh triggers. State whether the selected items remain separate or have been qualified as one composed Method.
  11. Complete the domain candidate branch. Construct or adapt the bounded candidate semantics with OCE result, intervention contribution, participants, affected Systems, situation facts, authority/capability/support/protection, mechanism hypotheses, implementation outcomes, organization results, stops, and allowed variation. Then use ME.1, ME.3, ME.5, ME.11, ME.13, ME.14, ME.15, and ME.16 as applicable. Obtain the applicable admission, trial, fit, worth, variant, and adoption results through those Methods.
  12. Observe and refresh the smallest claim. Bind Work, participation, implementation outcomes, organization results, and unintended consequences to the item, semantics, population, conditions, and window. Refresh only the defeated claim.