Category Archives: rants

Procurement Won’t Advance Until We F*CK SAVINGS!

… and, in the same breath, F*CK CONSULTANCIES THAT ONLY PUSH SAVINGS!

Recently there’s been a big push by some parties, including Procurious, to lead Procurement into the future, and in Procurious case, it was through an online Big Ideas Summit where they convinced a number of individuals to webcast to digital attendees on the same day on Procurement topics. But Procurement is not going to go anywhere until we first deal with the number one problem, and that is our continual focus on savings because of management’s continual mis-focus on savings.

the doctor is as appalled as the public defender (who blogged his dismay in “Bain Company Insights”) to find out that yet another big consultancy, in this case Bain & Company, recently published an article on Unearthing the Hidden Treasure of Procurement that classified the value of Procurement as the good old consultant’s snake-oil of basic spend aggregation, consolidation, and tough-negotiation to find savings.

Which is another crock of bullsh!t. (Seems we’ve been blogging about those quite a bit lately! But I guess someone has to!) The value of Procurement is cost-control (not savings), demand management, product-and-service-normalization, and overall value generation and maximization. NOT SAVINGS! First of all, there is no such thing as savings — “savings” just means you are paying more than you should. Secondly, anyone who applies proper Procurement principles to a category for the first time can quickly get prices down (near) to market pricing. Thirdly, and most importantly, as the public defender points out, there is no such thing as savings anyway as all savings, and especially those savings that resulted from bringing initial prices below market average, will be clawed back by suppliers, or the [the] new supplier / product [will] turn[s] out to be unsuitable, or oil prices [will] rise or something else happens (like a disruption from new supplier / carrier unreliability).

And this brings us back to our secondary thesis, not only do we have to F*CK SAVINGS but F*CK CONSULTANTS THAT ONLY PUSH SAVINGS! Only two types of consultants push savings, those that don’t know any better (and will not help your organization grow over the long term) and those that have learned the best way to make easy money is to just push the savings agenda because that means that you can re-source the same category every two or three years and if you split the categories appropriately, you will have re-sourcing work negotiating savings on the same categories forever more (because, as costs rise, new, fake savings opportunities will re-appear)!

The only way to move Procurement forward is to shift the focus from cost savings to value creation, with a focus on cost-control (and avoidance, but not savings), demand management, appropriate value-add selection, new supplier identification, and joint product/service innovation — where the real organizational savings will come from. And, as we indicated at the beginning of this post, the only way this will happen is if Procurement forces the conversation away from savings and towards value, regardless of the cost and how many big consultancies we have to tell off in the process!

All Aboard the M&A Train!

It seems that the M&A train, once sporadic, is now running on a regular schedule (thanks largely to Coupa and it’s 1B valuation that allowed it to raise enough cash to scoop up providers left, right and center). Is this good or bad? The answer is it all depends who you are.

Generally, when a company buys another, it does so with an objective in mind that, should the acquisition help it to complete the objective, helps the buyer and usually the set of customers that the buying company wants to satisfy. This might also include a sub-set of the acquired’s customers, which would then be helped in the process, but may also exclude a set of the acquired’s customers, which would not be help. Then there’s the acquired. Depending on the strength of the company, the goals of the management / owners on acquisition, and the alignment with the buying organization, it might be a good thing, or it might be a bad (or very bad) thing.

What do we mean? Let’s take each affected group at a high level and indicate what could be good or bad.

Buying Company

Potential Positive: New Technology

New technology offers the buying company a host of potential benefits including, but not limited to, new technology to sell its current customer base, new technology to bolt onto in a potentially new customer base, and process insights it did not have before.

Potential Negative: Dis-satisfied Customer Base

Expanding the customer base is not always a positive if the customers being acquired are not happy customers from the get-go. Even if the customers are happy, they might be unsettled by an acquisition …

Buying Company’s Customers

Potential Positive: New Technology

Not only does the buying company have new technology to sell, the existing customer base has new technology, that they might desperately need, to buy, and, moreover, they might also be able to buy at a discount because they are already spending with the vendor.

Potential Negative: Less Support

If the company acquired an unhappy customer base, all of the resources might be tasked with making the acquired customers happy because the company was acquired for those customers. This means that support for current customers would drop. And that’s not good.

Bought Company’s Customers

Potential Positive: Vendor has a bigger piggy bank

If the acquiring company has more resources, those could be spent improving the situation for the bought company’s customers. Better support, tech upgrades, more integrations, etc.

Potential Negative: Acquiring company is Mega-co

… and acquired company is mini-co, acquired only because it’s technology posed a future threat and mega-co decided the best risk mitigation was to buy mini-co when it was small and cheap with just a few customers as the acquisition cost dwarfed the potential losses to market share if mini-co succeeded in their efforts. In this case, Mega-co wouldn’t care at all about the customer base and could just ignore them completely.

Bought Company

Potential Positive: Bigger Piggy Bank

… which could be used to further the mission … but

Potential Negative: Lack of Support

… if the mission of the bought company does not match the mission of the buying company.

