One of my biggest issues with the ‘Project Management 2.0′ concept is that it is conceptualized around other ’2.0′ concepts like ‘Web 2.0′ and ‘Enterprise 2.0′; both of which are terms that emphasis and denote a technological dimension relating to human interactions. In that context, and following the same logic, PM 2.0 is meant to be denote the application of ’2.0′ technologies to enhance project management capabilities.
A recent article in the Harvard Business Review analyzed the reasons behind the failure of western Intelligence Services to prevent the recent terror attack on an American Airline. The article states that the whole episode represents a “massive failure of collaboration among intelligence and governmental officials”. The facts known about this terror attack are sufficient to conclude that although there was sufficient information to enable an effective prevention of this incident, it lacked nevertheless the final touch of connecting all the dots and consolidating the known data into effective management information.
The author of the HBR article concludes that despite the US (and other countries) investing in IT systems aimed at supporting the above detection and alert systems, it lacked nevertheless the investment in cultural change necessary to ensure that information is not only collected but is also shared. This, the author says, is a matter of cultural change, one that will encourage and foster not just collaboration but effective collaboration.
An interesting case study is cited by Professor Morten Hansen from the INSEAD institute, where SONY failed to launch an effective competition against the Apple iPod and, despite having a collective know-how and expertise in all aspects of designing and manufacturing an iTunes-iPod hybrid, “it turned out to be a failure because the individual departments did not work in unison”.
In an earlier post I have stated that ‘a fool with a tool is still a tool‘. The premise of that post was that a tool in the hands of an inexperienced user, will not generate the desired results. The observations cited above add another dimension to this claim. they highlight the point that even when used by experienced users, desired results are still dependent on other organizational factors, primarily based around cultural adaptation.

Pingback: Shim Marom
Pingback: Shim Marom
Pingback: gedpro
Pingback: Tweets that mention Collaboration is an attitude not a a tool | quantmleap -- Topsy.com
Pingback: Manuel A. Velázquez
Twitter Comment
Collaboration is an attitude not a a tool [link to post]
– Posted using Chat Catcher
Pingback: Jezabel González
Twitter Comment
Chapeau! RT @manuelvl: RT @gedpro: Collaboration is an attitude not a a tool [link to post]
– Posted using Chat Catcher
Twitter Comment
RT @gedpro: Collaboration is an attitude not a a tool [link to post]
– Posted using Chat Catcher
Pingback: Shim Marom
Pingback: Shim Marom
Pingback: Shim Marom
Pingback: uberVU - social comments
Pingback: Serge Guézénoc
Pingback: David BATHIELY
Pingback: Collaboration is an attitude not a a tool « quant.M.leap
Pingback: Christian Hennerfehr
Pingback: Shim Marom
Pingback: Adi Prabowo
Twitter Comment
RT @shim_marom quantmleap: Collaboration is an attitude not a a tool [link to post] #pmot #ftpm #pm
– Posted using Chat Catcher
Pingback: Shim Marom
Pingback: fellowstream
Pingback: Shim Marom
Pingback: Tony Collins
Pingback: Shim Marom
Pingback: Purple Projects
Pingback: Eric D. Brown
Pingback: Thomas Balt
Pingback: Karl Goldfield
Pingback: KommandCore Company
Pingback: Hannes Heckner
Pingback: Shim Marom
Pingback: Jo Ann Sweeney