How Do You Identify a Truly Stellar Supplier

Assuming one exists, how will you know one when you find one?

Five years ago, we asked how do you identify a stellar supplier? One way, as we pointed out, was to find a supplier that actively self manages. A supplier which measures, tracks, and even reports its own performance against SLAs and KPIs, accepts — and even helps to identify — the corrective actions it needs to take, actively works to not only meet expectations but exceed them, and communicates as soon as something happens that could threaten a KPI, SLA, commitment, or expectation.

Then, if you find multiple candidates, find a supplier that wants to collaborate. Find a supplier who will work with you to jointly identify opportunities for efficiency improvements and cost reductions and help keep costs down for all. This is even better. But is it as good as it gets?

No. You want a supplier who will open its books, at least so far as what it’s costs are that affect you. And what you can do to bring those costs down. That dives into its overhead costs and lets you know if energy, manpower, or cost of capital (if it needs to borrow to meet daily cash flow needs until you pay for finish goods 30 days after shipment) and what it could use from you to lower costs — such as faster payments, help with de-regulated energy negotiations, or production line improvements and lean initiatives to keep manpower costs steady. And into raw material costs, and where it needs more volume or negotiating leverage to keep costs down.

And then a supplier that helps you identify your tier 2 supply chain risks. What good does it do for a buyer to know it’s tier 1 risks when most disruptions begin further down the chain — and when the only way to possibly recover against them is to get early warning. A truly stellar supplier also works with you to put in place systems that will allow the supplier to report on potential disruptions in its supply chain (when raw materials don’t show up in time, when the quality of components it gets goes down, etc.) so you know when trouble might be brewing and, if your supplier needs help, when you can help it to prevent troubles later.

A truly stellar supplier doesn’t hide its risks and costs from you — it shares the and allows you to work with it hand-in-hand in lean efforts to create truly stellar supply chains.

Keep Your Self Driving Car. I’ll Still Choose Good Ol’ Alfred Every Day of the Week!

As the doctor pointed out back in 2014, calling #badwolf on self-driving cars is well-founded. Just last month we had more accidents involving self-driving cars (from Tesla and GM) where a Tesla “ploughed into the rear” of a fire engine in Culver City and where a GM car collided with a motorcycle in San Francisco.

And when you get injured, as in the case of the motorcycle driver, who do you sue? If the car is self-driving, then there’s no driver, just source code. Source code isn’t an entity, so all you’re left with is suing GM, as the cyclist whose motorbike was hit with the GM car is doing (as per this article in Engadget and this article in Popular Science). But is it the company? When technically it’s the software — written by who knows how many employees who used who knows what from open source to speed up development, which was again contributed to by who knows how many authors?

But you can’t sue software, it’s not an entity, at least not a legal one, and that can’t happen at least until we grant it intelligence … and the right to own assets. So, it’s GM, but are they liable under the law? And, if not, how can the individual in the vehicle, not driving, be held liable?

And what happens if the “AI” becomes artificially intelligent and decides to “improve its own code” or the code gets co-mingled with the company’s “sentiment analysis” technology and all of a sudden gains a strong “dislike” for the self driving cars of the competition and, using it’s limited action-reaction processing algorithms, determines the best course of action is to “crash into the competition cars”. What then? We’re driving cars with a “kill” switch we have no control over!

And we’ll never know if there is one! With 99M+ lines of code in an average self-driving car OS, how would you ever find the kill switch until it triggered? And if it triggered en-masse, all of a sudden we have Maximum Overdrive on a global scale! Are you ready for that? the doctor is not!

How Do We Drive Technological Advances? Part II

In Part I, we noted that this is not the first time we tackled the driving of technological advances, having preciously tackled the issue back in 2014 in our 3-part series (Part I, Part II, and Part III) where we noted that any organization that wanted to excel in Supply Management had to master the three Ts: talent, transition (not process) and technology and focussed in on technology in particular. However, not much has changed since we last tackled the subject — new technology adoption in the majority of organizations is still low, and even though 47.3% of the world’s population was online last year, we’re not sure the same statistic holds true in the business world.

And while we can’t say for sure why technological advance is slow and adoption of new technology solutions is low in an average platform, we are pretty sure that it has something to do with the fact that, especially where the older generation is concerned, especially for the older generation, they’ve heard the same old story hundreds of times before — it’ll make your work faster and better and your life easier. And, over the years, they’ve tried dozens of systems that made this claim, but few, if any, have delivered and most that delivered some still had drawbacks. At this point, any talk of trying a new solution just fills them with dread. And that’s not a great starting point for anything.

So you have to not only get past the dread and the suspicion and the outright animosity but get the key stakeholder, who, in this case, is a primary user, to an open state of mind where she is ready to try it and, hopefully, not only see how it will make her daily life easier, but like it.

And this is more than creating great tech with a great UX (which the doctor has been writing a lot about lately across the S2P cycle because just creating a system that works isn’t enough anymore), it’s creating great messaging that gets the message across. And this is as much psychology as it is marketing and definitely more psychology and marketing than technology.

Think about early adopters. Why do they adopt? Theories iclude:

  • they like the social status it brings them
  • they like to be the expert on new technology … and adopting new tech allows them to do the product research they need to be the expert
  • they want to solve their needs before their peers to stay ahead of the crowd

So, if you are targeting early adopters, you need to keep this in mind and have messaging to drive these points home. And that’s sometimes easier said than done … as run of the mill messaging will be something your target audience has probably heard a dozen times before. So, be creative.

Any other ideas to drive technological adoption?