Author Archives: thedoctor

Breaking Down The Barriers: Lead Times/Supplier/Carrier Issues & Supply Chain Visibility/Network Complexity

We’re continuing our foray into the top barriers to success that we outlined in our top barriers post that chronicles the barriers that keep coming up over and over again in every Procurement survey in our effort to ensure that you don’t have to read another state of procurement study for the next 5 years. Today we are covering supply chain visibility and the issues it creates.

A Brief History …

This is very closely related to our last barrier of supplier reliability. In many ways it’s the same, except this one is more from a supply chain focus than a procurement focus and is more focussed around logistics, warehousing, free trade zones (FTZs), etc. Not only do you have supply assurance issues now that you’re sourcing from tens of thousands of suppliers all around the world, but you have lead time and carrier issues as well as issues of network complexity and real-time transportation balancing.

The Problem

We discussed the core problems of supplier and third party management and supply chain visibility in our last barrier, but that was just scratching the surface.

We now have the problem of logistics planning, modelling and real-time tracking. This is much easier said than done when sourcing from half a world away. How does it get to the “local port”? How does it get to the “destination port”? How does it get from the destination port to the local warehouse? Do you need cross-docking and load consolidation/splitting anywhere in that delivery chain? If so, will this involve intermediate warehousing anywhere along the delivery chain and/or will you need to manage intermediate warehousing at a Free Trade Zone next to a port where you transship to a neighbouring country?

All of this should be done before a supplier is selected to understand how it will impact the current network? Will it utilize the existing distribution network fully (because the supplier is in a city where you have a carrier already that can tap right into your existing supply network in the region)? Partially (and require you to find a new carrier to a local hub and / or lease a new warehouse for storage and cross docking)? Or is it in a new region/country you have no supply network at all and would require considerable upgrades, or changes, to your supply network. Otherwise, if this is done after the contract is signed, it could be a mad dash to try and get something, anything, in place before the shipment is needed, leading to suboptimal decisions and network designs that negate all of the expected savings from the new supplier and/or the other expected advantages (such as carbon in the logistics chain, shorter lead times, etc.).

Then there is the issue of warehouse and (remote) inventory management, as we know that, done poorly, this can increase your logistics and product costs considerably! You pay the same for a warehouse lease whether it is empty or full. Power and heat are quite consistent too. Water might increase slightly if you have a large staff, but that’s it. This means only a warehouse that is consistently mostly full is cost efficient. (In other words, you want inventory flowing through it regularly and keeping it near capacity.)

And, of course, you want to integrate all of this into your supply chain visibility solution so that you’re not just maintaining visibility into your suppliers, but also your carriers and your warehouses. A full supply chain network view.

The Necessary Realization

Supply chain aware sourcing is quite a challenge. It’s not just the supplier, it’s the supply network — the carriers, the warehouses, the ports — and all of the players you need visibility into. That’s why you not only need the:

TPRM (Third Party Relationship Management) solution and the SCV (Supply Chain Visibility) solution discussed in our last post, but also need:

A Logistics / Transportation Management System (LMS/TMS) to maintain (near real time) visibility into your global transportation network to track where your goods are and when they are expected to reach each stop in your network and finally be delivered.

A GTMS (Global Trade Management Solution) that allows you to manage free trade zones, import and export documentation (to keep things flowing on time), and (those beautiful, beautiful) tariffs.

And, of course, you need to understand not only how to link all of these systems but deploy them in unison so everyone has the right view at all times.

Then, each person involved in the chain needs to know how to make use of the information presented, and make the right decision keeping the needs of the other department in mind as well as the organizational priorities and goals. Easier said than done as there is a need to balance, at a minimum, Procurement, Supply Chain, Logistics, Risk Management, Operations, and possibly, Finance.

The Technological Requirements

The technological requirements are considerable and require supply chain aware sourcing and sourcing aware supply chain and expertise from source to sink and back again on both sides.

A continuing reminder that if you want guidance in the short term, hope that your favourite provider reaches out to Bob Ferrari of Supply Chain Matters or the doctor and enables us to focus on writing the series (or in-depth e-book) explaining what modern Procurement and Supply Chain Tech needs to look like (and how it needs to be implemented) to address the challenges, reduce the risks, and address the priorities versus just dripping out tidbits as free time permits.

Most Consultants and Analysts Don’t Help You Select Solutions — Just Tech that Benefits Their Partners and Vendor Clients

It might not be the intent of the consultant or analyst who truly wants to help you, but this is what happens the vast majority of the time (and contributes to the 88% tech failure rate and 94% Gen-AI failure rate). There are a number of reasons for this.

