OCE.15 - Choose, Develop, or Refresh Organization-Change Methods

Type: Method pattern Status: Eternal alpha

Primary working result: an organization-change Method development-and-repertoire result for a named use. It contains either a repaired named-use repertoire, a bounded OCE candidate Method account prepared for Method Engineering qualification, or both, while keeping intervention contributions, implementation functions, situation claims, mechanisms, source/evidence limits, authority/capability/support conditions, affected Systems, outcomes, and refresh triggers distinct.

OCE.15:0 - Use This When

Use this pattern when practitioners need to choose, combine, construct, adapt, explain, or replace ways of changing an organization and the available material mixes stage models, intervention lists, implementation strategies, process models, determinant accounts, evaluation frames, local routines, consultancy packages, research findings, tools, training, and remembered practice.

Begin with the organization-change situation and the next OCE result. Choose one or both branches:

Repertoire branch: recover, qualify, compare, select, and refresh the smallest set of Methods, candidate accounts, and source contributions for the named use.
Domain candidate branch: construct or adapt the OCE-specific semantics of one bounded candidate Method – its receiving OCE result, intervention contribution, participants, affected Systems, authority, capability, support, protection, situation claims, mechanism hypotheses, outcome distinctions, stops, and allowed variation – then pass it to Method Engineering for identity, qualification, trial, fit, worth, variant, and introduction decisions.

The first useful result can be a small inspectable repertoire, a domain-filled candidate account, or an honest blocker. Do not use OCE.15 to declare a branded framework universally effective, turn an intervention label into a Method, infer adoption from participation, or treat a project, process, or case view as the Method.

OCE.15:0.1 - Working Distinctions

Name used here	Meaning
organization-change Method	An independently admitted reusable way of obtaining or preserving an OCE result under stated applicability and limits.
candidate Method account	An episteme describing a possible reusable way of doing while identity or applicability remains open. Track admission separately from inclusion in the repertoire.
intervention contribution	A bounded action, support, participation, communication, reinforcement, structural, or other contribution proposed for an OCE result. A label may be too coarse to identify a Method.
implementation strategy	A bounded contribution intended to improve implementation of an innovation or way of working. It is neither automatically a complete Method nor the implemented result.
process model	A description organizing implementation activities or temporal dependencies. Recover the reusable Method and actual Work separately.
determinant account	Claims about conditions that may enable, hinder, or explain implementation. Obtain an action sequence and any needed causal support separately.
evaluation frame	Questions, characteristics, measures, and comparison rules used to evaluate implementation. It is not an intervention.
implementation outcome	A result such as acceptability, adoption, appropriateness, feasibility, fidelity, cost, penetration, or sustainment for a named referent and window. Report it separately from the intended outside organization contribution.
organization result	The operating, contribution, coordination, capability, human-condition, customer, or other affected-System result whose change matters. It remains distinct from implementation activity and outcome.
intended mechanism	An explanation of how a contribution could change a named condition. State whether it is a hypothesis or has qualified causal support.
decision-sensitive situation claims	Claims about named Systems, relations, conditions, histories, resources, authority, technologies, institutions, populations, and continuing Work that can change selection or fit.
situation-change account	Observed or anticipated changes in those facts and the observation that reopens a fit, mechanism, support, status, or selection claim.
Method repertoire	The smallest inspectable set of admitted Methods, candidate accounts, source contributions, statuses, relations, evidence limits, gaps, and selection positions for one use.
MethodDescription and its carrier	A description states Method content; a file, book, card, software tool, or other medium carries that description. Training can use descriptions and carriers as support. Recover the Method described separately.
participation and adoption	Record actual participant contributions and relations. Qualify adoption for a separate bounded referent and window; assess capability, retention, effectiveness, and culture with the evidence required for each claim.

OCE.15:1 - Problem Frame

Recognizable schools and recipes make communication cheap but hide unlike functions: diagnosis, participation, strategy, process guidance, determinant analysis, evaluation, training, reinforcement, structural change, resource provision, and cultural work. A complete sequence is often applied when one bounded repair would do.

A useful OCE Method result therefore preserves what each item is for, its candidate or admitted status, situation claims, mechanism hypotheses, implementation outcomes, organization results, and adaptation triggers.

OCE.15:2 - Problem

A method base can become a shelf of brands. Popularity is treated as admission; a local success as effectiveness; a changed slide deck as a Method variant; attendance as adoption; a determinant framework as an intervention; and a favorable implementation outcome as the organization result.

