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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:30:20 UTC

OCE.3:4 - Solution

Generate a small decision set by changing the relations that matter to the contribution. Begin from the incumbent and current relation account; vary specialization, supplied-result, authority, assignment, access, coordination, provider, and human–AI relations; include affected participants whose knowledge can change a candidate; and stop when the set contains serious alternatives that challenge the favored concept’s assumptions, or a generation gap is explicit.

Use C.17 only after candidates exist, and only for novelty, diversity, value, or comparison characteristics actually judged. Use C.18 only when retained or open-ended exploration – including its Archive, Front, descriptors, telemetry or lineage – is part of the working question. Use C.11 or another applicable decision Method after alternatives, non-negotiables, uncertainty, and authority are explicit.

OCE.3:4.1 - Pattern-Use Unfolding

  1. Bind the comparison. Name organization, contribution, decision authority, horizon, current account, non-negotiables, and tolerated or blocking gaps.
  2. State comparison dimensions before forms. Name the supplied-result, Work, specialization, eligibility, assignment, authority, access, information-use, service and coordination relations that can change the decision. Keep differences in product/service architecture, human–AI or provider arrangements, capability, coexistence conditions and burden explicit.
  3. Choose bounded participants. Invite or otherwise obtain contributions from participants whose knowledge of actual Work, burden, local adaptation, authority, safety, service or providers can alter the candidate set or comparison. Record missing participation and protection limits; preserve decision authority separately.
  4. Generate materially different alternatives. Include incumbent-plus-repair; a changed specialization, contribution, or authority configuration; and a boundary/provider or human–AI alternative when plausible. Each alternative must change at least one named decision-bearing relation. Stop when another variant changes no live assumption or criterion, or record the unmet generation need.
  5. Decide whether retained exploration is current. For a one-time small decision set, proceed without Archive/Front apparatus. Use C.18 only for retained or open-ended exploration; use C.17 only to characterize candidates already present.
  6. Describe selected structures. Name possible constituents and relations. Use charts, maps, scenarios, prototypes, or mathematical lenses only for declared questions and state their losses.
  7. Expose feasibility assumptions. State required capabilities, authority, resource access, provider commitments, product/service claims, participation conditions, and continuing-service constraints.
  8. Compare contributions and burdens. Compare intended contribution, coordination, resilience, affected-System consequences, participant burden, service interruption, reversibility, and uncertainty.
  9. Choose, narrow, probe, or stop. Select under named authority, retain ties, or request the specialist result that changes the comparison. Selection does not establish organization relations.
  10. Return constraints and reopen evidence. Supply the selected questions and assumptions to downstream patterns and name observations that reopen them.

OCE.3:4.2 - Record the Result

Result positionRequired content
comparison boundaryOrganization, contribution, decision, authority, horizon, non-negotiables, and tolerated/blocked gaps.
generation accountDomain generation branches used, relation changed by each alternative, stop rule, discarded decorative variants, and any conditional C.18 use.
participant contributionParticipants sought, contribution used, missing voice, protection/burden limit, and effect on alternatives or comparison.
concept structuresPossible supplied-result, Work, eligibility/assignment, authority, access, information-use, service, coordination, capability, and provider relations.
assumptionsCapability, authority, access, commitment, product/service, participation, and service-continuity claims with status.
comparisonContribution, coordination, resilience, affected Systems, participation, coexistence, burden, reversibility, and uncertainty.
specialist returnsNeeded result, owning practice, scope, and effect on the comparison.
decision or stopSelection, narrowed question, probe, or stop; basis, alternatives, ties, and authority.
continuationDownstream constraints and evidence that reopens the comparison.

OCE.3:4.3 - What Changes in Practice

Teams compare possible organization relations rather than fashionable names. The incumbent can be repaired, product and organization structures can differ deliberately, participants can change the alternatives without receiving an automatic veto, and provider or AI contributions can be designed without pretending that outsourcing or automation supplies authority, capability, or results.