Top 10 learnings from an enterprise videoconferencing rollout. 11 slides and a guide.

1. Learning from an Enterprise
Videoconferencing Rollout

2. 1. Design for the customer
Business
Unit Function Leadership CEO
Internal Teams Customers and Partners
Cross-region Customer Use Cases
Sales Mktg Pdt
Mgmt IT

3. 2. Start small but fully
expect to scale – rapidly
Sales and Leadership tend to be early adopters

4. 3. Understand Potential Meetings
Customer
meetings
1:1
CEO Broadcast
All hands
Candidate
interviews
Training
Regional planning/
reviews
EXPECT:
Content Sharing
(video, presentation,
web content)
Recording of meeting
Question for the
security folks?

5. 4. Build the business case
Savings on travel
Don’t forget the intangibles:
Humanizing Relationships (next best alternative)
Work together anytime, anywhere – collaboration and mobility
Shorter timeline to get things done
A strong sponsor

6. 5. Know the Technology Components
“Skype for Business”
Network Security
In-room systems
Cloud services
Devices
+

7. 6. Make the “Technology” Decision 1
Buy from a service
provider or cloud
provider from the
outset (if possible)
Mobile devices will
want access from Day 1
“Skype for Business”

8. 7. Make the “Technology” Decision 2
In-room systems are still relatively
expensive
They also need owners, standardisation, policies, integration,
“evangelism”
Seamless experiences (cloud
service/ in-room/ device) are
crucial
Be clear about security needs

9. 8. Launch, Measure and Tune
Meeting minutes
on the network
Growth
Geographic
usage
Meeting minutes per
unit
Unit monthly
utilisation rates
Types of meetings
Active SBUs and
functions
Access methods
Helps to decide
when to redeploy
(in-room or
accounts)

10. 9. Learn to run a video meeting
Running a video meeting requires
skills
(Organising, planning, testing, running and content
sharing)
Your “Likeability factor” matters
http://huff.to/1xti86D
Build a self-learning and training
portal and a power user network

11. 10. Evangelise
Build a marketing plan to
sustain usage
Case studies help
Share through all internal
networks
30% to 40% utilisation seems the norm in steady state