The Key to Cost Reduction? Capture the Flag! Part III

In this series we have been discussing how Procurement is in vogue but that the only reason it is in vogue is because organizations need cost reductions and/or greater profit, and Procurement is currently seen as the ultimate path to profit. As a result, Procurement technology providers, GPOs, and consultancies — particularly those consultancies with a track record — are getting a lot of interest, and in the cases of some technology players in particular, a lot of money.

But not all companies are getting the returns they expect from their S2P platform, and it’s not always the fault of the provider — it’s often the fault of the data. Bad data. Dirty data. Data that causes you to miss over billings and duplicate billings, opportunities for volume consolidation, opportunities to spot new trends, and so on.

But how do you get that data under control? Especially when most systems allow any user to enter any data they want in description fields, not populate key SKU or cost center fields, and so on.

The traditional answer has been process, but process has continually failed, especially when organization’s have tried to scale it.

So what is the right answer? It’s hard to say, but it becomes less important if the opportunity for creating bad data is minimized. So how do you do that? You minimize the need for the end user to enter data in the first place.

This means you need a P2P system that not only minimizes the need for end users to enter data, but makes it easy for the admins to correct any oversights that would result in the end user entering data.

So what are the requirements for such a P2P system?

It depends on not only what you are buying but how you are buying it — for whatever procurement functions you support, they must be designed to minimize, if not eliminate, data entry. For example, if the organization has a lot of MRO and back-office purchases, the catalog must be complete, easy to maintain, and guide the buyer to the needed product, not an e-Form or RFX. If the organization needs a lot of services, then there should be well defined e-Forms for requesting standardized services which have all the requisite details, codes, and descriptions. If the organization needs specially configured products (like cars, computers, etc.), there should be standardized requests to preferred suppliers or standardized RFXs. And so on. The less user entered data, the better.

Moreover, it’s not just buyer users who create user error, its supplier users as well. So such a system must minimize the data required by the supplier. Once the supplier receives a PO, they should be able to simply and easily flip acknowledgements, shipping receipts by checking the boxes (and only overriding quantities if needed), invoices (from POs or shipping receipts), payment receipts, etc. with button clicks. The less, the better.

Anything that can be standardized and entered once should be standardized and entered once. And anything that isn’t standardized should go through a review queue to see if additional standard products, services, forms, etc. can be added to minimize future data entry requirements. The goal is single entry, and the use of correct single entries, as much as possible.

Only when data is under control can savings be identified, and realized. And only then will you have captured the flag.

The Key to Cost Reduction? Capture the Flag! Part II

As per our previous post, Procurement is in vogue. But, as we bluntly stated, only because organizations need cost reductions and/or greater profit, and Procurement is currently seen as the ultimate path to profit. As a result, Procurement technology providers, GPOs, and consultancies — particularly those consultancies with a track record — are getting a lot of interest, and in the cases of some technology players in particular, a lot of money.

And the money is deserved if those providers deliver the ROI they promise. But the ROI only materializes in the right circumstance when the solution is properly applied, but this is the kicker. Right circumstance, proper application. And this is easier said then done. Because the proper application of the solution needs to be applied from the start of the, strategically chosen, sourcing project to the final procurement of the final product or service deliverable.

Because, as we indicated in our last post, sourcing only singles out the savings opportunities, which should be negotiated and put into a contract, it doesn’t realize them. That’s the job of Procurement.

But Procurement can’t do it’s job without good, clean, relatively complete, data. But that’s something it rarely has. Procurement usually has bad, incomplete, scattered data which is often more misleading than not having data at all and going on a whim.

Typical POs consist of just buyer SKUs, typical invoices contain either (different) supplier SKUs or short descriptions, what gets entered into the AP system is usually a buyer’s shorthand for this, and then when it comes time to m-way analysis or spend analysis, it’s almost impossible. The data is bad, incomplete, and, simply put, dirty.

And, as a result, m-way matches fail, over-billings don’t get detected, overspend happens, and the strategically negotiated savings don’t get realized. Plus, as more and more data gets mis-classified, opportunities for spend consolidation don’t get identified since the true spend on a product, category, or supplier is never known.

But over-billings and lack of spend consolidation or strategic sourcing opportunities is just the beginning. The bad data can lead to poor procurement decisions when the wrong data is in the catalog (and an off-contract item is chosen when such a purchase should have been prevented), when not enough data leads to the selection of poor service providers who deliver inferior services, and when insufficient specifications result in large project, and thus cost, overruns.

There’s a reason why many organizations are still losing 0.30 to 0.40 on every dollar of negotiated savings, and it’s not (just) bad Procurement, it’s (bad) Procurement data. So if you want to capture the flag, you need to get your data in order.

