SharePoint sucks at document management – or does it? A metal perspective

Send to Kindle

This is an opinion piece, a different tack than a lot of my other topics. I’m going to attempt to use heavy metal music as my metaphor to get my point across. No idea if I will succeed :-).

Opeth \m/ \m/


Firstly, SharePoint, in my opinion, is a collaborative platform, more than it is a collaborative product. In the same way that Lotus Notes can be argued as a messaging platform. Both have their core competencies and solve particular types of problems. However, they can also be customised and sophisticated applications can be built upon the foundation they provide.  Note my emphasis on the word collaborative.

Secondly, like heavy metal, the term “document management“, is misused and misunderstood. It is simply a generic concept that needs to be broken down into sub-definitions or sub genres.

For those people who think the idea of listening to Celine Dion is a good way to spend an hour, it is exceedingly likely that they would consider heavy metal to be a single genre. But of course, us metalheads would beg to differ. As an example, you have Black metal, Death metal, Glam metal, Industrial metal, Power metal, Progressive metal and Thrash metal to name but a few. (However I personally would put power metal in the same bucket as a Celine CD πŸ™‚ )

So I am a progressive metalhead, I love Opeth and I would consider them to be the absolute masters of progressive metal genre. But, they are a band that frequently uses the ‘cookie monster’ vocal grunts commonly associated with death metal. Does that make them a death metal band? No it doesn’t. They may share some of the characteristics of death metal but are a very different beast.

So, as part of collaborating, we need to manage documents. We have a team of staff all working to achieve a goal and along the way, they need to work together as efficiently as possible. Time is money. That means timely access to the latest version of a document no matter where you are; the ability to track and maintain versions of documents; the ability to enforce internal processes such as peer review and signoff and so on.

Often, the end goal of this process is a document or set of documents that have a ‘final’ or ‘legal’ aspect to them. For example: A final report to a customer. Such a document needs to have this version, at this point in time, captured. At this point, the document becomes a record.

Now collaborative document management is very different from the more rigid and structured form of document management known as records management. Records are defined as “information created, received, and maintained as evidence and information by an organization or person, in pursuance of legal obligations or in the transaction of business”.

A really, brilliant, insightful post on this subject can be found at joiningdots blog and I am going to quote his list of the activities in relation to these two genres of document management.

Records Management:

  • Management of the record is more important than the content of the record
  • The record never changes (although its properties might)
  • Records require access controls, lots of them

Document Management/Collaboration:

  • Without content there is no document
  • The document changes a lot, that’s the whole point of collaboration
  • Access controls restrict and impede collaboration, the fewer there are the better

Now to continue the metaphor, here is the explanation of death metal vs progressive metal πŸ™‚

So collaborative document management and records management are similar to Progressive Metal and Death metal. They have some common characteristics, but have different goals and outcomes. Let’s now look at some of these characteristics in a SharePoint environment.

SharePoint Document Management Sucks?

No, it does not suck (although I will keep an eye on my website stats to see if a controversial title means more readers πŸ™‚ )

In my opinion, SharePoint is a really good collaborative document management system. It, however, is not as good a records management system.

Collaboration is about teams and productivity. What makes one team productive is not necessarily the same as what makes another team productive. A site with a document library for a sales and marketing team will likely have different columns, views and workflows than a document library for a bunch of IT geeks who are writing system documentation (yeah right – geeks write documents? πŸ™‚ )

SharePoint is great for document collaboration, because it is so flexible in how you structure sites and document libraries. It is common to see a SharePoint farm broken into broad, divisional based portal sites, with team based sub-sites within. There is often one or two columns that are relatively consistent across all document libraries in the farm. In addition to this, the various document libraries and content types within these sites will often have additional different columns, based on specific requirements of the team or division using that library.

