Showing posts with label McKinsey. Show all posts
Showing posts with label McKinsey. Show all posts

Wednesday, July 1, 2015

Six steps to successful supply chain collaboration

Payam Parsa at CELDi forwarded me a link to a fascinating article over the weekend. It talks about the challenges in establishing successful supply chain collaborations with your key business partners.

Here's a sobering statistic:  80% of all supply chain collaborations in the consumer packaged goods industry fail. This is true despite the best efforts of these companies who know that they are in a hypercompetitive environment where pennies can literally make the difference between survival and bankruptcy. Even with that backdrop, there is still the promise of huge potential payouts for those organizations that can transform these initiatives into success.

collaboration.PNG

I thought there were three key lesson that we ought to incorporate into any future activity:

  1. Turn win-lose into win-win with the right benefit sharing model
  2. Select partners based on capability, strategic goals, and value potential
  3. Establish a robust, joint performance-management system

For the first point, there are going to be times when the benefits are not equal for both parties. Creative solutions could help overcome that obstacle:

Here's one real-life example: a retailer and a manufacturer were able to reduce overall logistics costs between factory and store by cutting out the manufacturer's distribution centers and treating the retailer's distribution network as one integrated supply chain, from manufacturing plant to store shelf. However, the retailer's supply chain executives struggled to gain acceptance for the idea from their leadership because it resulted in the retailer carrying a far larger fraction of the logistics cost. 

Rather than shying away from such asymmetric collaborations, smart companies can make them work by agreeing on more sophisticated benefit-sharing models. These can come in the form of discounts or price increases to more fairly share increased margins or cost reductions, or they can involve compensation in other parts of the relationship. For example, when one retailer collaborated with a manufacturer on a co-branded product line, the manufacturer agreed to absorb the upfront product-development costs in return for an expanded share of the retailer's product offerings across a wider set of categories.
....
Similarly, in the product-flow improvement case described in the sidebar ("Opportunities for collaboration," below), the manufacturer provided the upfront investment in new retail-ready packaging, while its retail partner reaped most of the benefits in terms of increased availability and reduced labor costs. The two companies established a joint benefits pool and agreed to use a percentage of the savings to fund future cost-reduction efforts and a sales-improvement program.

The second point is also easily overlooked in the rush to collaborate:

The biggest potential partner might not be the best one. Many companies aim to collaborate with their largest suppliers or customers because they assume that the greatest value is to be found there. In many cases, however, this turns out not to be true. Collaboration may be of more interest to a smaller partner, which might invest more time and effort in the program than a very large one that is already juggling dozens of similar initiatives.

Finally, creating the right key performance indicators are an absolute necessity:

....By building common metrics and targets—and jointly monitoring progress—companies avoid the misaligned incentives that damage so many collaboration efforts. 
Picking the right metrics can be challenging, however, and it will inevitably involve trade-offs. In a collaboration to reduce logistics costs, for example, the partners may have to choose between a pallet configuration that's optimized to suit a retailer's restocking processes, which will reduce in-store labor costs, and one that optimizes truck fill, which will reduce transportation costs from distribution center to retail store.

How to overcome these potential conflicts? The trick is to keep things simple by picking the smallest possible number of metrics required to give a picture of the collaboration's overall performance, and then to manage those metrics closely, with regular joint reviews and problem-solving sessions to address trade-offs. The real power of any performance-management system comes from this frequent, robust dialogue between partners, yet this is also the element most commonly ignored or underemphasized by collaborating companies.

Wednesday, June 10, 2015

What is the question?

Original post:  Oct 7, 2013

Last week, I had an extended discussion with Michael Pheney of GS1 US. We were discussing the direction of the GS1 efforts in the United States now that the UDI rule has come out. There has been a flurry of activity, but much of it seems to be headed in a million different directions. I asked Michael for his opinion on this. I am hoping that at some point GS1 US reveals the outlines of their objectives for the coming year.

We are at a significant crossroads in our data standards efforts. We know that these efforts are critical to form the basic infrastructure which ties everything together. At the same time, there is no consensus for the best path forward. We can't really adopt the models used in other industries. There are too many differences between the drivers in a retail or grocery model that do not apply in the healthcare model. We need to figure out how we can get to a similar result by taking a very different road.

There are many people who are quick to point to the studies which say that there are all kinds of opportunities to save money in healthcare. In 1996, the EHCR study pointed to $11 billion in potential savings. A McKinsey study released earlier this year by GS1 also declares billions in potential savings. I think everyone agrees that this is the "answer" we are all seeking.

If we all agree on the results, I guess the search is for the right questions that will lead us to that answer. There are millions of possibilities. We've got to find the right ones that will end up where we want to go.

Over the weekend, the boys were watching a nature show about lions and giraffes. Normally, lions will not go after giraffes because they are vulnerable to killer kicks and the difficulty in climbing up a giraffe's back to get to the vulnerable throat. Scientists were amazed to discover multiple giraffe carcasses and wondered what was wrong. Over the course of the show, they eliminate one theory after another and find a potential explanation. It seems that a certain disease first started affecting giraffes. The weakened giraffes made for easy prey for the lions of the area. Once the lions got a taste for giraffe, they started to attack the healthier survivors and come up with tactics that allow them to slay the previously formidable opponents.

In the same way that the scientists pieced together this explanation, we'll have to dissect our supply chain and figure out how we can best apply the lessons learned in other industries. It will be vital that we do find the right questions that will take us to the desired solutions.

Monday, June 8, 2015

They get promoted for the class of problem they can solve

Original post on June 8, 2011

I recently ran across two separate quotes from high-powered IS executives that I wanted to remember.

The first is from a Senior VP in IS:

The problems you want your technical leaders to solve are too big for one person or one team.
These leaders must see the big picture, be quick studies, organize teams, break up finger-pointing,
use their broad and deep technical experience to guide investigations, and balance immediate
pressure to get systems back up at any cost while discovering and fixing the problems.

My role as senior VP over the application group was to provide political cover, “managing up”
and making any decisions the technical team didn’t think it could make.

My rule is, people don’t get promoted for what they know;
they get promoted for the class of problem they can solve.

The second is from a profile of a CIO:

The people I worked with at McKinsey during 1990-’94. They helped me transition from a techie
to being more well rounded. After one of my first meetings with a group of key client executives,
a McKinsey partner asked me what I thought. I outlined what I thought the best technical solution was.
He asked how I knew that was the right answer. The best I could come up with was,
it was intuition from my years of previous experience with similar situations.
He explained that without thoroughly understanding the client’s business and analyzing the data
around the various options, intuition could easily lead to the wrong answer.