But how do you do that? We’ll tackle this topic tomorrow.

The Key to Cost Reduction? Capture the Flag! Part I

Procurement is in vogue, but only because organizations need cost reductions and/or greater profit, and Procurement is currently seen as the ultimate path to profit. As a result, Procurement technology providers, GPOs, and consultancies — particularly those consultancies with a track record — are getting a lot of interest, and in the cases of some technology players in particular, a lot of money.

But do they deserve that money? Maybe, maybe not. It all comes down to the ROI delivered. Much of the technology out there is capable of delivering a good, if not great, ROI in the right circumstance when properly applied, but this is the kicker. Right circumstance, properly applied.

An e-Auction won’t save a penny applied to a category for the third time in a supplier’s market during inflationary times. In fact, it will likely result in a cost increase. An RFX will do nothing if the perceived value thereof in the recipient suppliers is not worth the cost of response. An optimization will do nothing if there is not enough data or the model is not properly constructed. An e-Catalog will be useless if the contracted product is not contained at the right price. And so on.

Moreover, the proper application of each technology product purchased requires the proper data. RFXs need appropriate supplier contract data to be delivered, proper questionnaires to collect the data, and proper cost models to collect the data, the application will never be properly applied. This goes double for optimization.

But this is only the start of the data debacle in many organizations that prevent procurement pursuits from delivering the sought after savings. Bad data doesn’t just stagnate sourcing, it also prevents proper procurement. Sourcing only singles out the savings opportunities, which should be negotiated and put into a contract, it doesn’t realize them. That’s the job of Procurement.

And that’s where you have to capture the flag!

At least Twenty Two Hundred and Sixty Five Years Ago Today …

The Pharos of Alexandria was constructed. Estimated to be over 100 meters in height, and one of the Seven Wonders of the Ancient World, it was built on the island of Pharos opposite the isthmus on which Alexander the Great founded the city of Alexandria. The lighthouse was commissioned by the Ptolemy I after the death of Alexander, and due to its location, it not only guided ships by day and night but secured safe access to the city of Alexandria.

We bring this up to show the long history of lighthouses, which to this day are important in the prevention of ships hitting the rocks and wrecking off the coast (like the Stephen Whitney did One Hundred and Seventy Years ago today off the southern coast of Ireland (killing 92 of 110 on board). And while the wreck resulted in the construction of the Fastnet Rock lighthouse, an early example of an oil burning lighthouse (replacing the previous wood or coal lighthouses). And while it didn’t have the brightness of the kerosene burning lighthouse that would replace it, it was a great start.

Because the ability to see in the dark is valued, especially at sea. And this is an extremely relevant metaphor to procurement often lost in a sea of data with no ability to see where the rocks are. This is important because without sight, not only will your organization not realize the Procurement Innovation that is to come we have been discussing all week, but it won’t even realize the opportunities available it today.

Stay tuned.

Procurement Innovation The Day After Tomorrow

This week has been all about Procurement Innovation and how maybe it’s a good thing that They Terk Er Jerbs! as the only jobs that are perfectly suited for software and robotic automatons are those that we really don’t want to do. Let them match line items. Let them scan barcodes. Let them push e-paper all the live long day. No one writes folk songs about the paper drivin’ man, so they can have the damn e-paper.

But they won’t stop at automatic e-paper or transaction mapping or even invisible buying. They will go deeper. They will go broader. They will take all that can be taken with computation alone. Wherever true intelligence is not needed, they will emerge. So where else will they emerge?

Software and the machines will be everywhere, in every job, and they will be there all the time. 24 / 7 / 365. They won’t be able to do everything, but they will be everywhere. In a presentation last week, the doctor covered a dozen different areas we’ll see them today, tomorrow, the day after tomorrow, and the day after that … just in Procurement alone. And these weren’t all the examples. We won’t cover them all in this blog (and if you want to know them all, keep your eyes out for an upcoming talk), but we will cover one today.

Specifically, once invisible buying is out of the way, one area they will considerably invade the average Procurement organization is through tail spend minimization. Not only will invisible buys take a chunk out of organizational tail spend, but all of that calculation will also identify

  • other buys that fit the MRO / regular re-order pattern that should be put under contract / rate card and left to invisible buys
  • buys that are becoming significant and should be analyzed for strategic sourcing

Not everything will fit in these 3 categories, but a big chunk will … and then further enhancements will take more and more out of tail spend until it becomes a vanishingly small part of organizational spend compared to what it is today. So watch for the future, it’s coming faster than you think.