Category Archives: Procurement Innovation

Dear Fellow Independent Consultants: How Can We Dispel the PROCUREMENT STINK!

Hopefully you know by now what the doctor is talking about, but if not, as per the Sourcing Innovation article from two months ago, PROCUREMENT STINKS and we should not deny it anymore.

In a nutshell, and just is just the tip of the garbage heap:

  1. Case studies are ranker than expired fish in a microwave on high.
  2. Approximately 85% of companies are AI-washing everything.
  3. The Gen-AI claims that it will deliver Procurement to the enterprise are FALSE.
  4. Intake/Orchestration is totally useless on its own.
  5. Consultancies are often more in the dark than the Procurement departments they are claiming they can help.
  6. DEI is being misused to push agendas and sometimes to Do Extra-legal Initiatives,

And, as per a poll put out by THE REVELATOR, we are especially concerned with the fact that 14% of practitioners would rather trust a salesperson or a marketer than a consultant or an analyst! (Now, part of this is probably due to the lack of independence from many consultancies who continually pushed their vendor “partners” on the client whether or not the “partner” was the best solution, but still, it’s not ideal. [And, hopefully, as a result of the bloodbath, the consultants who weren’t offering value to their clients were the first to go.])

As far as the doctor is concerned, the most trusted advisors in the space should be:

  1. analysts
  2. independent consultants

and that’s it! No sales people, no marketers, no influencers, no made up positions. Sales people are paid to sell, not to solve problems, and marketers are paid for leads and, in some organizations, there is no correlation between “leads” and the sales funnel.

So how can those of us not at a bigger consultancy, where we would be joined at the hip to preferred partners or subsidiaries (and not recommending them results in a pink slip), dispel some of the stink and regain some trust?

The first thing the doctor wants to state is that he has even less ideas here than he does for his fellow analysts. In fact, the ideas he does have should be pretty obvious.

1. Disclose any (formal) relationships we have with vendors that are recommended.

Even if a partner is the best recommendation for the client, we must still disclose the relationship, especially if there is any additional benefit we get from the recommendation (and definitely if the benefit is financial). (In addition, we should make extra effort to demonstrate that we did thoroughly evaluate the identified alternatives and have a number of reasons for the partner recommendation that are specific to the client’s needs).

2. Create RFPs based on identified needs, not free vendor templates or analyst map outlines.

It’s critically important that we don’t take shortcuts here because vendor templates are designed to ensure that the vendor who gave the template away always comes out on top (by focussing in on the requirements that the vendor executes best) and analyst map requirements focus on a set of requirements that the analysts can use to compare vendors on the same scale, not on a set of requirements that is relevant for selecting a platform for a specific customer, or even a customer of a specific size in a specific vertical.

3. Recommend vendors based on technical fit and hard requirements, not cultural fit and soft requirements.

Just like it’s not an analyst’s job to judge cultural fit or other soft factors in their analysis (as that varies too much by company to even take a shot in the dark), it’s not our job to tell clients who is a good fit — that’s for them to decide. We’re there to tell them which companies can provide a good solution, and let them decide who they are comfortable with as they will be stuck with the vendor for 3, 5, 7 or more years (not us)!

4. Make recommendations on expected ROI for the customer, not follow-on work potential.

At bigger consultancies, where the consultant is often joined at the hip to partners (and must use/recommend their solution if it can be force-fit), they are often also pressured to making the recommendation that will lead to the most follow-on work and engagement extensions (and, preferably, long drawn-out implementations and integrations). As far as the doctor is concerned, this is one of the most egregious things you can do. Especially considering that, in Procurement, work is never done and the client will always need more advice, new technology, and more help.

If we focus on the technology that will deliver the most ROI, then we are enabling the client to generate funding for additional projects and, hopefully, make us their consultant of choice in the process by focussing on them before us. The reality is that there isn’t a Procurement organization anywhere, not even in the upper quartile of Hackett Group top performers, that has all of the resources, technology and knowledge it needs. So we should never think it’s a one-and-done situation if we do well (and, moreover, do it at a fair price-point where we deliver an ROI).

