Category Archives: Procurement Innovation

Procurement Fundamentals — A Path to Innovation

Today’s guest post is from Bernard Gunther of Lexington Analytics.
He can be reached at bgunther <at> lexingtonanalytics <dot> com.

Every year, I look forward to going to conferences with the hope that I will get a chance to see a great deal of innovation and learn something new. Most years, I am largely disappointed. Is there innovation? Yes. But much of what is being presented relates to operational excellence, operational success or even operational “good-enough.”

Why is this? It’s a lot harder to innovate when you are still struggling to set up standard practices. Procurement systems and processes tend to be a patchwork of different approaches for different spend areas all jumbled together. Many organizations are just catching up to best practices. Let’s take the “101” starting point for any procurement organization, the basic spend analysis of vendor payments — understanding how much you are spending with each of your vendors. Recent surveys indicate that less than half of companies have a system for this. For those companies without a system, they seem to be doing ad hoc dumps of data from their AP system into Excel or a data warehouse with no consistency in the analysis. We all know this is not a best practice in procurement. If companies are not doing the basics well, they have little time to focus on innovation.

It’s not surprising that there are so many presentations about operational successes and so few about innovation at sourcing conferences. Operational success is a key element of a strong function and can deliver significant value, but should it be considered innovation? At a recent conference, I attended a wonderful presentation on Negotiation Fundamentals. One would think that everyone in a purchasing group would be well versed in this and applying the fundamentals regularly. But if you look around procurement organizations, you find that many people are not applying the core disciplines of procurement in effective ways.

Is there support for innovation at organizations? Successful companies are continually investing in innovation and developing new products and processes. These new products rarely just happen and not every new product idea is a success. This means that a procurement group interested in innovation should be doing three things:

1. Look for innovation. Innovation usually comes from new companies but it can also come from unexpected areas. But, in order to recognize it, you’ve got to be open to it. I remember when my grandmother came to visit us one summer from Germany. Like many older people she wasn’t open to trying new things. Her attitude was, “I don’t know that food, so I don’t want to try it,” or, “We have that at home too.” Because she wasn’t open to new things, she didn’t see anything new. She wrongly concluded at the end of her stay that food in America was just like Germany. Are you saying the same thing to innovation?

2. Invest in innovation. Is it 1% of your budget? 10%? Is it 5 projects? Is it 3 new vendors allowed in? Don’t know? If you don’t know, how are you making it happen?

3. Allow for “failure”. A group that is innovating is going to have failures, or “less-than-total” successes. But that’s okay if your environment rewards some risk taking. If not, your people will only attempt things they know will succeed — which is not innovating, it’s following. You need to be able to work on projects and initiatives that aren’t perfect. Success is usually the product of many such small failures. There are far too many projects / programs / implementations that are deemed too big to fail by the owners. Projects promising innovation in a company may get viewed as another procurement initiative ready to fail — over promising and under delivering. This atmosphere is rarely one that fosters innovation.

If you are already innovating — wonderful. But I suspect that most organizations would be delighted if Purchasing were to deliver better operational performance. If your organization is not ready for true innovation, perhaps focusing on operational success is the way to build your organization’s credibility. By demonstrating your ability to add value through the fundamentals, you are setting the stage for future innovation. When you do innovate, you can present it as delivering more of what the organization already values.

Public Sector vs. Private Sector Procurement : Does One Size Fit All? II

Yesterday we noted that if you were looking for a way to quickly and easily segregate the vast array of companies offering procurement solutions in the marketplace, you’d quickly find that they could quickly be divided into those that almost exclusively serve the public sector and those that almost exclusively serve the private sector. We also noted that public sector organizations operate quite differently than their private sector enterprise counterparts. We then discussed the differences in day-to-day procurement public sector organizations vs. private sector enterprises.

Based on the operational differences we identified, we reviewed the fundamental differences in workflow, awards, and approvals and discussed the underlying technology required to support both the public sector and private sector needs. And we found something quite surprising – pretty much the same solution was needed in both cases. Which left us scratching us head and asking, so what’s the difference?

Well, when you get right down to it, there are no differences in the fundamental e-procurement technology requirements for public sector and private sector organizations. They both need to create RFXs to solicit information, accept bids, generate awards, create and approve contracts, cut purchase orders and goods receipts, accept invoices, issue (e-)payments, and track and report on spending. And they need to be able to do it in a smooth and integrated manner that minimizes data entry (and eliminates rekeying of data already in the system, as that just leads to human error).

The fundamental differences are in the processes they use. Public sector organizations have one set of rules for whether it’s a public RFX, renegotiation with an incumbent vendor, or a direct award and private sector enterprises have another. Public sector organizations tend to use the RFX, Bid Management, and Contract Management solutions more heavily than their private sector counterparts who are free to chase the award with the greatest long-term value and use non-discriminating e-auctions and cutting edge decision optimization to get the best value for their shareholders. But the fundamentals of procurement don’t change.

