akseli.tekes.fi

45
Collaboration in Enterprise 2.0 Finpro David Coleman Managing Director Collaborative Strategies October 25 2007

Transcript of akseli.tekes.fi

Page 1: akseli.tekes.fi

Collaboration in Enterprise 2.0 Finpro

David Coleman

Managing Director

Collaborative Strategies

October 25 2007

Page 2: akseli.tekes.fi

©2007 Collaborative Strategies 2

Page 3: akseli.tekes.fi

Section 1: Introduction and Definitions

Page 4: akseli.tekes.fi

©2007 Collaborative Strategies 4

Critical Definitions• Communication: a message is sent from

person A to person B, and receipt is acknowledged by person B

• Interaction: a message is sent from person A to person B, and receipt is acknowledged by person B, and person B sends a message back to person A in reply.

• Collaboration- multiple interactions between two or more people for some common goal

Page 5: akseli.tekes.fi

©2007 Collaborative Strategies 5

Collaborative Data Model

• All collaborative interactions have to incorporate one or more of these four data types:– Structured Data (database)– Unstructured Data (e-mail, documents, etc.)– Conversations (IM, threaded discussions, etc.)– Tasks (actions in a project)

Page 6: akseli.tekes.fi

4 Benefits of Collaboration

1. Saving time or money (tangible)

2. Increasing quality (tangible…but less so)

3. Innovating and/or providing decision support (tangible but less than quality)

4. Easing access to and interactions with subject-matter experts (intangible)

©2007 Collaborative Strategies 6

Page 7: akseli.tekes.fi

Holistic Approach to Collaboration

©2007 Collaborative Strategies 7

Page 8: akseli.tekes.fi

Evolution of the Web

©2007 Collaborative Strategies 8

Web 1.0 – Web 4.0: From Nova Spivak, Radar Networks & Mills Davis, Project 10x

Page 9: akseli.tekes.fi

©2007 Collaborative Strategies 9

Limitations of Today’s Solutions• E-mail- inefficient conversations

– Lots of copies – Lots of total disk space – No centralized place to search – Can be multiple copies, or different versions of documents– No central place to point to a message or attachment by links

• IM/Chat – – Not persistent, – Often not searchable, – EIM + IM Clouds (Yahoo, Google, Skype, MSN, etc.)

• Discussion forums – – Centralized conversations – Searchable

Page 10: akseli.tekes.fi

©2007 Collaborative Strategies 10

Limitations of Today’s Solutions• Blogs –

– Thread together multiple conversations of an individual – Give that person a web identity, – Can also be a discussion with comments

• Wikis- – Negotiate and integrate many views in a group, summary– Removes duplicates and obsolete content– Not good for off-line working

• Virtual Team Spaces – – Secure – Persistent– Some document management– Sometimes IM/presence

Page 11: akseli.tekes.fi

Comparison of Enterprise 1.0 and 2.0 Characteristics and Drivers

©2007 Collaborative Strategies 11

Enterprise 1.0 Enterprise 2.0 Drivers

Static content and web pages, focus on content

Dynamic content, focus on interaction

Consumer Web 2.0 and social networking tools

Messages pushed by e-Mail Information pulled through RSS feeds

Users want to personalize their information.

Content produced, and edited according to policy

Content from Blogs, Wikis and other participatory

User created content

Asynchronous interactions (e-mail) Synchronous interactions (IM, Chat and SMS)

Net Generation, growing up with computers

IT imposed control of technology Individuals use new technologies and create content

Situational applications, and IT backlog

Search and Browse for information Publish and subscribe to information feeds

Overwhelming amount of information available

Transactional oriented interactions Relationship oriented interactions Expertise discovery, cross organizational teams

Organizational Taxonomy Folksonomy Tagging of content for individual use

One application for everyone Individual and niche applications IT backlog and situational applications

Page 12: akseli.tekes.fi

Section 2: E 2.0 and Collaboration

Page 13: akseli.tekes.fi

13

Stages of Evolution for Collaboration in the Enterprise

Stages of Adoption Collaborative Technology

Example Technology

Stage 1: Traditional Collaboration Telephone Face-to-face meetings E-mail

Stage 2: Specific Application Audio, video, and data conferencing

EIM, IM, Chat, and presence detection

Virtual team spaces

Stage 3: Collaborative Proliferation Multiple audio, video, and data conferencing tools

Yahoo!, MSN, AOL, Google, etc.

Groove, eRoom, WebOffice, etc.

Stage 4: Consolidation 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 environments

Standard desktop and Web interface for anyone

©2007 Collaborative Strategies

Page 14: akseli.tekes.fi

14

1. Sales & marketing (proposal development)

2. Customer service/support (exception handling)

3. R&D (new product development)

4. Value network management/relationships with external organizations, DPM, and project management (exception handling)

