Establish a Communication and Collaboration System Strategy
Collaboration should drive your collaboration tool selection.
RETIRED CONTENT
Please note that the content on this page is retired. This content is not maintained and may contain information or links that are out of date.IT’s broken approach to enterprise collaboration tools has led to:
- Users and business units circumventing IT and adopting their own solutions
- Redundant collaboration tools offering overlapping capabilities
- Far too many tools for IT to improve and/or maintain
Follow Info-Tech’s approach, and reap these benefits:
- Greater end-user adoption of your collaboration services
- A slimmer collaboration portfolio
- Higher end-user satisfaction
Book Your Workshop
Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.
Module 1: Identify What Needs to Change
The Purpose
- Create a vision for the future of your ECS.
Key Benefits Achieved
- Validate and bolster your strategy by involving your end users.
| Activities: | Outputs: | |
|---|---|---|
| 1.1 | Prioritize Components of Your ECS Strategy to Improve |
|
| 1.2 | Create a Plan to Gather Requirements From End Users |
|
| 1.3 | Brainstorm the Collaboration Services That Are Used by Your Users |
|
| 1.4 | Focus Group |
|
Module 2: Map Out the Change
The Purpose
- Streamline your collaboration service portfolio.
Key Benefits Achieved
- Documented the business requirements for your collaboration services.
- Reduced the number of supported tools.
- Increased the effectiveness of training and enhancements.
| Activities: | Outputs: | |
|---|---|---|
| 2.1 | Create a Current-State Collaboration Capability Map |
|
| 2.2 | Build a Roadmap for Desired Changes |
|
| 2.3 | Create a Future-State Capability Map |
|
| 2.4 | Identify Business Requirements |
|
| 2.5 | Identify Use Requirements and User Processes |
|
| 2.6 | Document Non-Functional Requirements |
|
| 2.7 | Document Functional Requirements |
|
| 2.8 | Build a Risk Register |
|
Module 3: Proselytize the Change
The Purpose
- Ensure the system is supported effectively by IT and adopted widely by end users.
Key Benefits Achieved
- Unlock the potential of your ECS.
- Stay on top of security and industry good practices.
- Greater end-user awareness and adoption.
| Activities: | Outputs: | |
|---|---|---|
| 3.1 | Develop an IT Training Plan |
|
| 3.2 | Develop a Communications Plan |
|
| 3.3 | Create Initial Marketing Material |
|