Category Archives: Talent

How Many Employees Should You Have in Procurement

Those of you who have been around for awhile will know that AQPC, Hackett, and, going way back AMR, and Aberdeen, among others, have been benchmarking and telling us for years how many employees your Procurement Organization should have based on organizational revenue.

Furthermore, those of you who have been paying attention will know that they’ve been telling you for years that the better you are, the less employees you should have.

And you probably believe them. But, THEY ARE WRONG!

Why?

All of these employee count recommendations were based on two fundamental assumptions.

1) You can automate your way to baseline, as every improvement in automation will allow you to shed employees.

2) Baseline is sufficient to maximize Procurement value.

The first assumption is true. As you automate the thunking, more and more tactical processing that requires no actual thinking is offloaded entirely onto the machines, and those resources are no longer needed for those tasks. At this point, you can redeploy them, or you can follow the crowd and reduce the headcount (while remembering that the true wisdom of crowds is that none of us is as dumb as all of us). (We’re not saying that you shouldn’t let the employees go. It all comes down to whether or not they have the skills to be redeployed in a value generating role. But more on that later. We are saying that you should think twice before reducing the headcount target. More on this later.)

The second assumption is false. Baseline is considered to be enough for an average organization to source the top 80% of their spend over the average contract window and sufficiently manage the critical suppliers.

But simply having enough headcount to do baseline sourcing events and manage a few suppliers is not necessarily enough to guarantee value. And that’s what it comes down to. Value.

If the buyers barely have enough time to setup and run the events, but don’t have any time to discover or qualify new suppliers, negotiate beyond initial bids, or work with existing suppliers to identify additional opportunities for cost saving (such as minor design/spec changes) or value creation (such as new value added services), then are they really providing any value (beyond simply adopting a bleeding edge sourcing platform that can automate an entire sourcing event and reducing headcount even further)? No, they aren’t.

Now that inflation is back with a vengeance, in any managed category, savings is out the window. The absolute best case scenario is you keep costs flat, but most of the time the best you will be able to do is reign in increases less than the market average increase (and less than your peers). So if you want, or need, savings, you need to redefine the category, the product, the service, the delivery, the network, etc. That takes a lot of expertise, creativity, focus, and time from true Sourcing professionals … focus and time they won’t have if they have to launch a new sourcing event every week because you are measuring Procurement success based on how low the headcount can go and not how much value Procurement can generate.

Similarly, if all buyers have time to do on the supplier management side is deal with critical issues and the fires that arise because of them, you’ll never get real value out of the relationship, never build the relationship to the point where you co-innovate and jointly take cost out of the supply chain, become a true customer of choice (and not a fake one based on standard contract rhetoric which only guarantees they won’t screw you in pricing more than any other customer), and never discover capabilities in your supply base that you never new existed (… capabilities that may allow you to offer new products and services with a greater profit margin).

Plus, if you’re only tackling the top 70% to 80% of spend and the top 10% to 20% of suppliers, what opportunities for significant spend reduction, or at least control, are you missing. There’s often more overlooked opportunity in the tail than the middle categories. And you’ll never know the true extent of the potential in your supply base if you only ever talk to 1 in 10 suppliers.

The right amount of headcount is the number of professionals that add value and an ROI 3X to 5X their fully burdened FTE cost. the doctor would hazard a guess that the right number is probably 2X what AQPC, Hackett, and others would have you believe. Look to these reports to understand what percentage of tactical headcount can be redeployed with the right automation, not for the right number of strategic headcount to retain. (Based on the current numbers, you should be able to redeploy 80% of your tactical head-count as you go from the bottom to best in class, but you only start redeploying headcount out of Procurement when adding more strategic resources doesn’t increase value at a 3X to 5X ROI.)

There’s Some Really Awful Procurement Job Seeking Advice Out There — Truly Awful!

On a weekly basis, the doctor scours the internet for recent developments and news in sourcing, procurement, and supply chain that major publications, analysts, bloggers, and the major LinkedIn trolls … errr … influencers might have missed. If you follow a half dozen thought leaders, analysts, major sources, etc., you won’t miss much, but deep searching can sometimes dredge up interesting tidbits, and other times can dredge up decaying waste that really should be left in the deep.

Recently, deep searching for procurement news dredged up one of the worst Procurement job seeker interview questions and answer articles he’s ever read. (These are bad in general, but if I was hiring, and you gave a single one of these answers, I’d end the interview then and there. You would have clearly demonstrated you do NOT have what it takes to survive one of the hardest back-office jobs there is, with new, unforeseen challenges arising daily.)

