bp303 taxonomy versus folksonomy: document management in a social age

60
© 2013 IBM Corporation BP303 Taxonomy Versus Folksonomy: Document Management in a Social Age Femke Goedhart | Business Consultant

Upload: femke-goedhart

Post on 14-May-2015

5.013 views

Category:

Technology


1 download

DESCRIPTION

With the rise of social business and platforms like IBM Connections, many companies are re-evaluating their document strategies. Ideals of employee-driven sharing, tagging and folksonomies are desired, but is all documentation really suited for the freedom of ‘social’? Do some types require more structure, process and control? If so, how do you determine this and integrate it with your social ambitions? This session will cover the principles of document management and social file-sharing. You'll learn how concepts like versioning, meta-data, retention, record and lifecycle management are important to you. We'll show you how to identify key requirements for document management within your organization and teach you how to strategically plan your way forward.

TRANSCRIPT

Page 1: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

© 2013 IBM Corporation

BP303 Taxonomy Versus Folksonomy: Document Management in a Social AgeFemke Goedhart | Business Consultant

Page 2: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Femke Goedhart

Business Consultant specializing in Social Business & Document Management Author on the IBM® Redbooks® team for “Self Assessment and Strategy Guide for Migrating from Domino Document Manager”

IBM Redbooks Thought Leader for the IBM Social Business Insights blog

Member of the Social Connections organizing team, the first global IBM Connections® User Group

IBM Champion Collaboration Solutions 2011-2012, 2013

LinkedIn: http://nl.linkedin.com/in/femkegoedhart

Twitter: @FemkeGoedhart

Blog: http://femkegoedhart.com

Company: http://silverside.nl

Slideshare: http://www.slideshare.net/femware

Silverside, IBM Premier Business Partner in The Netherlands. Making a difference in building Social solutions & adoption of collaborative software

2

Page 3: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Agenda

Evolution of knowledge The file management spectrum Document management elements Strategy Q&A

3

Page 4: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Agenda

Evolution of knowledge The file management spectrum Document management elements Strategy Q&A

4

Page 5: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

5

1960-1975

Page 6: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

6

1975-2001

Page 7: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

7

2001-2015

Page 8: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

8

Knowledge

Data

Information

Page 9: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

9

Company

End User

Page 10: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

10

Top-Down

Bottom-up

Page 11: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

11

Name Number City Country

John +1 702 022 112 Boston USA

Anna +31 754 442112 Amsterdam Netherlands

Sue-Ann +44 64 425 234 London UK

Mitchel +1 702 422 317 New York USA

Collaboration

File Management

ERP

Page 12: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

12

Systems of Record

Systems of Engagement

Page 13: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

94%6%

49%51%

1%99%

2002

1986

2007

2020

Information explosion

Digital versus Analog

Page 14: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

14

Knowledge is the new ‘oil’ of the power spectrum

Page 15: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

15

(Social) Document

Management

Taxonomy

Folksonomy

Page 16: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Agenda

Evolution of knowledge The file management spectrum Document management elements Strategy Q&A

16

Page 17: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

The 5 components of ECM

17

CAPTURE

MANAGE

STORE

PRESERVE

DELIVER

Page 18: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

18

Focus...

Document Management

CAPTURE

STORE

PRESERVE

DELIVER

MANAGE

Page 19: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

File Management spectrum

19

Company

End User

Page 20: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

20

InstantLong Term

Company

End User

Page 21: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

21

InstantLong Term

Company

End User

Document Collaboration Document Sharing

Page 22: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

22

InstantLong Term

Company

End User

Document Collaboration

Enterprise Content Management

Document Point Solutions

Document Sharing

Page 23: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

23

InstantLong Term

Company

End User

Document Collaboration(IBM Connections,

Quickr®)

Enterprise Content Management

(IBM FileNet®, IBM Content Manager®)

Document Point Solutions

(integrated business tools)

Document Sharing(file system, Dropbox)

Page 24: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

24

InstantLong Term

CompanyDocument Point

Solutions

End User

Document Collaboration

Enterprise Content Management

Document Sharing

Page 25: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

25

Document Centric

Infrastructure and Centralized

Ad-hoc Collaboration

Metadata oriented

Inside the firewall

People Centric

Open and collaborative

Community oriented

Content in context... user tags & ratings

Inside and outside the firewall

Traditional ECM

Social Content Management

Source IBM

“Predictability versus knowledge accidents...”

Page 26: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Working anywhere

Browser integration

Desktop integration

Mail & Office suite integration

Mobile support

26

Page 27: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Example: mobile file management

27

Page 28: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Example: mobile file management

28

Excerpt of Dropbox Terms of service as of Jan 2013

Page 29: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

29

Page 30: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

30

FileNet, Content Navigator

CMIS, Open Social

Page 31: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Document management in IBM Connections

31

ProfilesFind the people you need

