Part I - Frame the Change and Compare Organization Concepts

OCE.1 - Identify the Changed Organization and Intended Contribution

Type: Method pattern Status: Eternal alpha

Primary working result: a bounded organization-change focus naming the actual organization System, intended outside contribution, changed Work and capability questions, consequence-bearing Systems, decision and authority boundary, evidence gaps, next result, and one observation that reopens the focus.

OCE.1:0 - Use This When

Use this pattern when a request says “transform the organization”, “change the operating model”, “reorganize the team”, or “become AI-first”, but nobody can yet state which organization is changing or what outside contribution should improve. Enter when a chart, programme name, leader’s remit, or population label is standing in for the organization and the affected Work.

Begin with the decision that needs the focus and the contribution expected outside the organization boundary. Identify the actual organization System when systemhood matters. Keep the actual organization distinct from a possible future organization, a target chart and the programme for changing it. Treat a coalition, provider network or list of people as that organization only when the required System and relation claims are supported.

The first useful result is small: one organization, one intended outside contribution, the Work and capability questions that may need to change, the authority under which the focus can be used, and a bounded affected-System account or explicit discovery gap.

Do not use OCE.1 to choose strategy, grant corporate or legal authority, manage continuing operations, design a product, develop one person’s capability, or decide a target organization. Obtain the specialist result when it is the current blocker. Return to OCE.1 only if it changes the organization, contribution, affected Work, authority, or consequence boundary.

OCE.1:0.1 - Working Distinctions

OCE.1:1 - Problem Frame

Organization change is often named from the inside: a reporting line, function, headcount, technology introduction, merger programme, or leadership concern. Yet the reason for changing usually lies in a contribution outside that description: safer service, shorter evidenced delivery, restored reliability, a different customer outcome, or a new regulatory result.

Starting from the inside hides cross-boundary Work and can smuggle the preferred intervention into the problem. A bounded focus keeps the contribution, organization, affected Work, authority, and consequences visible before concepts are generated.

OCE.1:2 - Problem

Without a bounded focus, every later result can be locally polished and globally misplaced. A team can optimize one handoff while the intended contribution depends on another organization; call a provider part of the organization without a supported relation; treat employees as the only affected Systems; or widen an executive request into authority for every downstream decision.

The change effort then has no truthful stop because neither the receiving contribution nor the changed organization was fixed.

OCE.1:3 - Forces

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

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.

OCE.1:5 - Archetypal Grounding – PumpWorks AI-Inspection Releases

PumpWorks wants weekly evidenced AI-inspection releases while field service and support continue. The initial request says “make Engineering product-oriented and AI-first.” The chart does not decide whether the changed organization is all of PumpWorks, the Engineering organization, a release coalition, or a provider-inclusive whole.

The intended outside contribution is that PumpWorks-EngineeringOrg enables weekly evidenced AI-inspection releases usable by the product and service organization while current field service and support continue. Its value, feasibility, safety and achievement remain separate questions.

Changed Work questions concern product definition, electrical and software integration, safety evidence, model-artifact supply, release decisions, and field-service information returns. The capability question asks whether Engineering can repeatedly produce the evidenced release under those conditions. A plan, AI tool, or isolated build does not establish that capability.

Affected-System discovery includes the contributing practitioners, provider, customers and service personnel, released products, service Systems, and other Systems reached through supported safety, information, Work, or use relations. The focus records unknown customer-use and provider-authority paths.

The engineering director’s sponsorship is not universal authority. The next OCE.2 account must recover actual Work, supplied-result and information-use relations, holder assignments, safety and release authority, rig access, provider service and support relations, participation, and evidence windows. Reopen the focus if field-service or provider Work makes another organization System the decision-bearing subject.

OCE.1:6 - Bias-Annotation

OCE.1:7 - Conformance Checklist

• The opening names a receiving decision, first user, horizon, and useful stop.
• The changed organization is selected from materially different candidates with supported System status.
• The intended contribution names its receiver and conditions without claiming value or achievement by declaration.
• Work, capability, assignment, authority, access, participation, and supplied-result claims remain separately governed.
• Affected-System discovery uses supported relations or modal paths and states uncertainty and specialist returns.
• Claims about assignment, responsibility, sponsorship, permission, capability and authority have their respective support; none is inferred from another category alone.
• An “interface” is never used instead of the selected boundary and direct relations.
• Exclusions, next result, and an observable reopen condition are explicit.

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

OCE.1:9 - Consequences

The focus makes later recovery and concept generation answerable and reveals when the useful next result belongs outside OCE. Some requests narrow sharply or stop because the contribution, organization, authority, or consequence path is unsupported.

The cost is early disagreement about boundaries and evidence. That disagreement occurs before a target organization accumulates commitment and sunk cost.

OCE.1:10 - Rationale