From the consultancy side of the equation:

* Most Consultants are told to please clients and give the clients what they want.

The problem here is that clients don’t know what they want, because they don’t understand what they need. So when the client reps are asked they try to sound informed and recite long feature lists they believe that they are supposed to need based upon the most prevalent vendor marketing. The problem is that each of the client’s reps who are interviewed have different long feature lists that only partially overlap and when the consultants are done gathering requirements from the client, they have 500 feature requirements that result in a 600 question RFP that is totally meaningless as it’s functions, not features, that support processes, not tasks.

* Most Consultants are NOT experts on the tech or what’s available in the market.

When a consultancy is also an implementor and has vendor partnerships, their technology and market viewpoint is biased towards those vendors. There are two reasons for this:

  1. that is what their consultancy spends the majority of their time supporting, so they don’t have wide experience (and they aren’t encouraged to get it)
  2. they need to sell a certain amount of vendor partner products to maintain their gold/platinum/diamond standing, which means they are heavily incentivized to see one of their partner’s products as a solution to every problem

* Most Consultants usually start with the understanding of the problem you bring them without validating it’s the right one.

The only way to truly understand a client’s need is to start by undertaking a collaborative needs assessment based on a collaborative working session designed to get at the root issues the client is having, what processes they need, and where a technology-based solution should fit in the process. Without the right understanding of the core problem, the core processes required, and what type of solution they should be looking at — and why, the consultant is not going to ask the right questions, understand the reason for the “requirements” the client reps are bringing, and differentiate the requests on the right track (which need focussing) and the requests on the wrong track. This is one of the reasons we see so many RFPs with 500+ feature questions, because the clients don’t really understand the critical functions the client needs that should be focussed on.

From the analyst side of the equation:

* Most Analysts spend the majority of their time on the firm’s paying clients

They get minimal time with any non-clients, thanks to the sales gatekeepers who scare everyone away with the five to six figure sales pitches (that guarantee analyst time, research access, and at least one write-up which may or may not be behind a paywall) and thanks to their super busy schedule jam packed with “advisory” calls which usually boil down to “how good is this pricing or contract” or “which of the vendors on your map is best” and not “how do we go about identifying the right vendor with the right solution for us, which might not be on ANY of your maps”.

* Most Analysts base their recommendations off of where the vendor lands in a map, which is a flawed process

The big analyst firms produce quadrant maps that plot a vendor on two axes where one axis is something like “completeness of vision” or “strategy” and the other is “ability to execute” or “current offering”, where these axis are usually defined based on the mash-up of six to twelve scores where the majority are completely subjective on the part of the analyst scoring them. As a result, with the exception of the one analyst who took the vendor demos and did the review, they don’t really have any solid idea of why one vendor is really better than another, or where the biggest differences are. But most importantly, they have no insight into whether the vendor’s offering is best for you based on your needs because they not only have very limited ability to focus in on the dimensions of relevance to you, but very little depth in those dimensions to match to your specific needs.

Since the majority of consultants and analysts work at mid-size or larger Big X firms that have a lot of existing partnerships and vendor clients, that’s why you rarely get a good recommendation from a consultant or analyst, and why you end up being another casualty in the 88% failure rate (or the 94% failure rate if the recommendation involved Gen-AI).

The only real way to have a good chance of getting a good recommendation is to go with an independent consultant or small firm that has no vendor partnerships, no rigid maps, and no incentive to recommend one vendor over another. Because then there is no bias.

However, since you’re astute, you know this is only a baseline requirement. In addition to being independent (1), you also need a consultant and/or analyst with expertise and experience in the domain and the vendor landscape (2), and the knowledge of what process to follow and what questions to ask (3).

If you do a little bit of research (using your brain, not Gen-AI computed recommendations), you can easily find a lot of good consultants who satisfy the first and second requirements. The third requirement is the hard requirement to meet. Why? Most consultants don’t have a model and process backed methodology to do these types of engagements and rely entirely on past projects, so if your project isn’t similar to one they’ve done before, while they will truly be doing their best, they may not hit all the right points, especially if time (or budget) is tight. Your success is 100% dependent on their past experience, and you really have to vet well.

But if you can find a consultant or analyst who is backed up by a model-backed methodology with the right experience, your chances of success will flip from 12% to 88%, especially if that consultant also does project assurance. Because such a consultant or analyst, not biased to any solution, will use all of the knowledge and best practices learned by the firm in past projects (that were encoded into the model and methodology), greatly increasing the chance of a right recommendation for you. While success can NEVER be guaranteed (unlike failure), the chances can be exponentially increased. And that’s how you succeed in the real world in technology-based solution selection.

