Top Banner
The sad story of the Intranet Or why a conventional Intranet hinders innovation and kills productivity. Felix Binsack, TIMETOACT GROUP
35

The Sad Story of the Intranet

Aug 28, 2014

Download

Software

TIMETOACT GROUP

Many companies decide to use their Internet Web Content Management System for their Intranet too. Web Content Management Systems are excellent in top-down communication. IBM Connections is excellent in peer-to-peer collaboration. Using separate platforms for communication and collaboration causes content overlap, fragmentation and inconsistencies and confronts users and authors with difficult choices: where to publish and where to search content. Governance problems, user frustration and lost potential are the consequences.
The Web Content Management Extension (XCC) enhances IBM Connections with classic Web CMS capabilities and thus integrates the two antipodes of an intranet, i.e. peer-to-peer collaboration with top-down communication. IBM Connections with the Web Content Management Extension XCC creates a beautifully integrated Social Intranet. Learn how to manage internal communications with IBM Connections and why IBM Connections adoption and ROI will increase with XCC.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: The Sad Story of the Intranet

The sad story of the IntranetOr why a conventional Intranet hinders innovation and kills productivity.

Felix Binsack, TIMETOACT GROUP

Page 2: The Sad Story of the Intranet
Page 3: The Sad Story of the Intranet

First Act“Internet Innovation”

Page 4: The Sad Story of the Intranet

First Act “Internet Innovation”Once upon a time a company selected for their Internet website an innovative Web Content Management System or Portal platform with lots of great features. The criteria included:

Pixel Perfect LayoutAsset ManagementApproval Workflow ManagementMultisite Management Social Media IntegrationCommerce Support (Analytics, Campaign & Lead Management, Targeting)Supply Chain Management (for Portals only)

.

Page 5: The Sad Story of the Intranet

Second Act“Intranet Adoption”

Page 6: The Sad Story of the Intranet

Second Act “Intranet Adoption”Company wanted to recoup investment cost and decides to use their Internet Web CMS for the Intranet too. Top-Down Communication works OK, Internal Communications department is satisfied.

Page 7: The Sad Story of the Intranet

Third Act“Knowledge Lost”

Page 8: The Sad Story of the Intranet

Third Act “Knowledge Lost”Line of Business found the Web CMS / Portal too complex

for occasional usersLine of Business content was incomplete and got outdatedMail load kept increasing, productivity went downKnowledge remained locked in mail and file serversMost knowledge was not accessible

Page 9: The Sad Story of the Intranet

Forth Act“Collaborative Innovation”

Page 10: The Sad Story of the Intranet

Forth Act “Collaborative Innovation”Innovators implemented Enterprise Social SoftwareSome employees happily used the collaborative platform

Page 11: The Sad Story of the Intranet

Fifth Act“Fragmentation”

Page 12: The Sad Story of the Intranet

Fifth Act “Fragmentation” IUser Fragmentation

Some users refrain from the internal communications / web CMS based Intranet (“I do not need marketing”)Some users refrain from the collaborative platform (“If it is important it will be published by Internal Communications”)

Government IssuesMake Web CMS Intranet default homepageRepublish all relevant content from ESS in Web CMS

Page 13: The Sad Story of the Intranet

Fifth Act “Fragmentation” IIContent Fragmentation

Some managers choose to communicate as them-selves using the collaboration platformSome managers choose to communicate thru internal communications using the Web CMSEmployees need to search the Web CMS based Intranet and the Collaborative / Enterprise Social Software platform

Government IssuesContent overlap and redundancy cause inconsistency

Page 14: The Sad Story of the Intranet

Wouldn't it be great to have a truly integrated

Social Intranetthat serves

Communication and Collaborationequally well?

Page 15: The Sad Story of the Intranet

Why is it so difficult to integrate Internal Communications

with Collaboration?

Page 16: The Sad Story of the Intranet

Internal Communications and Collaboration are the

Antipodes of any Intranet!

Page 17: The Sad Story of the Intranet

Traditional Manager Internal Communications Manager Knowledge WorkerI do not care about social, if something is really important it will eventually show up in the Web CMS

Employees have to be aware of our priorities, strategy, values and important news

I do not care about the constant self praise

I need ESS to get my work done and stay in touch with my peersSocial software lacks

structureEverything important must be published on my platform

Social is great to develop ideas and exchange opinions

The Web CMS is too complicated to publish my departments information

I do not care about social as long as employees do not use it as a propaganda platform

My content must be created fast and easyI use mail for

communicationMy content needs to look great

We do not like to have two separate platforms with inconsistent content and user interface !

Hi, I am a…

Page 18: The Sad Story of the Intranet

Web Content ManagementTop-Down Communication

Social SoftwarePeer-To-Peer Collaboration

Stagnating Rapidly Growing

Top Down / 1:n Communication Bottom Up / n:n Communication

Approved Content / Directives Unofficial Content

Communication of Mgn. Ideas and Opinions Formation of Ideas and Opinions

Important Information stays on Top Popular Information stays on Top

Dedicated Authors with Intense Training User Generated Content (without Training)

Pixel Perfect Layout Form Follows Function

Set as default Homepage by Policy Set as default Homepage by Employee

"Management’s Intranet” "Employee’s Intranet”

Peer-To-Peer Collaboration

Internal Communi-

cations

The Antipodes

of any Intranet!

Page 19: The Sad Story of the Intranet

Intranet Strategies:How to deal with Intranet pillars Communication and Collaboration

Page 20: The Sad Story of the Intranet

Strategy 1: Internal Communications Only

Inefficient collaboration with mail and file servers All knowledge locked up in mail filesNo expert identificationNo employee participationNo informal learningNot appealing to young employees accustomed to social media

Internal Communi-

cations

Page 21: The Sad Story of the Intranet

Strategy 2: Collaboration Only

Peer-To-Peer Collaboration

Difficult to communicate the organization’s priorities, strategy, values.Difficulty to distinguish opinions and ideas from binding / formal information and directives.Difficulty to identify important information.No structure, everything sorted by last update / popularity.

Page 22: The Sad Story of the Intranet

Strategy 3: Side-By-Side Communication and Collaboration

Confusion and Governance ProblemsHow should managers communicate, as them-selves or thru internal communications?Where should employees look for content, in the Web CMS based Intranet or in Social Software?

Attention and Content FragmentationHalf of the employees visit Web CMS based Intranet and ignore collaboration, the other half use collaboration and ignores Internal Communications website.

Overlap, Redundancy and InconsistencySome content is inevitably going to be stored in both platforms.

Page 23: The Sad Story of the Intranet

Strategy 4: Enhance Communication with Collaboration

Insufficient collaborationCollaboration integrated into communication will never reach critical mass to become self sustaining.Intranet 2.0 based on user generated content / Enterprise 2.0 will not be achieved.

For enhanced Web CMS: Insufficient capabilities Activity Stream / Social capabilities / Enterprise collaboration missing.

For integrated platforms: Inconsistent UI Users must leave communication homepage for collaboration.Content fragmentation, overlap, redundancy and inconsistency, governance problems.

Page 24: The Sad Story of the Intranet

Strategy 5: Integrate Communication into Collaboration

No content overlap, redundancy, inconsistency Social software is more popular with employees.User generated content grows much faster then centrally managed content.

Page 25: The Sad Story of the Intranet

Introducing XCCWeb Content Management Extension for IBM Connections

Page 26: The Sad Story of the Intranet

XCC - Web Content Management Extension for IBM Connections

XCC is a lightweight Web CMS that integrates into IBM Connections. XCC leverages and utilizes IBM Connections for authentication, authorization, content storage, content approval, search, notification etc.XCC enhances IBM Connections with classic Web Content Management capabilities and thus integrates the two antipodes of an intranet, i.e. peer-to-peer collaboration with internal (top-down) communications.

Page 27: The Sad Story of the Intranet

XCC 4.1 - Demo Video

http://youtu.be/oNuY70eIs-Q

In the video:User ExperienceContent Master InterfaceWeb Master Interface

Page 28: The Sad Story of the Intranet

Mobile Apps (Android & iOS)

New menu item in IBM Connections Mobile AppAll Widgets are displayed in a serialized orderPhone and Tablet LayoutAuto switch between Vertical and Horizontal Layout

NEW

Page 29: The Sad Story of the Intranet

1. Improve Intranet User Experience2. Improve Internal Communications3. Increase IBM Connections Adoption

and ROI4. Reduce Complexity5. Cut Costs6. Accelerate Intranet Development

XCC – Key Advantages

Page 30: The Sad Story of the Intranet

1. Improve User ExperienceEliminate the dichotomy between top-down communication and peer-to-peer collaboration and create a truly integrated Social IntranetEverything is in one place, employees do not need to choose where to browse and search content Communication and Collaboration are either on the same page or available within one clickHigh degree of personalization (Region, Location, Department, Branch etc.)Excellent Mobile Experience (integrated in Android and iOS Apps and responsive layout)

Page 31: The Sad Story of the Intranet

2. Improve Internal CommunicationsInternal Communications is made social, i.e. its content can be liked and commented (unless commenting is disabled) Content publishing, liking and commenting is integrated into the Activity Stream and will be noticed by peersResponsibility can be effectively delegated to line of businessContent masters can not only create and publish content but curate content too (i.e. publish blog entries from employees on landing pages / homepage) Avoid content fragmentation, overlap, redundancy, inconsistency and governance problems

Page 32: The Sad Story of the Intranet

3. Increase Connections Adoption and ROI All employees have a crucial reason to visit IBM Connections to access the integrated Internal CommunicationsNewbies (and ‘silver surfers’) benefit from structured content Newbies discover content faster (even if they do not yet follow other employees or communities)Many employees can be involved in maintaining landing pages for business units, service units, locations and projects – those employees will be strong Connections power users and promotersXCC increases IBM Connections usage by 50% to 100%

Page 33: The Sad Story of the Intranet

4. Reduce ComplexitySimplicity for Authors

Creating content is really easy, no technical training required (i.e. management compatible)Everything is in one place: authors do not need to choose between two systems to publish their content

Technical ComplexityNo search integration required (all content is within one index)Read Access Management is given thru Communities, no project requiredSingle Sign On for CMS & Connections is givenActivity Stream and UI Integration are given, no project requiredPersonalization is really easy, no technical project required

Page 34: The Sad Story of the Intranet

5. Cut CostsEliminate Web CMS costs for

SelectionPurchaseImplementationIntegrationTraining and Running

another platform besides IBM Connections

Page 35: The Sad Story of the Intranet

6. Accelerate Intranet DevelopmentWith XCC Intranet projects shift focus within hours from technology to content.

Implementation is done in less then 20 MinutesCI adoption is very fast Content, navigation and pages can be created fast Intuitive page design with drag & drop of widgetsFast integration of

External content (Atom / RSS Feeds, iFrame, Web Clipping)Custom widgets