When results disappoint, practitioners cannot tell whether the problem lies in Method semantics, description, performer capability, authority, support, implementation, changing conditions, measurement, or the organization concept.

OCE.15:3 - Forces

Force	Tension
Practical speed	Teams need a contribution now, while Method identity and evidence cannot be granted by a familiar label.
Repertoire breadth	Several mechanisms prevent recipe lock-in, while an encyclopedic catalogue is unusable.
Domain development	OCE must supply domain semantics, while general Method identity and qualification remain in Method Engineering.
Changing conditions	Stable criteria support reuse, while situation facts change during organization-change Work.
Bundles	Contributions can complement one another, while interactions, burden, and causal contribution are hard to isolate.
Participation	Involvement can improve information, while it can be symbolic, burdensome, unsafe, or outside authority.
Evidence	Reviews improve grounding, while heterogeneous measures and settings limit transfer and causal claims.

OCE.15:4 - Solution

Start from the receiving OCE result, choose the repertoire branch, domain candidate branch, or both, and preserve every item’s function and status. Use OCE.15 to specify what the organization-change Method must do in its working situation. The current Method Engineering Principles Framework supplies general focus, repertoire, criteria, qualification, trial, fit/transfer, worth, variant/provenance, and introduction/revision results.

Recognition is cheap: a named recipe with no inspectable function, status, situation, evidence boundary, or receiving result is enough to enter. Assurance is claim-specific: Method admission, source reliance, situation fit, actual Work, contribution, implementation outcome, and organization result remain separate.

OCE.15:4.1 - Pattern-Use Unfolding

Name the receiving OCE result. State organization, contribution, OCE question, receiver, horizon, decision authority, and stop. Do not begin from a framework name.
Choose the branch. State whether the need is repertoire repair, domain candidate construction/adaptation, or both. Name the result that each branch must return.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.

OCE.15:4.2 - Record the Result

Result position	Required content
named use and branch	Organization, contribution, receiving OCE result, receiver, horizon, authority, stop, and selected branch or branches.
item identity/status/function	Method or candidate; separate intervention strategy, process model, determinant account, evaluation frame, description, carrier, tool, training, support, WorkPlan, actual Work, and local routine.
domain candidate semantics	Entry conditions, contributions/operations, dependencies, stops, result, variation; participants and affected Systems; authority/capability/support/protection; mechanism and evidence needs.
situation facts and changes	Decision-sensitive facts, observed or anticipated changes, and reassessment triggers.
implementation and organization results	Implementation outcomes with referent/window and distinct intended organization results.
sources/evidence	Source edition, population, setting, measures, design, used findings, limits, qualification window, and unintended-consequence questions.
views and structures	Project/process/case viewpoints; same Work; selected Method, Work, assignment, authority, support, or cultural structures; losses.
alternatives/bundles	Individual qualification, interaction, overlap, combined burden, contradictions, uncertainty, and status.
disposition	Repertoire, candidate return to ME, selected item/set/probe/stop, authority, alternatives, and next action.
refresh	Defeated claim, observation, currentness/retirement meaning, preserved history, and external return.

OCE.15:4.3 - What Changes in Practice

Practitioners stop asking which complete framework should be rolled out. They can repair a repertoire or construct the OCE-specific semantics of a candidate, distinguish strategy, process, determinants, evaluation, implementation outcomes, and organization results, and then use Method Engineering for general Method decisions.

OCE.15:5 - Archetypal Grounding – PumpWorks Method Result

PumpWorks needs ways to support current-relation recovery, concept comparison, participation, and a bounded capability increment while service continues.