Breaking Down The Barriers: Quality/Supplier Reliability/Continuity

We’re continuing our foray into the top barriers to success that we outlined in our top barriers post that chronicles the barriers that keep coming up over and over again in every Procurement survey in our effort to ensure that you don’t have to read another state of procurement study for the next 5 years. Today our focus shifts to quality and supplier reliability and continuity.

A Brief History …

Back during the Industrial Revolution and the Gilded Age, most corporations were vertically integrated down to the raw material supply. It was one big operation from raw material to processing plant to distribution to end customer. If there was a quality issue, it was your operation, you went to the factory, you had a stern talk with the factory floor manager, actions were taken, and quality improved. If supply wasn’t steady, it was a problem with your mines or farms and the solution was the same. You went to the mine or the farm, had a problem solving session with whomever was in charge, and that was that.

While the railroads may have required supply from a lot of different corporations, which resulted in the first handbook for modern purchasing (Handbook of Railway Supplies, 1887), most operations didn’t and, moreover, the railroad tycoons often owned many of the companies they needed. However, with the introduction of the Ford Model T in 1908 and the invention of the first modern electric refrigerator, the Domelre, in 1913 we entered an age where appliances and automobiles and other modern conveniences started to required specialized parts. As a result, as time progressed forward, more and more businesses began to specialize in the production of chemicals and parts to support the increasingly complex manufacturing requirements that arose in the production of these modern conveniences.

Supply reliability and quality became an increasingly important concern as operations went from having to source a few chemicals and parts to having to source dozens (and then when the age of electronics began, hundreds and eventually thousands). If there was a quality issue, you could complain, but you couldn’t ensure it would be fixed in a timely fashion. Thus, reliability of supply started to become an issue if you didn’t have alternatives.

Then global outsourcing began to step up in the 1960s and explode in the 1980s, especially to Japan and then to Taiwan for electronics and then to China and the rest of Asia for everything else. Supply chains extended halfway around the world for everything we buy daily. Quality may or may not match the sample (where the production batch may or may not be produced in the same factory), and if it’s poor, there’s not much you can do about it except to find a new supplier and wait weeks or months for a new shipment. But that’s even assuming you can assure supply at all.

The Problem

Supply chains have gone from tight vertically integrated operations in single corporate monopolies to overly extended and overly complex behemoths that span the globe, consist of multiple tiers (that can easily be 6 to 8 levels deep on average), and often consist of 10,000 or more suppliers because of electronics that supply commodity wiring and connectors and chasis to one-of-a-kind custom manufactured processors. We’ve went from a point where the head of production knew every key component in the product; where it was mined, processed, and made; and who was responsible for or supplied it to the point where maybe one person can name all of the tier 1 suppliers currently being used to produce a single product in question, even if it happens to be one of the core products produced by the company. And that’s a big maybe if there’s more then 10 tier 1 suppliers involved.

An average large organization now has tens of thousands of “active” suppliers that supply everything from office supplies and MRO to products and services for resale to services, with over 80% of these suppliers being in the tail in terms of overall spend (and, usually, number of purchases, with some “active” suppliers only being used once or twice in a year, and some only being used for one year). That still leaves a few thousand core “active” suppliers in the top / strategic spend categories, and it’s impossible to keep an eye on every one and be certain that the next (critical) order is going to come in. Especially when it’s not just supplier solvency and performance, but geo-political, logistical, and regulatory issues that can get in the way, disasters that can bring operations to a stand still, and economic issues (like trade wars) that can upend a supplier overnight.

The Necessary Realization

Not only are modern supply chains are too complex to manage without software, but so is supply assurance. This goes well beyond supplier selection for an award to continuous supplier monitoring from a compliance, performance, and risk perspective to ensure supply keeps coming in and proactively detect and predict issues that may arise.

This is not something any human, or team, can do without a lot of technological help. You need solutions for:

TPRM — Third Party Relationship Management — i.e. Supplier/Vendor Management on Steroids where you can track all continuously active direct tier 1 suppliers who are in the top 80% of spend or supply a sole source critical component or service and maintain their regulatory, compliance, insurance, performance, and risk profile that can be accessed before sourcing events, during regular performance reviews, when issues are reported, and so on.

