eTOM names our five Sales motions in one sentence of prose, then refuses to model them — and that refusal is the finding

Acronyms used throughout, expanded once here: eTOM = Enhanced Telecom Operations Map, TM Forum's business process framework, published as document suite GB921. SIP = eTOM's "Strategy, Infrastructure and Product" process area (M.3050.1 abbreviation list — not Session Initiation Protocol). ICSP = Information and Communications Service Provider (M.3050.1 abbreviation list), eTOM's name for the kind of company it models. CRM = customer relationship management. PCF = APQC's Process Classification Framework.

The question

Verbatim, from the Notion Research Backlog:

"Does the TM Forum eTOM specification (fetched, not just inferred) contain a per-function motion catalog that would change the Organizational Platform's '2 of 10 true motions' verdict?"

Context: eTOM was the one framework in the SCOR / APQC PCF / BIZBOK / eTOM quartet never actually fetched. [[2026-08-17-gtm-motion-origins-industry-reference-models]] graded eTOM "no motion catalog" from Wikipedia plus two HTTP 403s and flagged that inference as its own unresolved item — "eTOM's negative is inferred, BIAN's is fetched." This brief closes that gap.

Answer, up front: no, and the verdict does not move. eTOM contains no per-function motion catalog at any level of the 2007 ITU-T edition — which was read in full — nor anywhere in the reachable portion of the 2025 TM Forum release. That second clause is weaker on purpose: the 2025 material I could fetch is a 48-page excerpt covering four Domains and never reaches the SIP area, which is where the most motion-adjacent process in the 2007 edition lives. See the source-tier table below and the first open follow-up. But the negative is now fetched, not inferred, and it is a much more interesting negative than expected — eTOM does not merely omit a motion catalog, it declares channel-agnosticism as an explicit design principle, enumerates our exact Sales motion set as illustrative prose inside one process description, and then models the act of choosing channels as a standing process element with three children. That last part is a genuine refinement, and it is new.

Source tiers (read this before quoting anything below)

The Tier-A route, for reuse: ITU-T republishes eTOM as the M.3050.x sub-series and ITU-T Recommendations are free. https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-M.3050.2-200703-I!!PDF-E&type=items returns the 208-page PDF unauthenticated, no headers beyond a normal User-Agent. Edition IDs come from scraping https://www.itu.int/rec/T-REC-M.3050.2/en. Caveat that limits Tier A: M.3050.x froze at eTOM Release 7 in 2007. It is nineteen years stale. Tier B is what keeps the finding current.

What we already know (from the vault)

• The eTOM row in the parent brief was explicitly marked as an inference from absence. [[2026-08-17-gtm-motion-origins-industry-reference-models]] §3.1: "Read status: gated… Motion catalog: no. Channel (phone / web / self-service) appears inside CRM and Operations as detail, never as an orthogonal selection dimension… Caveat: this is an inference from absence across secondary sources plus two blocked primary pages, not a fetched negative." That brief's own verification banner lists "eTOM's negative is inferred, BIAN's is fetched" as outstanding item 5.
• The "2 of 10" verdict is currently quarantined, not adopted. spec/00-template-decisions.md (2026-08-17) records the ruling: the motions-origins brief "is quarantined (failed verification) and nothing below relies on it." D-1 chose the BIZBOK "configured-as" block (location / systems / org shape) over the SCOR-derived axis: substitutable | sub_function + variants: proposal, on the grounds that "locking a template on a quarantined brief's 2-of-10 verdict would build on the one source we agreed not to quote." The axis: field is deferred, not rejected — explicitly held open pending re-verification.
• The tree has since shipped the configured-as block and started conceding the point in prose. 03-motions/fn-it-security.md now reads: "It is a lane run alongside IT's other motions rather than an alternative to them." That is the substitutability test failing, written into the artifact by hand, one node at a time, without a schema field to carry it.
• The two sibling verifications both came back holding. [[2026-08-21-apqc-pcf-80-channel-motion-leaves]] confirmed PCF 8.0 left 3.5.6 / 3.5.7 / 3.5.8 (physical-outlet, field, digital sales) childless — APQC named our exact motion axis across two major versions and eighteen months and still declined to decompose it. [[2026-08-22-scor-digital-standard-level2-process-types]] killed the specific SCOR codes the parent brief leaned on but confirmed the structural argument: decomposition at Level 1, substitutable choice at Level 2.
• Reference-model coverage of our client verticals is thin and known-thin. [[2026-08-22-cstore-fuel-retail-reference-models]] found no process model at all for c-store/fuel retail from any industry body. Telecom is the opposite case — a lavishly modelled vertical — which is exactly why a fetched eTOM negative carries weight.

What the web says — the fetched primary text

1. Channel-agnosticism is a stated design principle, not an omission

M.3050.1 (03/2007), terminology entry 3.6 end-to-end process flow:

"The end-to-end customer processes recognized in the eTOM framework are generic sequences of activities that need to occur in the enterprise to achieve desired results (i.e., they are not specific to a particular ICSP business, product, channel or technology)."

And M.3050.2 (03/2007) §7.1, the Extended description of 1.1.1 Customer relationship management:

"CRM makes no distinction between manual or automated interactions with customers, nor whether interactions are by paper, telephone, web-based transactions or some other alternative arrangement."

This is the difference between "eTOM happens not to have a motion catalog" and "eTOM ruled channel out of the model on purpose." It is the latter. The framework's generality claim — M.3050.1: "The eTOM framework is defined as generically as possible so that it is independent of organization, technology and service" — is purchased precisely by discarding the axis our tree runs on.

2. eTOM decomposes Sales by pipeline stage, not by channel — a third axis we don't have

1.1.1.4 Selling (M.3050.2 §7.1) has five level-3 children:

Every one is mandatory and sequential. This is a funnel, not a catalog. It fails selectivity outright — no company runs a proper subset.

And the tell sits inside the first child. 1.1.1.4.1 Manage prospect, Extended description, final sentence:

"Prospects are assigned to the appropriate sales channel."

Channel exists in eTOM as a routing attribute of a prospect record. It is data, not structure.

Same pattern in the current release. Tier B, 1.3.5 Customer Interaction Management (Hierarchy Level 2), Extended description:

"Customer interactions can span over multiple channels (such as: phone calls, web self service and devices.) each party involved in the interaction has a role that mandates its credentials."

And 1.3.5.8 Authenticate User (Level 3):

"In self service channels the user may need to login in order to authenticate himself, in other channels the user my need to answer identity verification questions." (sic)

Four occurrences of "channel" in the whole 48-page v24.0 excerpt, all four attributive. Eighteen years, one full restructure into Domains, and channel is still a property of an interaction.

3. The one place eTOM does enumerate a channel catalog — and it is prose, not nodes

1.1.1.1.7 Support selling (M.3050.2 §7.1, under CRM – Support and readiness), Extended description:

"Support selling works in concert with all other marketing processes to determine the appropriate selling route or channel, and the required selling method and mechanism for specific market segments and channels, by product or product family, e.g., face-to-face contact, telemarketing, etc."

"…Channels may be retail storefronts, e.g., a third-party retailer or an enterprise's own storefront, various web sites or ISPs, B2B marketplaces or direct relationships with external parties, distributors for that product family, etc."

That single sentence names, in illustrative prose, five of our five Sales motions:

This is the third independent industry body to name our Sales motion set and then decline to model it — APQC named it and left the leaves childless, SCOR demoted retail order handling to the un-standardized Level 4, eTOM put it in an "e.g." clause. Three bodies, three different refusal mechanisms, same refusal.

(1.1.1.4.1 also carries "assigned to the appropriate sales channel" but names no channels. The Support-selling passage is the only enumeration found in 208 pages.)

4. The genuinely new contribution: eTOM models channel selection as a process with an owner

M.3050.2 §8.1.6, under SIP → Marketing and offer management:

1.2.1.6 Sales development — "Sales development processes develop the sales support and response for new and existing products… As an aspect of this, sales development processes define channels for selling the enterprise's products. It develops or ensures development of channel ability to sell and support products, including negotiating for the specific channel, defining or updating the account management process, developing pricing for a specific channel, etc."

Three level-3 children:

eTOM's answer to "where do the motions live?" is: they don't live in the model, because which ones you run is an output of a standing process that the model does contain. Scan → propose → build, with a named owner and its own performance indicators per channel.

5. Motion-shaped concepts get glossary definitions and zero process nodes

M.3050.1 defines, precisely, in the terminology section:

