Category Archives: Best Practices

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.

Affordable RFPs – The Real Reason(s) They Are So Rare, Part 2

Three articles ago, we noted that The Key to Procurement Software Selection Success: Affordable RFPs! was critical to getting the right technology to help manage your complex supply chain. This was because a proper RFP required a LOT of understanding to get it right, which we covered in detail in that article and summarized in Part 1. Then, two articles ago, we noted that we know all too well that most of you are asking Affordable RFPs — What Are Those? because you’ve never seen one. So in Part 1, after reviewing the requirements of a good RFP, and pointing out why you weren’t likely to get an affordable RFP from the majority of consultancies, we told you that they were still the answer because

  1. they could be affordable if Niche Consultancies stopped thinking like consultants
    and started thinking like enhanced product-and-data-based SaaS Management Providers,
  2. they only require knowledge management and expert augmentation to get it right, and
  3. if a consultancy understood this and was willing to make the necessary investment, they could quickly become a market leader.

Today we’ll explain what that means. We’ll start with the 10 types of understanding we outlined in our first article on The Key to Procurement Software Selection Success: Affordable RFPs!.

  • Procurement Maturity: the consultancy needs a maturity matrix, along with key capabilities at each level, key questions that need to be asked, and follow on questions (and contextual knowledge) to elicit the right details
  • Process Maturity: the consultancy needs a process progression flow to pinpoint where an organization is in each process, both from a human viewpoint and a technology enablement viewpoint
  • (Critical) Use Cases: not just from a standard “procurement” (“sourcing”, “supply chain”, etc.) point of view, but from an industry point of view; the consultancy needs a large library of standard (critical) use cases to build on
  • Current Technical Maturity: not just from an organizational point of view, but based on the progression of technology in a typical enterprise organization (which, of course, requires a knowledge of the history of tech to the present day along with progression flows along architecture, standards, models, etc. )
  • Missing Capabilities: based on the process and tech maturity, but also based on industry peers and leading solutions; requires all of the above AND all of the below
  • Key Solution Types to Address the Gap(s): knowledge of the standard modular / best of breed offerings in the space and related spaces, as well as knowledge of the standard must have, should have, and nice to have capabilities of each solution type, as well as the progression of technical maturity in each area; a rather extensive knowledge base will be required
  • Key Existing Solutions to Maintain: knowledge of the core, should have, and nice to have requirements of foundational ERP/MRP solutions and companion solutions in inventory, logistics, etc. (to make sure the S2P+ solutions will be enough to go to market for or if other modules / systems [and RFPs] will be needed); a more extensive database
  • Globalization Requirements: knowledge of what the e-procurement requirements are in each country the organization does business in, what languages will be absolutely necessary, what currencies will need to be supported, what government regulations there are for the products/services being sourced/sold, what industry regulations/standards need to be supported etc; internal databases or appropriate database subscriptions will be required
  • Service Requirements: knowledge of what requirements are needed for implementation, data migration, integrations, and maintenance; and how to judge if a vendor / service provider is up to the task
  • Unique Organizational Requirements: knowledge of industries and what differentiates them from a process requirement and solution requirement standpoint; detailed, but yet curtailed, knowledge in an internal database that matrixes this by industry, process, and technology solution

In other words, it means a LOT of detailed models, knowledge bases, and standard progressions as well as a lot of detailed knowledge on:

  • metrics where most organizations lie on the maturity curve(s)
  • vendors, what modules they offer, and how they stack up
  • once all of the above is racked, stacked, and mapped, what the core questions are
  • etc.

And that, of course, requires the consultancy to step up and

  • make some up-front and ongoing investments to build these knowledge bases that will
  • allow their intermediate associates to do the baseline work and
  • enable their experts to come in and finish it up in a fraction of the time compared to if they had to do most of the work themselves (i.e. 1/5 to 1/4).

This will allow most of the work to be done by the intermediate resources at a lower day rate, who will be more efficient with a knowledge base to build on, and then the expert to come in and review the work, identify the areas of weakness, and take it the last mile.

