Who is the First Person You Should Hire?

If I had a dollar for every time I’ve been asked that question-well you know how that story goes?  At every single conference across the globe I’ve spoken at, that question has been asked in some way, shape or form.  Almost every single client has asked that question or some variation thereof.  And the ones that did not should have asked that question.  You can think about it in terms of what is a critical role that you must fill in your Sourcing/Supply Chain organization or any other internal “support” function (IT, Finance, legal) or shared service to confirm my contemporary bona fides.

Before I give you the answer, we need to make sure that we are asking the right questions.  And for those of you that have been through TMG’s decision making module, that refrain will sound very familiar.  Remember the New England Journal of Medicine exercise where physicians were asked to evaluate patients for toncillectomies and they were wrong 49% of the time ?  Otherwise, we can turn to what a couple of my friends said.  Pete says “The most common source of mistakes in management decisions is the emphasis on finding the right answer rather than the right question.” My friend Al goes on to say basically the same thing: “The formulation of a problem is far more essential than its solution, which may be merely a matter of mathematical or experimental skill.”

Typically, would you agree that in most cases (not including yours of course):

  • Organizations struggle with convincing their stakeholders of the value they create?
  • They face strong resistance in expanding their influence or footprint?
  • Budget wars are an annual and the quarterly norm?
  • Savings numbers are always questioned for validity?

If any of the above is true, then the answer to the title becomes self-evident.  A Marketing person!  I kid you not.  In the first Sourcing organization I set up in my career 16 years ago we had a full time marketing person (Peter).  His job was to constantly market our services and we took a marketing approach to it.  This wasn’t about creating some spreadsheets or graphs of generated savings.  He had to make sure that we continued to expand our footprint inside the company.  To sell our value to the stakeholders.  To keep in constant communication with them.  To make sure we were getting repeat business.  To ensure that we were getting referral to other stakeholders.

Now I’m sure that you are doing all of the above but I’m talking about most of the other organizations.  We have not seen  a true marketing focus being applied to this effort and I’m always surprised by that.  Especially given the tools available today.  It does not necessarily mean that you need to have a full time dedicated resource but you do need to fulfill that role.  So next time you are sitting in a budget meeting being asked one more time to take another haircut, you may want to think about your marketing effort.  Oh, Pete is Peter Drucker and Al is Albert Einstein.  Let me know if you would like more details.

Did you like this? Share it:

Apple Kickback Scandal: A Lesson in Risk Management

Today’s post is from Dr. Lowell Yarusso, Senior Vice-President, Talent Management, of The Mpower Group (TMG) and a contributor to the News U Can Use TMG blog.

News reports that an Apple global supply manager is accused of receiving illegal kickbacks in return for providing access to inside information about Apple’s sourcing strategies reminded me of an old Baseball story.  A rookie was at the plate for his first at bat in “The Bigs”.  The umpire was one of those old timers who had seen it all.  The pitch came in on the borderline and the ump paused before making his call.  The impatient rookie quickly asked, “What was it?” The ump’s response, “Kid, it ain’t nothin’ ‘til I say it is.” The same can be said about risk.  It “ain’t nothin’ ‘til someone says it is”.

And that’s the rub.  While I’ve talked around this issue in several other blogs and articles, the Apple case focused me on it again.  The early efforts to determine where Apple went wrong seem to point out the frequent tendency to close the doors that have “Entrance” signs and to ignore the ones that say “Employee’s Only”.  Many of the comments I made in discussing employee theft (What’s in the Wheelbarrow: Theft and the Supply Chain) apply here as well.  But, more to the point, how does an employee get the opportunity to take hundreds of thousands of dollars in kickbacks without someone noticing?

Part of the problem lies in the way companies approach the issues of risk and security.  Before you can address a risk, you have to recognize that it exists.  Like the umpire said, until you put a name on it, it doesn’t exist, at least not in the sense that you can do something about it.  One of the key issues I raised re: the Barings Bank collapse (Risk Management Lessons from Barings Bank (RIP)) is the tendency to apply a “black box” mentality so long as results appear to be favorable.  In this case, I can only speculate that, if anyone asked about it at Apple, the response was something along the lines of “We made our goals; everything must be under control.”  The possibility seldom occurs to anyone that, sometimes, things are not just going better than expected; they’re going better than should be believed.

While there are lots of clues to such situations, in most cases, they seem to only become clear after the fact.  The natural assumption is that, because they were recognized after the risk was identified, no one could have seen them in time to do some risk mitigation.  That assumption is wrong.  The clues are always there and are always identifiable IF the organization takes risk management seriously and makes it a top priority, from both a leadership and a management perspective.

Leadership has to make honesty and integrity the cornerstones of the business.  Everyone, from the top down, has to make it clear that there is zero tolerance for behaviors that cross the line.  Apple’s reaction to the scandal has been vigorous and shows the right attitude at the top.  The question that I have is whether or not that same attitude has been driven down through the entire organization.  How many individuals at lower levels were more concerned about what cost goals they achieved than about how those goals were met?  Organizations need to continually and consistently talk about the values and ethics that are expected and the behaviors that will not be tolerated.  A placard on the wall proclaiming that “We are an ethical organization” quickly becomes part of the background if it is neither strongly reinforced nor vigorously applied.  That’s a leadership issue and it requires that leaders make calls on a daily basis so that everyone knows the balls from the strikes.

