How do you get started deploying collaboration?
In my meetings with Cisco customers, I find that companies have moved beyond asking “what is collaboration?” to “how do I get started?”
Corporate executives at the most senior levels are at a point where they understand the value of collaboration, how this will transform how we work and how IT really does deliver “services” (I’ll fully address the value proposition of collaboration in a later blog – stay tuned for that).
When it comes to actual deployment, I’ll use Cisco as one example. From an IT transformation perspective, our goal was to accelerate productivity, growth and innovation. We moved from sequential to agile development, from a rigid product life cycle methodology to one with rapid prototyping, from a “my way or the highway” approach to one of “wisdom of crowds,” and from a local, internal view to one that was global and will address the entire workforce ecosystem.
We identified six steps to transformation:
- Develop and communicate a shared collaboration vision for your company.
- Develop an enterprise-wide architecture approach. Collaboration has to be for the enterprise as you can’t collaborate across fragmented technologies.
- Identify which business pain points you are trying to solve: what are the key cross functional business opportunities?
- Develop an integrated technology roadmap.
- Deliver “mash – up”: workforce services that will surprise and delight your business.
- Communicate, communicate and communicate.
It was critical to involve all functional areas in our collaboration deployment – this was not just about IT, but about all areas of our company, including various business units, finance, HR, legal, sales, corporate positioning, marketing, engineering and corporate communications. The goal is to ensure that our collaboration solution reflects everyone’s requirements. Our Communications and Collaboration board has accountability and governance for how we’ve developed our integrated workforce experience (IWE).
We found that there is a tremendous amount of change management and communication required for deployment. Anytime you try to change employee behaviors – even in a fast-moving company like Cisco where our employees are generally savvy about technology (in fact, many are early adopters) – you have to counter entrenched habits. So continuous communication – from face to face meetings to virtual meetings to video, video, video to formal company announcements and forums – have been part of our overall effort to communicate and educate the company about the IWE vision and specific calls to action.
So far, we have about 60,000 IWE users out of 110,000 total employees and contractors worldwide. About half of the 60,000 are heavy users, the other half more casual users. We move to a full enterprise deployment to all 110,000 employees and contractors on November 12 on Cisco Quad. So, as you can see, we still have a way to go in our communication plans.
Next week I’ll address the topic of collaboration as not just about the technology but also as one that must include business process and how important the culture is in making the transformation.