3.19 outsourcing: "Outsourcing is when an enterprise contracts out one or more of its internal processes and/or functions to an outside company. Outsourcing moves enterprise resources to an outside enterprise and keeping a retained capability to manage the relationship with the outsourced processes."

3.20 out-tasking: "Out-tasking is when an enterprise contracts with an outside enterprise to provide a process, function or capability without transfer of resource."

These are textbook motions — mutually substitutable ways of producing the same functional outcome, and a real company runs a proper subset. eTOM defines them with more care than most consultancies and then never instantiates them. Across M.3050.2's 208 pages the strings outsourc* / out-task* / out tasking occur 53 times, and every occurrence is a conditional on some other process — "when these have been outsourced," "the service provider has outsourced specific activities to suppliers/partners." Never a node.

6. eTOM treats its own back office as a stub — three of our ten functions get no decomposition below level 2

Level-3 depth in M.3050.2 exists for the four Operations horizontals (CRM, Service Management & Operations, Resource Management & Operations, Supplier/Partner Relationship Management) and for the SIP area. Enterprise management (§9) is level-2 only, with exactly one exception in the entire clause: 1.3.2.6 Revenue assurance management, a child of Enterprise risk management, which gets three level-3 children (1.3.2.6.1 Manage revenue assurance policy framework · 1.3.2.6.2 Manage revenue assurance operations · 1.3.2.6.3 Support revenue assurance operations) and, under .2, seven level-4 grandchildren. Nothing else in §9 goes below level 2. The other six groupings — Strategic and enterprise planning, Enterprise effectiveness management, Knowledge and research management, Financial and asset management, Stakeholder and external relations management, Human resources management — stop dead at level 2.

1.3.7 Human resources management is representative: five level-2 children and stop. HR policies and practices · Organization development · Workforce strategy · Workforce development · Employee and labour relations management. No level 3. Those five are do-all sub-functions by inspection — the same shape our FN.HR.* nodes have — but eTOM never took them deep enough to be evidence either way.

So the coverage picture, stated precisely rather than as a headline count:

• Three of our functions — Finance, HR, Legal & Risk — sit entirely inside eTOM's level-2-only Enterprise management area. On these, eTOM is silent, not confirming. Do not cite it as corroboration for the back office.
• The remaining seven get level-3 depth somewhere, but on eTOM's own axes — the customer / service / resource / supplier-partner layering crossed with the fulfilment / assurance / billing verticals — which do not align with our function boundaries. Sales and Service both fall inside CRM; Operations and IT are split across Service Management & Operations and Resource Management & Operations; Marketing and Product share the SIP area's Marketing and offer management. So eTOM has depth there, but it is depth on a different cut, which is why only the Sales evidence in §2–§4 above transfers cleanly.

Either way, of the eight functions whose motion status the parent brief graded as contested (everything except Sales and Service), eTOM supplies usable evidence on none of them.

Convergences and contradictions