CommunitiesWork with people who share common roles and expertise

Home pageSee what's happening across your social network

Social AnalyticsDiscover who and what you don’t know via recommendations

Micro-bloggingReach out for help your social network

BookmarksSave, share, and discover bookmarks

BlogsPresent your own ideas, and learn from others

FilesPost and share, documents, presentations, images, and more

Document / Linked LibrariesSecurely manage and collaborate on business documents

WikisCreate web content together

ActivitiesOrganize your work and tap your professional network

ForumsExchange ideas with, and benefit from the expertise of others

Media GalleryAdd sizzle by sharing rich media like Photos and Videos

Ideation BlogsCreate ideas and leverage the crowd to develop them

Page 32: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Example of ECM libraries in IBM Connections

32

Page 33: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Examples of ECM attributes in IBM Connections

33

Taxonomy & structure through folders and hierarchies

Document types & Meta data

Review cycles

Versioning

Lifecycle management & locking

Lifecycle management

Page 34: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

34

InstantLong Term

Company

End User

Document Collaboration

Enterprise Content Management

Document Point Solutions

Document Sharing

Page 35: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Document Management in IBM Connections

35

FilesPost and share, documents, presentations, images, and more

Document / Linked LibrariesSecurely manage and collaborate on business documents

26

Community FilesShare, collaborate and relate files

Document LibrariesManage & control documents and ensure trustworthiness

Personal FilesStore my files

Page 36: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

ECM Magic Quadrant 2012 - Gartner

36

Community FilesShare, collaborate and relate files

Document LibrariesManage & control documents and ensure trustworthiness

Personal FilesStore my files

IBM

Page 37: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Translated to how you could use this....

3726

Document Libraries Run through approval cycles &

processing Manage published versions Retain & archive

Community Files Share with teams Collaborate & get feedback Co-author

Personal Files Concepts & early drafts Share selectively

Add to community

Add to library

Page 38: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Agenda

Evolution of knowledge The file management spectrum Document management elements Strategies Q&A

38

Page 39: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Document types & meta data

39

Page 40: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

40

Page 41: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Dynamic document management elements

41

Check-in Check-out

Versioning

Search and navigation

Security

Workflow / BPM

Page 42: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Record management and retention

42

ISO

RegulationLegislation

Compliance

Page 43: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

43

Let’s look at an example: Version management

Page 44: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

DRAFT

Example version management

44

DRAFT

Released version 2.0

PRODUCTION1.0

Released version 1.0

Lifecycle Management

PRODUCTION2.0

Approval

1.2

1.3

Cus

tom

er R

FC

1.1

Press 5 Press 5

Die

1.0

scr

appe

d

Page 45: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Examples of social attributes

45

Simultaneous editing : IBM Docs®

Page 46: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

But......

46

Version: 1, 2, 3, 4... Version: 1.0, 1.1, 1.2, 2.0...1.21.1

1.0

2.0

1

23

4

Page 47: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

47

01-02-2013Jan 2nd or Feb 1st?

Page 48: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Agenda

Evolution of knowledge The file management spectrum Document management elements Strategy Q&A

48

Page 49: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Deciding your organization’s strategy....

49

Codification Personalization

Page 50: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Ask yourself...

50

standard or customized?

mature or innovative?

explicit or tacit?

Codification Personalization

Page 51: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

51

Long Term

Enterprise Content Management

Codification

Document Collaboration

Personalization

Page 52: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

You need the other part too...

52

Long Term

Enterprise Content Management

Codification

Document Collaboration

Personalization

20-80?

Page 53: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Where are you?Where do you want to go?

53

http://ecm3.org/

Page 54: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Maturity Levels ECM3

54

Information is managed locally and individually

Document management is emerging but still poorly used

Various solutions, policies and procedures are in the process of being implemented but without a broader strategy. Lifecycle management is still in it’s infancy.

Content is managed pervasively and incorporates social/collaborative content management. Lifecycle management and retention have been covered.

Content management fully enabled in a flexible and integrated architecture allowing for quick implementation of new content and technology

Source: ECM3 Model http://ecm3.org/

Page 55: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Maturity Dimensions ECM3

55

Human

Information

Systems

IT ExpertiseBusiness ExpertiseProcessAlignment

Content/MetadataDepthGovernanceRe-useFindability

ScopeBreadthSecurityUsability

Source: http://ecm3.org/

Page 56: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

56 Source: ECM3 Model http://ecm3.org/

Page 57: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

57 Source: ECM3 Model http://ecm3.org/

Page 58: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

58

Page 59: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

Agenda

Evolution of knowledge The file management spectrum Document management elements Strategy Questions?

59

Page 60: BP303 Taxonomy versus Folksonomy: Document Management in a Social Age

60

Legal disclaimer© IBM Corporation 2013. All Rights Reserved.The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without

warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.All references to Greenwell refer to a fictitious company and are used for illustration purposes only.