So why are most e-Procurement companies either or?

I think the answer is two-fold.
(1) Most technology-focussed solution companies don’t understand the differences between public sector and private sector procurement, and thus focus on one or the other.
(2) Most technology solution providers are still selling B2B 2.0 solutions, which have been customized for one environment or the other. In order to support both environments on one platform, you have to have very flexible workflows that are extremely customizable by the customer (to meet their needs) and a user interface that is trivially easy to use. This is easy with flexible B2B 3.0 solutions, but almost impossible with rigid B2B 2.0 solutions.

And if you have the right platform, you can easily support both types of customers.

Public Sector vs. Private Sector Procurement : Does One Size Fit All? I

If you were looking for a way to quickly and easily segregate the vast array of companies offering procurement solutions in the marketplace, you’d quickly find that they could quickly be divided into those that almost exclusively serve the public sector and those that almost exclusively serve the private sector. And if you’re like me, you’d wonder Why Is That?

It’s true that public sector organizations operate quite differently than their private sector enterprise counterparts, and that’s good, because they’re supposed to. A public sector organization is supposed to first and foremost serve the public good, a private sector organization is supposed to first and foremost bring value to its shareholders. Public sector organizations need to be fair when awarding contracts in terms of minimum minority awards, small business awards, disadvantaged business awards, and woman-owned business awards, especially when all else is equal. Private sector organizations need to select the best vendor for the job — every time, as that is their duty to their shareholders.

But does it mean that the solutions have to be different? Are not the fundamentals of good end-to-end e-procurement the same whether you’re public sector or private sector? I guess that’s the Trillion Dollar Question, isn’t it.

Let’s start by examining your average public sector procurement organization a little more closely. Public sector is not only very policy driven, it’s very stake-holder driven. In the private sector, most purchases don’t require more than two approvals — the procurement specialist and, if the dollar value is high enough, her boss. Yes, the stakeholders need to be consulted and have to be given a chance to provide their input, but the contract can be inked once the procurement manager, and her supervisor with enough fiscal authority, sign off. In the public sector, most procurements require no less than four or five signatures. You have the procurement (or contract) specialist, her supervisor, the project/program/department manager who needs the product or service, the Equality Awards Office (EAO) responsible for insuring that enough awards are made to MWBE and disadvantaged vendors, and, if any clause or term in the agreement is non-standard, legal. If the procurement carries risk, you might need the signature of the officer responsible for risk management, if the procurement will result in recurring payments, you might need the approval of accounts payable or finance, and if the spend is significant enough, you might need a senior VP in addition to your boss’s signature. But all of this can be handled by a flexible workflow with a configurable approval chain.

In the public sector you primarily have RFPs and sealed bids where the award often HAS to be given to the lowest bidder who can fulfill the demand at the minimum level of quality, safety, and performance, whereas private sector organizations can select the bidder that they believe will generate the most value for them in the long run. This means that the public sector requires an extensive RFX application with weighted scorecards and good comparison reports … the same thing that the private sector has gotten for years since GE implemented the reverse auction and FreeMarkets made it famous.