• Convergence, and it is the strongest one in the sweep. SCOR, APQC PCF and eTOM were built by three unrelated bodies for three unrelated industries across three decades, and all three separate decomposition from configuration and refuse to standardize the configuration layer. SCOR keeps a Level-2 choice layer but re-cut it to customer-type and pushed retail order handling to an un-standardized Level 4 ([[2026-08-22-scor-digital-standard-level2-process-types]]). APQC named the channel leaves and left them childless across two major versions ([[2026-08-21-apqc-pcf-80-channel-motion-leaves]]). eTOM ruled channel out by design and put the enumeration in an "e.g." clause. Nobody with a standards committee has been willing to publish a motion catalog. That is either a warning or a moat, and which one it is is now the live commercial question.
• A refinement, not a contradiction, on the parent brief's characterization. The parent said channel "appears inside CRM and Operations as detail." True, but it undersells the case: it is not that eTOM buried channel, it is that eTOM declared channel out of scope in a definition, then re-admitted it as an attribute and as the subject of a meta-process. That is a more deliberate architecture than "detail," and it is the part that ports.
• A contradiction with our own artifact. eTOM decomposes 1.1.1.4 Selling into pipeline stages while treating channel as a prospect attribute. Our tree does the exact inverse — decomposes Sales into channels and carries no stage axis at all. Both cannot be the natural decomposition of Sales. Since eTOM and our tree disagree about what Sales is made of, and both are internally coherent, the honest reading is that Sales admits at least three orthogonal cuts — stage, channel, and customer type (SCOR's O1/O2/O3) — and the Organizational Platform has picked one and modelled it as if it were the only one.

Synthesis for RDCO

The verdict holds and the evidence base under it changed character. The "2 of 10 true motions" finding is not overturned by eTOM. It is not confirmed by eTOM either, on any of the eight functions the parent brief graded as contested: three of them (Finance, HR, Legal & Risk) sit in an area eTOM never decomposes below level 2, and the other five get depth only on eTOM's own customer/service/resource/supplier cut, which does not line up with our function boundaries. What eTOM does is upgrade the parent brief's outstanding item 5 from an inference to a fetched negative, and it does so with a stronger negative than the row it replaces: a design principle stated in a definition ("not specific to a particular ICSP business, product, channel or technology"), reaffirmed in the CRM scope note ("CRM makes no distinction… whether interactions are by paper, telephone, web-based transactions"), and still holding in a © TM Forum 2025 document. The row in the parent brief's scorecard should read "No — fetched, and by declared design" rather than "No — inferred." Nothing else in that brief moves on this evidence, and the remaining outstanding items (the 16 unsourced [PRACTITIONER] entries, the asymmetric two-part test, the Marketing downgrade) are untouched.

The thing worth actually building is 1.2.1.6. Our Organizational Map records "which motions run" as a static fact discovered during mapping. eTOM's structure implies that is a category error: which channels a company runs is the output of a process the company operates continuously — monitor the environment, propose changes, build the new channel — with defined targets and performance indicators per channel and a named owner. If that is right, then every client map we produce is a snapshot of a variable somebody in the org is paid to move, and the map does not currently record who that person is. There is no FN.SALES.* node and no ROLE.SALES.* seat corresponding to channel development, and the SIP-area placement is itself informative: eTOM puts channel development under Marketing and offer management, not under Sales. That is a testable claim about a real client's org chart — in a mapped organization, does anyone own channel development, and do they sit in Sales or in Marketing? Kwik Trip's FN.MARKETING was one of the three departments that could not be assigned to a motion. This is a candidate explanation for why: it may be running a motion-development process that our tree has no slot for.

On the schema decision that is actually pending. D-1 deferred axis: pending re-verification of the quarantined brief, and this brief does not re-verify it — it verifies one row of its scorecard. But it does supply a cheaper interim move. fn-it-security.md already says in prose that Security "is a lane run alongside IT's other motions rather than an alternative to them." That sentence is the axis: field, written by hand, unqueryable, and about to be repeated 27 more times in inconsistent phrasing as the remaining pages fill. Three reference models now independently distinguish the two shapes. Adding one optional boolean-ish field — call it what you like, axis: alternative | lane — costs a template line, makes the distinction machine-checkable, and does not commit to the 2-of-10 count or to any particular per-node assignment. The count is what failed verification; the distinction is what three primaries corroborate. Those can be separated, and separating them lets the artifact stop hand-rolling the concept in body copy.

On telco transfer, since the question asked. eTOM is vertical-specific in vocabulary (ICSP, service provider, resource/service/product layering, QoS/SLA) but the parts relevant here are not. The channel-agnosticism principle, the stage-vs-channel decomposition of Selling, and the channel-development meta-process are all stated in industry-neutral terms and none depend on anything telecom-specific. The limiting factor is not the vertical, it is coverage: eTOM models what a service provider does to customers, services, resources and suppliers in exhaustive depth, and treats its own back office as a stub. Cite it for Sales and Service structure. Do not cite it for Finance, HR, Legal & Risk, Product or IT.

Why this is in the vault

It closes outstanding item 5 on the verification banner of [[2026-08-17-gtm-motion-origins-industry-reference-models]] — the one open item that named eTOM specifically — and it does so before the 36-motion vocabulary locks in organizational-platform/03-motions/. It also puts a concrete, cheap alternative in front of the deferred D-1 axis: decision in spec/00-template-decisions.md, and identifies a specific missing node/seat (channel development, 1.2.1.6) that would be testable on the next client map.

Open follow-ups

• Does GB921 v24/v25 still contain a Sales development equivalent, and did the 2007 → 2025 restructure into Domains move channel development out of Marketing? The v24 conformance excerpt covers only Product/Customer/Service/Business Partner domains and does not reach the SIP area. Resolving this needs the full v24 or v25 guidebook, which means finding the tmforum.org/wp-content/ filename for it — the asset path is ungated, only the listing 403s.
• In a mapped client organization, does anyone actually own channel development as a job, and do they sit in Sales or in Marketing? Testable against the Kwik Trip org map, and it bears directly on why FN.MARKETING resisted motion assignment.
• eTOM decomposes Sales by pipeline stage; the Organizational Platform decomposes it by channel; SCOR DS decomposes by customer type. Is there a reference model anywhere that carries two of these axes simultaneously as separate, named dimensions — and if not, is single-axis decomposition a universal constraint of process-framework tooling or just a convention?

Related

• [[2026-08-17-gtm-motion-origins-industry-reference-models]]
• [[2026-08-21-apqc-pcf-80-channel-motion-leaves]]
• [[2026-08-22-scor-digital-standard-level2-process-types]]
• [[2026-08-17-apqc-pcf-function-motion-mapping]]
• [[2026-08-17-bizbok-operating-model-function-motion-mapping]]
• [[2026-08-22-bizbok-object-focus-invariance-real-estate]]
• [[2026-08-22-cstore-fuel-retail-reference-models]]

Sources

Tier A — full primary documents, fetched and read

• ITU-T Recommendation M.3050.1 (03/2007), Enhanced Telecom Operations Map (eTOM) – The business process framework (= TMF GB921 Release 7.0). https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-M.3050.1-200703-I!!PDF-E&type=items
• ITU-T Recommendation M.3050.2 (03/2007), Enhanced Telecom Operations Map (eTOM) – Process decompositions and descriptions, 208 pp (= TMF GB921 Addendum D Release 7.0). https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-M.3050.2-200703-I!!PDF-E&type=items
• Edition index scraped from https://www.itu.int/rec/T-REC-M.3050.2/en

Tier B — primary excerpt, current release

• GB921 Process Decompositions v24.0 — Business Process Framework (eTOM) Conformance Certification, JioChargeIT Additional Processes Self-Assessment Mapping Template, © TM Forum 2025, 48 pp. https://www.tmforum.org/wp-content/uploads/2025/06/eTOM-24.0_Conformance_Mapping_Template-JioChargeIT-AdditionalProcesses-VFRF-1.pdf

Tier C — listing metadata only, not read

• TM Forum resource listings for GB921 v21.0.5 / v24.0 / v25.0 / v25.5 / v26.0. https://www.tmforum.org/resources/suite/gb921-business-process-framework-etom-suite-v25-0/

Blocked (flagged, not retried)

• https://www.tmforum.org/resources/guidebook/gb921-customer-process-decompositions-v24-0-0 — HTTP 403 to curl with browser User-Agent

Vault

• [[2026-08-17-gtm-motion-origins-industry-reference-models]] — ~/rdco-vault/06-reference/research/2026-08-17-gtm-motion-origins-industry-reference-models.md
• [[2026-08-21-apqc-pcf-80-channel-motion-leaves]] — ~/rdco-vault/06-reference/research/2026-08-21-apqc-pcf-80-channel-motion-leaves.md
• [[2026-08-22-scor-digital-standard-level2-process-types]] — ~/rdco-vault/06-reference/research/2026-08-22-scor-digital-standard-level2-process-types.md
• [[2026-08-17-apqc-pcf-function-motion-mapping]] — ~/rdco-vault/06-reference/research/2026-08-17-apqc-pcf-function-motion-mapping.md
• [[2026-08-17-bizbok-operating-model-function-motion-mapping]] — ~/rdco-vault/06-reference/research/2026-08-17-bizbok-operating-model-function-motion-mapping.md
• [[2026-08-22-bizbok-object-focus-invariance-real-estate]] — ~/rdco-vault/06-reference/research/2026-08-22-bizbok-object-focus-invariance-real-estate.md
• [[2026-08-22-cstore-fuel-retail-reference-models]] — ~/rdco-vault/06-reference/research/2026-08-22-cstore-fuel-retail-reference-models.md
• Organizational Platform artifacts (not vault, phData project): ~/Documents/phdata-projects/organizational-intelligence/spec/00-template-decisions.md, ~/Documents/phdata-projects/organizational-intelligence/organizational-platform/03-motions/