I’m not going to link to the article in case the author is a real person who was assigned the grisly task by the publication of writing about something they clearly had no clue about and not auto-generated by a BS OpenAI tool trained on the worse mush it can find, because they don’t deserve the embarrassment if they are a person assigned to write about a subject they were clearly clueless about. However, I am going to quote the first three questions and responses and point out why any Procurement Director worth their weight in any commodity would quickly judge you as unworthy and show you the door, before it had time to finish closing, if you rattled off one of these extremely poor canned responses presented to you.

Q1: Describe your previous experience.

Not a bad question (but the interviewer should ask you about unique aspects of your relevant experience). But

With a background of over 10 years in procurement, I bring comprehensive experience spanning various aspects of the field. My expertise includes sourcing, supplier management, contract negotiation, and administration. Throughout my career, I have consistently delivered noteworthy cost savings and streamlined processes. Additionally, I possess in-depth knowledge of both local and international procurement laws and regulations.

Is NOT a good answer.

1) Presumably if you are applying for a senior procurement role, you have significant relevant experience, how many years you have is going to be clear from your resume, and if you don’t meet a baseline, you don’t get the interview. More meaningful is related experience that brings unique insights to the role.

2) Buzzwords are meaningless. If you don’t have any experience in sourcing, supplier management, or contracts, you’re not Procurement. This is super obvious. If you don’t have any specific skills, or deep knowledge of certain processes, back to the sea with you.

3) If you didn’t deliver savings or process improvements, you would have been fired. Multiple times. It would show on your resume, and you wouldn’t get the interview.

4) What local and international laws? There are 195 countries. These all have laws and regulations that affect Procurements in, from, and through their countries. These could be finance (post-audit/clearance, anti-bribery, etc.), human welfare, sustainability, or other laws. Get specific. If you spent a decade buying fruit from South America but the company wants you to buy semiconductor chips from China, Taiwan, and Japan — how does that help?

Q2: Tell us about your qualifications for this job.

Again, not a bad question (but the interviewer should focus in on your strongest or most unique). But

I hold a bachelor’s degree in business administration with a specialization in supply chain management. Over the course of 5 years, I have actively worked in procurement, honing my skills and expertise. My experience spans the management of both direct and indirect spend, granting me a comprehensive understanding of procurement operations. Moreover, I possess proficiency in various procurement software systems and boast a solid comprehension of contract law.

Is also NOT a good answer.

1) Obvious from the resume, but I can, and probably will in a later article, argue that most business / operations / supply chain programs are NOT (on their own) qualifications for Procurement. (Future article, because this rant is more than an article in itself.)

2) Repeating an answer, inconsistently (10 to 5 years), is useless and adds nothing beyond the resume (except confusion).

3) Again, buzzwords are meaningless. Indirect to one company is direct to another and vice versa. What did you buy? And what insights did you glean (that the average schmuck has no understanding of)?

4) Various systems. Do you mean email and Excel? A 20 year old version of SAP Ariba? A modern suite like Coupa or Jaggaer? Or BoB solutions like Anydata, Bonfire, ContractPodAI, DecideWare, EC Sourcing, etc. etc. etc.

5) Contract Law? Great! But what countries, states/provinces, and contract types are you most adept with. (And remember, expertise in contracts is NOT expertise in contract law. It’s pretty easy to be an expert in contracts if you do them enough, but without a solid legal understanding, it’s pretty hard!)

Q3: How would you describe your procurement process?

Finally, a good question. But

The procurement process typically starts with the receipt of a request for proposal (RFP) from a potential customer. This document outlines the customer’s specific requirements for the desired product or service. The procurement team will leverage this information to compile a comprehensive list of potential suppliers. Subsequently, they will issue a request for quotation (RFQ) to these suppliers.

Is NOT a good answer. It’s actually even worse then the answers above!

1) If you worked for a make-to-order / build-to-order organization, that’s typically the process. If you make off-the-shelf CPG, then the process starts with a forecast and an assignment to “get ‘er done“.

2) If the interviewer doesn’t know what an RFP is, you should run for the door.

3) You can’t procure without suppliers, so this is a standard step in every 5/6/7/8/9 step process out there!

4) DUH!

Not once does it get into any specific, unique, best practice details that show the deep understanding you possess of Procurement processes.

At this point in the article, the questions got slightly better — but the answers continued to be bad or even worse than this one.

It’s sad. None of them address what a Procurement Director / Chief Procurement Officer (CPO) is looking for.

The relative priority of desires will vary from CPO to CPO, but these are the big ones that all CPOs have in the back of their minds.

1) Education – a university degree; relevant to what you are buying is typically preferred if you are junior, any degree if you are senior; how does your education relate to the position you are applying for?

2) Experience – relevant experience in what you will be buying, not necessarily as a buyer, possibly as an engineer, depending on the expertise needed to do the job (just like you can teach a mathematician accounting but you can’t always teach an accountant advanced mathematics, you can teach a trained professional Procurement but you can’t always teach an average buyer the fundamentals of technology or engine engineering).

3) EQ (Emotional Quotient) – you will have to work in a team; how did you work in a team in previous job(s) for complex procurements

4) TQ (Technology Quotient) – you will have to use technology, and hopefully continually improving and evolving tech; what modern tech have you used?

5) Think-on-Your-Feet Adaptability – nothing will ever go according to plan, and you will have to fight fires on a daily basis and find solutions quickly to prevent minor bumps leading to major derailments

6) Strategic Thinking – how should you approach a category or a problem; how could you improve current processes based on current learning; what did you do that improved a process in the past or solved a difficult problem?

7) Risk Management Mindset – you can’t eliminate all risks, but you can mitigate many and manage others; how do you embed this in your process

8) Sustainability – both environmental and corporate; you often have to find a delicate balance; what requirements did you have and how did you meet them without skyrocketing costs

9) Mathematics and Cost Modelling – a quote is not a cost, it’s a quote; you need to understand core cost drivers to judge quotes; demonstrate this in at least one answer

10) Independence – you will need to continually learn and continually self manage; your boss won’t be available 24/7 and definitely not when you need to make a critical decision quickly to keep a project moving

The Procurement People-Process-Technology Pain Cycle …

Recently on LinkedIn, someone asked the trick question of which came first: process or technology. The answer, of course, was people since, when Procurement, the world’s second oldest profession, started, it was just a buyer haggling with the seller for their wares. and this is how it was for a long (long) time (and in some societies was as far as “procurement” progressed), until shortly after a culture advanced to the point where people could form private businesses that were entities unto themselves. Once these entities started to grow, and multiple people were needed to do the same job, they realized they needed rules of operation to function, and these became the foundations for processes.