An organization-change decision concerns the relations that need to change among actual Systems and Work. Beginning with outside contribution protects the reason for change while System and consequence recovery prevent an inside-only view. The pattern stops before concept generation because a bounded focus is already useful.

OCE.1:11 - SoTA-Echoing

Reopen when a recurring first-use case cannot orient change through one organization/contribution focus, or when evidence shows that an omitted System, relation, authority, or consequence class changes action.

OCE.1:12 - Relations

• A.1.SCR governs System recognition when systemhood is load-bearing; A.1.CSD governs affected-System discovery. Use their results to define the organization and consequence boundary for OCE.1.
• A.15.6 keeps project System, use, Work, Method, support, and development subjects distinct; A.10 governs evidence reliance.
• Strategy supplies direction and strategic commitments. Corporate Governance and specialist legal practices supply their authority results. Obtain the applicable authority result before relying on the focus for that decision.
• OCE.2 consumes the selected organization, contribution, Work questions, named organization-fact questions, affected-System gaps, and authority boundary. OCE.3 receives the focus only with a grounded current account or explicit tolerated gap.
• Use OCE.10 for target-organization working-culture questions arising from participation or adoption gaps; use OCE.17 for the culture of OCE practice among practitioners.

OCE.1:End

OCE.2 - Recover Current Organization Work and Arrangement

Type: Method pattern Status: Eternal alpha

Primary working result: a grounded current-organization account that identifies the actual Work, supplied results, holder assignments, authority, responsibilities, resource access, information use, material transfer, service provision, coordination, participation, and results needed by one organization-change decision, while keeping formal, observed, contradicted, and unknown claims distinct.

OCE.2:0 - Use This When

Use this pattern when a chart, process map, job catalogue, policy, target operating model, or leader interview is being used as a complete account of the current organization. Enter when a decision depends on how Work actually proceeds, who contributes, which assignments and authority relations obtain, what resources are accessible, or where formal and observed claims diverge.

Begin with a compatible OCE.1 focus or equivalent content. Select only the Work and direct relations that can change the decision.

The first useful result is a bounded account with each claim’s source, status, window and uncertainty. Stop when it supports the decision or identifies the gap that prevents it.

Do not use OCE.2 to invent target positions, assign holders, redesign contribution boundaries, or judge an informal relation defective merely because it differs from policy. Use OCE.3 for concepts and the owning downstream pattern for design or assignment.

OCE.2:0.1 - Working Distinctions

If an existing organization-position claim lacks an effective establishment basis or the OCE.5 identity criteria, do not infer a position from a title or description. Record the expected-contribution claim, eligibility claim, holder, and assignment separately, plus the missing position-establishment or identity basis.

OCE.2:1 - Problem Frame

Formal descriptions support authorization, communication, administration, or staffing. Observed Work exposes who resolves exceptions, which evidence reaches a decision, where providers enter, what resource is scarce, and which informal coordination preserves service. Both can matter; neither replaces the other.

Select separate contribution, Work, assignment, authority, resource-access, information-use, material-transfer, service-provision, and coordination structures for the decision. They can overlap without being isomorphic. A mathematical graph is an optional lens only after its nodes, edges, semantics, and use are selected.

OCE.2:2 - Problem

When the chart stands for the organization, a designer can move boxes while leaving the actual bottleneck untouched. When observation stands alone, a temporary workaround can be mistaken for a reusable arrangement and formal authority or safety obligations can disappear.

The resulting concept has no defensible baseline. Later claims cannot say which relation changed, whether it obtained before, or who bore the burden.

OCE.2:3 - Forces

OCE.2:4 - Solution

Recover the smallest evidence-bearing set of actual Work and direct organization relations that can change the decision. Use A.22 to select each structure and the direct FPF or domain governor for each relation. Preserve formal, observed, contradicted, and unknown statuses, evidence provenance, and currentness.

One decision-changing difference between a formal description and observed Work is enough to enter. Support each Work, supply, assignment, authority, access, information-use, transfer, service-provision or coordination claim with evidence appropriate to its meaning and time window.

OCE.2:4.1 - Pattern-Use Unfolding

