Let’s start this admittedly provocative post with a question: Anybody out there actually doing records management in SharePoint?
And before you answer, let me emphasize that I mean real records management, like, with actual, system-enabled automated disposition according to your retention schedule.
If you answered “yes” to this question, please jump immediately to the comments section and let us all know (and while you're at it, give us some indication of how on earth you're doing it), because based on my experience, I’d be willing to bet the answer to this question is going to be “no” in 99.9% of all cases.
And while I’m in a betting mood, I’d also be willing to bet that if you answered “yes,” you 100% aren’t doing it with out of the box SharePoint, because out of the box SharePoint can’t do records management at the level the vast majority of organizations require — it just doesn't, people, no matter how much Microsoft claims that it does, or trumpets that fact that they themselves use it to. But don't just take my word for it, ask Bruce Miller.
Gauntlet – Thrown
And lest you think I’m heaping blame on already blame-laden records managers out there, let me say right off the bat that the real problem with records management in SharePoint is that Microsoft doesn’t really understand records management or what it takes to enable it with an enterprise content management (ECM) system.
SharePoint 2007, was supposed to be “records management ready,” but required users to put all their records in a separate area (the records center) to manage them. Getting users to work in two different sites, one for records and one for the rest of their stuff? Say it with me: never, gonna, happen. And never did happen.
SharePoint 2010 didn’t get much better. True, you could now manage records in place, but 2010 drove records retention and disposition using content types, which, if you had a few hundred of them, were incredibly cumbersome to work with from an administrative and architectural perspective; which is precisely how many most organizations need at a minimum to support their retention schedules; which is why I haven’t seen a single organization using SharePoint 2010 to do real records management (i.e., with actual, system-enabled retention and disposition according to the retention schedule), and I run into a few hundred Fortune 1000 companies a year between projects, sales calls and events.
The Problem is Bigger than SharePoint
Now before I get accused of bashing SharePoint here, let me let you all in on a dirty little secret: 99% of organizations are not doing automated records management on an enterprise scale. And this is true whether they have SharePoint, IBM FileNet/P8/CMOD, EMC Documentum, OpenText, Hyland OnBase — whatever. In the end, it doesn't matter: for a whole host of reasons, some of them technical, some of them organizational, so few folks are actually doing automated records management that we could accurately say that no one is.
Let’s look at some anecdotal evidence for my claim and then turn to some of the reasons why before exploring how we might turn this around.
First, at every ARMA, AIIM, EFM or other ECM-related event I speak at, I always ask the audience, “who’s doing retention and disposition on electronically stored information (ESI) according to the retention schedule?” and I never get more than a hand or two in response … and then I ask a follow-up: “Even on shared drives and hard drives?” and all the hands go down.
Second, no client I’ve ever worked with (somewhere north of 120, all Fortune 1000) has managed to do automated records management on any significant basis. And if you widen the sample to all the Fortune 1000 clients my firm has worked with (somewhere between 400-500), there is only one, a North American bank, that is doing so.
- SharePoint is Already Legacy
- Are You Too Old to Work in Tech? IT's Midlife Crisis
- Has Google Just Reinvented Gmail?
- What to Do When Yammer Adoption Stalls
- Is Your Information Architecture Ready for SharePoint 2013?
- Microsoft Lync Can Spy on Enterprise BYOD Use
- Discussion Point: Is There a Secret Sauce for Employee Engagement?