There may be some file naming standards, but if not it doesn’t matter much, since the users can easily fill in the metadata columns when they save a document. ‘Folder hell’ is reduced and views allow for easer retrieval. Roaming users have offline copies of document libraries either in Outlook, Groove, Colligo or iORA and regularly sync the latest versions.

What a wonderful picture I paint ,eh? I can see Opeth right now, storing all of their tour info in their tours document library, but using a different document library for their songs guitar tab. The latter has a column that classifies the tab by album and author. Michael Akerfeldt, (Opeth’s amazingly talented singer/songwriter) has a sync version of all of this in Outlook on his laptop.

Compare to this…

A records management system is like a single giant document library. The columns are usually standard, no matter what the content. Usually the classification system (called a taxonomy) is based around a coding system that among other things, indicates record types, and the retention policy and compliance requirements for that record type.

That coding system is called a “File Plan”, and record managers love them, but the rest of us hate them with passion. Why? Well, they have about the same level of intuitiveness as the account codes for a chart of accounts, or time-sheets for that matter.

But they all serve a similar purpose, so I guess that makes sense. So I’ll explain better.

For general collaborative use between a team, record file plans just plain suck. This is because the coding system is based around “file codes” which are numeric representations of the taxonomy classifications. Those numbers mean a lot to the records people, but are not intuitive at all to the rest of us. Usually records are sub-classified 2 or 3 levels as well, as it’s rare to have a single level file plan. So here’s Opeth’s example file plan…

401 110 – Reports and Statistics

1.0 Merchandise

2.0 Tours

        2.1 Sweden

        2.2 Norway

(rock on baby! – file plans are just so metal!)

So imagine the above code along with a file number for the document, a number for its version, etc.


Now quite obviously if you are a record manager, this document is a report (401-110) about a gig in Sweden (2_1) that is document number 12345 and version number 3 (003).

I can just see Opeth’s Michael Akerfeldt using that naming convention for all his documents relating to the Sweden tour! Then when the tour is over, he can easily archive off his Sweden stuff (401-110-2_1) onto DVD!

Makes me wanna mosh! … NOT!

So many document libraries is not really a good thing for records management. Also, in SharePoint, a file plan style set of columns is difficult. it’s quite painful to have one column filter the value of another out of the box (ie pick your first category column and the list of values in the sub category is filtered). It’s a custom development job or you have to go with a 3rd party if you want to do that.

But no doubt you are aware that there is a records management capability in SharePoint 2007. But in reality, it’s not that fully featured. For the purpose of this article, I won’t get into that, but consider that the data is all in a big SQL Database. Typically this uses a very expensive, high capacity disk, yet some records, according to the file plan, are not worth the cost of that disk. (I.e. it costs more to store than the files are worth). But how to put them onto cheaper servers/media? if it’s one big document library then it’s one big SQL database.

Now don’t think for a second that I’m anti records management. I’m not at all. It is an essential technology. I’m just dumping on it from the collaborative end-user perspective to help my argument :-).

Confusion reigns!

Now in all seriousness, I have painted a pretty extreme example I know. But many companies do attempt to go down the path of treating all files as a record when they implement a document management system. Obviously record oriented file naming conventions like the one I demonstrated will not work for regular users, but many companies previously had a dedicated document control department for handling them, and only a small subset of the files (the ones that are records πŸ™‚ ) are treated this way . But when you get a system like SharePoint, it’s easy to think, “cool, now we can classify ALL documents via our file plan and make it much easier to manage our documents”

For me, that doesn’t compute. Power metal has the same effect for me.. what’s the point?

Does it work? I’m sure it does for many organisations. Some high end, 3rd party DMS products have been doing it for years. For me though, I was involved in a non SharePoint DMS installation back in the late nineties. Despite a pretty good GUI, with nice drop downs and easy to navigate metadata screen, the classification system was still too complex for the user base and they misclassified all of their files when saving.

Records Management then one day did an archive of a particular file code because the retention schedule told them to. The next day all hell broke loose! Users live files suddenly disappeared and the system happily presented them with a CD number, asking them to call records management department πŸ™‚

