OCE.1 - Identify the Changed Organization and Intended Contribution
Type: Method pattern Status: Stable
Primary working result: a bounded organization-change focus naming the organization to create or change, its actual or proposed status, the outside contributions and obligations relevant to the decision, changed Work and capability questions, consequence-bearing Systems, authority, local completion, any material evidence gaps, the next result if needed, and an observation that reopens the focus.
OCE.1:0 - Use This When
Use this pattern when a request says “set up a shared service”, “transform the organization”, “change the operating model”, “reorganize the team”, or “become AI-first”, but nobody can yet state which organization is needed 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 what the organization must make possible outside its boundary. For work on a creator, recover the relevant products in their intended use before choosing the creator’s arrangement. Identify an existing organization or describe the organization to be created; keep its actual or proposed status explicit. For a proposed coalition or provider network, identify the organizing relations that would have to hold. For a claim about an existing organization, establish the System and its effective relations.
The first useful result is as small as the decision permits: the organization, the intended contribution or related contributions it must provide, the questions about Work and capability that a change may affect, the applicable authority, and affected Systems or an explicit discovery gap. One contribution can suffice. A shared capability decision must retain the different product uses and obligations that can change it.
Use Strategy, Corporate Governance, Operations, product engineering or Human Capability Development when their work answers the question. For a missing professional result, identify the change claim it limits. Use an applicable result directly or obtain the contribution still needed. OCE.1 establishes the focus for later organization design.
OCE.1:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| changed organization | The organization selected for creation or change, with its actual or proposed status stated. A business-unit name or chart box helps locate it; its boundary and organizing relations require their own basis. |
| intended outside contribution | A result or preserved condition the organization is intended to supply to a containing, using, receiving, or neighboring System. Several such contributions can govern one shared-capability decision. Assess their value and achievement separately. |
| changed Work question | A question about performed or planned work whose result, performer, coordination or conditions may need to change. Distinguish it from work on the change programme itself. |
| organization capability question | A question about the named organization’s ability to perform a named Work family under stated conditions. Capability is not a position, tool, training event, resource, assignment, or isolated result. |
| decision-relevant organization facts | Separately governed claims about Work occurrences or planned work, supplied results and contributions, holder assignments, decision authority, resource access, information use, material transfer, service provision, coordination, and participation. These fact questions help choose what to investigate next. |
| affected-System account | The ordinary A.1.CSD result for Systems whose decision-relevant characteristics may change through supported relations or modal paths. Assess harm, benefit, interest and causal effect separately. |
| authority boundary | The independently supported relation under which a named System may issue or use the current organization-change decision. Ground the authority in the applicable rule, grant or decision. Sponsorship, budget or responsibility alone may leave it unresolved. |
| organization-change focus | The bounded result returned by this pattern. It selects attention and downstream questions; it does not select an organization concept or authorize change Work. |
OCE.1:0.2 - Organizations, enterprises and joint work
An organization is a System of agents and the means of their work, organized through effective, recognized obligations and authority. These relations establish who may decide, use means, assign and accept work, and enter commitments. Those arrangements give the organization the ability to coordinate work. A name or chart can help identify it. A proposed organization remains a design until the needed relations and means are established.
An organizational unit is an organized constituent of another organization. A department, council, temporary project group, or one agent with assigned means can be a unit. Its functional roles, institutional positions, holders and assignments remain different matters. A unit can perform several roles, and a position can continue while its holder changes.
An enterprise, in this Library, is an organization pursuing a defined product direction with a commercial purpose: an expected positive economic result from its offering. It has a mandate to form or change the offering, undertake economic obligations for providing it, choose means within permitted limits, and bear the assigned consequences for continuing that direction. Identify to whom receipts, material costs and risks accrue when judging the result. An actual loss does not by itself end enterprise status; purpose, arrangement and achieved return are different claims. Noncommercial organizations remain organizations without needing this classification.
An internal enterprise is such an enterprise that is an organizational unit of another organization. Its mandate specifies the offering and commitments it may change, means it may use, how receipts and costs are attributed, who accepts its result and who can continue, revise or stop the direction. It can operate through the containing organization’s legal arrangements. A separate legal entity and unrestricted independence are unnecessary; the containing organization’s reserved rights and other participants’ obligations still apply.
A service department performing assigned work within an externally set budget remains an ordinary unit when others retain the offering and economic decisions. A manager, internal tariff or profit-centre label supplies no missing mandate. If that unit receives the relevant rights and consequences, its arrangement changes and internal-enterprise classification can become warranted. Discretion over a technical method or savings within a budget can coexist with another unit’s authority over offerings and commitments.
An extended enterprise is an organization of joint work by several organizations that retain their own boundaries. Their mutual obligations, decision rights, result transfers and resource arrangements enable coordinated work for named products and uses. A product System they agree to create, change, sustain in use or retire is the system-of-interest of that extended enterprise. Agents acting for the organizations establish or accept the objectives and commitments; the product’s intended use and effects give reasons for those decisions. Recover that organization from the actual agreements and work. A supplier graph, common owner or sequence of purchases alone does not establish it. Participants can belong to several such arrangements without committing all their work and means to one project.
These distinctions use different grounds. Enterprise concerns economic purpose and mandate; extended enterprise concerns the organization of joint work across organizations; internal concerns a constituent relation. An extended enterprise also qualifies as an enterprise only when its economic arrangement meets that definition. Legal-entity status is a separate institutional matter. A common boss, legal entity or budget is not required for coordinated joint work, and a participant’s commercial purpose need not be shared by every other participant.
Use ordinary names and questions first: which product, which unit, whose promise, whose decision, whose means? Classify only where the difference affects the work. OCE.2 recovers evidence of existing relations. For a proposed organization, recover the contributors and relations the concept would reuse, keeping unestablished contributions as assumptions. Use OCE.3:4.1.1.2 to develop a proposed mandate. OCE.6 helps establish which assignments and enabling relations are in effect and which still require their holders’ action.
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
A carefully developed change can concern the wrong organization or contribution. 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.
Until the contribution and organization are bounded, the team lacks a basis for deciding when its work on that change is complete.
OCE.1:3 - Forces
| Force | Tension |
|---|---|
| Urgency | Leaders want a target quickly, while a false organization boundary makes later speed expensive. |
| Familiar labels | Charts and programme names aid orientation, while they can hide the actual System and relations. |
| Outside contribution | The focus must be bounded, while a shared organization decision can depend on several products and receivers with different obligations. |
| Consequence breadth | Employees and customers are visible, while providers, service Systems, products, natural Systems and future users may also bear consequences. |
| Authority | A bounded decision needs a legitimate issuer, while responsibility, influence, sponsorship, and access can be mistaken for authority. |
| Reopening | The focus must be useful now, while evidence about Work, contribution, authority, or affected Systems can defeat it. |
OCE.1:4 - Solution
Select the smallest organization-and-contribution focus that can orient the current change decision without dropping an obligation that could change it. Establish the product uses and contributions needed, then locate the organization and capability to create or change. Use A.1.SCR when an actual System claim needs recovery and A.1.CSD for affected-System discovery. Return the Work and capability questions, authority, participation questions and local result needed by downstream patterns.
Use an adequate existing strategy or organization-change brief as input. If it already establishes the contribution, organization, authority and consequence boundary needed here, reuse that content. If the direction remains disputed, seek the strategy decision or keep the focus conditional. Use its result wherever it settles or changes the organization question.
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
- 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.
- Recover the intended outside contributions. Name the products or other results, receivers, uses, conditions and commitments that can change the decision. For creator work, follow §4.1.1 from product use to needed capability and local completion. Reuse a sufficient account. Seek a missing strategy or domain result when the focus depends on it.
- List materially different organization candidates. Consider a formal entity or unit, an organization spanning joint work, or one including providers when each is plausible. Use §0.2 to distinguish the arrangement where that matters and
A.1.SCRwhen System identity changes the decision. Keep actual organizations, proposed organizations and a return to a non-organization question distinct. - 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.
- 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.
- Discover consequence-bearing Systems. Use
A.1.CSDfrom the organization, contribution, affected Work, horizon, and decision. Include employees, providers, customers, products, service Systems, neighboring organizations and other material Systems when supported. - Recover authority and specialist returns. Name the authority subject, decision scope, window, and basis. For any missing professional judgment or decision, state the question and identify the authority, practice or service that can answer it.
- Select, return, and reopen. State the organization and its status, contributions and obligations, included questions, affected-System scope, any exclusions or rejected candidates, the local completion condition and any further result needed. Name an observation that reopens the focus, such as a changed product use, commitment or authority.
OCE.1:4.1.1 - Derive the organization-change focus from product use
Start with what should become possible or remain possible when the product is used. Name the product System being created, changed, sustained in use or retired, the extended enterprise organized for that undertaking, its participating organizations and agreements. Identify the agents entitled to establish or accept the objectives and commitments, the users and relevant surrounding conditions. In a service, identify the system whose condition the service changes or preserves. Recover the obligations that depend on this use: a promised delivery, acceptable result, response interval or continuing availability. For retirement, state the use that ends and the condition the assigned work must achieve. Each participant can have a bounded obligation; the present extended enterprise need not consist of the product’s original creators. The user, beneficiary, buyer, payer and investor can be different parties. Funding makes work possible; usefulness and fitness for use need their own grounds.
Then work back to what the creator must be able to supply and which organizational change could obtain that ability. The reason for a workshop can be repeatable production of a surface suitable for a customer’s assembly under an agreed order flow. For this machining service, recover the agreements organizing the workshop and receiving organizations’ joint work. The changed part is the product SoI of that extended enterprise; the workshop is the creator. The workshop needs the relevant technique, people, measurement, material and equipment together. Purchasing a machine closes a supply contribution; it leaves workshop capability open if the machinist, measurement or material access is missing. If the planned product or means proves infeasible, reconsider the affected choice. Another means may provide the same required capability.
Keep the product and the organization in view together. In creating or changing an organization as creator, retain the product-side SoI as the common reference for the work. Name the organization as the creator being engineered, or system-in-hand. For its design, consider its use, functions, arrangement, characteristics, limits, means of realization and its own creators. These engineering questions do not require renaming it SoI. Its project can have a separate budget, contract and acceptance. Outsourcing the same reorganization, opening a new contract or calling the contractor a producer of enterprises leaves this product basis unchanged.
Retain several uses when the decision is shared. For a common laboratory, recover the test regimes, result requirements, timing and obligations of the product lines that use it. Keep differences that alter capacity, equipment, competence or priority. Group common demands, then examine their joint use of scarce means. Neither a single convenient product nor an undifferentiated name such as “pump products” is sufficient when the differences change the design. The focus need not cover unrelated product work. OCE.3:5.4 shows how two uses alter a shared laboratory decision.
Distinguish a supplier’s product from the same creator work under a new contract. A machine-tool maker can have the tool as its SoI while the receiving factory uses it as a creator. An engine maker can supply an engine for a stated aircraft application or class of applications while an aircraft maker treats it as a subsystem. Recover the supplier’s substantive obligation for a usable supply, the receiving use, actual decision boundaries and acceptance. A customer may specify the design and use concept; owning the whole product strategy is not a prerequisite. Use the supplier’s actual obligation and the receiving use to judge the SoI within the agreed scope. Moving the factory’s existing organization-change work to a consultant leaves it work on the aircraft’s creator. Renaming that work or its payment does not create the supplier case.
A firm can itself be bought, sold or valued, and its assets can have value separately from continued production. Keep that economic object and decision available. In engineering the operating organization, justify its capability through the products or classes of future use it is to support. A price or transaction does not replace this basis. A real change of product direction requires its own decision and revised grounds.
Make local completion finite. Identify the capability or other contribution this project must deliver, who may accept it, the conditions to demonstrate and the obligations that continue afterwards. For a claim that the capability has been realized, use applicable evidence or qualify it through OCE.9. Acceptance can occur before future product operation when the agreed evidence supports the local claim. Preserve assumptions about future use, accepted risks and who will decide when new evidence arrives; the contractor’s responsibility stays within its agreed scope.
When intended use is uncertain, retain specific possibilities and the inquiry needed to distinguish them. A bounded research project can finish with a warranted answer or a reason to stop expenditure. Independent research retains its own knowledge question and subject standards; research for a capability decision additionally establishes what that answer warrants for the decision. A research result is not realized organization capability. Noncommercial contributions, preservation of an existing service and preparation for future use can justify work without an immediate sale or an invented finished product.
OCE.1:4.2 - Record the Result
| Result position | Required content |
|---|---|
| use boundary | First user, receiving decision, horizon, and useful stop. |
| organization candidates | Candidate Systems or intended referents, supporting relations, any missing grounds, the selected organization and any material alternatives rejected. |
| intended contribution | Relevant product uses or other results, receivers, obligations, conditions, and unresolved value or performance questions; retain several where the decision depends on them. |
| changed Work and capability | Work families, current or intended status, supplied-result or contribution relations, and capability questions. |
| organization facts to recover | The particular questions still needed about assignment, authority, access, information use, transfer, service, coordination or participation. |
| affected Systems | A.1.CSD reference or bounded Systems, supported relations or modal paths, possible changed characteristics, gaps, and specialist returns. |
| authority | Subject, decision scope, window, basis, and evidence boundary; otherwise an authority blocker. |
| continuation | Local result, acceptance boundary and any remaining obligations, any further result needed and one observable reopen condition. |
OCE.1:4.3 - What Changes in Practice
The practitioner can explain which organization is being engineered, which product uses or other contributions justify its capability, and what its change project can finish. Downstream concepts answer to those contributions, Work and capability questions, affected Systems and actual authority. The focus remains bounded while retaining the products, providers and continuing obligations that can change the decision.
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.
| Candidate | Current disposition |
|---|---|
PumpWorks legal and operating company | Too broad for this organization-design decision; corporate and legal questions remain specialist returns. |
PumpWorks-EngineeringOrg | Selected actual organization System because the named Work and decision concern its cross-functional engineering contribution. |
| “AI release team” | Not an actual organization System; retain as a possible future concept label. |
| AI provider plus PumpWorks Engineering | A possible cross-boundary configuration, not an obtaining organization whole. Provider relations must be recovered directly. |
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 product-side SoIs remain the inspection-equipped pump installations: PumpWorks, contributing suppliers and receiving operators have agreed the supply and service responsibilities organizing their extended enterprises. Engineering is the creator being changed; a consultant hired to perform the same reorganization would keep that basis. 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
| Recurring bias | Likely drift | Repair |
|---|---|---|
| chart-boundary bias | A box becomes the changed organization. | Test System identity and the relations needed by the decision. |
| intervention-first bias | “Agile”, “AI-first”, or a target operating model becomes the contribution. | State the outside contribution and changed Work first. |
| employee-only bias | Only people inside the formal unit are treated as affected. | Trace supported relations to consequence-bearing Systems without inferring value or harm. |
| sponsor-authority bias | A visible sponsor is assumed to hold every decision right. | Recover subject, scope, window, basis, and evidence for authority. |
| capability-by-resource bias | A tool, hire, training event, or budget is reported as capability. | Name the Work family and conditions and obtain capability evidence. |
| whole-by-cooperation bias | Repeated cooperation with a provider creates one organization. | Keep Systems and their obtaining relations distinct. |
OCE.1:7 - Conformance Checklist
- The opening names a receiving decision, first user, horizon, and useful stop.
- The selected organization and its actual or proposed status are clear. Any material alternatives were distinguished on their own grounds.
- The contributions name their receivers, relevant product uses, conditions and obligations without claiming value or achievement by declaration.
- Work on a creator retains the product-side SoI and its extended-enterprise agreement basis; any claimed supplier distinction is grounded in the substantive supply, use, decision and acceptance boundaries.
- Several products remain distinguishable when their differences or shared demands change the decision, and local completion has a bounded acceptance basis.
- 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.
- Where the account relies on an “interface,” it identifies the boundary and the direct relations involved.
- Any exclusions, any further result needed, and an observable reopening condition are explicit.
OCE.1:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “The whole company is transforming.” | Name the decision and compare organization candidates at the smallest decision-changing grain. |
| “Our goal is to implement Team Topologies.” | Treat the topology as a possible concept; recover the contribution first. |
| “Employees are the stakeholders.” | Discover consequence-bearing Systems and keep interest, representation, protection, benefit, and harm separate. |
| “The executive asked for it, so authority is covered.” | Recover the authority relation for each relied-on decision scope. |
| “Training the team creates the capability.” | Treat training as a possible intervention and evaluate capability for the Work family separately. |
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.
Resolving disagreement about boundaries and evidence takes effort. Doing it early can prevent commitments and expenditure on the wrong target.
OCE.1:10 - Rationale
An organization-change decision concerns which relations may need to change or be established among the Systems and work under consideration. 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
Practice question. What is the smallest defensible focus for an organization-change decision before a target configuration is chosen? The selected answer combines an intended outside contribution with a supported organization boundary, decision authority and consequential outside relations. Its gain is a usable focus even when an executive label, provider boundary or affected population is misleading; it does not supply the strategy itself.
A serious alternative is the strategy-led framing in Galbraith’s Star Model, especially its Strategy and Implications sections. It starts from direction and criteria for design trade-offs, then coordinates structure, processes, rewards and people. This remains a substantive practitioner alternative although the text is historical; its current hosting date does not make it new research. Adopt deriving organization-design criteria from the contribution and direction. Adapt that framing in OCE.1:4.1, steps 1–4 and 7, by separately establishing the organization and authority to which the change applies. Reject treating a sponsor’s remit as sufficient evidence for every needed decision.
Compare the two on the same bounded task, with the same existing strategy, permitted records, participants and decision deadline. Either can identify the weekly evidenced release in the PumpWorks case. OCE.1:5 additionally makes the competing organization referents and separate safety/release authority inspectable before the concept is built. This is useful where those claims are unsettled; it costs explicit boundary and evidence work. A strategy-led inquiry is shorter when those premises are already clear, and an adequate result from it is reused under OCE.1:4. The added work is worthwhile when it can settle a consequential uncertainty about the focus. This comparison uses the stipulated PumpWorks conditions.
Albert’s 2023 online/2024 issue account supplies another serious starting point: choose among activity, decision-representation and legal-entity perspectives. Adopt their possible divergence and adapt them to the candidate-boundary questions in OCE.1:4.1, steps 3 and 5. A perspective-led focus can suffice for a known entity. For a provider-spanning proposal, the selected OCE answer adds the System question from A.1.SCR and consequence discovery from A.1.CSD, rather than inferring a whole from one representation. Albert’s point-of-view argument is not an exhaustive organization ontology or empirical validation of this method; requiring all three perspectives for every small use is rejected.
The work-design review by Fraccaroli, Zaniboni and Truxillo provides a consequential limit on a focus confined to output and structure: the work people perform and their outcomes also matter. Adapt that concern in OCE.1:4.1, steps 4 and 6, through separate Work and affected-System questions. The accessible abstract of Aust et al. (2023) supports outcome-specific caution, not a ranking of interventions. Neither source turns consequence discovery into proof of benefit or effectiveness; OCE.1:0 and OCE.1:5 keep those questions separate. No fuller Aust result is relied on here.
Reopen when a recurring case cannot be bounded this way, a credible alternative obtains an equally usable focus with less total work, or new evidence about organization identity, authority or consequences changes the focus or what the decision-maker can rely on.
OCE.1:12 - Relations
A.1.SCRgoverns System recognition when systemhood is load-bearing;A.1.CSDgoverns affected-System discovery. Use their results to define the organization and consequence boundary for OCE.1.A.1.STMsupplies the product-use-to-creator reasoning used in §4.1.1.A.15.6distinguishes the systems involved, temporary project work, plans, Methods, support and continuing development;A.10governs 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.2consumes the selected organization, contribution, Work questions, named organization-fact questions, affected-System gaps, and authority boundary.OCE.3receives the focus only with a grounded current account or explicit tolerated gap.- Use
OCE.10for target-organization working-culture questions arising from participation or adoption gaps; useOCE.17for the culture of OCE practice among practitioners.