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

Name used here	Meaning
organization concept	A possible organization configuration described far enough to answer one decision. Its Work and relations remain possible until realized and observed.
concept alternative	A materially different way to satisfy or revise the intended contribution, including repairing the incumbent configuration.
selected structure	Constituents and relations selected for a comparison use, such as contribution, Work, assignment, authority, resource-access, information-use, service, coordination, or capability structure.
view	A description produced under a viewpoint. Project, process and case viewpoints ask different questions; charts, maps or models can present the resulting descriptions.
bounded generation move	The OCE.3 move that varies decision-bearing relations through incumbent repair, changed specialization/contribution/authority, and boundary/provider or human–AI alternatives, then stops at a small serious set.
participant contribution	Evidence or a proposed alternative supplied by people or other Agents whose knowledge of actual Work, burden, authority, safety, service or providers can change the set or comparison. Participation is not consensus or veto.
concept assumption	A claim that must hold for feasibility or worth but is not established.
coexistence and change burden	The demands and risks of changing while continuing Work shares the same conditions. These include learning and migration effort, provider and governance demands, service interruption, opportunity costs, and the effort or risk of reversal.
organization-concept comparison	Alternatives, criteria, evidence, uncertainty, consequences, decision or stop, and reopen conditions. It is not a target organization by itself.

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

Force	Tension
Diversity	Serious alternatives reveal assumptions, while decorative variants waste attention.
Comparability	Shared concerns aid comparison, while concepts allocate contributions and burden through unlike structures.
Participation	Actual Work knowledge can change alternatives, while participation can be burdensome, unsafe, or outside authority.
Novelty and continuity	New relations may unlock capability, while incumbent relations carry memory, authority, and service continuity.
Product/organization alignment	Mirroring can reduce some coordination, while one-to-one correspondence is contingent.
Decision speed	A bounded selection is useful, while scalar scores create false precision.

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

Bind the comparison. Name organization, contribution, decision authority, horizon, current account, non-negotiables, and tolerated or blocking gaps.
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.
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.
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.
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.
Describe selected structures. Name possible constituents and relations. Use charts, maps, scenarios, prototypes, or mathematical lenses only for declared questions and state their losses.
Expose feasibility assumptions. State required capabilities, authority, resource access, provider commitments, product/service claims, participation conditions, and continuing-service constraints.
Compare contributions and burdens. Compare intended contribution, coordination, resilience, affected-System consequences, participant burden, service interruption, reversibility, and uncertainty.
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.
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

Result position	Required content
comparison boundary	Organization, contribution, decision, authority, horizon, non-negotiables, and tolerated/blocked gaps.
generation account	Domain generation branches used, relation changed by each alternative, stop rule, discarded decorative variants, and any conditional `C.18` use.
participant contribution	Participants sought, contribution used, missing voice, protection/burden limit, and effect on alternatives or comparison.
concept structures	Possible supplied-result, Work, eligibility/assignment, authority, access, information-use, service, coordination, capability, and provider relations.
assumptions	Capability, authority, access, commitment, product/service, participation, and service-continuity claims with status.
comparison	Contribution, coordination, resilience, affected Systems, participation, coexistence, burden, reversibility, and uncertainty.
specialist returns	Needed result, owning practice, scope, and effect on the comparison.
decision or stop	Selection, narrowed question, probe, or stop; basis, alternatives, ties, and authority.
continuation	Downstream constraints and evidence that reopens the comparison.

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.

Concept	Possible relation changes	Main promise	Main burden and uncertainty
`OC-PW-FUNCTIONAL-REPAIR`	Retain functional assignments; establish named electrical-evidence supply and use, safety acceptance, release decision, rig-access priority, and field-service information-return relations	Preserves specialist depth, current authority, and low migration burden	Coordination load may remain high; weekly recurrence is unproved
`OC-PW-STREAM-ENABLING`	Create a stream-aligned release configuration with explicit Safety and platform contributions while retaining functional capability homes	Shortens some evidence and decision paths	Requires new assignments, authority, access, and capability; scarce specialists may be overloaded
`OC-PW-PROVIDER-HYBRID`	Expand provider model-operation and evidence-preparation contributions while PumpWorks retains safety, release, exception, recovery, and service decisions	May increase specialist capacity	Commitment, access, assurance, recovery, knowledge retention, and authority remain unresolved

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

Recurring bias	Likely drift	Repair
topology prestige	A fashionable form becomes the only serious concept.	Generate alternatives by changing named relations, including incumbent repair.
diagram diversity	Several views count as several concepts.	Compare underlying possible relations.
expert-only design	Designer knowledge excludes actual Work and burden.	Obtain bounded participant contributions and record missing voices.
mirroring determinism	Product architecture dictates organization structure one-for-one.	Test named correspondences and deliberate non-mirroring.
resource invisibility	A concept moves scarce capability or burden without showing it.	Compare participants, resource windows, and transferred burden.
selection-as-reality	The chosen concept is reported as the new organization.	Preserve possible status until realization and observation.

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

Anti-pattern	Repair
“Choose between functional, matrix, and product.”	Name the contribution, authority, access, service, coordination, capability, and burden relations that differ.
“Team Topologies is the target architecture.”	Use its concepts for one candidate and compare unlike alternatives.
“Organization should mirror product architecture.”	State the proposed correspondence and test exceptions and burden.
“The provider owns the AI part.”	Recover contribution, commitment, access, assurance, recovery, responsibility, and authority separately.
“The workshop generated options, so participation is covered.”	Show whose knowledge changed which alternative and whose absence remains material.
“The highest weighted score wins.”	Preserve non-negotiables, uncertainty, incompatible measures, and authority.

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

Source line	Retained contribution	Use boundary
Current FPF `A.22`, `C.17`, `C.18`, `C.11`, `C.30`, and `C.32.CONWAY`	Selected structures; characterization of existing candidates; conditional open-ended exploration; bounded choice; architecture and mirroring distinctions.	Use these patterns for their stated questions; generate the organization-specific alternatives and participant/burden comparison here.
Conway (1968) and Colfer & Baldwin (2016)	Communication and product structures can constrain one another; mirroring has exceptions.	Test the correspondence for the chosen product and organization; allow exceptions and compare alternatives.
Skelton and Pais, `Team Topologies` (2019; 2025)	Stream-aligned, enabling, platform, subsystem, and interaction concepts can generate candidates.	The line is software-heavy. Establish authority, capability and effects separately for the local case.
Schulze-Meeßen and Hamborg, participatory work-design representations	Participant-facing prototypes can improve some recognition and acceptance.	Keep the study’s recognition and acceptance results separate from evidence about organization relations and participants’ contributions.
Heusinkveld and Smits, organization-design knowledge perspectives	Design ideas should be examined through plural development and translation perspectives.	Use the perspectives to examine design knowledge, then make the local concept decision under the applicable authority.

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.