Making an intranet or parts of it available on mobile involves much more than just making it “responsive”. “Mobile” enables communicators to reach new non-desk audiences, but also creates previously unknown technical and practical challenges as a consequence.

1. Mobile Intranet for ALL
8 Key Questions
Frank Wolf, Eyo EmployeeApp

2. Eyo EmployeeApp: SaaS Mobile-First Intranet CMS

3. Why a mobile channel?
Engagement ✓ Reach ✓

4. 2/3 of all employees don‘t work at a desk. In
most companies they don‘t have access to
corporate email or intranets.

5. Frontline employees are your brand and they are
the ones that actually need more information!

6. „Mobile services in 2014 did
not achieve predictions based
on 2013 data“
„Mobile progress (in 2014)
has been slower than we
expected“
Mobile Intranet: slow progress so far.

7. What needs to be solved?

8. Is not the main challenge!

9. Which use cases
and content?
Intranet-channel or
independent
solution?
How to manage
users?
Native app or web
app?
How is the app
distributed?
New ideas for mobile
communication?
Fit to overall
intranet strategy?
Voluntary or
mandatory?
1
2
3
45
6
7
8

10. Global penetration
1%  73%
Global Mobile Penetration 1995-2014
Everyone now has a smartphone
85%
Americans between 18-29
Internet usage tipped to mobile
50%
Internet usage on mobile vs. desktop
http://www.pewinternet.org/2015/04/01/us-smartphone-use-in-2015/ & http://www.kpcb.com/internet-trends ; slide inspired by Bessemer Venture Partners „State of
the Cloud Report 2015“ & http://www.zdnet.com/article/research-74-percent-using-or-adopting-byod/
BYOD acceptance
74%
Organizations using or adopting Bring-Your-Own-Device
1. “Mobile” is a valid channel now to reach the
majority of employees.

11. Voluntary (BYOD)
Purpose: better information for
employees, facilitate everyday work
Devices: private smartphones + often
private (data) tariffs
Alternatives: need to be offered for
basic information ( terminals, PCs, a
remaining limited edition of the
employee-newspaper, bulletin
boards,…)
Advantage: introduction is easy and
economical
Disadvantage: less connection to core
work processes
Mandatory (Intranets so far...)
Purpose: mobile support of core work
processes
Devices: smartphones / tablets + tariffs /
WiFi provided by the company
Alternatives: not needed
Advantages: cost savings and direct
improvements in the work process
Disadvantages: higher investment costs,
high efforts for operation of the devices
1. Voluntary or mandatory?

12. 2. Challenge: content that fits the
mobile channel
Less content
Occasional users
Personalization
Few documents
Scrolling>links
...

13. Communication CollaborationInformation
ServicesMobile potential:
HIGH
Mobile potential: MEDIUM
Mobile potential: MEDIUM
Mobile potential:
MEDIUM
2. What content should be mobile?
Criteria: target group, complexity, security requirements, mobile „moment“

14. SECURITY VS. REACH
Information worker
+ collaboration
+ documents
+ business critical
=more sensitive content
Non-desk employees
+ private devices
+ no MDM or VPN
+ easy access (saved login)
=more reach
3. Intranet channel or independent?

15. Intranet Employee
App
Authentication
with BYOD
Internal network
User
Content
3. Our approach for BYOD.

16. 4. User management.
@company email?
Active directory?

17. 4. User management options.
A) Direct connection to a company directory (e. g. Active
Directory)
+ works automatically
- often, not all employees are included
B) Semi-automatic import (e. g. CSV file)
+ easy to implement, high security
- limited manual effort
C) Manual maintenance in the employee app's user
management.
+ no integration effort
- manual maintenance efforts - not suitable for companies
with more than 300 employees
D) Login with a business email address - users will be
identified as valid through their @company email and will
be able to create an account
+ easy onboarding
- a business email is needed, manual solutions needed for
employees leaving the company
User onboarding
1
23
User
maintenance
User
deletion

18. Ç√
DEVICE API
WEB BROWSER
HTML +
Java Script
Ç√
DEVICE API
NATIVE CONTAINER
HTML +
Java Script
Ç√
DEVICE API
NATIVE CONTAINER
Native Code
WEB HYBRID NATIVE
5. Native app or web-app?
• Access to device API: push,
camera, location
• Distribution via app-stores
• Offline

19. 6. App distribution.
Example for Apple:
• Public App Store
 Not just employees
 Easy to distribute
 Apple review
• B2B App on Business Store
 Just employees
 Not visible on public store
 Apple review
• Enterprise Developer Program
 Just employees
 No automatic update
 No Apple review

20. Intranet
Employee
App
FIREWALL
Intranet
Intranet
Employee
App
Local
content
FIREWALL
Intranet
Employee App
NEWS
FIREWALL
7. Integration and intranet strategy.
Predictions:
• Monolithic intranets will decline
• Increased focus on different audiences
• „Communication intranet“ vs. „Collaboration intranet“

21. 8. New ideas for (mobile) communication?
Local + Pictures
•Local and in-time
•Picture and videos
•Everybody can do this
•Simple editing is key
•Not just business related (black
board)
Puls-surveys
•Daily or weekly
•Fast feedback
•Great way to measure and
improve at the same time
Future
•Standardized content
•Games and events (e.g. EM
2016 betting game)
•Content as a service (e.g.
healthy working)
•Industry-specific tools

22. Closing the Intranet Gap for
Non-Desk Workers.
Eyo is the employee app for engaging and interacting with those
2/3 of all worldwide employees who do not work at a desk.
Frank Wolf
frank@eyo.net