Group items tagged

Document management is all about workflow, control, and risk mitigation. Its objective is summarized perfectly by the two words in its name: "documents" and "management". It got its start in the legal departments of pharmaceutical companies, who were concerned to make sure that their companies were producing documentation in full compliance with regulatory requirements. A DMS thrives where there are a) documents already being created as part of a business process; and b) those documents need to be closely checked in, checked out, supervised, edited, approved, and stored following a consistent and audit-proof process.

Collaboration, by contrast, is all about people working together to share ideas, notes, questions, comments, etc. Collaboration does not typically follow a standard process; it is much more free-form and free-flowing. Documents are not typically the format of choice. Asking a question or creating a meeting agenda or to-do list doesn't require a document; it just requires typing some words and putting them where other people can see and edit them. That's why so many people simply fire off an email when they collaborate; it spares them the unnecessary step of creating a document.

When asked about the relationship between DMS and collaboration tools, what I said was that some of the content in a typical DMS really belongs there. These are the documents associated with highly regulated processes. But most of the content in a typical DMS--to-do lists, meeting notes, press clippings, conversations, working papers, personal observations--doesn't really belong there. It's in the DMS because there was no good place to put it. That's where a collaboration suite can do a much better job. A good collaboration suite can liberate that content from the tyranny of documents and nested folders, and will encourage people to use it for actual working materials.

In many cases, you will want to integrate the two. Law firms, for example, are absolutely dependent on their document management systems to manage their filings and other legal documents. But we're increasingly seeing them set up collaboration suites to capture all the discussion around the documents, how to use them, what they mean, and so on. The two systems are integrated with links from the collaboration suite into the corresponding DMS records.

What I'm saying amounts to this: Use your document management system to manage documents, and use your collaboration suite to collaborate.

unfortunately SocialText is not very good at linking to the documents in the obvious place (attachments).

Content is made of people: from ECM to E2.0 Der Vortragende Lee Bryant ist CEO von Headshift aus London. Sein Vortrag beschäftigt sich mit der Transition von Enterprise Content Management zum Enterprise 2.0.

Bryants Herangehensweise an Enterprise 2.0 fasst er mit folgenden Punkten zusammen: Public feeds & flows: internal and external RSS, feeds based on subjects, persons, group or search Bookmarks & tags: people store, share, tag, vote or comment on useful links and news Blogs & social bookmarks: social objects shared within networks and discussed in blogs Group collaboration: intimate groups/teams organize knowledge in wikis and group systems personal tools: organise your “stuff” by tags; arrange in a portal; manage networks and feeds Dabei geht es ihm vor allem auch darum, diese Dinge als Stimulanz für die pragmatische Umsetzung der alltäglichen - geschäftskritischen - Aufgaben einzusetzen.

Lee Bryant stellt kurz die wichtigsten Vertreter der Enterprise 2.0 Tools vor, die wir auch hier beschrieben haben. Dabei spielt auch Atlassian Confluence eine Rolle. Microsoft Sharepoint kommt bei ihm aber eher schlecht weg, was die Akzeptanz als Enterprise 2.0 Plattform angeht.

Post Wide Web: Das Intranet der Schweizerischen Post

Social Computing bei MLP Finanzdienstleistungen

Einsatz eines Unternehmens-Wikis für das Wissensmanagement am Beispiel von IT-Delivery-Prozessen der REVACOM GmbH