Item	Function and status	Situation/mechanism hypothesis	Evidence boundary and next use
`C-PW-PARTICIPATORY-WORK-RECOVERY`	Candidate Method account: reconstruct one release case with protected contributions from Product, Electrical, Software, Safety, Field Service, platform, and provider participants	Opportunity to contribute, meaning, and belonging may improve information quality; participation adds burden and may be unsafe	Use as an `OCE.2` evidence probe only with authority, confidentiality, and burden limits
`C-PW-EVIDENCE-RETURN-REPAIR-TRIAL`	Domain candidate: in sampled releases, require Electrical to supply compatibility evidence, the integration holder to use it, Safety to issue an evidence-acceptance result, and the release director to issue the release decision; observe each direct relation and stop on safety or service breach	Visible evidence-use and authority relations may improve coordination; recurrence and reinforcement remain hypotheses	No trial exists. Send the candidate semantics to ME for qualification and trial design; a successful occurrence would not establish whole-organization capability
`C-PW-STREAM-ENABLING-INCREMENT`	Candidate account for one stream-aligned increment with enabling Safety and platform contributions	Shorter handoffs may improve coordination; scarce-specialist overload and identity loss compete	Team Topologies is a concept source, not effectiveness proof; assignments, authority, access, coexistence, and service evidence are required
`C-PW-PROVIDER-HYBRID-INCREMENT`	Candidate account expanding provider contribution under named access, assurance, exception, recovery, and release-authority relations	External capacity may improve ability; dependence, knowledge loss, and authority ambiguity may worsen results	Provider commitment and authority are unresolved; selection stops until those results exist
`PW-QUARTERLY-HANDOFF-PRACTICE`	Observed local-practice account, not an admitted Method	Current coordination may preserve specialist assurance but contribute to delay	Keep as evidence; use ME candidate recovery only if reusable semantics are needed

For this use, participatory Work recovery is an implementation-strategy contribution inside a candidate Method. The release-case sequence describes the process; claims about missing rig access and authority form a determinant account; the evaluation frame supplies the questions for the measurement plan. Record actual participation separately. Assess feasibility, fidelity, and sustained use as distinct implementation outcomes, and weekly evidenced releases with continuing safe service as organization results. Use the evidence appropriate to each question.

Use project, process, and case views to coordinate commitments, recurring evidence contributions, and one release’s changing evidence. Identify the reusable Method separately. The repertoire branch can select the participatory probe; the domain candidate branch can return the evidence-relation candidate account to Method Engineering for qualification and trial design. Attendance records support an attendance claim; keep decision-bearing contributions and adoption separate.

OCE.15:6 - Bias-Annotation

Recurring bias	Likely drift	Repair
brand-recipe bias	A framework is treated as one admitted universal Method.	Recover reusable contributions, function, status, sources, and situation limits.
framework-function collapse	Determinants, process, strategy, evaluation, and outcomes become interchangeable.	Record each item’s function and receiving use.
stage-sequence bias	A teaching or project order becomes a lifecycle.	Preserve dependencies, overlap, early stops, and several views.
participation-romance	More involvement is assumed beneficial and harmless.	State purpose, authority, protection, burden, missing voices, mechanism, and consequences.
resistance label	Capability, authority, resources, incentives, access, mastery, meaning, belonging, participation, or protection collapse into a person defect.	Diagnose the named condition or relation.
static-situation bias	Conditions are assessed once.	Record changed facts and reassessment triggers during change and continuing Work.
evidence inheritance	Findings transfer automatically to an adaptation or bundle.	Bind evidence to semantics, population, conditions, alternatives, and window.
carrier-as-Method	A playbook, course, tool, canvas, or workshop becomes the Method.	Keep Method, description, carrier, support, Work, and result distinct.

OCE.15:7 - Conformance Checklist

The result names the receiving OCE use, authority, stop, and repertoire/candidate branch.
Every item retains its identity, status, function, and limits of supported use.
Domain candidate construction supplies OCE semantics and returns general Method decisions to the named ME results.
Situation claims state the relevant facts, their observed or anticipated changes, and what those changes mean for use.
Strategy, process model, determinant account, evaluation frame, implementation outcome, and organization result remain distinct.
Mechanisms remain hypotheses or evidence-bearing claims.
Capability, assignment, permission, authority, access, support, provider commitment, and protection remain distinct.
Project, process, and case views describe the same Work; the reusable Method is identified separately.
Bundles expose overlap, interactions, contradictions, burden, and status.
Refresh names the smallest defeated claim and preserves unaffected uses and history.

OCE.15:8 - Common Anti-Patterns and How to Avoid Them

Anti-pattern	Repair
“Kotter versus ADKAR: choose one.”	Recover contributions, functions, mechanisms, situations, evidence, and smaller alternatives.
“Use CFIR as the change Method.”	Use a determinant account only for the bounded questions it answers; choose or construct action separately.
“Communication and training handle resistance.”	Identify the condition that defeats the contribution or makes participation unacceptable. Choose a repair for that condition; training requires a learnable contribution to repair.
“We tailored the slides, so this is our Method variant.”	Send changed reusable semantics to ME; otherwise maintain the description, support, or local Work result.
“Everyone attended, so adoption and success are proven.”	Obtain separate participation, implementation-outcome, organization-result, capability, retention, and culture evidence.
“The process view is our change Method.”	Name the viewpoint and same Work; recover the reusable way of doing separately.

