Inherited Sourcing Doctrine in Merged Service Estates

From WFM Labs
Three inherited sourcing doctrines, each correct for the business that wrote it, drilled through by one schema.

Inherited sourcing doctrine in merged service estates is the condition in which a service organization formed through successive acquisitions carries several sourcing rules at once — each decided independently by a predecessor company, each correct for the business that wrote it, and none reconciled with the others. Sourcing Design Axes: Node and Client Ownership establishes that this incoherence is not drift but a stratified record of several coherent designs; this page takes that diagnosis as given and asks what follows from it. The condition is what several correct local answers look like when they are placed side by side, and it is the ordinary starting position of any estate assembled by combination rather than grown from one design. This page describes the archetypal doctrines that collide, why the collision is a schema problem before it is a strategy problem, and the reconciliation method that follows. The general argument for measurement-before-comparison in a consolidated estate is at The Case for Adaptive Workforce Management.

The archetypes that collide

Four heritages, each with its own playbook, arriving in one company with nothing to merge into. The inconsistency is inherited, not anyone's fault, which is what makes it fixable without blame.

Three sourcing doctrines recur across service industries, and a merged estate of any age usually holds at least two of them.[1]

  • Mid- and back-office only. Customer-facing work stays in owned centers; fulfillment, documentation and processing go to suppliers. The premise is that the customer boundary is where quality risk concentrates, so suppliers are kept behind it.
  • Everything to suppliers, competitively. Front, middle and back office are all contracted, often to several suppliers at once so that competitive tension holds price and performance. The premise is that the business is a coordinator of delivery rather than a deliverer, and that continuity risk is managed through multiplicity.
  • Own centers only. The business builds and runs its own delivery footprint, including lower-cost captive centers, and treats supplier capacity as exceptional. The premise is that tenure and culture are the quality mechanism, and both are properties of employment.

Each doctrine is internally coherent. Each was chosen by a leadership team that understood its own business, its client base, its labor markets and its capital position. The mid-and-back-office rule is right for a business whose brand promise sits at the customer boundary; the competitive multi-sourcing rule is right for a high-growth business that cannot build capacity as fast as it wins; the own-centers rule is right for a business whose service complexity makes proficiency slow to build and expensive to lose — the premise Placement Rules and the Tenure Contract examines, holding that expertise cannot be contracted while the rate at which people leave can be. The error is not in any doctrine. It is in the assumption, made after the combination, that the estate now has one doctrine when it has three.

Why the doctrines freeze

The four-eras account does not treat sourcing, but it supplies the mechanism by analogy. Each predecessor institutionalized its sourcing logic the same way an operation institutionalizes a planning philosophy — in contracts, in the shape of its supplier portfolio, in the vocabulary its commercial teams used to sell, and in the measurement instruments its operations used to judge delivery.[1] The integration literature makes the same point from the acquirer's side: value in an acquisition is realized or lost in the integration of processes and practices after the deal, not in the deal itself.[2] A doctrine embedded that deeply does not update when the company changes hands. The contracts run to term; the vocabulary continues to be spoken; the instruments continue to produce numbers that look comparable and are not. The same mechanism that lets an operation run current technology on a previous era's philosophy lets a merged estate run one commercial brand on three sourcing philosophies.

The collision surfaces in three places.

  • Service constructs with no shape in the model. Each heritage sold service in its own tiers, and when the tiers are consolidated into one commercial ladder, the constructs that carried the hardest constraints — a regulated segment, a premium construct that survives in delivery but has no slot in the new packaging — are the ones the unified ladder has no place for.
  • Vocabulary that diverges quietly. The same word — dedicated, designated, shared, front office — means different things by heritage, and the divergence is invisible until a placement decision or a contract turns on it (see Designated, Shared and Dedicated: What the Words Implement).
  • Instruments that cannot be compared. Each heritage measured quality, occupancy and headcount on its own definitions, so an apparent performance difference between two nodes may be a definition difference, and a decision made on it is made on noise (see Sample Size and Detectable Difference in Quality Measurement and Headcount Reconciliation in Service Operations).

A schema problem before a strategy problem

The instinctive response to inherited doctrine is to pick a winner — to declare one heritage's rule the estate's rule and migrate the others toward it. It fails for a structural reason: each doctrine is indexed on the organization that wrote it, and the organization is not a stable object. Sourcing Design Axes: Node and Client Ownership states the test directly: if a reorganization would force the sourcing architecture to change, the architecture was indexed on the wrong things. A doctrine that says "brand A's back office goes to suppliers" is indexed on a brand that any subsequent combination can absorb. A doctrine that says "premier clients get dedicated teams" is indexed on a commercial tier that any repackaging can redefine. Neither survives the integration it is supposed to guide.

The durable index is the work itself. Every unit of service work has stable properties — the kind of work it is, who owns the client relationship, its eligibility constraints, its language, its coverage hours, its proficiency requirement — and each heritage's doctrine is, on inspection, a rule about some subset of those properties expressed in the vocabulary of one organization. "Mid and back office to suppliers" is a rule about asynchronous, decomposable, fast-to-proficiency work. "Own centers for complex service" is a rule about synchronous, judgment-bearing work with long ramps (the dichotomy is Service Chain Decomposition and Node Sourcing's, where sourcing tier is a property of the node rather than the queue or the client). Translated onto work attributes, the three doctrines stop contradicting each other and become three partial answers to the same question, each strongest on the work its authors knew best. That translation is the schema. The strategy is what gets computed on it afterward. The Case for Adaptive Workforce Management gives the two disciplines that make the schema usable — measure before comparing, and index the architecture on properties of the work rather than the organization chart — and notes that integration itself is the forcing function, because platform and account migrations cannot land without shared definitions.

The reconciliation method

Reconciliation proceeds in five steps. They are not a simple chain: steps 2 and 3 both work from the inventory produced by step 1 and can run in parallel, step 4 tests the premises named in step 2, and step 5 consumes the output of both branches. The sequence is a practitioner method rather than a tested procedure.[1]

  1. Inventory the doctrines as written. Collect each heritage's sourcing rule from the artefacts that actually carry it — supplier contracts and their scope clauses, commercial offer definitions, placement decisions on record — rather than from current leaders' descriptions, which tend to describe the rule as it should have been. Date each arrangement to the doctrine that produced it; that converts a blame conversation into an archaeological one.
  2. Name each doctrine's premise. Every rule encodes a belief about where quality risk, continuity risk and cost sit. Writing the premise down separates the belief, which can be tested, from the rule, which was its consequence.
  3. Translate each rule onto work attributes. Replace organizational nouns — brand, region, tier, team — with the properties of the work the rule was actually about. This is the step that dissolves most apparent contradictions, because rules that conflict on organizational vocabulary frequently agree on work attributes.
  4. Test each premise against the estate's own evidence, on one instrument. Where a heritage believed suppliers were worse at customer-facing work, the estate's matched comparisons either support it or do not (see Comparing Delivery Arrangements for why a comparison posed between places or suppliers has no answer, and what unit permits a fair one); where a heritage believed tenure was the quality mechanism, the tenure-controlled comparison either supports it or does not (see Placement Rules and the Tenure Contract). Premises that fail are retired regardless of which heritage held them.
  5. Decide per node, and record the decision as a rule with an owner. The output is not a winning doctrine but a placement rule set indexed on work attributes, with each rule carrying the evidence that justified it and a named owner who can change it.

The literature on acquisition integration arrays four modes on two axes — the need for strategic interdependence and the acquired unit's need for autonomy — yielding absorption (full consolidation, dissolving the acquired unit's boundary), symbiosis (interdependence built while autonomy is deliberately preserved), preservation, and holding.[3] The framework is contingent: it prescribes no mode as generally superior. M&A Workforce Integration Patterns states the same contingency in workforce terms — absorb, federate, hybrid — and sets the conditions under which each applies, Marks and Mirvis argue that combinations fail through the combination process — inadequate strategic and psychological preparation before the deal, and cultural clash during integration — rather than through the financial logic of the deal alone.[4] Read against them, inherited sourcing doctrine sits in the symbiosis cell on the sourcing question specifically, because each heritage's rule holds genuine knowledge about the work its authors ran; collapsing all of them into one heritage's vocabulary discards that knowledge along with the contradictions — even where absorption is right for the platform and the reporting line.

Failure modes

The five below are recurring rather than exhaustive.[1]

  • Declaring a winner. One heritage's doctrine is adopted estate-wide because its sponsor is the more senior, and the work the other heritages understood better is placed by a rule written for different work.
  • Averaging. Contradictory rules are softened into a blended policy that constrains nothing — every placement remains an argument, now with three authorities to cite.
  • Re-litigating per deal. In the absence of a schema, each placement decision reopens the doctrinal argument, and the estate accumulates rulings rather than rules.
  • Mistaking the instruments for the operation. A heritage that scored itself on its own instrument looks better or worse than a heritage on another instrument, and the difference is treated as capability when it is definition.
  • Waiting for the migration to finish. Definitions are deferred until platforms are unified, when the platform migration is precisely the event that cannot proceed without them (see Platform Migration as a Definitional Forcing Function).

Maturity Model Position

Inherited doctrine does not place an estate at a single level. Each heritage may sit at Level 2 or Level 3 on the WFM Labs Maturity Model™ — a forecast produced, schedules built to it, variance acted on intraday — while the connections between heritages sit at Level 1, because no shared schema exists across them. Nothing above Level 3 — probabilistic planning, value-based routing, placement as a standing mechanism — can be built on connections that have no shared definitions. This is a further case of the unevenness for which the maturity curve makes honest placement a range rather than a point: there the unevenness runs between functions, here it runs between heritages, and the drag is in the connections.

See Also

References

  1. ↑ 1.0 1.1 1.2 1.3 Practitioner observation across multi-heritage service estates; a consistent pattern rather than a measured result.
  2. ↑ Ashkenas, R. N., DeMonaco, L. J., & Francis, S. C. (1998). Making the deal real: How GE Capital integrates acquisitions. Harvard Business Review, 76(1), 165–178.
  3. ↑ Haspeslagh, P. C., & Jemison, D. B. (1991). Managing Acquisitions: Creating Value Through Corporate Renewal. Free Press.
  4. ↑ Marks, M. L., & Mirvis, P. H. (2010). Joining Forces: Making One Plus One Equal Three in Mergers, Acquisitions, and Alliances (rev. and updated 2nd ed.). Jossey-Bass.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=Inherited_Sourcing_Doctrine_in_Merged_Service_Estates&oldid=4392"