Frank Wolf: Going mobile with your intranet

transcript

„Enterprise mobility has hit a speed bump“

„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.

GOING MOBILE WITH YOUR INTRANET

Frank Wolf, Co-founder Staffbase

ABOUT ME: INTRANETS FOR 15 YEARS

Staffbase allows companies of any size to easily launch their own mobile app for internal communications. It's like a branded intranet in the pocket that can be downloaded from the public app store.

Your own Employee-App

build-in CMS

key use cases -ready to go

your mobile channel to reach all employees

MY EXPERIENCE WITH “MOBILE”

PLEASE INTRODUCE YOURSELF

1.  Name, company and role 2.  What’s your “State of mobile?” 3.  Do you have specific questions and

expectations for the workshop?

Which use cases?

Mobile = available on my smartphone?

Which technology / vendor options exist?

One app or many apps for each employee?

Which technical hurdles may appear?

Why have a mobile channel of the intranet?

Fit to overall intranet strategy?

Audience? 2

GUDING QUESTIONS FOR TODAY.

INTERNAL COMMUNICATION

EMPLOYEE ENGAGEMENT

Everyone now has a smartphone

90% Americans between 18-29

BYOD acceptance

Organizations using or adopting BYOD

MOBILE IS A GAME CHANGER

Which use cases?

Audience? 2

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

VOLUNTARY OR MANDATORY.

Which use cases?

Audience? 2

Which use case?

WHAT’S DIFFERENT WITH MOBILE?

TOP LEVEL INTRANET USE CASES.

MOBILE INTRANET USE CASES.

Criteria: target group, complexity, security requirements, mobile moment

GIVE AND TAKE.

Which use cases?

Audience? 2

„Mobile“ does not equal „Mobile“...

Be careful: with great power comes great responsibility!

PUSH IS A „GAME CHANGER“.

DEVICEAPI

WEB BROWSER

HTML + Java Script

DEVICEAPI

NATIVE CONTAINER

HTML + Java Script

DEVICEAPI

NATIVE CONTAINER

Native Code

WEB HYBRID NATIVE

•  Access to device API: push, camera, location

•  Distribution via app-stores •  Offline

THERE IS NO WAY ARROUND NATIVE APPS.

Which use cases?

Audience? 2

What are your challenges for a mobile channel?

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

(Social) Intranet Employee-App

Behind the firewall / advanced security measures

Users + content

OUR APPROACH.

WHAT ABOUT THAT OLD DREAM OF JUST ONE INTRANET PLATFORM?

Intranet Employee

FIREWALL

Intranet

Employee App

Local content

FIREWALL

Intranet

Employee App

FIREWALL

Predictions: •  Monolithic intranets will decline •  Increased focus on different audiences •  „Communication intranet“ vs. „Collaboration intranet“

DIGITAL WORKPLACE.

Which use cases?

Audience? 2

Options (Apple) •  Public App Store •  B2B App Store •  Enterprise Developer

Program •  Download on intranet Criteria •  Target group? •  Irritated customers? •  Apple Review •  Updates (automatic!) •  Barrier for employees

APP DISTRIBUTION.

HANDLE WITH CARE: APPLE AND CLOSED AUDIENCES.

@company email? Active directory?

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

User maintenance

User deletion

MANAGE USERS.

Challenge: content that fits the mobile channel

Less content Occasional users Personalization Few documents Scrolling>links ...

Which use cases?

Audience? 2

Alerting solutions

Platform One app with multiple features and API to extend it. Massively simplifies adoption and management.

Reach Support for non-desk workers (mobile-first, alternative onboarding without corporate email, employer branding, pricing)

Single purpose apps Chat, Shift planning, Engagement, Mobile forms, News...

App-builder/development platforms

Intranets/Enterprise portals Disruption through wider reach

AN EVOLVING TOOL CATEGORY.

Frank Wolf EmployeeApp GmbH frank.wolf@staffbase.com staffbase.com

Frank Wolf: Going mobile with your intranet

Internet