So what does this mean for Coupa, Trade Extensions, and their customers? the doctor knows you want to know, but the doctor will not provide his thoughts until the acquisition is complete.

A Great UIX is MORE than just a Version Number

… and MUCH MORE than just a minor version number!!! Soon after the doctor and the prophet published the first part of their UIX guide, the doctor received a copy of a mass email from a vendor claiming that they couldn’t agree more and that their new release, X.Y+0.1 now met that requirement. Pretty bold claim!

As we haven’t yet reviewed the current release, we can’t comment, but we imagine that it would not be that much different than X+Y, which we did see. Now, we’re not saying in this case that X+Y wasn’t good, it was, or that the vendor won’t be a leader if it participates in the upcoming solution maps, as it has as good of a shot as anyone else, and probably better in some ways, but UI and UIX doesn’t change over night, and definitely doesn’t change much on a minor, almost quarterly, release cycle.

And a bold claim like this, especially a bold claim coupled with a minor release, can cause the vendor more harm than good as it can lead to unrealistic expectations in the mind of analysts and, more importantly, potential customers that might then hold it to an unrealistic standard when evaluating the solution than the analysts, and more importantly, customers would otherwise convey upon the solution. This could cause the vendor’s solution to be scored lower than it should be, and even lower than an inferior solution from a competitor (as compared against the customer’s specific needs) which would then be, incorrectly (with respect to the customer’s specific needs) chosen.

Moreover, a great UI / UIX does not need to be sold — one look and the UI/UIX and it sells itself. All a vendor with a great UIX needs to do is promote all of the great things the solution can do and all of the processes that it solves and get in front of the potential customer. That’s it.

Remember, as Scotty always said, under-promise, over-deliver. After all, how else do you expect to get a reputation as a miracle worker?

UNSuitable Procurement Spend Classification!

Brian Seipel of Source One Management Services recently shared his Pros and Cons of using UNSPSC for spend classification, indicating that the best taxonomy for you, including UNSPSC, was determined by your primary goal.

According to Brian, if your goal was to hit the ground running fast and base analysis on a tried-and-true standard, then UNSPSC was a great start because, as a standard, it is:

  • pre-developed and ready-to-use,
  • capable of expressing a good degree of granularity, and
  • widely available from vendors and a significant number of data enrichment options exist.

And this sounds great, but, any services vendor with a spend analysis offering (Insight Sourcing Group – SpendHQ, Spendency, Sievo, etc.)

  • has one more standard taxonomies designed for Procurement that it has been using for years and years (that has been refined across dozens, if not hundreds, of clients) and that it regularly achieves great results with
  • and these taxonomies are highly granular, usually to at least four levels of detail, and sometimes more and
  • can be enriched from dozens of sources using pre-defined mappings that the expert spend services group has ready-to-go

And when you look at it this way, there are really no benefits. (Well, there is one benefit to UNSPSC, and that is easy H(T)S code mapping, but that’s a Finance/AP benefit, not a Procurement one!)

However, the benefits of a custom Procurement taxonomy:

  • alignment to organizational Procurement/Sourcing needs
  • flexibility and capability to be re-organized on the fly
  • ability to support different levels of granularity in different categories (so that drill down is only available where it makes sense)

can not be found in UNSPSC. It’s one rigid unaligned structure. It can’t be remapped and re-organized as needed to support changing spend responsibility (such as department-specific IT services being taken out of IT spending and mapped to the appropriate departments). And the granularity cannot be altered. Allowing spend to be analyzed in some cases down to nonsensical levels.

So while it may be standard and universally supported (and even useful from a Finance/AP point of view), it really is an UNSuitable Procurement Spend Classification. So, when it comes time to do spend analysis, do NOT use it. (Select a system that supports multi-classification and finance can have their UNSPSC pound-cake and you can have your feathery souffle.) Are we clear?

(And yes, if asked, even consultants who do not like UNSPSC will say it’s a reasonable option because they are told to never directly contradict a client who signs the cheque, and if the CFO who signed the PO wants it, for whatever half-baked reason, guess what is all of a sudden a viable option … )

We Don’t Need Another Hero!

the doctor‘s response to the public defender‘s post on “What’s the Future of Procurement? How the Rogues Will Become the Heroes”

Out of the ruins
Out from the wreckage
Can’t make the same mistake this time
We are the relics
The last generation
We are the ones they left behind
And I wonder why we are always after change
Dancing around the way, till nothing pure remains

We don’t need another hero
We don’t need to know the way forth
All we want is rules stopping
Mavericks

Looking for something
We can rely on
There’s gotta be something better out there
Rules and processes
Their day is coming
All else is descriptive vapourware
And I wonder why we are always after change
Dancing around the way, till nothing pure remains

All the stoics say
We don’t need another hero
We don’t need to know the way forth
All we want is rules stopping
Mavericks

So what did we do with our lives
If we don’t leave our mark
Will our story shine like a light
Or end in the dark
Give it all or nothing

We don’t need another hero
We don’t need to know the way forth
All we want is rules stopping
Mavericks

While flexibility, collaboration, and innovation are to be nurtured and cherished … if the system is the workaround, then something’s wrong …