May 3, 2007 2
Three issues in Supply Chain Management 2.0 – Part 2
As mentioned previously, Michael Lamoureux is hosting this year’s Big Bad Blogger Throwdown at his blog – Sourcing Innovation. Here is the link to the announcement of the cross-posting cornucopia. As recounted in the first part of this series at Three issues in Supply Chain Management 2.0, I listed out my three top issues that I think are important for firms to be cognizant about. They were:
1. Supply Chain Talent
2. Closed loop Supply Chain Management
3. Supply Chain Collaboration
In this post, I will delve into the first of the three issues in a more substantive fashion including trying to answer such heady questions such as Why the issue is important?, Why if a company did nothing about, its apocalypto now? and What if anything a company should do at all? (This is code for “You should really be hiring us Supply Chain bloggers as consultants” or something like that). As I write this, what is perking up from the top of my head like that strand of hair that will just not fall into place no matter the steady grooming in process, is the silly realization that I am acting like a theologian pontificating on sin, fall and redemption – version 2.0, no less. If you didn’t get that last line, never mind, its just my confession. So here we go!
Background:
Just in case, you haven’t read the previous post in this series, here is a brief recap of what is in situ. I inquired into what could be termed SCM 1.0 and SCM 2.0 and the relation that both have with Web 2.0. After that, thanks to the good people at O’Reilly and Chris Alexander, I opined about Design Patterns in Web 2.0 which are recounted below:
1. The Long Tail
2. Data is the Next Intel Inside
3. Users Add Value
4. Network Effects by Default
5. Some Rights Reserved
6. The Perpetual Beta
7. Cooperate, Don’t Control
8. Software above the level of a Single Device
This is how Web 2.0 lives and breathes – the above is the central and structural DNA of the anarchic ecosystem that is spreading through the internet. So how do my issues figure against that Web 2.0 paradigm?