5. Training (internal and external)

6. Decision support/crisis management

Critical Processes with Collaborative Leverage

©2007 Collaborative Strategies

Page 15: akseli.tekes.fi

15

Financial Services

Healthcare/Pharmaceutical

Government

High Tech

Manufacturing

Education

Professional Services

Telecom

Based on research done inQ2, 2005 for CS’ RTC report

Top Verticals for Collaboration

Driving Collaboration into Industries

©2007 Collaborative Strategies

Page 16: akseli.tekes.fi

©2007 Collaborative Strategies 16

Finding Opportunities: Vertical & Process MatrixFinancialServices

Health,Pharma.

Govt. HighTech

Manu. Education Prof.Services

Telecom

Sales,Marketing

Proposal development

Proposal development

Customer Service or Support

Exception handling

R&D New service creation

Development of new molecules

New product creation

Value Network Management

RFP development and evaluation

Training Sales force education for new service

Doctors continuing education

Policy and process training

Decision Support, Crisis Mgt.

Deal leak damage control

Drug development resource priorities

Page 17: akseli.tekes.fi

17

Today’s Buyers of Collaboration Technologies• Risk averse - want to know it works for others in their

organization or field• Technology neutral• Looking for a specific solution• Must fit with their current

infrastructure• Requires little or no training• Has an intuitive ROI

Changing Buyers of Collaboration

©2007 Collaborative Strategies

Page 18: akseli.tekes.fi

Collaboration 3.0• The semantic web

• Ability to transfer knowledge rather than information

• Immersive collaborative environments (audio and video conferencing in Second Life)

• Content expressed in a natural language

• A common standard (RDF) for websites to publish the relevant information in a more readily machine-process-able and integrate-able form

• Bots and Intelligent Agents

18©2007 Collaborative Strategies

Page 19: akseli.tekes.fi

ICE: Immersive Collaborative Environment

Qwaq Forums (Beta)-Persistent virtual workspace, -Drag-and-drop content. Based on Croquet (open source 3D development environment)

19©2007 Collaborative Strategies

Page 20: akseli.tekes.fi

20

Virtual Worlds – Second Life

Collaboration 3.0

©2007 Collaborative Strategies

Page 21: akseli.tekes.fi

Section 3: VTS, Social Networks, and Online Communities

Page 22: akseli.tekes.fi

Web 2.0 VTS tools

• Near-Time

• Huddle

• Clearspace

• Near-time

• Teamworkzone

• Central Desktop

• Nexo

• Collanos Workplace

• Openteams

©2007 Collaborative Strategies 22

Page 23: akseli.tekes.fi

23

Collaboration 2.0 Virtual Team Spaces

©2007 Collaborative Strategies

Page 24: akseli.tekes.fi

Social Network and Community Tools• Q2Learning • iCohere• Affinity Circles• GroupMembersOnly• Collanos• Foldera• Leverage Software • Smallworldlabs• Social Platform • Web Crossing • CollectiveX • Me.com• Sparta Social Networks

©2007 Collaborative Strategies 24

Page 25: akseli.tekes.fi

Functions from Community tools• User Profiles

• Visual Targeted Matchmaking

• Expertise Discovery

• Community chat

• Integrated opinion polls

• Private messaging (IM)

• Blogs

• Wikis

• Quick connect

• Multimedia file sharing

• Customized notifications

• Tagging, tag clouds and social tagging

• Presence

• RSS feeds

• Discussion forums

• Group and role administration

• Integrated calendar management

• Rating and ranking of content

• Reputation engines

• Sponsorship and advertizing engines

• Community e-mail marketing

• Community activity reporting

©2007 Collaborative Strategies 25

Page 26: akseli.tekes.fi

Types of Communities

• Customer communities

• Media communities

• Internal/ enterprise communities

• Consumer communities

• Partner or channel communities

• Event communities

• Member communities©2007 Collaborative Strategies 26

Page 27: akseli.tekes.fi

Social Network - example

©2007 Collaborative Strategies 27

Page 28: akseli.tekes.fi

3 R’s Of Community

• From CommunityXperts:– Resources– Recruiting– Recognition

©2007 Collaborative Strategies 28

Page 29: akseli.tekes.fi

Section 4: Mashups: Opportunities for Situational Applications

Page 30: akseli.tekes.fi

30

SaaS (Software as a Service)

• “By 2008, half of all software will be sold as a service.” (Gartner, May 2005)

• From client-server architecture to “Web native” app design

• From site licenses to “as-used” or fixed-fee subscription

• From customer-owned servers and staff to “Web hosted” deployment and support

“Self Service” Trend

©2007 Collaborative Strategies

Page 31: akseli.tekes.fi

“Self Service” Trend

