In the world of IT it seems like it is often too easy to throw things together. New technologies are bought and implemented. Integrating them with existing hardware and software is an exercise in duct tape and shoe horns that happens after the initial rollout. Security is something that is tacked on months, or even years later, immediately following a major security event and executive management questioning the judgment of having left the system insecure for so long.
Given all of that, it is nice to see an organization stop and take a look at how you might approach a UC project if you wanted to get it right. Because, while it may *seem* easy at the time to just stick things together with chewing gum and determination, and you may realize some short term benefit from being on the bleeding edge of using some cool new technology, it will eventually come back to haunt you. It may be months, or it may be years, but an IT network, more specifically a UC implementation, will eventually start to crash and burn and show its ill-fated lack of planning.
To help organizations get it right the first time, Verizon has developed a set of guidelines or best practices to use when approaching a UC deployment project. Here are the major steps to their plan:
- Invest in advanced IP networks
- Inventory technology and personnel resources
- Align technology with business objectives
- Establish a benchmark for success
- Create a comprehensive roadmap
- Maximize impact of UC&C on business processes
- Tackle security at the onset
- Determine capabilities for ongoing management
- Develop support systems and processes
- Train and educate end users
- Measure and modify