SCV — Supply Chain Visibility Solutions — that tracks and monitors your supply chain at least to tier 3, and further if possible. You’re going to have a tier 1 problem if your tier 2 supplier goes bankrupt, becomes inaccessible to the tier 1 supplier because of new sanctions or border closings (due to geopolitical tensions or uprising), or happens to be near the epicenter of a significant natural disaster that at the very least will cut off supply lines even if its plant wasn’t damaged. You need to be monitoring to the extent possible critical tier 2 and tier 3 suppliers that you know provide the majority of parts and raw materials that go into your products, especially if your tier 2 and tier 3 suppliers have limited options. And if there’s an issue, you need to know months in advance because chances are your tier 1 won’t realize an issue until your tier 2 is late, which could be way too late for you to find another source of supply.

And, more over, you need to be developing ready-to-go mitigation plans and processes to react the minute you realize there is a disruption anywhere in your critical chain or the products delivered don’t meet the quality requirements. Tagging and monitoring isn’t enough (even assuming you can get all the data in that you need to tag and monitor appropriately), you need to know how to pre-plan, react and adapt quickly to a completely unexpected situation, and execute efficiently.

This means you need a to understand not only your supply chain and production requirements, but also risk identification, risk mitigation, and risk plan execution. Moreover, you need to understand it beyond what an average risk manager in Risk Management (who are looking at more immediate Legal and Cyber risks understand it!)

The Technological Requirements

The technological requirements are considerable and require supply chain aware sourcing and sourcing aware supply chain and expertise from source to sink and back again on both sides.

A continuing reminder that if you want guidance in the short term, hope that your favourite provider reaches out to Bob Ferrari of Supply Chain Matters or the doctor and enables us to focus on writing the series (or in-depth e-book) explaining what modern Procurement and Supply Chain Tech needs to look like (and how it needs to be implemented) to address the challenges, reduce the risks, and address the priorities versus just dripping out tidbits as free time permits.

Breaking Down The Barriers: Org and/or Tech Execution Support Capability

We’re continuing our foray into the top barriers to success that we outlined in our top barriers post that chronicles the barriers that keep coming up over and over again in every Procurement survey in our effort to ensure that you don’t have to read another state of procurement study for the next 5 years. Now it’s the barrier of organizational support and, specifically, technical support. (Most organizations just don’t have the IT Crowd they need!)

A Brief History …

As we discussed with the top barrier to success, siloed ways of working, with each successive innovation, business, and process improvement, became more complex and required more education and experience to perform. As a result, with each successive innovation, the available talent pool shrinks. Moreover, with the average large organization having eight (8) or more departments (Finance, Ops, HR, Legal, Sales, Marketing, IT, R&D, Manufacturing, Procurement, Supply Chain, Logistics, Risk Management, etc.), each department is always stretched and needs more organizational support. Plus, the number of IT systems both available and implemented in an average organization has skyrocketed from a handful (an accounting system, a MRP, and basic word processing) to, according to a recent Zylo survey, 660+ SaaS applications (on top of dozens of installed systems). (That’s average. Some organizations have more than 1,000 SaaS applications!) Despite this scary fact, there’s still only one understaffed IT department.

The Problem

In a nutshell, due to the proliferation of complex processes and their component tasks as well as the combinatorial explosion of systems and software to implement and, theoretically, support those tasks, there has been a similar, combinatorial, growth in the need for organizational and IT/Tech execution support in each enterprise department.

The Necessary Realization

The answer here is not easy. It’s not even easy to explain all of the factors you need to understand. But we will try.

First of all, as per an upcoming barrier to success, there is a talent gap in many areas. This is true even if there isn’t a shortage of available talent in the market since organizations have fixed budgets and can’t always hire all of the talent the organization could use, so there could still be a talent gap internally.

Secondly, even if the organization has talent capable of dealing with every support requirement, there’s only so many hours in a day and only so many individual support calls that an overworked (IT) support employee can take.

Thirdly, despite promises that technology would solve everything since the introduction of the first MRP (over 60 years ago), it hasn’t, and the technology project failure rates, which have never dropped below 66%, have been rapidly rising for the past 5 years or so and recently reached an all-time high of 88% (with some informal and formal indications, including a recent MIT study, that AI technology project failure rates are now as high as 95%). (See our article on two and a half decades of project failure.)

As a result, there is no perfect or simple solution to this one. However, there is a simply stated solution, and it is this:

Identify all of the tasks and processes that can be automated and automate them. (And, as per many, many articles on this site — this does NOT mean [Gen]-AI!)

However, this is easier said than done. It requires the classic people – process – technology approach which involves your best people identifying and documenting the right process, along with all of the exceptions, then figuring out what can be automated with technology, and finally taking the time to identify the right technology, define the implementation plan, oversee the implementation, do the testing and validation, and train all of the stakeholders who have to interact with it how to do so appropriately. In other words, as SI likes to say, it’s the modernized talent – transition – technology approach.