I’ve never seen such a quick file plan redesign πŸ˜‰

So why is it that many companies confuse collaborative document management and records management? I’m not sure, but I sure as hell know that for my money, you should not approach SharePoint 2007 with some preconceived idea that it is going to solve all your records management needs. I can predict it now. You will spend weeks arguing with the stakeholders over a taxonomy, document a file plan that they will all approve, despite not actually reading and then find that SharePoint cannot easily accommodate your requirements out of the box. Your project plan and budget will blow out, senior management will be pissed and you will blame Microsoft for releasing a substandard product.

But who’s fault is it really? πŸ™‚

Thanks for reading..

P.S: Recommended Opeth tracks: Bleak, Deliverance, Master’s Apprentice, Drapery Falls

Print Friendly, PDF & Email
 Digg  Facebook  StumbleUpon  Technorati  Slashdot  Twitter  Sphinn  Mixx  Google  DZone 

No Tags

Send to Kindle
Tagged , , , . Bookmark the permalink.

35 Responses to SharePoint sucks at document management – or does it? A metal perspective

  1. Pingback: CleverWorkarounds » Learn to talk to your CFO : Collaboration Scenario - Part 3

  2. Pingback: CleverWorkarounds » Selling MOSS (the moral of the story)

  3. Pingback: CleverWorkarounds » Why do SharePoint Projects Fail? Part 4

  4. Pingback: CleverWorkarounds » Opeth vs Tech.Ed - impossible dilemma!

  5. Ant says:

    Now I’ve seen it all, using Opeth to explain MOSS’s Document management.. could only be Paul Culmsee.

  6. admin says:

    Hey Ant! How are ya?

  7. Pingback: CleverWorkarounds » Opeth - Watershed review

  8. Schitaz says:

    Are you saying that this situation is like watching “American Pie” for seeking porn rather than an XXX hardcore movie ??!!! so what’s your alternative & best solution for that ?!!! and by the way, to 99.9% of people METAL IS METAL & I like Modern Rock πŸ™‚ …

  9. admin says:

    Modern Rock! Oh no that sounds like Matchbox Twenty! Please nooooooooo! πŸ™‚

  10. Pingback: CleverWorkarounds » Book Review - Essential SharePoint 2007

  11. Jeff Boshey says:

    Sharepoint is about limited document management. Most document systems are based on limited document collaboration.

    There’s a new player in the game and they offer complete collaborative document management.

    Check out

  12. Peter Smith says:

    You articled clarified my mind. I had never understood records management people anyway.

  13. Pingback: Make Amazing Recordings At Home On A Very Limited Budget!! |

  14. James says:

    Hey, don’t knock Power Metal! Although saying it’s akin to listening to a Celine Dion CD is slightly true πŸ˜›

    A good article that explains the difference between records management and document management. Makes me rethink my project slightly (good job I’m in the very early stages still, defining the Problem).

  15. Ed Lee says:

    I have only just started reading you site and it ‘rocks’ just like Opeth. Just missed out on seeing them ( by one day) when I was on holiday in Florida this year and missed them again when I was back in the UK… gutted. Ed

    Keep up the great writing

  16. Sharepoint is not too bad at document management, it just doesn’t make it easy for Records Management

  17. Pingback: CleverWorkarounds » The one best practice to rule them all - Part 1

  18. Greg Kamer says:

    That’s awesome! I love SharePoint and metal! I have to agree one of Opeth’s best tunes is the Drapery Falls. That’s the track that got me listening to them in the first place. Heard them play at Hellfest via DVD…not in person unfortunately.

  19. Neil Homer says:

    Cheers. Next time any of my users ask for the zillionth time if they can dump their 100000 files into sharepoint I’ll point them here. I’ve used the sql storage argument often myself.

  20. Pingback: Dziuban - Writings And Audio. |

  21. Steve says:

    To add to overall confusion is the Document Management industry, who equates the term with scanned documents, not version control and or management of digitally sourced files.

    PSIGEN – SharePoint Scanning and Imaging Solutions

  22. michael says:

    Myself and a colleague have set up a sharepoint document management page that links back to several .mhtml documents. The documents open up differently depending upon the views that are available. In “Explorer View” the documents open in a web explorer and in “All Documents” view the documents open up with the default word processing program…Word.

    We would like for the files in “All Documents” to open up in explorer. Does anyone have an idea as to how this can be done.

    Thanks a million,


  23. Great post. I really like the notion of collaborative document management vs structured document management. On the subject of the structured document management I would further argue that SharePoint’s core document storage is inadequate for higher order structured document management. The reason is that SharePoint supports only single-file documents. I.e. a logical document is stored as a single file in SharePoint. In order for SharePoint to truly excel as a DM system, SharePoint needs to support multi-file documents. When I say “multi-file” document, I mean something like a compound document or virtual document. Yes, SharePoint Server 2010 has document sets, but they are more like the SharePoint version of Office Briefcase rather than true multi-file documents.

    SharePoint’s single-file document limitation manifests itself in the areas of versioning, workflow, and security. The details are too lengthy to go into in a comment, so I published a separate post on the subject here:


  24. illirenue says:

    Hi guys, i ‘ve spent quite a while here reading your posts today, so i decided to register here too.

  25. IObject says:

    thanks for the article. I am planning a sharepoint site for a small office. Using your information, could a simple soution be to use a document library in outlook for collaboration and review, then use MS OneNote in another library as a records management. I understand these are very crude compared to custom deployed sites but is it on the right track.

  26. admin says:

    OneNote for records management? Thats not something that would normally spring to mind. Can you elaborate on you idea?



  27. online document manager says:

    online document manager

    FileVista is a web document manager for storing, managing and sharing files online through your web browser. It is a web based software which you install on your web server to fulfill web document management requirements of your company or organization.This web document manager allows your users to upload, download and organize any type of file with an intuitive user interface.

  28. Pingback: CleverWorkarounds » The facets of collaboration part 5: It’s all Gen-Y’s fault – or is it?

  29. Sue says:

    Thanks for a great post! My employer (software dev/asp) has formed a Sharepoint team. Threw me for a loop that Phase I will likely be Document Management….and the left me out of the initial team. They don’t know the huge difference betweeen document management and records managment. I’m accounting…the ORIGINAL Records manager…have been for nearly 40 years…the hard (copy) stuff for heaven sakes. I SO get what you are saying! Thanks, Sue

  30. Sue says:

    PS: RE: Account Codes for a Chart of Accounts…DOES TOO make sense…if you have a clue…but I’m afraid that too has gone by the wayside (I mean “QuickBooks is an Accounting sytem? UGH! πŸ™‚ Thanks again…you made my evening! (I don’t do metal….cep’t what was metal in the late 70’s. LOL!)

  31. admin says:

    Thanks for the reply and I am glad you liked that article. I also suggest reading the “Learn to speak to your CFO” articles if you are an accountant πŸ™‚



  32. Process Computer Services says:

    Sharepoint is often more than what many companies need and tends to be overly complex.

  33. Pingback: Sharepoint sucks | Goleartu

  34. I recomend Sharepoint document management software JungleDoc. It enables users to create new documents or items with no additional effort, as it reuses existing document content and properties, which frees you from typing or having to copy and paste when creating a new document. It takes properties and parts of an existing document and transfers them to a new one, thereby eliminating mistakes and saving you up to 90% of the time needed for data input or copy and paste operations.

  35. Brian says:

    Honestly, none of the comments have mentioned a better system than sharepoint. Do we have to accept that sharepoint is the best of a lot of sucky solutions? Please tell me if there is a better one

Leave a Reply

Your email address will not be published. Required fields are marked *