Using Wikis With Enterprise Content and Process Management

3,314 views

Published on

Slides from a presentation to Toronto Wiki Tuesday on June 1st, 2010

Published in: Business
0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,314
On SlideShare
0
From Embeds
0
Number of Embeds
751
Actions
Shares
0
Downloads
79
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

Using Wikis With Enterprise Content and Process Management

  1. 1. Using Wikis with Enterprise Content and Process Management<br />Sandy Kemsley<br />www.column2.com<br />@skemsley<br />
  2. 2. Or...The Wiki/ECM/BPM Debate<br />
  3. 3. About Me<br />Enterprise process and content stuff<br />ECM/BPM since…whoa, that long?<br />Papers on BPM and social software<br />Social media maven<br />Five+ years of blogging (column2.com)<br />“The Hungry Geek” at IgniteTO (bit.ly/HungryGeek)<br />I’m tweeting this (@skemsley)<br />
  4. 4. Decisions, Decisions<br />
  5. 5. But In Reality...<br />
  6. 6. Content:Wikis and ECM<br />
  7. 7. Content Management Features<br />ECM<br />Document-focused<br />Document lifecycle, records & retention mgmt<br />Fine-grained security<br />Pre-defined structure and taxonomy<br />Check in/out & versioning<br />Wiki<br />Not restricted to document format<br />Collaborative creation<br />Coarse-grained security<br />User-created taxonomy<br />Interactive editing with history and rollbacks<br />
  8. 8. Selection Philosophies<br />ECM Default<br /> Use wikis for pure content that requires no level of security and maximum levels of accessibility.<br /> Use ECM for everything else.<br />Wiki Default<br /> Use wikis for all internal content by default, unless specific factors dictate the use of ECM.<br />
  9. 9. When To Use A Wiki<br />Created by multiple authors<br />Accessible to a wide, internal-only audience<br />Frequent updating with revision tracking, but no approval or versioning<br />
  10. 10. When To Use ECM<br />External origin/participants<br />Only exists as a document, e.g., PDF<br />Requires precisely-formatted print-ready version<br />Requires versioning<br />Requires fine-grained security control<br />Requires records/retention management<br />
  11. 11. Wiki-to-ECM Transition<br />Initial collaborative content in wiki for brainstorming<br />Reformat and check in to ECM as version 1 of controlled document<br />May continue discussion in wiki with link to document in ECM<br />
  12. 12. Process:Wikis and BPM<br />
  13. 13. Process Management Features<br />BPM (and ECM)<br />Predefined structured process<br />Does not require content<br />Includes human and automated tasks<br />Complex branching, rules and event handling<br />Analytics and KPIs<br />Wiki<br />Wiki to manage a process<br />Case management<br />Project management<br />Documentation trail of manual process<br />Add-ons to manage wiki content lifecycle:<br />Wiki content approval<br />Ad hoc human task management<br />
  14. 14. The Line Blurs<br />BPM gets more unstructured:<br />Ad hoc process definition<br />Adaptive case management<br />Wiki workflow gets more structured:<br />Predefined workflows<br />Content lifecycle management<br />Unstructured human workflow may be done successfully in either<br />
  15. 15. Wiki/ECM/BPM:All Together Now<br />Use case: Insurance claims<br />Faxed-in claim reports and customer-facing documents in ECM to manage retention and security<br />Pre-defined structured claims processes in BPM to meet regulations<br />Claims exceptions using collaboration capabilities in BPM<br />Claims best practices and tips in wiki, updated by claims staff<br />
  16. 16. Summary<br />Clear use cases exist for each of wikis, ECM and BPM<br />Large overlap between wikis and ECM for internal content<br />Large overlap between wikis and BPM for unstructured processes<br />
  17. 17. Questions?<br />Sandy Kemsley<br />www.column2.com<br />@skemsley<br />

×