Managing Content ChaosDynamic Workflows using EMC Documentum xCP
AgendaIntroductionThe SituationThe ProjectThe PlanThe ExecutionThe Results
A little about me…Chris CampbellWorked in Content Management for over ten years.
Project manager in telecom and Producer in multimedia
Experience in both financial,  medical and manufacturing industries.
Extensive work in quality assuranceFun StuffQA Lead for Ensemble Studios maker of Age of Empires video game series.
I don’t have a uvula…The SituationWhat have I got myself into?
TakeawaysLearn why are parallel workflows better than sequential.Learn how to combine hundreds of workflows from a dynamic process into a single workflow.Project experience:Know your users betterLearn how to design the “perfect” applicationOvercome objections when the word “compliance” comes up in conversation
The Company – A medium sized financial services companyOrganized 1958 More than 284,000 client families$16.4 billion  in managed accounts and brokered mutual funds$51.2 billion in-force life insurance policies$623 million in banking assets
The Company – The environmentAround 300 people in the home office in 16 departmentsRecent leadership turnover (CEO, CTO)New corporate philosophy being implemented.IT department transitioning from Java to .NET
The Project“You want to do what now?”
The ProblemOver 200 documents need approval every month30 different types of documentsUp to 16 different departments need to approveEach approval needs to be recorded (compliance)A single generic form used to gather approvalsNo written guidelines on process
The ResultConfusion on who needed to sign what
A single person had to “shuttle” each document to each individual signer
Any review meant leaving the document with the reviewer
Reviewer could take forever
Often lost or forgotten
If a reviewer was busy or not there, the document “babysitter” had to come back.
The process usually took all week, if not longer.
Created temptation to take shortcuts
Easy to lose track
Everything became “HOT” and “Top Priority”The PlanStep 1: Get DocumentsStep 2: ???Step 3: Profit!
Gathering RequirementsThe “In a perfect world…” Use Case“What would the perfect application do to solve your problems?”Don’t Be Afraid! Be Bold and Imaginative!
The perfect solution would:Handle all my documents
30 Different Types
Send documents to who needed them when they needed them
16 departments and know who those reviewers are
Be easy to use
Be familiar to users; no learning curve – intuitive
Only show users what they need when they need it.
Track my documents
Reporting, auditing
Versioning
Be secure
Compliance, securityFind my documents easilySearch“Oh, by the way…”I don’t want to be involved unless absolutely necessary.I want to see everything.Could it send me a reminder if I forget?Certain items can be exceptions.Some items have to be done sooner than others.Sometimes I need certain people to review a document that don’t review things normally.My own personal wish:Everything has to be done in one workflow.
The execution“If you vote for me, all of your wildest dreams will come true.”

Managing Content Chaos

Editor's Notes

  • #3 Situation – A little bit about the company, the situational background at the timeProject – What exactly did the project sponsors want out of the software to solve the problems they sawPlan – A blueprint how my team decided to tackle the problemExecution – How it all went downResults – What did we see a year later?
  • #7 Don’t mention company if possible. (Sheesh… the backstory on this.)
  • #13 When gathering requirements, it is more than valid to ask the question: What would the perfect application do to solve your problems?That allows you to ask the people who use the application everyday what they think and what are their “pain points”.
  • #17 Don’t reinvent the wheel!Check to see if there are already written policies regarding documents: Retention policies, record definitions, etc.Is there a defined “language” or terminology that everyone can agree to? For example, what exactly is a “client communication”?Is there a taxonomy already defined?
  • #18 This isn’t an insult to the user base. It’s a generalization of attitudes and feelings that most people will encounter when facing change. The UCL reference is for humor. Good ol’ Saturday Night Live.
  • #23 There is logic available to split the workflow along several paths but eventually needs to combine again. The Join task functionality is limited in that it doesn’t know at runtime if Dept. A and B need to review the task; or if it Dept. B and C; or all three. Now expand the problem to 16 departments.
  • #24 Yes, it’s from Ghostbusters. Originally in Documentum 5.3, I had to use a replacement Split and Join function. With 6.5 and above, just the replacement Split was necessary.
  • #26 Using the concepts learned, it’s easier than ever to use a single workflow to handle dynamic situations… Not just based on content type, but anything requiring a decision matrix.
  • #33 Workflow Summary
  • #37 I haven’t met a department that didn’t groan when the word “compliance” is mentioned and have resistance. You MUST convince people that compliance is in their best interest, or face a constant uphill battle. Best way to convince these people is a little ol’ psychology. Make a straw man argument. The bad guy is someone else and you don’t want to be on his side do you?