1. Bound the recovery use. State organization, contribution, decision, horizon, Work families, selected structures, and exclusions.
2. Collect sources for the needed claims. These may include charts, position descriptions, policies, decision records, Work products, observations, interviews, provider records and service evidence. State what each can establish.
3. Recover actual Work and results. For a relied-on Work claim, recover the performers’ A.13 basis and the A.15.1 occurrence basis. Keep plans, routine descriptions, schedules and reports distinct from the Work occurrences they describe. When the basis is incomplete, record the supported observations and the missing basis.
4. Recover supplied-result and boundary relations. For every relevant path, name supplier and receiver Systems, result or content, direct predicate, conditions, and evidence. Distinguish a contribution supplied, information used, material transferred, decision issued or accepted, service provided, resource accessed, and coordination occurrence.
5. Recover position-related claims without invention. A current organization position requires its establishment and continuation basis. Otherwise record only the position description, expected contribution, eligible system-role kinds, holder Systems, and assignments that are separately supported. Use A.2.1 for obtaining assignments.
6. Recover authority, responsibility, resources, and access. Name each direct relation. Record a blocker instead of inferring authority or access from hierarchy, responsibility, budget, or tool presence.
7. Compare formal and observed claims. State agree, contradict, unknown, or changed-window for each decision-changing pair. Ask what result and consequence the difference has; do not call it dysfunction by default.
8. Inspect participation and consequences. Identify whose Work and burden are absent, which affected-System questions remain open, and which sensitive claims require protection or specialist handling.
9. Stop at the decision boundary. Return the account, gaps, and constraints when they are enough to generate concepts or expose a blocker. Do not design the target inside the baseline.
10. Reopen from evidence. Reopen the smallest Work or relation claim when a new occurrence, source edition, participant account, provider condition, authority decision, or service result defeats it.

OCE.2:4.2 - Record the Result

OCE.2:4.3 - What Changes in Practice

The organization is no longer represented by one chart. Practitioners can see which Work and relations matter, where formal and observed claims differ, what remains unknown, and which gap must be resolved before a concept or coexistence decision can be trusted.

OCE.2:5 - Archetypal Grounding – PumpWorks Current Relations

The OCE.1 focus selects PumpWorks-EngineeringOrg and weekly evidenced AI-inspection releases while service continues. Recovery is limited to release Work, result supply and use, decision authority, provider service, rig access, and field-service information return.

The account records sampled occurrences and source windows. Organization capability and causal-bottleneck claims need additional evidence appropriate to those claims. The rig-access gap, separate safety and release decisions, informal service return, and provider exception path constrain OCE.3 and a future OCE.11 decision.

OCE.2:6 - Bias-Annotation

OCE.2:7 - Conformance Checklist

• The account names one decision, horizon, selected structures, and exclusions.
• Sources state scope, window, sensitivity, and evidential limits.
• Actual Work is separate from plans, routines, process descriptions, and reports.
• Contribution supply, information use, material transfer, decision, service provision, access, and coordination remain distinct.
• A position claim has an establishment/continuation basis, or only its separately supported neighboring facts are recorded.
• Job title, position, system-role kind, holder, assignment, capability, responsibility, participation, and authority remain distinct.
• Every authority and access relation names its participants, scope, window, basis, and evidence.
• Formal/observed differences have explicit status and are not judged by mismatch alone.
• The result stops before target design and supplies usable constraints.

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

OCE.2:9 - Consequences

The baseline can support concept generation because claims are tied to subjects, relations, evidence, and windows. It can also preserve valuable informal contributions that a target design might destroy.

The cost is plural representation. Contribution, authority, Work, access, and information-use structures may need different views. Their non-isomorphism is a finding.

OCE.2:10 - Rationale

Ground the account in observed Work and supported direct relations. Separating formal and observed claims makes discrepancies inspectable. Requiring a position-establishment basis prevents a title or description from becoming an organization object by wording alone.

OCE.2:11 - SoTA-Echoing

Reopen when representative use exposes a decision-changing relation the result cannot preserve, or when a stronger source changes how formal and observed claims should be compared.

OCE.2:12 - Relations

• OCE.1 supplies organization, contribution, Work/capability questions, affected-System gaps, authority boundary, and horizon.
• A.22 governs selected structure identity; direct relation patterns govern supplied-result, assignment, authority, access, information-use, transfer, service, and coordination claims.
• Use A.13 for the performer basis, then A.15.1 for actual Work; use A.2.1 for assignments. Support each claim needed by the receiving decision.
• OCE.5 governs organization-position identity and descriptions; OCE.6 governs holder assignments and enabling relations. Until their needed result is available, record the missing position-establishment or identity basis rather than inferring a position.
• OCE.3 consumes the grounded Work and direct-relation account. OCE.11 consumes it for change/continuing-Work coexistence.

OCE.2:End

OCE.3 - Generate and Compare Organization Concepts

Type: Method pattern Status: Eternal alpha

Primary working result: a bounded organization-concept comparison stating how alternatives differ in contribution, Work, assignment eligibility, authority, resource access, information use, service, coordination, capability, provider involvement, coexistence and burden; which participant contributions or missing voices matter; the decision or honest stop; and evidence that reopens the comparison.

OCE.3:0 - Use This When

Use this pattern when one incumbent arrangement, target operating model, topology, reporting-line change, centralization/decentralization slogan, or provider proposal is being treated as inevitable. Enter when the organization and intended contribution are bounded and enough current Work and relation evidence exists to generate serious alternatives.