OCE.15:9 - Consequences

The organization can maintain plural change Methods without arbitrariness and can develop domain candidate semantics without duplicating general Method Engineering. Practitioners see why an item is present, what it can do, which conditions and mechanisms are assumed, and what outcome it can and cannot establish.

The cost is disciplined status and evidence work. Popular interventions can remain source contributions or candidate accounts; bundles need explicit interaction reasoning; selected candidates can still fail in actual Work.

OCE.15:10 - Rationale

Organization-change Methods address changing organization relations, affected people and Systems, distributed authority, continuing service, and heterogeneous intervention evidence. These conditions change what practitioners must do. Use Method Engineering and FPF for general questions of Method identity, architecture, qualification, trial, fit, worth, variants, introduction, and culture.

Recover the relations among the Method, performed Work, descriptions, capability, instruments, roles, variants and culture. Project, process and case management can offer different viewpoints on the same Work. OCE.15 uses both connections to develop the organization-change Method repertoire.

OCE.15:11 - SoTA-Echoing

Source	Retained contribution	Boundary and practitioner implication
Hagl et al., change-management intervention review	Intervention families and ability, motivation, and opportunity-to-contribute mechanisms support repertoire fields.	The synthesis is not a universal sequence; interactions, boundaries, measurement, and consequences remain open.
Ekendahl et al., context-based adaptation	Decision conditions must be assessed and reassessed while change unfolds.	Use the study’s entity/process perspectives to inspect changing conditions; qualify the local adaptation Method separately.
Kamarova et al., behavior and organizational-change synthesis	Mastery, meaning, belonging, and participation counter recipe and “resistance” reduction.	The synthesis is selective and primarily individual-level.
Wang et al., implementation-framework scoping review and Nilsen, taxonomy	Determinant, process, strategy, evaluation, and measurement purposes must remain distinct.	Use the taxonomies to distinguish functions, then select or construct the Method needed for the local result.
Powell et al., ERIC strategies	Discrete implementation strategies can be candidate contributions.	Determine the required sequence, local fit, and effects for the selected contributions.
Damschroder et al., updated CFIR and Reardon et al., CFIR User Guide	A determinant framework requires project-specific boundary and construct operationalization.	CFIR is not designed to develop an innovation or specify the implementation process and is not a universal OCE Method.
Proctor et al., implementation outcomes and ten-year review	Implementation outcomes need named referents and remain distinct from service, client, and organization results.	Causal relations among strategies, mechanisms, implementation outcomes, and downstream outcomes remain weakly established.
Current Method Engineering Principles Framework	General Method results, connected conceptual synthesis, and several viewpoints on one Work.	OCE.15 consumes the named ME results and adds only organization-change semantics and use.

Reopen when a source or representative use exposes a materially different domain contribution, framework function, mechanism, situation change, outcome boundary, bundle interaction, or candidate-development need, or when Method Engineering makes an OCE move redundant.

OCE.15:12 - Relations

The supplying product is the current Method Engineering Principles Framework named in the framework dependency account. ME.1 supplies Method focus, ME.2 named-use repertoire structure, ME.3 situational criteria, ME.5 individual qualification, ME.11 trial, ME.13 fit/transfer, ME.14 worth, ME.15 variants/provenance, and ME.16 introduction/observation/revision.
OCE.15 supplies the receiving OCE result, organization-change contribution, participants and affected Systems, decision-sensitive situation facts, authority/capability/support/protection, mechanism hypotheses, implementation outcomes, and organization results. A domain candidate remains a candidate until the applicable ME results say otherwise.
OCE.1 supplies organization and contribution; OCE.2 and OCE.3 can supply current relations and concepts. Any OCE pattern can request a named-use repertoire or domain candidate.
OCE.10 can consume a qualified contribution for participation or target-organization working-culture repair and return observations. OCE.13 supplies later organization and affected-System observations. Qualify any Method-effectiveness claim against the evidence and intended use.
OCE.16 consumes a compatible Method/repertoire result for simultaneous Work. OCE.17 concerns enacted OCE discipline culture and can supply bounded feedback; it is not the owner of the target organization’s culture.