Records Management 2.0

Community Topic(s):

Keywords: facebook, Social Media, Records Management, rm 2.0, Twitter, linkedin

Current Rating:
(0 ratings)

 

It's an interesting time to be a records manager. Many of my blogging colleagues have noted the increased emphasis on information governance, and the prospect of increased regulation in the financial sector was a frequent theme at the AIIM 2010 conference last week.

At the same time, a number of vendors, both new and "legacy", showed up at the conference with social media offerings. Some of these were positioned as competitors to SharePoint; others targeted the interest in Facebook and other social media services but with the promise of ensuring compliance with the aforementioned requirements.

And yet it was clear in my discussions on breaks and at networking events that for many organizations, the desire remains to use Facebook, Twitter, and other commercial social media tools. There are two main reasons for this. First, the promise of "free as in beer" tools is a huge factor. Most of the major social media tools are free, or at such low cost compared to more traditional content management and collaboration tools that they might as well be. The economy appears to be turning around, but purse strings haven't loosened up completely just yet.

The other reason is that these tools are where the users are. In other words, it's nice to think about having an inside-the-firewall Twitter, but that ain't Twitter. This is especially important where the tool will be used to interact with external constituencies, such as government Facebook fan pages or broker-dealers using Twitter or LinkedIn.

I draw a number of conclusions from this. Organizations are already using these tools. Like email, many organizations have policies in place to address their usage; also like email, many of these policies focus primarily if not exclusively on acceptable and/or effective usage of the tools - for example, they provide guidance on user names and pictures, proscriptions against offensive posts, or how to respond to comments.

But there is very little discussion of how to deal with the recordkeeping and compliance issues raised. Steve Bailey wrote a book called "Managing the Crowd: Rethinking Records Management for the Web 2.0 World" a couple of years ago where he raised some of those issues, but he readily acknowledged that he didn't have all the answers. James Lappin, another UK-based records management consultant, also blogs on these issues. And there are a few others of us out here thinking about how to apply 60+ years of records management strategies and techniques to these tools - but we don't have all the answers yet either.

So this is my starting point for what I hope to focus on in my blog posts. Records management is records management. Records are determined by their content and value to the organization, not by their format or where the information is physically stored. But the tactics will be different for these tools for a number of reasons that I will explore over the coming weeks. We have tactics for some tools and some use cases; others will need to be developed to address some of the unique characteristics of social media. And of course some will come from the application of judicial rulings and case law. What I do know is that records managers need to learn the tools and start thinking about how to manage them now, as they are being introduced, rather than ignoring them as we did with email.

Report

Rate Post

You need to log in to rate blog posts. Click here to login.

Add a Comment

You need to log in to post messages. Click here to login.

Comments

James Lappin

Hi Jesse, I am interested in the implications of the recent announcements by Facebook and Twitter on identity management in organisations. Facebook and Twitter are making a play to be the identity platforms for the internet, they want us to be able to log on with our twitter or facebook names wherever we go on the internet. Organisations also manage the identities of their staff using tools like Microsoft's Active Directory. It is going to be very interesting to see how organisations and individuals cope with these dual identities, particularly when, as you point out, organisations use Facebook and twitter for business purposes. Could you envisage a situation where people log onto a business application using their Facebook ID?
Report
Was this helpful? Yes No
Reply

Bryant Duhon

The more that I use Skype, this community, hootsuite (for Twitter), and my work email (Outlook); the idea of being able to sign in once to gain access to everything that I use holds a certain appeal. Though I'm certain it also scares the bejesus out of anyone in charge of security/risk. That's why your last sentence, James, made me think of an online Driver's License. One central, authenticated identity that gets you into any bar that you want!
Report
Was this helpful? Yes No
Reply

Philip Rimmington

I believe that users of ecm who work with customer documents don't need to use records management tools. I think records management should work automatically behind the scenes. Does anyone dissagree with this approach? If so, why?
Report
Was this helpful? Yes No
Reply

Randy Moeller

After 25 years in business records management I know the chance of stopping new tools is quite remote. Records management long ago needed to rethink (in business anyway) how to approach the ever changing field of record creation. No I don’t bother to argue what is a record, what isn’t. If ‘it’ can be possible evidence in litigation, it’s a company record. Don’t micro-manage the issue and I don’t think we can micro-manage records in some of these technologies either.

Risk tolerance can help. What is your risk tolerance with a wiki? Example; you and the vendor build a contract using a wiki. It contains all the comments and edits but a final version is generated into a .pdf and you use a web hosted e-sign tool to sign and store the original. Your risk tolerance question, how long do you keep the stuff in the wiki? High tolerance; the contract is signed so dump the wiki as the contact terms are the contract terms. Low tolerance; keep as long as the contract retention time just in case.

Of course the other issue is understanding what the wiki is being used for but the higher (or dare I say bigger bucket) you view the tool the easier the answer may be. Someone once said if your problem is too small for a solution, make the problem bigger. I think that is an approach for at least some of the technologies as no one is using Twitter to create a laboratory notebook.
Report
Was this helpful? Yes No
Reply

This post and comment(s) reflect the personal perspectives of community members, and not necessarily those of their employers or of AIIM International