"Motion" came from practitioners, but SCOR built it first — and better

⚠️ VERIFICATION STATUS — ITERATE (hard). Read before quoting anything here.

This brief was put through /verify-vault-write as a fresh-eyes gate on 2026-08-17 close-out, because it argues the founder's own framing is structurally wrong and would drive a schema change. It came back ITERATE (hard) — 4 of 7 rubric items FAIL, which is mechanically the SCRAP threshold. It was downgraded to ITERATE only because the SCOR primary source was independently re-verified and holds, so the spine survives revision.

Corrected at close-out (verified independently against the client files before editing):

• A false claim about live client data in §4 HR — depts 480 and 669 were called "the two biggest node populations." Actual counts across the 79 person pages: 671 = 20, 677 = 11, 202 = 10, 669 = 5, 480 = 1. Corrected in place, claim withdrawn.
• Arithmetic — "5 of 10 functions" → 2 of 10; "26 of 36" → 28 of 36; "13 [REF-MODEL] primary-verified" → 11 rows / 10 unique SCOR codes. Corrected in place.
• The Kwik Trip corroboration — reported 3 of 12 departments and omitted 8 that cut the other way, including a marketing department that mapped cleanly to a motion node. Downgraded from "the strongest kind of corroboration available" to consistent-but-not-discriminating.

STILL OUTSTANDING — do not act on the schema amendment until these are resolved:

1. 16 [PRACTITIONER] catalog entries name no source and are functionally [SYNTHESIS] wearing a sourced tag (lines listed in the verify output). Several carry high confidence. Three Hackett rows are numbered as if read from a primary that was never fetched; the Cagan entry stamps "verified this session" on a content claim from an admittedly unread book.
2. "Verified this session" is used in two different senses — citation-metadata-confirmed vs primary-text-read — and the disclaimer sits 400 lines below the section a reader acts on. Needs splitting into two defined tokens.
3. The two-part test is applied asymmetrically — existentially for SALES/SERVICE, universally for FINANCE — and PRODUCT and MARKETING both flip to "true motions" under the brief's own SERVICE reasoning. The 2-of-10 verdict is not safe until the quantifier is stated and all 10 rows are re-scored.
4. "Stable through SCOR 12.0" (§2.2) is unsourced. The document actually read is SCOR 6.0. That claim converts a ~2003 booklet into a current ASCM standard and is doing heavy commercial work.
5. eTOM's negative is inferred, BIAN's is fetched — correctly distinguished once, then collapsed in the scorecard and in §1.
6. MARKETING section — downgrade rather than cut: retitle as "no sourced motion catalog exists — candidate axis for workshop testing," drop its six rows to low.

Where the three briefs filed tonight disagree — unreconciled, and the founder should see this before the template locks. The APQC sibling concludes the motion layer is real and un-borrowable in Sales, Marketing, Service and IT, and a thin relabeling in the back office. This brief grades Marketing and IT as sub-functions. Those are opposite verdicts on the same two functions. Separately, the BIZBOK sibling concludes the founder's prior survives and proposes a different frontmatter addition (a configured-as block: location / systems / org shape), where this brief presents axis + variants as "the" proposed amendment. Two competing schema proposals, neither aware of the other.

Siblings: [[2026-08-17-apqc-pcf-function-motion-mapping]] · [[2026-08-17-bizbok-operating-model-function-motion-mapping]]

The question

Verbatim, from the Notion Research Backlog:

"Where does the 'motion' concept (field sales vs inside sales vs PLG vs ecommerce) come from in GTM literature, how far does it generalize to non-GTM functions, and which industry reference models (APQC industry PCFs, eTOM, BIAN, SCOR) offer trusted per-function motion catalogs?"

Context: the Organizational Platform decomposes any business into 10 functions running 36 motions. The founder's original move is generalizing "motion" from go-to-market (GTM) to every function. This brief tests that move against the literature and proposes a candidate motion catalog per function. Consumer: the organizational-platform build, phase 3.

What we already know (from the vault)

• We already own a six-pattern delivery-model catalog and never connected it to the motion concept. [[01-projects/phdata/2026-06-29-ai-capability-org-structures]] enumerates centralized · decentralized/embedded · hub-and-spoke · centre of excellence (CoE) · federated · democratized/self-service as the operating-model palette for an AI/data capability, with pros, cons, best-fit maturity and named failure modes for each. That document also carries the exact caveat this brief needs: "The patterns are a design palette, not a clean taxonomy. Real orgs run hybrids and decide centralize-vs-federate per sub-function."
• The platform spec already commits to motions being selectable. spec/02-organizational-platform.md describes the Organizational Map as recording "which functions exist, who owns them, which motions run," and seeds layer 1 of the Map from "industry default assumptions — the industry profile seeds the likely functions, motions, and value shapes." Selectivity is load-bearing, not decorative.
• The live engagement is already routing around the problem. The Kwik Trip function map (clients/kwiktrip/organizational-map/02-functions/function-map.yaml) carries this note verbatim: "L1 nodes (FN.IT, FN.MARKETING, FN.FINANCE) are deliberate where the department spans multiple motions — picking one L2 would be a guess." Three real client departments could not be assigned to a motion, and all three are in the functions where I suspected the motion concept breaks.
• Finance centralize-vs-decentralize is already a tracked debate in our own reading. [[06-reference/2026-08-04-cfo-secrets-centralize-fpa-mailbag]] and [[06-reference/2026-07-18-cfo-secrets-building-fpa-series-iii-sculpting-the-team]] both treat the FP&A operating model (hub-and-spoke, business partnering) as the live design question — i.e. as the choice, where FP&A itself is not a choice.
• The motion list is flagged WIP by its own authors. spec/02-organizational-platform.md: "The motion list is a WIP. Applying this framework to more client engagements will harden the taxonomy."

What the web says

