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:50:10 UTC

OCE.1:4 - Solution

Select the smallest organization-and-contribution focus that can orient the current change decision. Recover the actual organization through A.1.SCR when needed, use A.1.CSD for affected-System discovery, then state the intended contribution, Work and capability questions, authority, participation questions and result needed by downstream patterns.

An ambiguous transformation request is enough to enter when the receiving decision lacks a clear organization or contribution. Before relying on the focus, obtain evidence for its claims about System identity, Work, contribution, assignment, authority, access, participation, capability and consequences.

OCE.1:4.1 - Pattern-Use Unfolding

  1. Name the receiving decision and first user. State who needs the focus, what decision it enables, the horizon, and what useful result permits a stop.
  2. List materially different organization candidates. Consider a formal entity or unit, an organization spanning cross-boundary Work, or one including providers when each is plausible. Keep a return to a non-organization question available. Use A.1.SCR only when System identity changes the decision.
  3. State the intended outside contribution. Name the receiver, relevant conditions, and supplied result or preserved condition. Keep strategy, value, benefit, and performance as separate questions.
  4. Recover changed Work and capability questions. Name the Work families, result or contribution relations, performer or coordination facts, and capability claims that could change. Do not infer them from a chart, proposed position, plan, or tool.
  5. Name other decision-relevant organization facts. Ask which holder assignments, authority relations, resource-access relations, information-use relations, material transfers, service provisions, coordination occurrences, and participation facts must be recovered next. If a source calls these an “interface”, select the boundary and direct relations before relying on it.
  6. Discover consequence-bearing Systems. Use A.1.CSD from the organization, contribution, affected Work, horizon, and decision. Include employees, providers, customers, products, service Systems, neighboring organizations and other material Systems when supported.
  7. Recover authority and specialist returns. Name the authority subject, decision scope, window, and basis. Return unresolved strategy, governance, legal, safety, labor, operations, engineering, finance, or person-capability results to their owners.
  8. Select, return, and reopen. State the organization, contribution, included questions, affected-System scope, exclusions, rejected candidates, next result, and one observation that reopens the focus.

OCE.1:4.2 - Record the Result

Result positionRequired content
use boundaryFirst user, receiving decision, horizon, and useful stop.
organization candidatesCandidate Systems or intended referents, supporting and missing relations, rejected alternatives, and selected organization.
intended contributionReceiver, contribution claim, conditions, and unresolved value or performance questions.
changed Work and capabilityWork families, current or intended status, supplied-result or contribution relations, and capability questions.
organization facts to recoverNamed assignment, authority, access, information-use, transfer, service, coordination, and participation questions; no catch-all relation.
affected SystemsA.1.CSD reference or bounded Systems, supported relations or modal paths, possible changed characteristics, gaps, and specialist returns.
authoritySubject, decision scope, window, basis, and evidence boundary; otherwise an authority blocker.
continuationNext useful result and one observable reopen condition.

OCE.1:4.3 - What Changes in Practice

The practitioner stops treating “the organization” as self-evident. Every downstream concept or intervention must answer to one contribution, actual Work and capability questions, affected Systems, and a real authority boundary. The focus remains small without erasing providers, customers, continuing service, or specialist constraints.