Commonality of Failure
Wednesday: May 23, 2007 11:43 AM
After studying and reviewing actual implementation of Enterprise 2.0 efforts, I have come to the following conclusion. You can classify implementation as either failures or successes. There seems to be a wide diversity of reasons for the successful ones. However, the failed ones are oh so similar. They look alike, feel alike, and commonality is the norm. What are the common themes?
No Leadership, Support, and no one is held Responsible
No Vision, No Strategy, and No Direction
Poor, if any at all, Communication Plan
No Metrics for Self Evaluation
No Client-Support; The “Build it and they will come” mentality is pervasive
No Business Model
No Acknowledgement that the internal corporate world is not like the Intranet
Functionality Overload
Run by IT, Designed by IT, and a complete void of Design
Tool Focused with a complete disregard for Products, Services, and Solutions. Remember, Sharepoint is a tool not a product. Products are what you do with the tool. More to come on this subject.
After studying and reviewing actual implementation of Enterprise 2.0 efforts, I have come to the following conclusion. You can classify implementation as either failures or successes. There seems to be a wide diversity of reasons for the successful ones. However, the failed ones are oh so similar. They look alike, feel alike, and commonality is the norm. What are the common themes?
No Leadership, Support, and no one is held Responsible
No Vision, No Strategy, and No Direction
Poor, if any at all, Communication Plan
No Metrics for Self Evaluation
No Client-Support; The “Build it and they will come” mentality is pervasive
No Business Model
No Acknowledgement that the internal corporate world is not like the Intranet
Functionality Overload
Run by IT, Designed by IT, and a complete void of Design
Tool Focused with a complete disregard for Products, Services, and Solutions. Remember, Sharepoint is a tool not a product. Products are what you do with the tool. More to come on this subject.
Comments (1)
I agree that IT-only projects have a high failure rate. IT egos often lead well meaning professionals to think that they can pull off large projects on their own without involvement from other areas of the enterprise.
Posted by: Jeff Livermore on May 23, 2007 15:48