Begin with a compatible OCE.1 focus and OCE.2 current account or equivalent content. State which gaps are tolerated and which block comparison.

The first useful result is a small decision set of materially different possible organization concepts. Describe each concept with its assumptions, participant input, supporting evidence, trade-offs and authority conditions. A rejected concept remains useful when it exposes a hidden contribution or burden.

Do not use OCE.3 to make a concept obtain, establish a position, assign holders, establish capability, authorize change Work, or prove adoption or effectiveness. Send selected design questions to OCE.4–OCE.8 and realization to OCE.9.

OCE.3:0.1 - Working Distinctions

OCE.3:1 - Problem Frame

Organization concepts arrive with persuasive forms. Charts foreground reporting; team topologies interaction; provider proposals service boundaries; process views recurring contributions. Each can expose a question, but none contains every authority, capability, resource, contribution, or consequence relation.

Concept generation must vary decision-bearing relations rather than redraw one configuration. It must include incumbent repair and obtain design knowledge from participants whose Work or burden is otherwise hidden.

OCE.3:2 - Problem

A favored concept turns evidence collection into confirmation. Practitioners compare names instead of relations, infer capability from a proposed position, infer authority from hierarchy, and hide the burden of continuing service.

Several diagrams may still be views of one concept. Without a serious alternative and participant contribution, the decision cannot expose which assumption makes the preferred concept better.

OCE.3:3 - Forces

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

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.

OCE.3:5 - Archetypal Grounding – PumpWorks Concepts

The comparison uses PumpWorks-EngineeringOrg, weekly evidenced AI-inspection releases, the OCE.2 account, and non-negotiable safety authority, evidence traceability, and continuing service.

Product, Electrical, Software, Safety, Field Service, platform, provider, and service-liaison participants contribute knowledge of actual Work, scarcity, burden, authority, exceptions and provider conditions. Missing customer-use evidence remains visible; participation does not transfer the release decision.

A chart view can show possible position descriptions; a process view recurring release contributions; a case view one release’s evidence and next decision; and a project view transition commitments and conflicts. These are views of possible or actual Work and relations, not four concepts.

The small set needs no Archive or Front. C.17 may characterize diversity or novelty after the three concepts exist. If later exploration retains many variants and lineage across decisions, that new use can invoke C.18.

If the authorized decision-maker must decide before provider and capacity evidence arrives, the honest result is a narrowed choice between functional repair and stream/enabling plus named probes. Selection supplies design constraints; it does not make a configuration obtain.

OCE.3:6 - Bias-Annotation

OCE.3:7 - Conformance Checklist

• The comparison has a compatible focus and grounded current account or explicit blocking gaps.
• Comparison dimensions distinguish proposed relations, arrangements, capability, coexistence conditions and burden before forms are chosen.
• Participants whose Work or burden can change the alternatives contribute under bounded protection and authority.
• The set contains materially different relations and an incumbent-repair branch.
• C.17 characterizes existing candidates; C.18 appears only when retained or open-ended exploration is current.
• Each concept names possible direct relations; views remain descriptions.
• Capability, authority, access, provider commitment, and continuity assumptions remain explicit.
• The decision does not convert selection into an obtaining organization.
• Downstream constraints and reopen evidence are explicit.

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

OCE.3:9 - Consequences

A target organization is no longer a picture selected by familiarity. Practitioners obtain alternatives with visible participant knowledge, feasibility, consequences, and transition burden.

The cost is that a favored concept can remain unresolved. More evidence or a smaller probe may be required before selection.

OCE.3:10 - Rationale

Organization concepts are possible relation structures for a named contribution. Several views can help, but the decision turns on relations and consequences. A bounded domain generation move avoids importing open-ended search apparatus into every design while keeping that option available when retained exploration is real.

OCE.3:11 - SoTA-Echoing

Reopen when a recurring concept family cannot be generated by these branches, a representation hides a decision-bearing relation, or actual realization defeats the comparison dimensions.

OCE.3:12 - Relations

• OCE.1 supplies organization, contribution, authority boundary, and affected-System scope. OCE.2 supplies actual Work, direct relation evidence, and gaps.
• OCE.3 supplies bounded organization-concept generation. C.17 characterizes candidates already present; C.18 governs retained/open-ended exploration only when current; C.11 governs bounded choice.
• A.22 governs selected structures; C.30 and C.32.CONWAY govern architecture and mirroring claims.
• OCE.4, OCE.5, OCE.7, and OCE.8 consume selected constraints for specialization, positions, product/service alignment, and human–AI/provider configurations. OCE.11 consumes current and possible relations for coexistence.
• Use OCE.9 to realize the selected concept; identify performed Work and changed organization relations from their evidence.

OCE.3:End