The First CPO at a Decentralized Group

Reject both extremes. Full centralization would trigger the resistance already visible and would fail on local knowledge in a group with 12 distinct operations. Full decentralization has produced the 18% price variance and 41% expired contracts, so it is not a baseline to defend. Recommend a center-led model with clear decision rights.

Design.

• Category management at group level for the top 15-20 categories covering roughly 65% of the $620M - direct materials, logistics, MRO, IT, professional services. Category managers own strategy, sourcing events and supplier selection; business units execute and own local service levels.
• A center of excellence for analytics, contract management, supplier risk and e-sourcing tools. This is where the four hires go: two direct-material category managers, one analytics lead, one change and communications lead.
• Business unit procurement retained for local buying, expediting and operational supplier management, with delegation-of-authority thresholds set in writing.
• Category councils with a BU representative on each, chaired by the category manager. They are consulted on strategy and informed on execution; they do not hold a veto.

Sequencing matters more than structure.

• Months 0-3: baseline spend, consolidate supplier data, deliver two or three visible quick wins in MRO and logistics where the variance is already measured. Cost-neutral in year one is met through headcount redeployment and tooling consolidation, not through savings that have not landed.
• Months 3-9: category strategies for the top eight categories, run as waves with finance validating savings before they are counted.
• Months 9-18: contract implementation, supplier consolidation, and SRM for the top 30 suppliers.

Decision rights document. Write down who decides, who consults and who is informed for each category and each spend threshold. Most center-led failures are governance failures, not design failures.

Diagnose the objection before answering it. The stated objection is speed; the underlying concerns are usually loss of control, budget ownership, and being held accountable for service levels they no longer control. Address the underlying concerns, not the stated one.

Start with the one who is engaged, not the one who is refusing. Use the logistics contract as a pilot with the other two units. Publish the actual numbers - the 18% MRO variance is already a shared fact - and let the result create the argument.

Make the shared contract safe for the holdout. Offer written service levels, a named local contact, a 30-day exit or re-entry clause at the first renewal, and a guarantee that their unit's delivery performance will not fall. Offer them the chair of the logistics category council, which gives them influence over specification and supplier selection without giving them a veto. Give them the choice between joining the sourcing event and running their own - and show the price difference between the two options rather than asserting it.

Share the credit and the savings. Agree in advance how savings are attributed and whether they stay in the BU P&L. If centralization takes the savings out of the BU budget, every BU president will resist regardless of the business case. Publish a savings-sharing rule before the first wave.

Escalate once, late and with data. Do not open with the CEO. If the holdout still refuses after a written offer of safeguards, bring a one-page decision paper to the CEO with the price gap, the service protections offered, and the recommendation. Use escalation once; repeated escalation converts a commercial disagreement into a personal one.

Protect the relationship. The CPO needs these people for the next five years of category plans. Winning the logistics contract but losing the relationship is a net loss.

Roadmap.

• Months 0-3, establish credibility: spend cube, supplier master cleansed from 3,400 toward a managed core, delegation-of-authority signed, two quick-win sourcing events in MRO and logistics, savings baseline agreed with Finance.
• Months 4-9, build the engine: category strategies for the top eight categories covering about 60% of spend, 12 sourcing waves launched, contract remediation on the 41% expired, four hires onboarded.
• Months 10-18, land and sustain: contract execution, supplier consolidation in the top 30 relationships, SRM scorecards, compliance monitoring, wave two for the next eight categories.

Savings build. $620M x 5% = $31M. Be explicit about where it comes from: price variance elimination in MRO and indirect (roughly 30% of the target), direct-material sourcing waves (roughly 45%), contract compliance and maverick spend recovery (roughly 15%), and demand and specification management (roughly 10%). A target with no bottom-up build is a number, not a plan.

Metrics.

• Realized savings validated by Finance, reported in the P&L, not just negotiated.
• Spend under management: percentage of $620M on group-negotiated contracts and under active category strategy.
• Contract compliance and the count of expired contracts, from 41% to under 10%.
• Supplier consolidation: active suppliers from 3,400 to a targeted number by category.
• Cycle time from requisition to contract, and BU stakeholder satisfaction, because the resistance will resurface if service degrades.
• Cost neutrality in year one: procurement operating cost against savings delivered.

Reporting cadence. Monthly to the CFO with the savings bridge reconciled to the finance ledger, quarterly to the CEO with the roadmap, risks and BU adoption. Never report a saving that Finance has not signed - the first disputed number destroys the credibility the whole model depends on.