How to Migrate to IP Telephony
Build a cross-functional team., Get your users on board., Do your homework., Capitalize on what has worked in the past, and learn from the mistakes of others. , Ensure user requirements drive design requirements., Crawl first, walk proudly, and run...
Step-by-Step Guide
-
Step 1: Build a cross-functional team.
Put together a team that has both technical expertise and represents users.
Key members include an executive sponsor, a project lead, technology experts, and subject-matter experts from across the organization.
When global or multinational regions are involved, include members from each. -
Step 2: Get your users on board.
Resistance to change is normal and should always be anticipated.
Manage user expectations by using education and frequent communication to mitigate mystery and uncertainty. , Understanding your organization's culture is critical to successfully implementing new technology on a large scale.
Consider questions such as:
•Does your company encourage risk taking?
•What have previous technology deployments taught you about how users prefer to be trained? ,, Develop surveys and focus groups to identify user-preferred services and features.
Use the survey as a tool to identify critical communications features, validate key business needs, gauge risk tolerance and user discomfort, and identify key functionalities that are paramount to your business. , Your implementation strategy should allow you to progressively move faster as your experience levels become more efficient.
The number of employees, complexity of user requirements, size of the organization, and how widely all are dispersed affect your migration strategy.
Develop a strategy that accounts for all the variables that could change or affect implementation of the network. , Success depends on several considerations, most important among them is planning.
In fact, implementations usually consist of 80% preparation and 20% installation.
Quite simply, if you focus on your plan first, the implementation will be much smoother. , A successful Day 2 handoff (defined as the time period immediately following cutover of your new IP telephony solution) requires a well developed support plan, with four elements:
•Team: people who can resolve the entire spectrum of issues
•Processes: use the ones you already have in place rather than creating new ones
•Services: internal and external teams, management tools, and global coverage
•Tools: network monitoring tools to resolve problems before they become visible to users , Most large enterprises have hundreds of lines and circuits that, through the years, have either been forgotten about or are simply unused.
View your IP telephony implementation as an opportunity to start anew, as well as clean and prepare the IP infrastructure.
So, when the implementation team begins the conversion, remove as many unused lines off the PBX as possible, and only convert those lines that are actually in use. , The team member responsible for the retrofit cleanup should enter all PBX leases into a spreadsheet and develop a project plan to keep the returns on track. , Whether an IP telephony implementation involves 200 phones or 20,000 phones, change management will be the most challenging ongoing process to maintain, but not because of routine changes or software upgrades.
Maintaining a strict, yet manageable and scalable, process will be critical to your success, so eliminate as many unknowns as possible by documenting your procedures and capturing lessons learned. -
Step 3: Do your homework.
-
Step 4: Capitalize on what has worked in the past
-
Step 5: and learn from the mistakes of others.
-
Step 6: Ensure user requirements drive design requirements.
-
Step 7: Crawl first
-
Step 8: walk proudly
-
Step 9: and run aggressively.
-
Step 10: Follow the 80/20 rule.
-
Step 11: Ensure a successful handoff.
-
Step 12: Keep your new network clean.
-
Step 13: Plan for PBX lease returns.
-
Step 14: Look back
-
Step 15: move forward
-
Step 16: and prepare for the future.
Detailed Guide
Put together a team that has both technical expertise and represents users.
Key members include an executive sponsor, a project lead, technology experts, and subject-matter experts from across the organization.
When global or multinational regions are involved, include members from each.
Resistance to change is normal and should always be anticipated.
Manage user expectations by using education and frequent communication to mitigate mystery and uncertainty. , Understanding your organization's culture is critical to successfully implementing new technology on a large scale.
Consider questions such as:
•Does your company encourage risk taking?
•What have previous technology deployments taught you about how users prefer to be trained? ,, Develop surveys and focus groups to identify user-preferred services and features.
Use the survey as a tool to identify critical communications features, validate key business needs, gauge risk tolerance and user discomfort, and identify key functionalities that are paramount to your business. , Your implementation strategy should allow you to progressively move faster as your experience levels become more efficient.
The number of employees, complexity of user requirements, size of the organization, and how widely all are dispersed affect your migration strategy.
Develop a strategy that accounts for all the variables that could change or affect implementation of the network. , Success depends on several considerations, most important among them is planning.
In fact, implementations usually consist of 80% preparation and 20% installation.
Quite simply, if you focus on your plan first, the implementation will be much smoother. , A successful Day 2 handoff (defined as the time period immediately following cutover of your new IP telephony solution) requires a well developed support plan, with four elements:
•Team: people who can resolve the entire spectrum of issues
•Processes: use the ones you already have in place rather than creating new ones
•Services: internal and external teams, management tools, and global coverage
•Tools: network monitoring tools to resolve problems before they become visible to users , Most large enterprises have hundreds of lines and circuits that, through the years, have either been forgotten about or are simply unused.
View your IP telephony implementation as an opportunity to start anew, as well as clean and prepare the IP infrastructure.
So, when the implementation team begins the conversion, remove as many unused lines off the PBX as possible, and only convert those lines that are actually in use. , The team member responsible for the retrofit cleanup should enter all PBX leases into a spreadsheet and develop a project plan to keep the returns on track. , Whether an IP telephony implementation involves 200 phones or 20,000 phones, change management will be the most challenging ongoing process to maintain, but not because of routine changes or software upgrades.
Maintaining a strict, yet manageable and scalable, process will be critical to your success, so eliminate as many unknowns as possible by documenting your procedures and capturing lessons learned.
About the Author
Henry Wright
Creates helpful guides on crafts to inspire and educate readers.
Rate This Guide
How helpful was this guide? Click to rate: