McKinsey published their latest enterprise procurement transformation report and most of it is right. Strategic sourcing centralization. Spend analytics. Supplier risk management. AI-augmented contract workflows. ESG integration into supplier evaluation. The framework is solid and the case studies are real. There is one category of indirect spend where the report's prescriptions fail in practice, and that category happens to be where my customers and I live every day. Here is the gap, why it matters, and what to do about it if you are running a procurement function and trying to apply McKinsey's framework to a workwear or branded merchandise program.
What McKinsey gets right.
The report's core argument is sound. Enterprise procurement functions have spent the last 15 years optimizing for spend visibility and contract leverage, and they have largely succeeded on direct spend categories. The next horizon is indirect spend.the long tail of categories like office services, professional services, marketing, IT consulting, branded goods, and yes, workwear. The report identifies the standard tactics: category council governance, supplier consolidation, e-procurement platforms, integrated spend analytics, AI for contract workflows. All of this is right for most indirect categories.
The case studies in the report show category-level savings of 12 to 24 percent on consolidated indirect spend. The math is real on most of the categories cited. Office supplies. Travel. IT consulting. Marketing services. All categories where the standard strategic sourcing playbook compresses fragmented supplier bases into managed ones, and the savings show up on the spend line.
What they got wrong.
The piece the report misses is what I will call the "operational program" subset of indirect spend. Workwear programs. Branded merchandise programs. Safety PPE programs. Uniform programs. These categories look like indirect spend on the surface, and they should respond to strategic sourcing tactics in theory, but in practice they do not behave the same way as office supplies or travel.
The difference is operational. An office supply category is a buying relationship. A workwear program is a running operation. The vendor in the office supply category fulfills orders against a catalog. The vendor in the workwear program runs an embedded operational service: inventory management, lifecycle tracking, regulatory documentation, regional distribution, fitting coordination, compliance audits. The buyer in the office supply category is a procurement analyst. The buyer in the workwear program is the procurement analyst and the safety officer and the operations manager and the regional supervisor.
The strategic sourcing playbook.consolidate suppliers, drive unit cost down, manage by KPI scorecard.works for categories where the buying relationship is transactional. It breaks for programs where the buying relationship is operational. When you apply the playbook anyway, you end up where the FR account I wrote about earlier ended up: a vendor optimized against the wrong objective function, a program drifting in substance while the scorecard improves on paper, and an eventual program failure attributed to the vendor that was actually caused by the procurement framework misapplied.
Why McKinsey's framework misses this.
The reason is structural. McKinsey's procurement transformation engagements are scoped by spend category. The team running the engagement is incentivized to demonstrate savings on the category P&L. The savings are easier to show on direct, unit-price-driven categories than on operational programs. The natural consequence is that the framework recommends what works on the easier categories, and the operational program categories get pushed into the same template even when the template does not fit.
It is not a malicious oversight. It is a methodology problem. The consultants doing the work are not in the field at the compressor station watching the worker who got the wrong-size FR coverall delivered through the consolidation initiative. They are looking at the spend roll-up showing the consolidation savings. From their seat, the program looks like a win. From the safety officer's seat, the program is leaking compliance documentation and the workers are quietly complaining and nobody is escalating the operational problem because the scorecard says everything is fine.
What to do about it.
- Carve operational programs out of the standard indirect spend template. Workwear, uniform, safety PPE, and branded merchandise programs deserve their own governance and their own scorecards. Apply the strategic sourcing playbook to office supplies, not to FR.
- Add program-substance KPIs to the scorecard. Compliance documentation completeness. Regional inventory match to actual exposure. Safety officer time saved. Worker fit-out completion rate. These metrics tell you whether the program is working, not just whether the invoices are correct.
- Build a dual-reporting model. The vendor reports to procurement on price and contract performance, and to operations on program substance. Both reports get reviewed quarterly. Neither one is the master.
The bigger pattern.
This is a generalizable critique that applies to most enterprise consulting frameworks when they meet operational programs. The frameworks are built around categories that respond to spend optimization. The operational programs require something different. The procurement leader who recognizes this carves out the operational programs and runs them differently. The procurement leader who does not ends up implementing the McKinsey framework across all of indirect spend and watching the operational programs degrade quietly over 18 months while the scorecard improves.
The report is worth reading. The framework is worth applying to most of indirect spend. The gap is real and worth knowing about before you apply it to your workwear program. If you are 12 months into a strategic sourcing implementation that swept workwear into the standard template and you are starting to hear complaints from your safety officers and operations leads, this is the diagnostic. The framework is mostly right. The category boundary is the part that needs adjusting.