driving innovation through enterprise 2.0

Post on 14-Jan-2015

566 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

DESCRIPTION

ARK Presentation August 2008

TRANSCRIPT

Stuart FrenchDaniels Sharpsmart

Take-aways

Benefits of Collaborative Innovation

How culture and collaboration interact

Outline some tips for implementation

Enterprise 2.0

The mix is moving towards Blogs, Wiki, RSS & Podcasts

The Asia Pacific region showed the greatest satisfaction in 2008

Successful use of Web 2.0 can lead to structural and cultural change dubbed “Enterprise 2.0”

Making definitions clear

Defining Innovation

Bring something new to the environment Bring something new to the environment

Bring something new to the environment

Collaboration 2.0 multiplies The novelty of invention The speed of delivery

Defining Innovation

Defining Collaboration

Collaborate - /klabbrayt/ verb work jointly on an activity

or project.

It is Not Communication Cooperation

Defining Collaboration

How does Collaboration effect Innovation?

My Research: Culture effects Wiki use Use of the wiki also effects

communications and culture

Defining Collaboration

David Snowden Innovation requires

Starvation Pressure Perspective Shift

Enterprise 2.0 helps build a collaborative culture which improves an organisation’sability to shift perspective

Understanding the interaction betweenCorporate Culture and Collaborative Tools

Successful Examples

Open source Apache web server Developed with

No central ownership No single Project Manager

Out did Sun, Microsoft & IBM

Successful Examples

Peer Production Harnessing external talent Keeping up with users Reducing costs Taking friction out of

inter-firm collaboration Developing social capital

Successful Examples

Clandestine Collaboration Google Search Amazon Profiles

Passive, not active Benefit from others use

Web 2.0 TechnologiesWeb 2.0 Technologies

Why not Inside the Enterprise ?

Web 2.0 and Enterprise 2.0

What is the Same?

Evolutionary growth model Very intuitive and easy to use Web / Ajax based Focus on Community then Process

Why not Inside the Enterprise ?

Web 2.0 and Enterprise 2.0

What is the Difference?

Focus on Business needs Security & Integration with corporate IT Integration, ie: Single Sign-in Customer Support Transparency &

Quality

Possible Applications

Wiki study of 5 SMEs showed 31 different uses for wikis, including: Project Management tool Basic CRM Documentation Collaborative spec development Collaborative problem solving Deciding which pizzas to order for the team

lunch“Its too much mucking around!”

High-level Collaboration

External International cultures Out-sourcing Off-shoring Privacy concerns

Internal Collaboration

Discovering Internal Resources

When Collaboration Works?

Clear Purpose

Common Sense of Community

The Daniels Wiki

Bringing many minds to bear: Project Management

Scope documents Timelines and resource allocation Tasklists Progress reports Exception tracking QA

The Daniels Wiki

Bringing many minds to bear: Collaborating across Time-Zones

The Daniels Wiki

Bringing many minds to bear: Collaborating up the chain of command

The Daniels Wiki

Bringing many minds to bear: Collaborative

Problem Solving

The Daniels Wiki

Bringing many minds to bear: Collaborative

Problem Solving

Supplying the Raw Materialsfor Innovation in a Changing Environment

Staying Grounded

Its about matching YOUR Desired Outcomes, Culture and Tools Don't get caught by hype What works for others may not work for you Get professional advice

Must understand Business Enterprise 2.0 Preferably product agnostic

Focus on Holistic Capability

Stages of Adoption

Collaboration Technologies

Stage 1:Traditional Collaboration

Telephone Face-to-face Meetings

E-mail, phone, fax, other classic technologies

Stage 2:Specific Problems and Applications

Audio, Video & Data Conferencing

EIM, IM, Chat & presence detection

Virtual Team Spaces (VTS)

Stage 3:Collaborative Proliferation

Multiple A/V/D Conferencing tools

Yahoo, MSN, AOL, Google

Groove, eRoom, WebOffice, etc.

Stage 4:Consolidation and Standardization

Standardize on SIP/Simple or XMPP

One Client for all IM clouds

Common virtual team space for everyone

Stage 5:Virtual Work Environment

Standard tools in place

Integration with Mobile Environment

Standard Desktop & Web Interface for anyone

Research Surprises

Size does not always equate to perceived success by management Be careful what measures you use

Wiki update is amazingly fast when transferring from other tools because of ease of use Old system: 5 years 120 pages Wiki system: 1 year 1000+ pages (by 17

users) Changeover time: 2 months!

Required competencies for participating in an open knowledge and innovation-sharing environment

Implementation Tips

Implementation Tips

“Both too much and not enough management proved detrimental to the success of the wiki.” – French, 2008

Pilot for the quick ROI to prove the concept Integrate tool into existing business processes Assure smooth integration from existing work flows Develop guidelines and best practices Find a champion Plan for Change Mgt issues But most of all:

Find the balance

Implementation Tips

Manage the transition to Enterprise 2.0 From Command & Control To Connect & Collaborate

• Learn to balance Control with Distributed Authority– Who needs to make the decision?• What knowledge do they need to make the

right choice?• Getting the balance wrong stifles

collaborative innovation

Finding knowledge and support

on your Web 2.0 journey

More Information

Sources / References Blogs

Anecdote – Shawn Callahan Trends in Living Networks – Ross Dawson Enterprise 2.0 – Andrew McAffee Delta Knowledge – Stuart French

More Information

Books Australian KM Standard - AS 5037-2005

Prescriptive not descriptive SME Version - HB 190-2006

Wikipatterns Collaboration 2.0

Resource list on page 253

Key Points

Digital Collaboration is a powerful trend Culture is something you grow, not

manipulate Innovation is cultural not just for R&D Balance Command & Control with

Connect & Collaborate Beware driving with the rear-view mirror Stay grounded, implement slow and wide Get good guidance

Thanks:•IA Web Trends•Daniels Sharpsmart

“Collaboration is an emergent property of the complex system of relationships we call culture.”

Extra

Influencing a complex environment

“In a complex system, you can never fully know the outcome in advance” – Snowden

Extra

Influencing a complex environment Beware 20-20 Hindsight

Retrospective Coherence

Extra

Influencing a complex environment

Twigs Leaves = Possible futures

Branches = Possible decisions

Trunk = The present

Roots = The past

- Edward de Bono

Extra

Influencing a complex environment Beware 20-20 Hindsight

Retrospective Coherence Develop an environment where people are

comfortable to make decisions without all the information

Be slow to judge after the fact Learn how to look forward

Rear-view mirrors only work when the road is straight

What has this got to do with Web 2.0? Unstifled innovation is key to adoption and returns

Extra

Influencing a complex environment Do

Safe-Fail adoptions Let systems evolve and even die out

consider starting outside the firewall Let the users decide what is more

practical to achieve their local business goals

Have IT simply focus on the provisioning and security aspects

Extra

Influencing a complex environment Don’t

Insist on perfection Look for single solutions Try to control instead of encourage use Rely totally on official modes of

communication Expect people

to never make a mistake to know everything

Extra

top related