From the management perspective, organizations have to craft their processes and procedures to reflect their commitment to ethical conduct.  In the sourcing arena, that means that there should be a periodic review of results that focuses not only on such issues as adherence to internal control procedures but also considers whether or not results are consistent with business expectations.  And, yes, every organization assumes its suppliers will bend over backwards to make them happy.  But, if one person has a significantly better track record, if one category area is always out in front in terms of hitting should-cost estimates, exceeding requirements, or in other ways outperforming the norm, red flags should go up.  Unfortunately, such a situation is frequently called “great work” rather than “potential risk”.  And, as in baseball, the pitch becomes what it is called.

Another management issue is that of the reward structure for the sourcing organization.  Bonuses based on cost savings are a two-edged sword.  They not only motivate good sourcing practices, they also provide powerful temptations to cut an ethical corner here or there so that bonus goals are met.  It should be obvious (and usually is in retrospect) that a sourcing group that consistently meets its price reduction goals year in and year out may not be working with the best interests of the organization as its primary motivation.  (I have seen situations where buyers asked suppliers to spread an offered price reduction over three years rather than granting it in the first year so they would be sure to make their numbers now and in the future!)  Here, again, what you call it becomes what it is.

The bottom line is that organizations need people, like the umpires, who look at the pitch dispassionately and call it as they see it.  A great tool in this regard is the application of scenario planning as part of the risk assessment effort.  One approach is to establish a process review system that includes the question, “What would we expect to see if someone broke faith with our ethical code?”  While there is no guarantee that such a review would have spotted the issue at Apple sooner, by naming surprising results a risk, the potential problem might have been identified and investigated more diligently.

What’s your take on this area of risk?  I’m interested in your thoughts, especially with regard to: 1.  Do you think that Apple’s experience is only remarkable because it was discovered, i.e., does this kind of thing go on far more than we realize?  2.  What have you seen that falls into the realm of risks that “…ain’t nothin’ ‘til someone says it is”?

Did you like this? Share it:

What “Supply Chain Management”?

Here are two definitions which I found on Wikipedia that I would like you to consider:

Supply Chain - A supply chain is a set of organizations directly linked by one or more of the upstream and downstream flows of products, services, finances, and information from a source to a customer.  (Mentzer et al., 2001).

Supply Chain Management – Supply Chain Management is the systemic, strategic coordination of the traditional business functions and the tactics across these business functions within a particular company and across businesses within the supply chain, for the purposes of improving the long-term performance of the individual companies and the supply chain as a whole (Mentzer et al, 2001).

We like to talk about this thing called “Supply Chain Management” but few companies are actually doing it.  Most companies have a CEO, a COO (responsible for operations), a CFO (responsible for finance), a CIO (responsible for information technology), CE (responsible for engineering /quality) but how many companies have a Chief Supply Chain Officer who is responsible for the end to end Supply Chain.  By the way, if you reread the definition of a Supply Chain, the “C” level executives noted above all have a role to play in the end to end Supply Chain whether they know it or not (mostly not).  So some might say that it is the CEO’s responsibility but does he/she really have time to provide the necessary level of oversight? 

Many companies that have designated a Supply Chain leader or have a Supply Chain organization have adopted a very narrow definition of a Supply Chain which may include purchasing, logistics, warehousing transportation, etc. but almost never includes finance, operations or engineering.  How can you have “systemic, strategic coordination” of all the business functions in an end to end Supply Chain when each functional organization operates in its own organizational silo under a set of metrics that are usually not aligned with the one another?  So, in other words, true “Supply Chain Management” isn’t happening.  I chuckle when I read the myriad of articles that have been published regarding, the “integrated supply chain”, the “optimized supply chain”, the “flexible supply chain” and the latest thinking which is defined as “value chain management”.  These are all great models but few of them address the biggest issues – resistance to change and lack of collaboration.

I spend quite a bit of time training Strategic Sourcing and Supply Chain (narrow definition) organizations.  The number one frustration they experience is that most of the issues that occur in the end to end Supply Chain are blamed on Procurement (Purchasing / Sourcing) or the suppliers when in fact many of the issues are caused by other functional organizations within the Supply Chain.  I believe one of the key reasons is the lack of understanding of the true definition of Supply Chain and the roles within it for all functional areas.  Of course siloed organizations and misaligned metrics don’t help either.

I have actually tested my assumption around the “lack of understanding”.  When presented with the opportunity, I have asked the CFO, CIO or CE what their definition is of a Supply Chain and their role in it.  I most often hear the narrow definition AND that their organization has no role – very telling indeed.

Watch for future blogs as I explore some of the potential solutions . . . . . . .

Did you like this? Share it: