collaboration


  • It Takes More Than Sharing Information to Prevent Terrorist Attacks

    More than eight years after lack of collaboration among intelligence agencies contributed to the September 11, 2001 terrorist attacks on the United States, the Central Intelligence Agency is facing new allegations that it failed to share vital information that could have thwarted last week’s attempted bomb attack on Northwest flight 253.  

    ODNI Logo President Obama yesterday scolded the United States Intelligence Community for “a systemic failure” because intelligence agencies apparently never shared all of their information about the suspect before he boarded the plane and was ultimately subdued by passengers. The National Security Agency reportedly had information that Al Qaeda operatives in Yemen were preparing a Nigerian to commit a terrorist attack against the United States. And the Central Intelligence Agency had reportedly met with the father of Umar Farouk Abdulmutallab , the suspect, at the U.S. Embassy in Nigeria. The suspect’s father apparently informed the CIA of his son’s radicalization. Had there been greater collaboration among agencies, President Obama has said that the suspect’s name would have appeared on the so-called No Fly List, which likely would have prevented him from boarding the Northwest plane.

     

    According to the lead story in today’s Wall Street Journal, officials of the National Counterterrorism Center which acts as a clearinghouse for terrorism data, have indicated that the CIA failed to share all of its information with other agencies.

     

    The problem is that terrorists are often highly collaborative, but the Intelligence Community has lagged behind in embracing collaboration. The 911 Commission Report recommended a reorganization of the 16-agency Intelligence Community under a Director of National Intelligence. The report also recommended increased information sharing among agencies to thwart future attacks. Subsequently, President Bush signed the Intelligence Reform and Terrorism Prevention Act of 2004 which established the Office of the Director of National Intelligence (ODNI), the National Counterterrorism Center, and called for “open-source intelligence.” In 2007, ODNI implemented a 100-day plan and a 500-day plan for Integration and Collaboration among agencies.

     

    As part of the new commitment to collaboration, the Intelligence Community adopted A-Space, modeled after MySpace and Facebook, so that analysts could share information across agencies. The community has also adopted Intellipedia, a cross-agency wiki.

     

    On the sixth anniversary of the terrorist attacks, I gave a speech to the Intelligence Community. The speech was sponsored and hosted by ODNI. In the speech and during subsequent meetings with senior intelligence officials, I insisted that it would take much more than tools and a top-down collaboration initiative for the Intelligence Community to actually collaborate. Our research at The Culture of Collaboration® Institute indicates that in any organization, people may buy into collaboration as a concept, but in practice it’s a totally different story. Therefore, reducing fear of collaboration and changing behavior are crucial to cultural shift.

     

    Clearly, intelligence requires protecting classified information just as corporations must protect trade secrets. But aside from keeping outsiders from obtaining information, many career intelligence officers have been conditioned to embrace secrecy within their community. This fosters information hoarding, intra-agency rivalry and intelligence failures. It takes more than new tools and technologies and more than even an act of Congress to abandon this deeply-engrained conditioning.

     

    Sharing information among agencies is undoubtedly necessary, but thwarting attacks requires much more. Even if agencies make information available to one another, people need to know how to act on that information.  Therefore, I will reiterate here two major points on which I’ve counseled senior intelligence officials:

     

    1) Favor on-the-fly decisions over chain-of-command decisions.

    2) Encourage spontaneous interaction over scheduled encounters and meetings

     

    The White House and intelligence officials can talk ad nauseam about sharing information. If, however, analysts and other intelligence personnel are expected to run decisions “up the flagpole” and are inclined to schedule meetings rather than connect with colleagues and hash out issues on the fly, it will remain difficult to thwart attacks.

     

    As I noted in The Culture of Collaboration book, "the in-box culture is dead." And if asynchronous information sharing persists without the necessary real-time cultural components, intelligence failures will continue. The cultural shift necessary to prevent security lapses like the one aboard Northwest flight 253 involves moving beyond information and data sharing—and embracing real-time collaboration.



  • Cisco’s John Chambers: the Hardest Part is the Culture

    I was watching Cisco CEO John Chambers do his trademark walk-and-talk style keynote yesterday at the Hilton San Francisco Union Square as Cisco was kicking off its Collaboration Summit when suddenly John interrupted his pitch for collaboration.

     

    “Do you know what the hardest change is in this?” he queried the audience rhetorically. “As any CEO will tell you, it’s the culture.”

     

    John’s observation resonated with me in that the fundamental premise of The Culture of Collaboration book is that “without a culture of collaboration, the best processes, systems, tools and leadership strategies fall flat.” In the book, I also note that “the overwhelming reason why collaboration eludes organizations involves culture.”

     

    Understanding the role of culture in creating a collaborative enterprise is paramount, particularly as Cisco introduces 61 collaboration products. Collaboration tools are key enablers, but they are far more effective in enabling collaboration in enterprises with collaborative cultures and processes.  Cisco has been focusing on collaboration more than any other initiative as an organizational imperitive and in product efforts. Now the company is fixated on persuading customers that it has reached a milestone in innovating collaboration. With that in mind, Cisco vice president of enterprise solutions Alan Cohen, a history buff and blogger, noted that Cisco was announcing its slew of products on the 20th anniversary of the Berlin Wall’s fall and observed that it was one of the “biggest transitions in our history.”

     

    As Tony Bates, Senior Vice President and General Manager of the Enterprise Group, highlighted Cisco’s major product introductions, he emphasized the increasing role of video in collaboration—from Flip Video camcorders to WebEx web conferencing to telepresence—and the interactivity of these tools. You can read details of the product announcements here.

     

    At a cocktail party following the keynotes, Tony and I had an engaging conversation about how the role of video has evolved. I mentioned that when I was researching my first book, Personal Videoconferencing, in the mid-1990’s, there was considerable push back against real-time video as a viable business tool. People were scared of the camera, and there was a pervasive view that one needed to have highly-honed presentation skills to use videoconferencing. Tony observed that people are increasingly accepting that the way they conduct themselves in meetings and in one-on-one workplace interactions is good enough for many video interactions.

     

    Currently, most telepresence and web conferencing interactions are scheduled. As organizational cultures evolve to support more real-time collaboration, video interaction will become more spontaneous. Then real-time video will transcend communications and become part-and-parcel of collaboration.