5. Don’t take on projects we’re not qualified to do.

While this might get you fired at a bigger consultancy where the motto is the traditional consulting motto of “sign now, figure it out later” (because they have enough expertise and people across enough areas to do it), we need to be better (because we don’t have expertise anywhere or a lot of people to fall back on). If we’re approached with something that’s not in our wheelhouse as a consultant, we take it to the rest of the company. If it doesn’t fit anyone’s wheelhouse, we need to politely decline the work. If it means we never get asked again, then we know that’s a client we wouldn’t want to work for as any client with working brain cells would be impressed and honoured to know a consultant who didn’t just say yes but instead thought about whether or not they could deliver enough value relative to their price tag before accepting the work.

Furthermore, if we take the time to educate the client on what our services are and where we could help, we should be the first call they make when they have the right project, and maybe even get it in a sole-source negotiation if the project doesn’t cross a mandatory public bid threshold. People worth working for value honesty, and are very likely to come back to you, either at their current company or their next company, if you are honest about what you can and can’t do and what value you can provide. (Furthermore, if you investigate the company and can identify something you could do to help them, nothing stops you from proposing that project and working with them to close that project while helping them find the right consultant for the project you can’t do.)

At the end of the day, no one ever ruined their reputation by saying no to work they weren’t suited for — they ruined their reputation by taking on work they weren’t qualified to even talk about and then f6ck1ng it up royally.

the doctor‘s not sure it’s enough, but it’s a start, and if other independent consultants make an effort to figure out how to restore our reputation, maybe we’ll find the answer, provide the value that we are engaged to provide, and get back the trust we should have.

Proper Project Planning is Key to Procurement Project Prosperity! Part 1

Ten years ago we wrote about the importance of Project Assurance, and how it was a methodology for keeping your Supply Management Project on Track (Part I, Part II, Part III, Part IV, and Part V).

We told you that Project Assurance, which takes a proactive approach and tries to identify issues, and implement mitigations, before they arise, involves the organization periodically stopping to objectively assess project failure points as they arise, typically with the help of an outside third party who can be completely objective, to identify what is and is not being done well and what could cause failure later if not adequately addressed now.

In traditional Project Assurance, there are six health assessments at six critical points in every project (for each of the six initial project phases defined by the classic waterfall project methodology). In particular, there is an assessment at each of the following steps:

  • Strategy (Pre-Presentation)
  • Acquisition (Pre-Vendor Selection)
  • Planning (Pre-Design)
  • Design (Pre-Acceptance)
  • Development (Pre-Testing)
  • Testing & Training (Pre-Acceptance)

And that the right assurance expert can help you with

  • expectation management during the strategy development
  • narrowing the procurement gap during the acquisition phase
  • aligning the troops during the planning phase
  • delineate the disconnect during the design phase
  • evaluate for acceptance during the development phase
  • tame the transition during the testing and training phase

And we stand by these posts and the importance of a third party expert helping you with the assurance ten years later, because we feel that if more companies adopted the methodology, we might not be in the situation a decade late where we still have a ridiculously high failure rate in procurement technology projects (as well as technology projects as a whole), that, depending on the study quoted, still exceeds 80% in some cases.

But we also recognize that, given the complexity of both modern Procurement (which hasn’t had so many issues to deal with simultaneously in over two decades), and modern technology, project assurance isn’t enough to save a project that isn’t planned right from the get go. (You just don’t have time to identify and fix all the problems once things get underway and you have the army of grunts simultaneously doing the implementation, all the integrations, and training as they try to rush an enterprise project that used to take two years and get it done in 9 months so they can promise payback within a year (which never happens when they do this — but that would be a different rant).

So, in this short series, we are going to dive into the project steps and help you understand what you need to do to get it as right as you can and greatly increase your odds of success.

Follow the Money — To Find the Spigots that can Turn it Off!

A recent CPO Crunch article over on Procurement Leaders said to Follow the Money as a focus on profit contribution can provide a starting point for improving supply chain transparency.

The article states that having knowledge of our suppliers is one thing, but it’s quite another to have a good understanding of who are suppliers’ suppliers are … not to mention those even further beyond and in a complex, risk-riddled world, such visibility is crucial and can bring meaningful competitive advantage.

In other words, following the money can increase profitability by allowing you to optimize the flow. Which is true, but only half the picture.

The other half is how the flow can be diverted or stopped. Two important things to remember about money flows. First, if these money flows present an opportunity for you, they present an opportunity for others. Not just outright theft of money (or product), but skimming, fraudulent billings/overpayments/handling fees (or your goods don’t move), and even fraudulent good substitution (with knockoffs). Secondly, if any input to any of these flows stops (beyond your visibility), the entire flow stops. And these flows could stop 6 levels down at the source.

For example, let’s say you are in medical device manufacturing or microwave-based manufacturing. Then you need thulium, which is one of the rarest rare earth minerals in the world. If a mine closes, even temporarily, and that mine is the only source of supply into your raw material or component supplier (that produces your enclosed radiation source or manufacturing ferrites), what do you think is going to happen? Production will stop, and your inventory will disappear. Or if you need a custom chip for the control system in your high end electric car, and the one plant currently capable of producing it experiences a fire. (This HAS happened, and chip shortages have been responsible for MULTIPLE shortages in MULTIPLE automotive lines. Just Google it.)

If your only production is in a country with geopolitical instability or deteriorating relations with your country, and borders (temporarily) close, what happens? And so on. If you don’t know the myriad of ways the spigots can be turned off, it doesn’t matter how well you know, or optimize, the money flow. These days, it’s all about risk management, visibility, and quick reaction if a spigot gets turned off to get it reopened again.

The More Things Change …

… the more they stay the same … and the more relevant the past, and the education of, becomes.

Ten years ago today, the doctor asked are you doing it wrong?

Ten years later, the question is just as valid now as it was then. Because if you were doing it right, your supply chains wouldn’t be in such disarray.

Ten years ago we noted that, if you’ve been following the media, you know that we have reached a point were most major business publications are now putting focus on Supply Chain as your top risk and your top opportunity and that they have been preaching the following solutions to not only tame the risk but increase the opportunity.

1. Comprehensive Category Management

Nothing has changed here. One consulting firm is literally sending the same email newsletters they were sending a decade ago on the topic because it’s still relevant, and most firms are still doing it wrong.

As the doctor noted a decade ago, spot buying individual categories at market lows or evening running reverse auctions at opportune times is not category management, not in the least — nor is running your buys through a “magic” or “delightful” intake-to-procure platform (better called “faketake” as a colleague of mine will point out). As was said before, Category Management isn’t just about grouping all seemingly related items and running an event, it’s grouping items that have related characteristics that allow the items to be sourced effectively under the same strategy — which could even be early renegotiation with an incumbent who might give you a great deal to keep you from going back to market. It’s taking a holistic strategic approach, not just mapping to UNSPSC or some out-of-the-box 2-level taxonomy and running with it. And not doing it is what’s resulting in stock-outs and cost-overruns. Because now, it’s not just price, it’s quality and supply assurance. Especially supply assurance. Which brings us to …

2. Supply Chain Risk Monitoring

Not much has changed here, even though the technology now exists for it to change at the majority of multi-national companies. A decade ago, we noted that natural and man-made disasters devastate supply chains when they result in raw material or product unavailability for weeks or months. When a company doesn’t understand their dependence on a single source or the risks that single source is subject too, they can figuratively get caught with their pants down to say the least. Still holds true today.

A month ago we also noted that most leading companies in the Risk Management arena are now tracking and monitoring their tier 1 supply base for not only missed deliveries, but late shipment dates and inquiring immediately when something is late shipping. However, by the time a shipment is late, it’s often too late to go to another source if the reason for the lateness is the lack of an important raw material. Multi-tier monitoring is key, but most Procurement departments are only now exploring supplier risk management in their supplier management module / application, which is tier 1 — even though we now have a number of great solutions that can monitor to at least tier 3, if not down to the source of each raw material in your supply chain. Considering that any good supplier information management solution will allow you to push in risk, compliance, performance, and visibility data, there’s no reason not to be monitoring your critical supply chains. Especially now that we can easily handle:

3. Big Data

What used to be the biggest buzzword-du-jour (before all this useless Gen-AI, desired only by Dr. Evil himself), Big Data is still desirable, but only to the extent you actually have valid, verified, data. Considering that the algorithms that actually work predict demand, acquisition cost, projected sales, etc. based on trends — unverified non-demand, cost, price data (for the wrong product) is NOT going to be of any help.

Get a real data analysis tool, validate the data at your disposal, and use it to your advantage, no more, no less.

e-Procurement Implementation Success Goes Well Beyond The Basics

the doctor was quite disappointed with this article over on the WorldBank Blogs on 10 success factors for implementing [an] e-Procurement System because all of these “factors” were generic success factors for the implementation of any technical system. Let’s look at them at a high level (and direct you to the article for a description of what the requirements are if they aren’t immediately clear to you):

Governance Principles
all projects need to be managed and governed, so this is pretty much a “d’uh!”
Transparency on Legal and Regulatory Frameworks
any platform that processes any personal, payment, or classified data HAS to adhere to Legal and Regulatory frameworks of ALL countries the corporation operates in, so this is obvious for any platform that requires it
Strategy Ownership and Sustainability
it’s classic project management, no owner, everything goes to cr@p
Implementation and Integration Challenges
preparing for this is just a given
Technical Infrastructure and SaaS-based Systems
all technology implementations need to integrate with the current infrastructure and SaaS systems that contain the necessary data, so this is pretty much a “d’uh!”
Training & Capacity Building
well, you need the capacity and the training regardless of the system being implemented
Engage Stakeholders Actively
without stakeholder support, it will be hard to get the resources for a timely, successful implementation of any technology
Align with International Standards
technology should always align with any regulatory standards in place
Clear Communication and Change Management
necessary for the success of ANY project, not just a technology project, so this is pretty much a super “D’UH!”
Data Security and Privacy
if the data is personal, payment, classified, trade secret, etc. etc. etc. then security and privacy is of more concern than the tech, so, another ‘d’uh!”

e-Procurement success goes beyond the basics. There are too many six, seven, and, for some multinationals locked into 5-year contracts, eight figure acquisitions that have failed to deliver on the promises made. This is because the selection, implementation, and utilization of such systems goes beyond most back-office tech to get right.

Selection

In our recent article on The Key to Procurement Software Selection Success: Affordable RFPs!, we noted that selecting the right vendor was paramount to success, and a critical requirement in this selection process was a GOOD RFP.

Furthermore, that RFP needed to specify, among a host of requirements:

  • typical use cases
  • target processes
  • globalization requirements
  • data migration requirements
  • integration requirements

Why are we calling these out? Because these define the key factors for implementation success!

Implementation

Key Factors are thus:

Primary Components / Modules
… that are needed to support the critical use cases and target processes, that need to be implemented and demonstrated first
Test Cases
that must be passed, in priority order, to ensure the use cases and target processes can be accomplished
… including multi-lingual use cases
that support not only the customer organization requirements but the supplier requirements
Data Migration Requirements
spelled out in detail, as well as cut-over requirements
Cross-System Bi-Directional Integration Requirements
spelled it in minute detail, not just push to the ERP … and considerably more than just a high level holistic strategy … when it comes to tech, the devil truly is in the details and chaos emerges when you overlook even one

Utilization

A system not utilized is a failed system, even if the implementation and integration goes as well as can be reasonably expected. Utilization is critical, especially early on, or widespread adoption will never be reached. This is why it’s paramount that the functionality required for the critical use cases be implemented and tested first so that utilization of key capabilities can begin as soon as possible, leading to adoption.

In other words, the basic checklist for technology implementation is nowhere near enough for the successful implementation of procurement technology — that success requires going deep.