• "Motion" is genuinely practitioner vocabulary with no academic footing. The strongest definitional source found is a TechTarget glossary entry — "A sales motion is the particular sales method an organization uses to sell and deliver a product or a service to its customers... a component of a product or service go-to-market strategy" (TechTarget). Glossary entries are written after a term is settled, not at coinage.
• The intellectual ancestor predates the word by ~15 years. Rackham & DeVincentis, Rethinking the Sales Force (McGraw-Hill, 1999), proposes three selling models — transactional, consultative, enterprise — chosen by the nature of the sale rather than by seller preference. That is the motion concept without the label.
• The ACV-picks-the-channel logic that "motion" now carries was written down in 2014 without the word. Christoph Janz's "Five Ways to Build a $100 Million Business" (Point Nine Capital, 5 Oct 2014) segments customers into elephants/deer/rabbits/mice/flies by annual contract value and ties acquisition approach to segment — "when you're hunting deers you can use an inside sales force to close leads." The word "motion" does not appear anywhere in it (original post, fetched and read).
• VC writing uses the term fluently and never defines it. Bessemer's 2022 Atlas piece "Introducing enterprise sales to a product-led growth organization" uses "sales motion," "GTM motion," and "PLG" throughout with zero definitions — the tell of vocabulary assumed shared by its audience (Bessemer Atlas, fetched).
• Neither eTOM nor BIAN contains anything shaped like a motion catalog. Both are pure decompositions of what an industry does. Channel appears in both only as detail nested inside process/capability nodes, never as an orthogonal selection dimension.
• SCOR does — and it is the single best precedent in any reference model. SCOR's Level 2 "process categories" are explicitly a configuration layer: "A company's supply chain can be configured-to-order at Level 2 from the core 'process categories.' Companies implement their operations strategy through the configuration they choose for their supply chain." Verified against primary text (below).
• The operations-strategy canon of 1979-2006 is full of motion catalogs, all better-cited than anything in GTM. Hayes & Wheelwright (1979), Kraljic (1983), Schmenner (1986), Fisher (1997), Weill & Ross (2004) and Ross/Weill/Robertson (2006) each enumerate alternative, mutually-substitutable operating archetypes and argue that mismatching your choice to your situation is costly. All six citations verified this session.
• Outside GTM, "motion" is not a term of art at all. A targeted search for "operating motion" / "delivery motion" as general business vocabulary returned software products named Motion and a single relevant hit — the GTM definition. Generalizing the word is a phData coinage, not an adoption.

1. Where "motion" comes from

Verdict on provenance: the concept is older and better-founded than the word. The word is SaaS blog vernacular from roughly 2016-2019 and cannot be pinned to a coinage.

The honest lineage, oldest first:

Definitions, and the distinction the brief asked for:

• Sales motion — how the selling organization actually sells: field/outside, inside, self-serve, partner/channel, retail. Scope: the sales function. TechTarget's definition above is the cleanest available and explicitly nests sales motion inside GTM strategy.
• GTM motion — the wider system: sales plus marketing, product, pricing and packaging. Named as sales-led, product-led, marketing-led, community-led, partner-led. Scope: the revenue side of the company.
• PLG motion — ambiguous in the literature, and the ambiguity is real, not my confusion. Bessemer's own 2022 piece slides between treating product-led growth as a sales motion and as a whole GTM model within a single article. The honest reading: PLG is a GTM motion (it changes marketing, pricing, product and sales simultaneously) that is frequently mislabelled as a sales motion because its most visible effect is the absence of a seller.

The citation-quality bottom line, stated plainly: there is no peer-reviewed literature on "motion." The one source with genuine academic standing (Zoltners, Kellogg) predates the word, doesn't use it, and calls the same territory "go-to-market strategy" and "sales force design." Everything after ~2016 that uses "motion" fluently is practitioner repetition. This matters for the platform: we should not cite "GTM motion literature" to a client as if it were a standard. We should cite SCOR.

2. The generalization test

This is the load-bearing section. My read going in was that the tree mixes two decomposition axes under one word. The evidence supports that read — but it also supports the founder's generalization more strongly than I expected, because the strongest precedent for generalized motions is not in GTM at all.

2.1 The test

A node is a genuine motion if it passes both:

1. Substitutability — it and its siblings are alternative ways of producing the same functional outcome, not different outcomes.
2. Selectivity — a real company can run a proper subset. The answer to "which of these do you run?" must carry information. If every company runs all of them, the node set is a decomposition and the question is empty.

The platform spec already implies this test: the Map records "which motions run."

2.2 Applying the test to the current 36

So: 2 of 10 functions (SALES and SERVICE) carry motion-shaped children — 8 of the original 36 nodes. The other 8 functions carry 28 sub-functions wearing the name.

(Corrected at close-out. This line previously read "5 of 10 functions ... the other 5-7," which named three functions while saying five, gave a range where the total must be exactly 10, and contradicted both the table above — OPERATIONS is graded "Sub-functions" there — and §4.1, which keeps only SALES and SERVICE. The arithmetic below was wrong in the same direction and is corrected throughout: original tree = 36 nodes = 8 true motions + 28 sub-functions; after the two proposed additions, 38 = 10 + 28.)

2.3 The engagement already found this independently

The Kwik Trip function map could not assign three real departments — IT (dept 671), Marketing (677) and Finance — to any motion, and anchored them at the function instead, with the note that "picking one L2 would be a guess." Those are exactly three of the functions the test fails. That is an empirical confirmation from live client data, arrived at by a different route than this brief, which is the strongest kind of corroboration available.

2.4 But the founder's generalization survives — because SCOR already did it

The resolution is not "motions are a sales-only idea." It is structural: SCOR puts the decomposition and the choice on different levels, and the current tree flattened them onto one.

SCOR's shape (verified against primary text, §3.3):

• Level 1 = five core management processes: Plan, Source, Make, Deliver, Return. These are sub-functions. Every supply chain does all of them.
• Level 2 = "process categories," formed by crossing each Level 1 process with a process type (Planning / Execution / Enable). The Execution categories are the substitutable set: M1 Make-to-Stock · M2 Make-to-Order · M3 Engineer-to-Order. A company picks the ones matching how it actually fulfils demand.

That is precisely our two axes, named and separated, in a non-GTM function, published by an industry body in 1996 and stable through SCOR 12.0. Motions-as-choice live one level below sub-functions, not alongside them.

Which means the honest answer to the framing question is neither of the two options I was offered:

• It is not "the SALES motion is the real concept and the others are impostors." The others are real too — they are just at the wrong depth.
• It is not "the two cases are the same concept at different granularity." They are genuinely different axes; conflating them is what produced the un-assignable Kwik Trip departments.
• It is: the founder's generalization is correct in substance and premature in structure. Every function does have a motion catalog. In SALES and SERVICE the catalog happens to sit directly under the function, so the flat tree works by accident. Everywhere else the catalog sits under a sub-function, and the flat tree put the sub-function in the motion slot and left the actual motions unmodelled.

2.5 There is a whole rigorous literature of motion catalogs, and it is 20-45 years old

The most surprising result of this brief: the operations-strategy and enterprise-architecture canon of 1979-2006 contains at least five independently-authored, cleanly-citable frameworks that pass the substitutability-plus-selectivity test outright — every one of them predating the word "motion," and all of them stronger citations than anything GTM produced. All five below were verified this session.

They share a common shape: two orthogonal dimensions crossed into a small matrix, each cell a genuinely different operating archetype, and the prescriptive payload is always "match your choice to your situation; mismatches are costly." Kraljic is the cleanest of all on our test — it does not merely name categories, it prescribes categorically different behaviour per quadrant. Ross/Weill/Robertson is the best enterprise-level analogue to the whole motion thesis: an explicit whole-company choice among four models, where the strategic act is picking one and building consistent capability around it, and half-committing across incompatible models is the failure. A multi-site retailer is the textbook Replication shape (high process standardization, low process integration).

Two negative cases, which are as informative as the positives:

• Galbraith's Star Model (strategy · structure · processes · rewards · people, Organization Design, 1977) is not a motion catalog. It is a decomposition of design levers — a "do all of these," not a "pick one." It is exactly the trap this brief is screening for, and it is one of the most-cited org-design frameworks in existence. (Galbraith's actual alternative-choice list — functional / product / market / geographic / matrix, including front-back — lives diffusely across his later work, not in one canonical citation.)
• Dave Ulrich's 1997 Human Resource Champions is the same trap, and I had it wrong going in. The 1997 book is organized around four HR roles — strategic partner, change agent, administrative expert, employee champion — which every HR function performs simultaneously. That is a decomposition. The "three-legged stool" delivery model (shared services · centres of expertise · business partners) that practitioners call "the Ulrich model" is a later, practitioner-derived framing; the earliest documented usage traced this session is a 1999 HR Magazine article quoting David Holborn of Mercer, with the structural pattern apparently already in practice at companies before that. Do not cite this as "Ulrich (1997)." Cite it as documented industry practice.

2.6 How back-office motion catalogs actually come into being

That Ulrich correction generalizes, and it is a real finding rather than a housekeeping note. The functions with clean motion catalogs — manufacturing, procurement, service operations, supply chain, enterprise/IT architecture — got them from single landmark papers with named authors. The functions without them — HR service delivery, finance and back-office shared services, legal operations — have the substitutable patterns in practice, documented by multiple credible bodies, but no single canonical citation; the taxonomy is restated slightly differently by every consultancy and re-cut every survey cycle.

Concretely, on the shared-services / global business services (GBS) axis:

• The Hackett Group describes a three-layer GBS model: high-volume transaction-processing centres (typically offshored) · centres of excellence · on-site business partners co-located with business units.
• Deloitte's Global Business Services Survey (biennial since 1999; 2025 is the 14th edition) works in GBS / global capability centre / shared services centre / centre of excellence vocabulary and reports roughly 65% of organizations blending outsourcing into their delivery model — but the page fetched did not present a clean named taxonomy.
• SSON (Shared Services & Outsourcing Network) references a similar family — managed service delivery, global delivery model, shared services/SSC/GCC, CoE, hybrid — but no single primary article stating it canonically was retrieved.

So the recurring back-office vocabulary — retained/embedded · centre of excellence · shared service centre (captive) · outsourced/BPO · offshore captive or GCC · hybrid GBS · automated/touchless — is real and operative, but it is trade-body consensus, not a framework. Cite it as "documented industry practice across multiple trade-research bodies," never as "the X et al. framework." Our own six-pattern catalog in [[01-projects/phdata/2026-06-29-ai-capability-org-structures]] is an instance of exactly this genre: real, useful, internally consistent, and with no single external citation behind it. That is fine, provided we label it honestly.

3. Industry reference models as motion sources

3.1 eTOM (TM Forum, telecom) — no motion catalog

Read status: gated. The TM Forum GB921 suite page and the ODA "About" page both returned HTTP 403 to automated fetch; nothing was read from a TM Forum primary document. What follows is from the Wikipedia overview article (fetched) plus search snippets.

• Originated as the Telecom Operations Map (2001), extended to eTOM the same year, renamed the Business Process Framework in 2013, published as document suite GB921 on a rolling release cadence.
• Decomposes across levels 0-4. Level 0 has three vertical groupings — Strategy, Infrastructure & Product; Operations; Enterprise Management — with a horizontal matrix of customer / service / resource / supplier-partner layers cutting across.
• Downloads are behind at least a registration gate, likely membership; not confirmed from a fetched page.
• Motion catalog: no. Channel (phone / web / self-service) appears inside CRM and Operations as detail, never as an orthogonal selection dimension. This is a pure process decomposition. Caveat: this is an inference from absence across secondary sources plus two blocked primary pages, not a fetched negative.

What ports: the level-of-decomposition discipline. What doesn't: everything else.

3.2 BIAN (banking) — no motion catalog

Read status: three official BIAN pages fetched and read; the detailed Service Landscape portal is registration-gated and was not read.

• Service Landscape 14.0 released 13 March 2026, adding Service Domains for AI-enabled use cases, updated Behaviour Qualifiers, and stronger ISO 20022 alignment; BIAN is explicitly expanding scope into payments and insurance (BIAN news release, fetched).
• Three tiers: Business Areas → Business Domains → Service Domains (BIAN Service Landscape overview, fetched). A figure of 322 Service Domains circulates for v11.0 (Nov 2023); not verified for v14.
• Motion catalog: no. Across all three official pages read, there is no mention of channel (branch / digital / call centre / broker) as a modelled dimension and no discussion of delivery-model variants. Service Domains define what a bank does, not how it is delivered. This is a fetched negative across three pages — a meaningfully stronger negative than the eTOM one.

3.3 SCOR (ASCM, supply chain) — yes, and it is the payoff