And a consultancy who saw that and made the investments could scale up their operation by allowing their top resources to be four times as productive and support four times as many customers (as well as supporting their customers through the implementation in the project, change management, data migration, and assurance roles. (We only said that they had to be vendor neutral, and not be an implementation provider for the vendor’s software. Everything else is process or organization centric, and as the experts, that’s the work they should be doing, and the most valuable work to be done.)

Again, Affordable RFPs are the answer and maybe someday we’ll see a herd of those mythical unicorns.

How Should a Provider Qualify a Client?

Carefully.

But let’s backup.

Not that long ago, THE REVELATOR penned a post that asks what are the most important things a solution provider needs to know about a practitioner-client.

This was followed by a post that asked why are some clients successful and others not.

And the answer here is simple:

The Wrong Fit.

Which means that if the provider wants a successful client, they need to make sure the client is the The Right Fit and that they, as a provider, have The Right Stuff.

It’s not about the size of the cheque the client can write, it’s about the size of the value the provider can deliver, because if the provider can’t deliver value, there will only be one cheque. But if the provider does a great job, the cheques will keep coming year after year after year. And those cheques will get bigger over time. (A successful organization focusses on lifetime value, not one-time value.)

So, how does a company qualify a client?

In the comments, the doctor outlined a few key points that included:

  • what problems is the client looking to solve (and why)
  • what problems should the client be looking to solve (and why)
  • are those problems the provider can appropriately solve at a price point the client can afford, at a TQ (Technology Quotient) level the client can handle, and at a realistic ROI both parties can be happy with

But first, the provider needs to answer the following:

  • what problems does their solution solve, and solve well
    … and do they have successful clients they can point to
  • what processes do the successful clients follow,
    and can those processes be easily adopted by other organizations
  • what culture does the company have, and what cultures does the provider mesh with

And then, the provider needs to figure out:

  • if the problems the client is looking to solve are the problems the client should be solving
  • if not, can the client be educated into the problems they should be looking to solve (and can the provider accomplish that)
  • are the client’s problems appropriate to the provider’s solutions
  • and will the client adopt the right process modifications
  • and, finally, will the companies cultures mesh

And if any of these questions come up no, the client is not one the provider should take.

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.

Affordable RFPs – The Real Reason(s) They Are So Rare, Part 1

Two articles ago, we noted that The Key to Procurement Software Selection Success: Affordable RFPs! was critical to getting the right technology to help manage your complex supply chain. This was because a proper RFP required a LOT of understanding to get it right, including, but not limited to:

  • Procurement Maturity
  • Process Maturity
  • (Critical) Use Cases
  • Current Technical Maturity
  • Missing Capabilities
  • Key Solution Types to Address the Gap(s)
  • Key Existing Solutions to Maintain
  • Globalization Requirements
  • Service Requirements
  • Unique Organizational Requirements (less than you think, but those that exist are situation critical)

And this required a breadth of understanding across

  • the market
  • process evolution
  • use case specification
  • … including what must be technology backed
  • … and what should be technology or data enhanced
  • common module/solution types that mind the gap
  • internal foundations
  • the unique requirements, regulations, and resignations of each country you do business in
  • the services your team, and current partners, can and can’t do — even service specializations you didn’t know exist
  • what other organizations do

And most of this you won’t have in house. So you need Affordable RFPs. But we know all too well that you are all asking Affordable RFPs — What Are Those? because, as far as you know, they don’t seem to exist. And we hear you, because they rarely exist at mid-sized and larger consultancies  (because only a select few from their talent pool can do it efficiently and relatively cost-effectively and those resources with deep experience are going to be dedicated to any F500/G3000 that can afford to pay the A rates to keep them as a dedicated advisor), and unless you are a larger mid-size buying a mini-suite, they don’t even exist at the Niche Consultancies where they should be common.

We also spent a fair amount of time explaining why they don’t exist, even though one would think that they should be readily available at the niche consultancies (as this could not only make those niche consultancies true leaders in Procurement but also help them grow). In this last case, it was because it was typically only their senior resources that could do these projects, and since these projects aren’t currently quick to complete, it doesn’t take long for a senior resource day rate to add up. And, as we noted before, while this won’t be that much when you are larger mid-sized organization looking for a mini-suite or suite, if you’re just looking for one or two modules to fill a gap, this could add up to quite a bit.

So if this is the case, why are we telling you that Affordable RFPs are the answer if they’re almost impossible to find?

Because:

  1. they are the answer,
  2. they would be affordable at Niche Consultancies if those niche consultancies stopped thinking like consultants and started thinking like enhanced product-and-data-based SaaS Management Providers, and
  3. they only require knowledge management and expert augmentation to get it right.

So what would a Niche Consultancy have to do to get it right?

We’ll outline that in our next part. But it starts with investment. (And how many partners at consultancies want to invest their money? They were brought up on the Wall Street Mantra — Other People’s Money.)