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: obtain a proposed reusable way of changing an organizational contribution. Recover where a current attempt fails, work from the receiving need back to the action that could supply it, and connect that action to the participants, conditions and returns it needs. Explain why the proposed intervention should address this difficulty, what would defeat it, and what can vary on another occasion. Use Method Engineering for whichever qualification, trial, fit, worth, variant or introduction decisions the intended use requires.
A sufficient current Method or result can finish the use directly. Otherwise the first useful result can be a small inspectable repertoire, an explained candidate procedure, or an honest blocker at a named missing operation or condition. Identify the function of a named framework or intervention. Claims of admission, effectiveness, adoption and actual use each require their own grounds.
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. Identify the strategy’s operations and evaluate any claimed implementation outcome separately. |
| 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. Use it to assess an intervention and its results. |
| 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 bear on selecting a Method, establishing its fit or limiting its use. |
| 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. |