But when business buying began, there was typically no technology beyond the chair the employee sat in, the table they used to support the paper they wrote their processes and records on (and the drawers they stored the paper in), the quill and ink they used to write with, and the container that held the ink. And in many civilizations, it was like this for hundreds of (and sometimes over a thousand) years. The first real technological revolution that affected the back office was the telephone (invented in 1876, the first exchange came online in 1878, and it took almost 30 years for the number of telephones to top 1,000,000 (600K after 24 years, 2.2 million after 29 years). [And it took 59 years before the first transatlantic call took place.] The next invention to have a real impact on the back office was the modern fax machine and the ability to send accurate document copies over the telephone. Even though the history of the fax machine dates back to a 1843 patent, the modern fax machine, that used LDX [Long Distance Xerography], was invented in 1964, with the first commercial product that could transmit a letter sized document appearing on the market in 1966. Usage and availability was limited at first (as the receiver need to have a fax machine compatible with the sender), but with the 1980 ITU G3 Facsimile standard, fax quickly became as common as the telephone. But neither of these inventions are what we consider modern technology.

When we talk about “technology” in modern procurement, or modern business in general, we are usually talking about software or software-enabled technology. This, for some businesses, only became common place about 30 years ago (since most businesses could only afford PCs, and even though they were invented in the 1970s, it was the 80s before they were generally available commercially, and the 90s before most smaller businesses could afford them [for the average employee]), and only commonplace in the largest of businesses 50 years ago. Once has to also remember that the first general purpose automatic digital computer built by IBM (in conjunction with Harvard) only appeared in 1944, and that IBMs first fully electronic data processing system didn’t appear until 1952, and, as a result, back office technology really only began in the fifties, and was only affordable by the largest of corporations. (Furthermore, even though he first MRPs were developed in the 1950s, the first general commercial MRP release wasn’t until 1964, and it took over a decade until the number of installations topped 1,000. [And MRP came before ERP.]) In other words, technology, beyond the telephone [and fax] did not really exist in the business back office until the MRP. And it wasn’t common until the introduction, and adoption, of the spreadsheet. The first spreadsheet was VisiCalc, on the Apple II, on 1979. This was followed by SuperCalc and Microsoft’s Multiplan on the CP/M platform in 1982 and then by Lotus 1-2-3 in 1983, which really brought spreadsheets to the masses (and then Excel was introduced in 1985 for the Mac and 1987 for Windows 2X). (And 36 years later Excel is still every buyer’s favourite application. Think about this the next time you proclaim the rapid advance in modern technology for the back office.)

In other words, we know the order in which people, process, and technology came into play in Procurement, and the order in which we need to address, and solve, any problems to be effective. However, what we may not fully realize, and definitely don’t want to admit, is the degree to which this cycle causes us pain as it loops back in on itself like the Ouroboros that we referenced in our recent piece on how reporting is not analysis — and neither are spreadsheets, databases, OLAP solutions, or “Business Intelligence” solutions as every piece of technology we introduce to implement a process that is supposed to help us as people introduces a new set of problems for us to solve.

Let’s take the viscous cycle created by incomplete, or inappropriate, applications for analysis, which we summarized as follows:

Tool Issue Resolution Loss of Function
Spreadsheet Data limit; lack of controls/auditability Database No dependency maintenance; no hope of building responsive models
Database performance on transactional data (even with expert optimization) OLAP Database Data changes are offline only & tedious, what-if analysis is non-viable
OLAP Database Interfaces, like SQL, are inadequate BI Application Schema freezes to support existing dashboards; database read only
BI Application Read only data and limited interface functionality Spreadsheets Loss of friendly user interfaces and data controls/auditability

This necessitated a repeat of the PPT cycle to solve the pain introduced by the tool:

Technology Pain People Process
Spreadsheet Data Limitations Figure out how to break the problem down, do multiple analysis, and summarize them Define the process to do this within the limitations of existing technology
Database Performance Issues Define a lesser analysis that will be “sufficient” and then figure out a sequence of steps that can be performed efficiently in the technology Codify each of those steps that the database was supposed to do
OLAP Stale Data Define a minimal set of updates that will satisfy the current analysis Create a process to do those updates and then re-run the exact same analysis that led to the identification of stale data
BI Tool inability to change underlying rollups / packaged views define a minimal set of additional rollups / views to address the current insight needs, as mandated by the C-suite create a process to take the system offline, encode them, put the system back online, and then do the necessary analysis

In other words, while every piece of technology you implement should solve a set of problems you currently have, it will fail to address others, introduce more, and sometimes bring to light problems you never knew you had. Although technology was supposed to end the pain cycle, the reality is that all it has ever done is set it anew.

So does that mean we should abandon technology? Not in the least. We wouldn’t survive in the modern business world anymore without it. What it means is that a technology offering is only a solution if it

  1. solves one or more of the most significant problems we are having now
  2. without introducing problems that are as significant as the problems we are solving

In other words, technology should be approached like optimization (which, in our world is typically strategic sourcing decision optimization or network optimization). Just like each potential solution returned by a proper mathematical optimization engine should provide a result better than the previous, each successive technology implementation or upgrade should improve the overall business scenario by both solving the worst problems and minimizing the overall severity of the problems not yet addressed by technology.

This is why it’s really important to understand what your most significant business problems are, and what processes would best solve them, before looking for a technology solution as that will help you narrow in on the right type of solution and then the right capabilities to look for when trying to select the best particular implementation of that type of technology for you.

Talent is Scarce, but Remember EQ and TQ are not Interchangeable!

the doctor realizes just how limited the supply of top Procurement talent is, and how tempted you might be to hire any apparent “talent” that you come across, especially if you get the okay among constant (brain-dead) hiring and training budget cuts (when Procurement is one of the few organizations that can consistently deliver a return many times it’s operational cost), but when you are filling your Procurement roles, chances are that at least one of them is going to be an TQ-heavy role. And whereas you can replace Procurement knowledge with IQ, you can’t replace Technical Knowledge with IQ, at least not quickly.

This is important because, given how important it is for a new hire to fit in, a company is often ready to hire the minute a candidate comes along that:

  • has the personality that fits the corporate culture,
  • has influential charisma, and
  • has intellectual potential.

or, in other words, has the right EQ.

This is important, and should be the deciding factor among multiple candidates that can do the job, but you should first make sure the candidate can do the job she is being hired for. If it is highly technical in nature (i.e. leading the implementation and customization of a new S2P system to support organizational processes and transform them along the way), then she needs to be rather technical in her background and have a good knowledge of what the systems can do, how they do it, and what the organization will need from them.

These are not basic Procurement skills or category expertise that can be taught to any candidate with a high IQ, some common sense, and a background in the industry. These are skills that typically take years of training and experience to develop.

In other words, before hiring, first

  • clearly identify the role that needs to be filled
  • the key technical / experiential skill sets that are needed
  • what, if anything, can be made up with in-house / third party training if the candidate has the right IQ and work ethic

and limit consideration to those candidates. At this point, you can let EQ prevail (even if one candidate would take 6 weeks of training and another 6 hours, because even if a candidate required no training, the wrong attitude would prevent that candidate from ever fitting in). But not before. Remember that before you get overzealous. At the end of the day, the job needs to get done, and the perfect candidate is not the perfect candidate if he can’t do the job.