38
No Single Vendor Owns the Future of Work @CerysHearsey / @Postshift

No single vendor can own the future of work

Embed Size (px)

Citation preview

Page 1: No single vendor can own the future of work

No Single Vendor Owns

the Future of Work

@CerysHearsey / @Postshift

Page 2: No single vendor can own the future of work
Page 3: No single vendor can own the future of work

*Shift: a journey

Page 4: No single vendor can own the future of work

A bit about me

Head of Consulting@PostShift My job: make complex thoughts into simple projects

Page 5: No single vendor can own the future of work

(Unsurprisingly) The future of work changes everything…‣ customer engagement ‣ products & services ‣ enterprise IT ‣ business models ‣the nature of the firm

Page 6: No single vendor can own the future of work

SOCIAL TECHNOLOGY

‣Social Business strategy‣E2.0 / SocBiz platforms‣Use cases / process surrounds‣Adoption & awareness

social tech as the entry point

ORG DESIGN

‣Agile / podular teams‣Networks and communities‣Open / data-driven working‣Customer / market pull

SOCIAL TECHNOLOGY

FUTURE OF WORK

‣New roles and tasking‣Network-centric leadership‣Business model innovation‣New business structures

ORG DESIGN

SOCIAL TECHNOLOGY

Page 7: No single vendor can own the future of work
Page 8: No single vendor can own the future of work

Structure

•Decentralised •Resilient •Adaptive &

Emergent •Networked •Service-

oriented

Culture

•Open •Customer-

centric • Innovative •Experience-led •Purposeful

Practice

•Agile & Iterative •Data-driven •Collaborative •Task-focused •Podular

Digital needs new organisational attributes

Leadership

•Curious •Situational • Inclusive •Serving •Connected

Page 10: No single vendor can own the future of work

Double click to edit...

10

Page 11: No single vendor can own the future of work

Most large orgs lack a future of work tech strategy

Page 12: No single vendor can own the future of work

Orgs are simplifying (or trying)

Page 13: No single vendor can own the future of work

Its almost like we re-wound to 2005…

Page 14: No single vendor can own the future of work

Problem 1: what tool to use when?

Page 15: No single vendor can own the future of work

Problem 2: poor user experience when crossing tools

Page 16: No single vendor can own the future of work

some of our workforce expects faster-paced

change… how can we cope with that?

Page 17: No single vendor can own the future of work

speeds

Synchronous

• Chat

• Real-!me collabora!on

• Co-ordina!on

Semi-synchronous

• Messaging

• Social Networks

• Project collabora!on

Asynchronous

• Storage

• Search

• Documenta!on

• Long-term collabora!on

Page 18: No single vendor can own the future of work

scale/intimacy

Macro: cruising and surveying networks

• Exper!se loca!on

• Topic-based filtering

• Search & find

Meso: personal networks & loose !es

• Signals & sharing

• Status updates

• Messaging

• Recommenda!ons

Micro: finding people and working together

• Collabora!on

• Co-working

• Private messaging & chat

• Real-!me presence

Page 19: No single vendor can own the future of work

Building a layered ecosystem

Page 20: No single vendor can own the future of work

Layer 1: the Hub

Page 21: No single vendor can own the future of work

Layer 2: enterprise-level solutions

Page 22: No single vendor can own the future of work

Layer 3: team point solutions

Page 23: No single vendor can own the future of work

Layer 4: individual productivity tools

Page 24: No single vendor can own the future of work

Layering up

Page 25: No single vendor can own the future of work
Page 26: No single vendor can own the future of work

Use cases using the right tool for the right job

Page 27: No single vendor can own the future of work

but this still doesn’t go far enough in creating an

ecosystem for the future of work

Page 28: No single vendor can own the future of work

Double click to edit...

28

As a leader, I need to share industry informa!on and

ideas with a wide network, so that I can help people

understand the market and our compe!tors be"er.

As a HR specialist, I need to support the crea!on of agile

teams with appropriate policies and governance, so that

the organisa!on can have the flexibility to innovate and

grow.

As an employee, I need access to a full skills and

capabili!es catalogue, so that I can iden!fy informal

learning opportuni!es.

example capabilities

Page 29: No single vendor can own the future of work

four approaches to defining target organisational

capabilities

Page 30: No single vendor can own the future of work

30

Page 31: No single vendor can own the future of work

Double click to edit...

31

Page 32: No single vendor can own the future of work

Double click to edit...

32

Page 33: No single vendor can own the future of work

Double click to edit...

33

Page 34: No single vendor can own the future of work

mapping capabilities

Page 35: No single vendor can own the future of work

the future of work requires a holistic view

Core Systems

Master Data S’ware Services/

ProcessesSkills/ People Products Capabilities

Page 36: No single vendor can own the future of work

a final thought

Page 37: No single vendor can own the future of work

Double click to edit...

37

the shadow org: your future firm

Page 38: No single vendor can own the future of work

Questions?

http://postshift.com/diagnostic