The public sector needs to support the lowest common denominator in terms of issuance of POs and receipt of invoices. If a supplier still operates out of a 1970’s production plant and can only accept and receive faxes, then the organization has to deal with paper for part of its procurement process whereas a private sector organization can dictate that it will only accept invoices electronically. But e-Procurement solutions have been accepting attachments for over a decade, and allowing the user to define the appropriate meta-data (vendor, po #, contract #, line items, quantity, amount, taxes, total invoice amount, etc.) for just as long. So it’s still easy for a data entry clerk to create an e-invoice in the system on behalf of a vendor and print, and fax, an e-PO on behalf of the public sector organization.

And so on.

So what’s the difference?

Come back tomorrow for Part II!

(Supply Chain) Initiative Cost Justification

Last year, over on the e-Sourcing Wiki, I brought you The Quest For Purchasing Fire, a guide on how to develop the internal strategies for selling the procurement tools internally. This process had two key steps that, if not done properly, could be major stumbling blocks in getting your initiative off the ground. These key steps were defining the value proposition and building the business case.

The fact of the matter is, when you get right down to it, often the biggest stumbling block is to secure funding for your initiative. Unless the project happens to be a pet project of the CEO or CFO, chances are you won’t be able to secure funding unless you have a clearly stated and easily understood kick-ass value proposition and a well-researched and documented business case to back it up — preferably one that shows big dollar signs to the company’s favor. Thus, it’s important to zero in on the cost-justification in both of these steps and reduce the decision to one that should be a no-brainer ( especially since we know that, in some companies, it would appear that having a functioning brain is not a requirement for an executive position ). If your CEO and CFO can see a significant ROI, which includes an ROI in the near-term, which they know makes Wall Street and / or the private investors happy, they’re much more likely to find the money you need “in the budget” than if they don’t see a savings opportunity that will make them look good.

That’s why it was nice to see an article last month over on the Supply Chain Digest site that offered up “six steps to improved cost justification for supply chain and logistics initiatives”. Simply put, when it comes to understanding the best way to put together a cost justification for your project, you can use all the good, free, advice that you can find.

The article offered up six useful guidelines to consider when putting together your value proposition and proposal. At a high level, these guidelines were:

  • Understand your company’s investment analysis model
    What does your CFO care about? IRR (Internal Rate of Return), PP (Payback Period), NPV (Net Present Value), ROIC (Return on Invested Capital), etc? Make sure to use the measures your CFO is comfortable with and wants to see. It will help insure that your proposal makes it to the top of his pile.
  • Link funding requests to key corporate strategies and objectives.
    The CEO wants to further the corporate strategies and objectives outlined by the Board, because, simply put, his success in that area positively impacts his annual review, and bonus. Talk to those strategies. That will make sure your initiative gets his attention.
  • Develop a Strong Summary with a Detailed Back-Up
    Your CEO is busy. Very busy. Probably doing stuff that’s not all that important (but that’s not entirely his fault – boards and wall street like to waste an executive’s time), but stuff that consumes his or her time nonetheless. Therefore, it’s important that you have a strong, straight-to the-point, executive summary that says why the company should do this, and what results it will have … because that’s all he or she might have time to read. However, if your CEO likes what she hears, he or she will ask the CFO or another member of the management team to “dive into it” which is where the detailed calculations and supporting materials come into play.
  • Use the Numbers to tell a story.
    Remember, the CFO likes numbers. So base the story around those numbers. “We will generate a 300% ROI by implementing an e-Procurement system that … “.
  • Review Preliminary Justification with Key Stakeholders
    And make sure to to have them verify every assumption that you make. The last thing you want is for the manager tasked with verifying your submission to find that one of your key assumptions is wrong. Even if the affect is minor on the final ROI calculation, being overworked, he’ll likely assume that the whole plan must be faulty, throw it out, and vote nay without even giving you a chance to correct it. But if you meet with the key stakeholders and everyone agrees, you can get it more-or-less right the first time and not have to worry about your initiative getting killed off before it even has time to begin.
  • Triple Check to Eliminate Math Errors and Risky Assumptions
    A CFO is likely to assume that if you can’t add, since you have a spreadsheet to do it for you, you probably can’t do anything else you say you can do either, and deny your project without even considering it. And CEO’s don’t like risk, so if you can get (almost) the same results with less risky assumptions, you should use them.

Good advice all around.

The Purchasing Leader’s Guide to a More Successful Team

Recently, Next Level Purchasing (now the Certitrek NLPA) published “The Purchasing Leader’s Guide to a More Successful Team” that outlined Seven Steps For Improving Skills and Getting Better Results. Noting that many organizations only have one or two superstar team members that can handle the most challenging projects, that a purchasing department should be the organizational center-of-excellence, and that there’s no reason your entire team can’t excel, Charles Dominick, President & CPO of Next Level Purchasing put together a simple seven step process that any organization can follow to improve their team. The document might not cover every possible thing that one could do, but it’s a great start as any department that effectively implements and masters the steps provided will certainly be above average as a result.

The seven steps outlined by the document are:

  • Document Departmental Goals
  • Identify the Necessary Skills
  • Develop a Methodology to Assess Skills
  • Determine Skill Gaps
  • Define a Skills Development RoadMap
  • Improve Skill Levels
  • Measure & Sustain Improvements

They are important because:

  • It’s hard to identify necessary skills without goals.
  • Once you’ve identified the skills, you can identify who should have them.
  • You need to know how competent your people are with respect to each required skill to assess gaps.
  • You need to know what the gaps are in order to identify appropriate training.
  • The roadmap helps you identify which skills are important.
  • Skill level improvements are accompanied by improvements in sourcing results.
  • Measurements let you know how effective each skill level improvement initiative was and helps you select the “training” that is most appropriate for your team.

And you should definitely download “The Purchasing Leader’s Guide to a More Successful Team” because:

  • It gives you some examples of the right way to state measurable goals.
  • It outlines common skill dimensions that you should be sure to consider.
  • It defines three different skill assessment methods.
  • It tells you what’s important when it comes to skill gap identification.
  • It describes five different ways you can prioritize professional development.
  • It outlines different ways you can improve skill levels.
  • It gives you some ideas for measuring skill improvements in a manner that can be communicated to management.