• The end user understands their problem better then any vendor will, so why can’t they design, build and deploy the application (solution) for it.

• Don’t want to go to IT want to be their own “hero”, customize it for their situation

• Collaboration vendors starting to respond – – Open Xchange– eProject (6)– SiteScape v7– WooFu (online forms and database)– Qwaq (3D rooms for interaction)

31©2007 Collaborative Strategies

Page 32: akseli.tekes.fi

Mash-up takes < day; Integration > day• John Musser’s Mashup Feed 2.63 mash-ups/day• Rafe Needleman estimates 7-10 mash-ups a day• Music Industry Term (DJ Plays 2 songs together)• Data/Content or programs combined in a new way

• Widgets: – “Embeddable chunks or reusable code. Widgets are also known as modules, snippets, and plug-ins. Widgets can be written in HTML, but also in JavaScript,

flash and other scripting languages that will be run when the page is called.”– WidgetBox.com– Snipperoo Widget Directory– Clearspring – Widget syndication– Sexy Widget (blog)

• Mash-up Backbones– Salesforce.com (AppExchange)– WebEx (now Cisco) Connect– OpenSam– IBM QED Wiki

©2007 Collaborative Strategies

Mash-ups: Background

32

Page 33: akseli.tekes.fi

Mash-up Mechanics

33©2007 Collaborative Strategies

Page 34: akseli.tekes.fi

Mash-up Continuum

©2007 Collaborative Strategies 34

Page 35: akseli.tekes.fi

Mash-up Ecosystem

©2007 Collaborative Strategies 35

Page 36: akseli.tekes.fi

Mash-ups and the Enterprise• Two types of Enterprise Applications

– ERP apps – serviced by IT

– Situational apps.• Reusable code

• Hosted

• May only be used temporarily

• Not a good ROI for IT/ application

• ROI for enterprise comes from hundreds of applications

• According to Gartner by 2010, 80% of enterprise applications will be mashups

©2007 Collaborative Strategies 36

Page 37: akseli.tekes.fi

Enterprise 2.0 Mash up Tools• Not a complete list

– IBM QEDWiki

– BEA Aqualogic Ensemble

– OpenSAM (ShareOffice)

– Yahoo Pipes

– Kapow (OpenKapow)

– Microsoft Popfly

– Dapper

– Datamashups.com

– Nexaweb Studio 2.4

• Grazr

• JackBe

• Near-Time

• Above All Studio

• Procession, Process Engine/Designer

• RatchetSoft, Rachet-X Studio

• RSSBus

• SAP Visual Composer

• Teqlo

©2007 Collaborative Strategies 37

Page 38: akseli.tekes.fi

Mash-up Questions

• How long did it take to build?• How useful is it? Does it fill a critical need?• How easy is it to use? Who will use it?• What is the cost or business model for the Mash-

up? How do I make $?• Are there any security issues? Where does the data

come from? Is it used outside the firewall?• Does it interact with an ERP application?

©2007 Collaborative Strategies 38

Page 39: akseli.tekes.fi

Section 5: Opportunities

Page 40: akseli.tekes.fi

Online Office Opportunities

• Online Office Tools– Central Desktop– WebOffice– InfoStreet– Contact Office

©2007 Collaborative Strategies 40

Page 41: akseli.tekes.fi

Talent 2.0 Opportunities

• “Fun” is important to Net Geners– Interviews in Second Life, more entertaining

and lower cost– Use of innovative technologies can help to

attract talent– E 2.0 Companies looking for new leaders; some

may be guild masters in WoW– Talent Pools: eLance, Odesk,

©2007 Collaborative Strategies 41

Page 42: akseli.tekes.fi

MyAdmin Opportunity

• Already services for virtual Accountants

• But not for Admins– Fragmented market, networks of admins– Most are not entrepeneurial– Network has to guarentee quality– Charge fee to admins, and transaction fee to

customers

©2007 Collaborative Strategies 42

Page 43: akseli.tekes.fi

What VC’s want• Low risk

– Have the product/service built– Have paying customers– Need $ for scaling up (sales/marketing)– Need to show big returns for the $

• Micro Investing ($100k - $250k)– First Round Capital– Bay Partners

©2007 Collaborative Strategies 43

Page 44: akseli.tekes.fi

Where VCs are investing

• Facebook applications

• Virtual Worlds companies

• Mobile and infrastructure plays

• Green technologies

©2007 Collaborative Strategies 44

Page 45: akseli.tekes.fi

David ColemanCollaborative Strategies

www.collaborate.com

“The Collaboration Blog”

415-282-9197

[email protected]

Collaboration 2.0:Technology and Best Practices for Successful

Collaboration in a Web 2.0 WorldBy David Coleman and Stewart Levine

Link to website of book:http://happyabout.info/collaboration2.0.php