This has to be done for each process individually, and the time and effort required will vary. Especially when it comes time to identifying the right technology which, the majority of the time, will not be the tech-du-jour in the latest hype cycle. Sometimes it will be a 60 year old algorithm wrapped in 20 year old RPA. It’s not the tech, it’s the outcome … and whatever gets you there as quickly, efficiently, and free of unnecessary human effort as possible. (Remember, machines are great at thunking, as they can do trillions of calculations in the time it takes us to do 10, which is something we are not good at; but they are not great at thinking, as they are not intelligent, but that is something we are good at — but yet we spend 80%+ of our time doing tactical data processing best left to machines when we should be more focused on strategic decisions and the human element of business.)

It will take a lot of time, but if the organization as a whole follows the 80/20 rule, and focusses in on the processes that are taking the most time and deals with those first, one by one, and doesn’t fall for the vendor and consultancy hype and get misled down the wrong path, within a few years, they will start to make significant progress and within a decade will have all of the time consuming processes under control. (After all, the average journey to best in class by a committed organization is eight (8) years, as determined by the Hackett group in the 2000s.) In fact, within a couple of years of just automating one process at a time, you’ll will suddenly realize that you have made significant strides well beyond what the big consultancies will promise, but never deliver with big-bang AI projects that never end.)

The Technological Requirements

The technological requirements are considerable and require supply chain aware sourcing and sourcing aware supply chain and expertise from source to sink and back again on both sides.

A continuing reminder that if you want guidance in the short term, hope that your favourite provider reaches out to Bob Ferrari of Supply Chain Matters or the doctor and enables us to focus on writing the series (or in-depth e-book) explaining what modern Procurement and Supply Chain Tech needs to look like (and how it needs to be implemented) to address the challenges, reduce the risks, and address the priorities versus just dripping out tidbits as free time permits.

Breaking Down The Barriers: Lack of Funding

We’re continuing our foray into the top barriers to success that we outlined in our top barriers post that chronicles the barriers that keep coming up over and over again in every Procurement survey in our effort to ensure that you don’t have to read another state of procurement study for the next 5 years. Our barrier today is lack of funding.

A Brief History …

This ties into the barrier of insufficient business wide support which will be discussed in a future installment and it relates to the barrier of silos that we discussed in our first installment. The simple fact of the matter is that, as more and more departments were created, the piece of the pie each department received shank. Similarly, as system and process needs increased, the costs to operate increased. This double edge sword slashes budgets to the bone.

The Problem

As a result of the explosion in departments, and departmental needs, you have more departments fighting for more pie than actually exists. That’s the problem in a nutshell!

The Necessary Realization

Sadly there is no real solution here. Because, while theoretically, the solution is to:

  • build realistic ROI models and
  • prove the value incrementally with a staged implementation of the plan the ROI models were built on

every other department can do that as well, and why should you get more pie than they do?

Your only chance of getting your fair share of the pie, and getting it first, is to:

  • Prove the value before the request goes in.

You will need to find a very low cost tool, pseudo-hack your own solution for RFX, Analytics, SXM, Invoice Automation, etc., and demonstrate a significant value over a significant period time, at least a quarter, and preferably two or three quarters or find a low cost mid-market sourcing execution provider that has a barebones offering you can put on the P-Card for your core team. Then, build a realistic ROI model that demonstrates the full value you could extract from your process if you could upgrade your solution to handle all activities of the type (which might require buying a mature for-purpose solution from a real Sourcing and/or Procurement vendor that has been in business for half a decade to a decade and has all the workflows and capabilities you need to replace the low-cost startup minimal tools you are using now or, if you just licensed the core module from a mini-suite provider for a small number of users, license the rest of the suite, equip the rest of the Procurement organization, and contract some services to customize the workflows and capabilities as needed). The reality is that most low cost solutions or start-ups are 60% solutions at best and moving up and scaling out to 80% or 90% solution will have a huge increase on ROI (as a result of a huge increase in efficiency).

The Technological Requirements

The technological requirements are considerable and require supply chain aware sourcing and sourcing aware supply chain and expertise from source to sink and back again on both sides.

A reminder that if you want to address the problem once and for all, you need the right technology with the right capabilities that support the right processes. If you want some guidance into what this is, hope that your favourite provider reaches out to Bob Ferrari of Supply Chain Matters or the doctor and enables us to focus on writing the not yet written series (or in-depth e-book) explaining what modern Procurement and Supply Chain Tech needs to look like (and how it needs to be implemented) to address the challenges, reduce the risks, and address the priorities. Since most of it has not yet been written, it’s a big effort that, for now, we will only be able to drip out as free time permits in the future.