Read status: PRIMARY VERIFIED. The official Supply-Chain Council booklet Supply-Chain Operations Reference-model — Overview of SCOR Version 6.0 was downloaded and its full text extracted and read locally (mirrored at Georgia Tech: https://www2.isye.gatech.edu/~lfm/8851/Sources/SCOR/SCOR%206.0%20OverviewBooklet.pdf). Every quotation and code below is from that document. The current-release questions (SCOR DS) are separately flagged as unverified.

Origin. Developed in 1996 by PRTM (now part of PwC) and AMR Research (now part of Gartner), endorsed by the Supply Chain Council, which merged into APICS and then ASCM.

The three-level structure, verbatim from the booklet:

• Level 1 — "Top Level (Process Types)" — "defines the scope and content for the Supply Chain Operations Reference-model. Here basis of competition performance targets are set."
• Level 2 — "Configuration Level (Process Categories)" — "A company's supply chain can be 'configured-to-order' at Level 2 from the core 'process categories.' Companies implement their operations strategy through the configuration they choose for their supply chain."
• Level 3 — "Process Element Level" — "defines a company's ability to compete successfully in its chosen markets."

And on how Level 2 is used: "Practitioners select appropriate process categories from the SCOR configuration toolkit to represent their supply-chain configuration(s)."

The configuration toolkit is a matrix of SCOR Process (Plan / Source / Make / Deliver / Return) against Process Type (Planning / Execution / Enable):

The Execution categories — the actual motion catalog, verbatim:

• Source: S1 Source Stocked Product · S2 Source Make-to-Order Product · S3 Source Engineer-to-Order Product
• Make: M1 Make-to-Stock · M2 Make-to-Order · M3 Engineer-to-Order
• Deliver: D1 Deliver Stocked Product · D2 Deliver Make-to-Order Product · D3 Deliver Engineer-to-Order Product · D4 Deliver Retail Product
• Return: SR1/DR1 Return Defective Product and siblings (defective / MRO / excess)

D4 Deliver Retail Product is real, named, and confirmed in primary text. Note that D4 has no Source or Make counterpart — retail delivery is a genuinely distinct fulfilment pattern that the model had to add outside the stocked/MTO/ETO progression. For a convenience-store and fuel retailer, D4 is the motion.

Licensing. ASCM opened SCOR to free public access in 2021, reversing the prior members-only gate; the SCOR DS digital standard is reported as free of charge behind a free ascm.org account. We did not get past that gate — every automated attempt at ascm.org pages and PDFs returned 403 or unrenderable output. Treat "free" as reported, not verified. Certification and training are separately paid.

The SCOR DS gap — flag this before anyone cites it. SCOR DS (2022) restructured Level 1 to Plan, Source, Transform, Order, Fulfill, Return, with Orchestrate as a Level 0 layer: "Make" broadened to "Transform" to cover services, and "Deliver" split into "Order" and "Fulfill" for multichannel commerce. That much is corroborated across independent secondary sources. Whether the Level 2 process types survived into SCOR DS, and under what codes, is unresolved — no source found addresses it, and the primary documents were inaccessible. Given SCOR DS explicitly advertises "process changes supporting retail, omnichannel," the retail branching plausibly expanded, but that is a guess. Someone with a free ASCM login needs to open the live standard and check.

3.4 APQC industry PCFs — narrow read: substitution, not alternatives

Read status: no APQC page was successfully fetched; apqc.org returned 403 throughout. All of the following is from search snippets. (A sibling brief covers the cross-industry PCF's structure and licensing properly.)

• Industry PCFs exist for at least: Retail, Consumer Products, Aerospace & Defense, Automotive, Broadcasting, Energy & Utilities, Banking/Financial Services, Petroleum, Pharmaceutical, Telecommunications. Retail is versioned through 7.2.1; Consumer Products through 7.2.2.
• The Retail PCF (built with Microsoft as subject-matter expert) restructures the cross-industry taxonomy by replacing generic categories 2-5 with retail-specific ones — 2.0 Develop and Manage Customer Experience, 3.0 Market Products and Services, 4.0 Merchandise Products and Services, 5.0 Deliver Products.
• Motion catalog: apparently no. This reads as industry-specific process categories substituted into the operating/value-chain slot, not an enumerated set of alternatives. The framework is described as covering "a wide variety of retail formats with a particular focus on omni-channel retailers" — channel as a cross-cutting lens applied within categories, not as parallel branches the way SCOR splits by fulfilment type. Unconfirmed against primary text.
• Grocery / c-store: gap, not a negative. Nothing surfaced on fuel, foodservice or convenience-store formats within the Retail PCF. The primary document would settle it and was not accessible.

3.5 Reference-model scorecard

4. Candidate motion catalog, by function

How to read the tags. Two independent labels per entry — never collapse them.

Source tier:

• [REF-MODEL] — lifted from an industry reference model, verified against fetched primary text
• [CANON] — a named published framework; citation status stated inline
• [PRACTITIONER] — consultancy, analyst or trade-body literature
• [VAULT] — our own prior artifact
• [SYNTHESIS] — my own construction. No external source enumerates this. Treat as a hypothesis.

Confidence (high/med/low) = how confident I am this is a real, recognized, substitutable pattern that a client would recognize when asked.

Structure note: where the current tree's node is a sub-function, I list it as such and put the motions underneath it. That is the amendment in §5.

FN.SALES — motions sit directly under the function ✅ keep

Why add PLG: it is distinct from DTC/ecommerce. Ecommerce is a storefront transaction; PLG is a free-tier-to-expansion loop inside the product. The question named PLG explicitly and the tree has no home for it. Low cost to add; irrelevant to Kwik Trip; relevant to most software clients.

FN.SERVICE — mostly motions ✅ keep, with a delivery axis added

Cross-cutting delivery choice for all four: in-house · outsourced/BPO · offshore captive · hybrid follow-the-sun. [PRACTITIONER], high confidence — the entire contact-centre BPO industry is this one choice.

The academic anchor worth knowing: Schmenner's service process matrix — "How Can Service Businesses Survive and Prosper?", Sloan Management Review, Spring 1986, 21-32 — sorts service operations into service factory · service shop · mass service · professional service on labour intensity × customer interaction/customization. [CANON], citation verified this session, top-tier practitioner-academic. It is a genuine typology of alternative service-operating archetypes, but it classifies the business, not the department, so it belongs in the industry-profile seeding layer rather than in the motion tree.

FN.OPERATIONS — sub-functions; the motions live below them ⚠️ amend

Core production (sub-function) — motions:

Complementary and more granular: the Hayes & Wheelwright product-process matrix — "Link Manufacturing Process and Product Life Cycles," HBR, Jan-Feb 1979, 57:133-140 — job shop · batch · assembly line (connected line flow) · continuous flow, a genuine positioning choice keyed to product volume and variety. [CANON], citation verified this session, top-tier practitioner-academic. (Do not conflate it with the authors' companion Mar-Apr 1979 piece, "The Dynamics of Process-Product Life Cycles," which is also cited for this matrix.)

Kwik Trip worked example, and it is a good one: the c-store's core production is store operations and foodservice, and a single store runs M1 and M2 simultaneously — the hot case and bakery are make-to-stock, the fresh-made sandwich is make-to-order. That is the motion concept doing real, non-obvious work on the live account, sourced from a 1996 industry standard rather than a SaaS blog.

Maintenance & facilities (sub-function) — motions: reactive/run-to-failure · preventive/time-based · condition-based/predictive · reliability-centered maintenance (RCM), plus the orthogonal in-house vs contracted choice. [CANON] in reliability-engineering literature (RCM traces to the Nowlan & Heap report for the US Department of Defense, 1978) — cited from author knowledge, not verified this session. Confidence in the existence of the catalog: high. Confidence in that specific citation: medium.

Quality control (sub-function) — motions: end-of-line inspection · statistical process control · Six Sigma/DMAIC · total quality management · built-in-quality (jidoka/Toyota Production System). [CANON] quality-management canon, not verified this session. Existence high, citation medium.

Real estate & facilities development (sub-function) — motions: own/develop · lease · franchise/dealer-owned · sale-leaseback · third-party developed. [SYNTHESIS], med. Highly load-bearing for a c-store chain, where company-operated vs dealer-operated site strategy is a defining structural choice.

FN.SUPPLY_CHAIN — sub-functions; SCOR supplies the motions ⚠️ amend, best-sourced function in the tree

Procurement (sub-function) — motions, primary verified:

Plus the delivery-model choice: centralized/category management · decentralized/site-level buying · outsourced (GPO or procurement BPO) · hybrid. [PRACTITIONER], high. (Kwik Trip's dept 680 "Category Management" maps here — centralized category management is a motion, not a sub-function.)

Adjacent, and the single cleanest motion catalog in the whole canon — but scoped to the item, not the org: Kraljic's purchasing portfolio matrix, "Purchasing Must Become Supply Management," HBR, Sep-Oct 1983 — leverage · strategic · non-critical/routine · bottleneck, on profit impact × supply risk, with a categorically different sourcing approach prescribed per quadrant (strategic → long-term partnership or vertical integration; bottleneck → secure supply and safety stock; leverage → competitive tendering; non-critical → process simplification). [CANON], citation verified this session. Because it segments the spend category rather than the organization, carry it as a tagging dimension on procurement, not as a motion.

Distribution/fulfillment (sub-function) — motions:

Kwik Trip note: self-distribution — company-owned commissary, bakery, dairy and fleet — is the distinguishing operational trait of this class of retailer, and it is exactly a motion choice (self-distribute vs 3PL vs DSD/vendor-direct). This is a place where the motion frame produces a client-recognizable insight on the first pass.

Inventory & planning (sub-function) — SCOR's P1-P5 are planning-type categories, not substitutable alternatives, so they do not port as motions. Real motion axis: centralized planning (S&OP/IBP) · site-level replenishment · vendor-managed inventory · automated/algorithmic replenishment. [SYNTHESIS] + [PRACTITIONER], med.

Function-level modifier worth carrying: Fisher's efficient vs responsive supply chain — "What Is the Right Supply Chain for Your Product?", HBR, Mar-Apr 1997, 75(2):105-116 — a two-way choice matched to functional vs innovative product demand patterns. [CANON], citation verified this session. Two motions, not many, but a genuinely substitutable pair and a strong industry-profile seed: a c-store's core assortment is functional/efficient, its foodservice and seasonal programme is innovative/responsive, which predicts a split supply chain.

FN.MARKETING — sub-functions ⚠️ amend

Current four (Brand & content, Performance/demand gen, Product marketing, Communications) are disciplines every marketing organization of scale staffs. Kwik Trip's dept 677 already had to anchor at the function because it spans three of them.

Proposed motion axis (demand-generation model), all [PRACTITIONER] or [SYNTHESIS]:

Honest assessment: this is the weakest-sourced function in the catalog. No reference model and no canonical framework enumerates marketing motions. Everything here is practitioner vocabulary or my own construction. Do not present it to a client as sourced.

FN.FINANCE — sub-functions; delivery model is the motion ⚠️ amend

The three current nodes are universal. Every company does AP/AR, FP&A and tax/treasury. The selectivity test returns zero information.

Proposed motion axis, applied per sub-function — the finance service-delivery model. Note the sourcing caveat from §2.6: this is trade-body consensus, not a named framework. The closest thing to a citable spine is The Hackett Group's three-layer GBS model (transaction-processing centres · centres of excellence · on-site business partners); the fuller list below is the operative vocabulary across Hackett, Deloitte's Global Business Services Survey and SSON.

This axis is where AI use cases actually land, which matters for the platform's downstream purpose: "AP is a shared service centre" and "AP is embedded per business unit" imply completely different automation opportunities, whereas "the client has AP" implies nothing.

FN.HR — sub-functions; the "three-legged stool" is the motion ⚠️ amend

Function-level motion axis — the HR service-delivery model, popularly "the Ulrich model": HR shared services · centres of expertise · HR business partners (+ a corporate HR core). [PRACTITIONER], high confidence in the pattern's reality and near-universal adoption; low confidence in the attribution. Verified this session: Ulrich's Human Resource Champions (HBS Press, 1997) is organized around four HR roles — strategic partner, change agent, administrative expert, employee champion — which is a decomposition, not a choice set. The three-legged delivery structure is a later practitioner formulation, earliest documented usage traced to a 1999 HR Magazine article quoting David Holborn of Mercer. Present this as documented industry practice, never as "Ulrich (1997)."

Per sub-function:

Kwik Trip note: high-volume hourly store recruiting is plausibly a structurally different motion from corporate recruiting — different funnel, different cost model, different automation surface — though that distinction is [SYNTHESIS], not sourced. Correction (2026-08-17 close-out): an earlier version of this line claimed depts 480 and 669 were "the two biggest node populations in the client map." That is false. Counting the (NNN convention across the 79 person pages in 04-people/: 671 = 20, 677 = 11, 202 = 10, 669 = 5, 820 = 3, 478 = 2, 480 = 1. The two largest are IT (671) and Marketing (677) — which are among the departments this brief cites as evidence the taxonomy fails, not where an HR amendment would pay off. The "pays off soonest on the live account" claim is withdrawn; it had the client's own data backwards.

FN.IT — sub-functions ⚠️ amend

Function-level motion axis — sourcing/delivery model: insourced · managed service/outsourced · offshore captive or global capability centre · staff augmentation · vendor-managed SaaS. [PRACTITIONER], high.

Per sub-function:

The Data & analytics row is the single cheapest win in this brief: a fully-written, sourced, failure-mode-annotated motion catalog already exists in our vault for the function phData sells into. It has never been wired into the platform.

Related but distinct: Weill & Ross's six IT governance archetypes — IT Governance: How Top Performers Manage IT Decision Rights for Superior Results, Harvard Business School Press, 2004 (MIT CISR) — business monarchy · IT monarchy · feudal · federal · IT duopoly · anarchy. [CANON], citation and archetype names verified this session. These enumerate who holds decision rights, not how work is delivered. Carry as a separate governance tag; do not file as a motion.

FN.PRODUCT — sub-functions ⚠️ amend, and check function fit for retail

Function-level motion axis: in-house product organization · outsourced/agency development · offshore captive · open-source/community-led · acquired-and-integrated portfolio. [SYNTHESIS] + [PRACTITIONER], med.

Sub-function motions:

• Product mgmt — a two-way choice: feature/delivery teams (build a prioritized roadmap of outputs) vs empowered product teams (given problems, measured on outcomes). Cagan/SVPG, Transformed: Moving to the Product Operating Model, 2024. [PRACTITIONER], verified this session — and note the correction: Cagan uses "feature teams" and "delivery teams" near-synonymously, so this is two alternatives, not three. Med.
• Engineering/R&D — closed vs open innovation (Chesbrough, 2003) is the likely academic anchor for the in-house/partner/acquire choice. [CANON], not verified this session. Med.
• Design — in-house design team · agency · embedded-in-squad · design system/central platform. [SYNTHESIS], low-med.

Flag a real taxonomy problem: for a convenience-store retailer, FN.PRODUCT as currently defined (software product management, engineering, design) barely exists. The analogous work is merchandising and private-label product development, which the tree currently files under SUPPLY_CHAIN.PROCUREMENT via category management. Either FN.PRODUCT needs a non-software reading, or the industry profile needs to mark it not-applicable for retail. This is a function-level issue that the motion amendment does not fix.

FN.LEGAL_RISK — sub-functions ⚠️ amend

Risk management is the one place where the substitutable set is a per-risk choice rather than a per-organization one — same distinction as Kraljic. Carry it, but tag it as item-level, not org-level.

A worked negative, and a good sanity check on our own test: CLOC's "Core 12" is frequently reached for as a legal-operations framework. It is a decomposition of the twelve competencies legal operations performs — financial management, vendor/firm management, technology, business intelligence, strategic planning and so on. Every legal-ops team does all twelve. It fails the selectivity test outright and must not be filed as a motion catalog. This is exactly the mistake the current tree made in eight functions, committed by a trade body in ours.

4.1 Summary of proposed changes to the 36

Do not rename any id. The platform README is explicit that client files cite FN.* ids and they never change. Everything above is additive.

Convergences and contradictions

• Convergence, and it is the finding. Three independent lines arrived at the same place: (a) the literature review, which found the substitutable-pattern concept sitting one level below the decomposition in SCOR; (b) the live Kwik Trip function map, which could not assign IT, Marketing and Finance departments to any motion and anchored them at the function; (c) our own AI-capability reference doc, which already said orgs "decide centralize-vs-federate per sub-function." Three routes, one conclusion: the choice axis lives below the sub-function.
• Contradiction with the tree's own premise. The spec says the Map records "which motions run," which presupposes selectivity. For 26 of 36 nodes the answer is always "all of them," so the field carries no information. Either the nodes change or the claim should.
• Contradiction between the question's framing and the evidence on sourcing. The question treats GTM literature as the origin and industry reference models as the corroboration. The evidence inverts this: GTM has the word and no rigour; SCOR has the rigour, a primary-verifiable document, a 1996 publication date, and even the retail-specific category we most need. We should be citing SCOR to clients, not blog posts.
• A pattern in how motion catalogs come into being, which we should expect to keep hitting. Functions with clean catalogs — manufacturing, procurement, service operations, supply chain, enterprise/IT architecture — got them from single landmark papers with named authors, 1979-2006. Functions without them — HR service delivery, finance and back-office shared services, legal operations — have the substitutable patterns in practice and multiple credible bodies documenting them, but no canonical citation; the taxonomy is re-cut by every consultancy each survey cycle. Where we are doing original synthesis, it is almost always in the second group. That is a defensible place to be doing it, and it should be stated rather than disguised.
• A small housekeeping contradiction worth clearing. Our vault's org-structures reference names the engagement QuikTrip; the platform's live client folder is kwiktrip. These are two different real companies. Confirm which is which before an industry profile gets seeded off the wrong one.

Synthesis for RDCO

The founder's generalization is right, and the current tree is the wrong shape for it. Those are two separate claims and both hold. "Motion" — a set of mutually-substitutable patterns for running a function, where a company picks 1..n — is a real, general concept that exists in non-GTM functions with far better documentation than GTM ever produced. SCOR has been publishing exactly this since 1996, calls it a "configuration toolkit," states its purpose in words we could paste into a client deck ("companies implement their operations strategy through the configuration they choose"), and even ships the retail-specific category (D4 Deliver Retail Product) that our live account needs. Behind SCOR sits a whole 1979-2006 operations-strategy and enterprise-architecture cluster — Hayes & Wheelwright, Kraljic, Schmenner, Fisher, Weill & Ross, Ross/Weill/Robertson — six independently-authored, top-tier-cited frameworks doing the same thing across manufacturing, procurement, service operations, supply chain and enterprise operating-model choice, decades before anyone said "motion." The generalization does not need defending. It needs sourcing, and the source is not the GTM canon.

What does need amending is the tree's depth. SCOR separates the decomposition (Level 1: Plan/Source/Make/Deliver/Return — everyone does all of them) from the configuration (Level 2: M1/M2/M3 — pick the ones you run). The Organizational Platform collapsed both onto one level, and the result is that 2 of 10 functions got motion-shaped children and the rest got sub-functions wearing the name.

The Kwik Trip corroboration is weaker than this brief originally claimed, and the claim is hereby downgraded. The function map does anchor the IT, Marketing and Finance departments at the function with a note that picking one "would be a guess" — that is verbatim and real. But the brief reported 3 of 12 departments and omitted 8 that cut the other way: 378 and 797 → FN.OPERATIONS.MAINTENANCE, 387 → FN.MARKETING.BRAND_CONTENT, 478 → FN.LEGAL_RISK.RISK_MGMT, 480 → FN.HR.RECRUITING, 669 → FN.HR.TALENT_OPS, 680 → FN.SUPPLY_CHAIN.PROCUREMENT, 809 → FN.OPERATIONS.REAL_ESTATE. All eight assigned cleanly into nodes this brief calls sub-functions. Marketing appears on both sides — dept 387 mapped to a marketing motion without difficulty while dept 677 anchored at the function — so node type cannot be the cause. The map's own YAML states the actual cause, and it is department breadth rather than axis confusion: "dept spans all four IT motions," "spans brand/performance/comms motions," "spans FP&A and AP/AR." A single "Sales" department spanning field and inside would anchor at FN.SALES identically, under nodes this brief certifies as true motions. So the map is consistent with the thesis but does not discriminate it from the department-granularity explanation. It is not "the bug report," and it is not an independent third route to the verdict.

The proposed amendment is small and additive, which is the point. Motion pages currently carry three frontmatter fields (id, name, function). Add two: axis: substitutable | sub_function, marking honestly which kind of node each is; and, on sub_function nodes, a variants: list holding the actual motion catalog from §4. No id changes, no filename changes, no breakage of the client-id continuity check. The 36 nodes stay exactly where they are — 10 of them get labelled as true motions, 26 get labelled as sub-functions and gain a variant list underneath. The industry-profile seeding layer then becomes genuinely predictive rather than tautological: seeding a convenience-retailer profile with D4 Deliver Retail Product, self-distribution, high-volume hourly recruiting, trade/shopper marketing, and a company-operated-vs-dealer real-estate motion is a set of falsifiable claims a client can correct in a workshop. Seeding it with "this company has AP/AR" is not.

For phData's commercial position, the sourcing story is the asset. A competitor can also say "we map your org." What is harder to answer is "our operations and supply-chain motions come from SCOR, the ASCM standard your supply-chain leadership already knows; our data-and-analytics motions come from the six-pattern operating-model catalog we published; here is the confidence rating on every node and here is which ones are our own synthesis." Two practical follow-ons. First, the Data & analytics row in §4 is free — we wrote that catalog in June for this same client family and never wired it into the platform; doing so costs an afternoon. Second, be disciplined about where the synthesis is thin: MARKETING has no reference model, no canonical framework, and the weakest confidence ratings in this brief. If a motion catalog is going to be challenged in a room, it will be that one.

Why this is in the vault

This is the framework-research round the Organizational Platform README gates its content-section template on ("the hand-section template locks at exemplar time, after the framework-research round"). It settles what a motion page's hand-written section should contain — a definition, a source citation, and a confidence tag — and proposes the specific frontmatter amendment (axis + variants) needed before the 36 motion pages are written, so the pages don't have to be rewritten after the first exemplar.

Open follow-ups

• Did SCOR DS preserve the Level 2 process types, and where did D4 Deliver Retail Product go when "Deliver" split into "Order" and "Fulfill"? SCOR DS advertises "process changes supporting retail, omnichannel," which suggests the retail branching survived or expanded, but no source found addresses it and every automated fetch of ascm.org was blocked. This is the highest-value open question in the brief: if SCOR DS expanded retail fulfilment into several named categories, that is a ready-made, standards-backed motion catalog for the exact client we are serving.
• Is there any function outside supply chain where an industry body has published a substitutable-pattern catalog, rather than a process decomposition? SCOR is the only one of four reference models that did it. Was that an accident of supply chain's engineering culture, or has someone done the equivalent for service operations, maintenance (ISO 55000 asset management?) or finance? A negative answer is as useful as a positive one — it would tell us the SCOR pattern is genuinely rare and worth naming as our own contribution.
• Does the marketing-motion gap reflect the literature or the discipline? Marketing is the only function where nothing — no reference model, no canonical framework, no trade body — enumerates alternative operating patterns, despite marketing being heavily written about. Is that because marketing genuinely resists this decomposition, or because the enumeration exists under a different name (media mix? channel strategy? the "marketing organization archetypes" work some consultancies publish)?
• Does a company's enterprise operating model predict its function-level motions? Ross/Weill/Robertson's four models (Coordination, Unification, Diversification, Replication) classify a company by process standardization × integration. A multi-site retailer is textbook Replication. If Replication reliably implies centralized procurement, standardized store operations and federated real estate, then the industry-profile seeding layer could be driven off one enterprise-level classification rather than 10 independent function guesses — a materially cheaper Map.

Related

• [[01-projects/phdata/2026-06-29-ai-capability-org-structures]] — our own six-pattern operating-model catalog; directly reusable as the FN.IT.DATA_ANALYTICS motion list
• [[06-reference/2026-08-04-cfo-secrets-centralize-fpa-mailbag]] — centralize-vs-decentralize as the live FP&A design question
• [[06-reference/2026-07-18-cfo-secrets-building-fpa-series-iii-sculpting-the-team]] — FP&A hub-and-spoke and business-partnering as the finance delivery motion
• [[06-reference/concepts/growth-loops]] — the adjacent GTM-canon cluster this brief's provenance section sits against

Sources

Vault

• [[01-projects/phdata/2026-06-29-ai-capability-org-structures]]
• [[06-reference/2026-08-04-cfo-secrets-centralize-fpa-mailbag]]
• [[06-reference/2026-07-18-cfo-secrets-building-fpa-series-iii-sculpting-the-team]]
• [[06-reference/concepts/growth-loops]]

Working tree (phData, not vault)

• organizational-platform/README.md, spec/02-organizational-platform.md — the 10×36 tree, id scheme, frontmatter contract, Map-population layers
• clients/kwiktrip/organizational-map/02-functions/function-map.yaml — the "L1 anchor, picking one L2 would be a guess" note

Reference models

• SCOR — PRIMARY VERIFIED. Supply-Chain Operations Reference-model: Overview of SCOR Version 6.0, Supply-Chain Council. Downloaded and full text extracted locally; all Level 1/2 quotations, the configuration-toolkit matrix, and codes S1-S3 / M1-M3 / D1-D4 / SR1-SR3 / DR1-DR3 / P1-P5 / EP-ER read directly from it. https://www2.isye.gatech.edu/~lfm/8851/Sources/SCOR/SCOR%206.0%20OverviewBooklet.pdf
• SCOR general history, SCOR DS Level 1 restructure (Plan/Source/Transform/Order/Fulfill/Return + Orchestrate), and the "free of charge" claim — https://en.wikipedia.org/wiki/Supply_chain_operations_reference (secondary, fetched and read). SCOR DS Level 2 status unresolved; ascm.org returned 403 to all attempts — gated, not read
• BIAN Service Landscape overview — https://bian.org/deliverables/service-landscape/ (official page, fetched)
• BIAN Service Landscape 14.0 release, 13 Mar 2026 — https://bian.org/news-room/bian-unveils-new-service-landscape-14-0-to-accelerate-ai-ready-banking-architecture/ (official page, fetched); detailed Service Landscape portal registration-gated, not read
• eTOM overview — https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) (secondary, fetched). TM Forum GB921 suite page and ODA About page both returned HTTP 403 — not read
• APQC industry PCFs — apqc.org returned 403 throughout; no APQC page fetched. Retail PCF category structure and version numbers are from search snippets only, unverified against primary text

GTM provenance

• Christoph Janz, "Five Ways to Build a $100 Million Business," Point Nine Capital, 5 Oct 2014 — http://christophjanz.blogspot.com/2014/10/five-ways-to-build-100-million-business.html (fetched and read; the word "motion" does not appear in it)
• Bessemer Venture Partners Atlas, "Introducing enterprise sales to a product-led growth organization," 14 Feb 2022 — https://www.bessemervp.com/atlas/introducing-enterprise-sales-to-a-product-led-growth-organization (fetched and read; uses "sales motion," "GTM motion," "PLG" with no definitions)
• TechTarget, "sales motion" — https://www.techtarget.com/searchitchannel/definition/sales-motion (fetched and read)
• Rackham & DeVincentis, Rethinking the Sales Force (McGraw-Hill, 1999) — transactional/consultative/enterprise selling models. Book listing and chapter structure confirmed from search results; text not read
• Zoltners, Sinha & Lorimer, Sales Force Design for Strategic Advantage (Palgrave Macmillan, 2004), incl. a "Go-To-Market Strategy" chapter — existence and chapter title from a Springer Nature listing; chapter is paywalled and was not read
• SiriusDecisions history (fd. 2001; Demand Waterfall 2005, rearchitected 2012, Demand Unit Waterfall 2017; Go-to-Market Execution Model, 2017 Summit; Channel Operating Model) — https://en.wikipedia.org/wiki/SiriusDecisions and Forrester blog listings (search results; primary research subscription-gated, not read)
• OpenView / Blake Bartlett as originator of "product-led growth" (~2016) — UNVERIFIED. Two OpenView pages were fetched and neither substantiated the coinage claim
• HBR sales-force-structure literature (Zoltners et al.) — not accessed; HBR paywalled

Organization-design and operations-strategy canon

Verified this session — citation, year, venue and category names confirmed. Evidence basis is scholar/citation-database listings, publisher pages and encyclopedic sources; HBR and Sloan Management Review article texts are paywalled and were NOT read. Treat the citations as confirmed and the content characterizations as drawn from abstracts and secondary summaries.

• Hayes & Wheelwright, "Link Manufacturing Process and Product Life Cycles," Harvard Business Review, Jan-Feb 1979, 57:133-140 — job shop / batch / assembly line (connected line flow) / continuous flow. https://hbr.org/1979/01/link-manufacturing-process-and-product-life-cycles · https://en.wikipedia.org/wiki/Hayes-Wheelwright_matrix
• Kraljic, "Purchasing Must Become Supply Management," Harvard Business Review, Sep-Oct 1983 — leverage / strategic / non-critical / bottleneck, on profit impact × supply risk, with distinct sourcing approaches per quadrant. https://hbr.org/1983/09/purchasing-must-become-supply-management
• Schmenner, "How Can Service Businesses Survive and Prosper?", Sloan Management Review, Spring 1986, 21-32 — service factory / service shop / mass service / professional service. https://www.researchgate.net/publication/12997398_How_Can_Service_Business_Survive_and_Prosper
• Fisher, "What Is the Right Supply Chain for Your Product?", Harvard Business Review, Mar-Apr 1997, 75(2):105-116 — efficient vs responsive, matched to functional vs innovative products. https://hbr.org/1997/03/what-is-the-right-supply-chain-for-your-product
• Weill & Ross, IT Governance: How Top Performers Manage IT Decision Rights for Superior Results, Harvard Business School Press, 2004 (MIT CISR) — business monarchy / IT monarchy / feudal / federal / IT duopoly / anarchy. https://cio-wiki.org/wiki/Weill_Ross_Framework
• Ross, Weill & Robertson, Enterprise Architecture as Strategy: Creating a Foundation for Business Execution, Harvard Business School Press, 2006 (MIT CISR) — Coordination / Unification / Diversification / Replication, on business-process standardization × integration. Note the imprint: HBS Press, not Harvard Business Review Press, which did not exist under that name until c. 2010-11. https://umbrex.com/resources/frameworks/organization-frameworks/mit-cisr-operating-model-quadrants-coordination-unification-diversification-replication/
• Mintzberg, The Structuring of Organizations, Prentice-Hall, 1979, and "Structure in 5's: A Synthesis of the Research on Organization Design," Management Science 26(3), Mar 1980, 322-341 — simple structure / machine bureaucracy / professional bureaucracy / divisionalized form / adhocracy. The 1980 journal article and the 1983 trade book Structure in Fives are distinct works; do not merge them. The volume/issue/page pinpoint is moderately, not fully, verified. https://umbrex.com/resources/frameworks/organization-frameworks/mintzberg-organizational-configurations/
• Galbraith, Star Model, Organization Design, Addison-Wesley, 1977 — strategy / structure / processes / rewards / people. Cited here as a negative case: a decomposition of design levers, not a motion catalog. https://jaygalbraith.com/wp-content/uploads/2024/03/StarModel.pdf
• Ulrich, Human Resource Champions: The Next Agenda for Adding Value and Delivering Results, Harvard Business School Press, 1997 — four HR roles (strategic partner, change agent, administrative expert, employee champion). Also a negative case: the "three-legged stool" delivery model attributed to this book is not in it; earliest documented usage traced to a 1999 HR Magazine article quoting David Holborn of Mercer. Ulrich's original text could not be fetched; the attribution finding rests on secondary summaries. https://www.thedigitaltransformationpeople.com/channels/people-and-change/updating-the-ulrich-conceptual-outcomes-model-part-1/
• Cagan / SVPG, TRANSFORMED: Moving to the Product Operating Model, 2024 — feature/delivery teams vs empowered product teams, a two-way choice. Primary text not fetched. https://www.svpg.com/transformed/

Delivery-model trade literature — real practice, no canonical citation

• The Hackett Group, three-layer GBS model — https://www.thehackettgroup.com/global-business-services-hackett/ (secondary summaries; specific list not confirmed from a fetched primary page)
• Deloitte Global Business Services Survey (biennial since 1999; 2025 = 14th edition; ~65% blend outsourcing into their delivery model) — https://www.deloitte.com/us/en/services/consulting/services/shared-services-survey.html (page fetched; did not present a clean named taxonomy)
• SSON (Shared Services & Outsourcing Network) delivery-model vocabulary — no primary article fetched; search-engine synthesis only
• Thomson Reuters Institute + Georgetown Law + Oxford Saïd, Alternative Legal Service Providers report (2019/2021/2023/2025; 2025: $28.5B market, captive ALSPs up six-fold since 2015) — https://www.thomsonreuters.com/en-us/posts/legal/alsp-report-2023/ (press releases and secondary summaries; report PDFs are form-gated and were not read)
• CLOC Core 12 legal-operations competencies — cited as a negative case (a decomposition, not a motion catalog); the canonical 12-item list at cloc.org/cloc-core-12/ was not successfully fetched. https://cloc.org/newsdesk/cloc-announces-updates-to-its-core-12-functions-of-legal-operations/

Named in the catalog but NOT verified this session — check before quoting to a client

• Chesbrough, Open Innovation (2003) — closed vs open innovation
• Nowlan & Heap, reliability-centered maintenance report for the US Department of Defense (1978)
• ISO 31000 / COSO ERM risk-treatment set (avoid / reduce / transfer / retain) — standards not fetched
• ITSMA as originator of "account-based marketing" (early 2000s)

Terminology check

• Targeted search for "operating motion" / "delivery motion" as general business vocabulary returned no established non-GTM usage. Generalizing "motion" beyond go-to-market is a phData coinage, not an adoption of existing terminology.