Last Week, I described my effort to begin crafting an Information Policy that will apply to one of our most recent SharePoint solutions. Eventually, I hope to have a collection of these policies bundled into a comprehensive information policy for our company. That may not happen in the 5 to 7 years that remain before I retire, but I’ve heard that it’s good to have goals. This first attempt was presented to the department earlier this week and the draft was well received, even after I explained that most of the work that remains will fall to them. We moved onto the other agenda items, but we kept coming back to the information policy, and I began to realize just how important this document is going to be. The point where this became most clear was well into the meeting when one person asked “how is this [SharePoint site] really any different than the K: drive?”
It’s not the first time we’ve been asked this question in the years that we have been trying to move our content from shared folders to SharePoint, but this was perhaps the easiest it has ever been to answer that question.
“It’s different because we can answer three questions for every document on this site that we can’t usually answer for content on the K: drive:
1) Why did we create this document?
2) Who was involved in its creation and disposition?
3) Why did we keep it?”
The inability to answer those three questions is why most of the content on the K: drive will end up staying there. Once the shared drives become read-only; it will take a lot of effort to explore the content and answer those questions. That task will get even harder when the people who were here as those documents were created retire. The loss of tacit knowledge has already begun to affect our ability to classify older documents, without reading them and without a little guess work, and it’s only going to get worse.
One of the tasks that this group has to accomplish is to move a lot of historic content into the site we created for them. This effort will be guided by the information policy, and the experience will help them refine the policy. A good example of how this will work came as we demonstrated Boost Solutions’ Classifierproduct for them. I’ve written about this product before, but in a nutshell, it lets you quickly tag and process a lot of content that has similar qualities. We stumbled upon two documents that looked like good candidates, a draft contract from a vendor and a list of changes that our staff had proposed. Before we could process these, the head of the department asserted that “we should not keep these, because, in this case we only care about the final contract” which we also had. This led to a short discussion of the kinds of documents where we want to keep drafts and review commentary and the kinds of documents where we don’t. This distinction mapped well to the library structure we had created and there was a placeholder section in the draft information policy for that kind of management decision to be documented.
Other elements of the policy are equally important for helping future employees answer those three questions. For example, there is a section titled Definitions. In the draft of that section, I included the words, library names and metadata elements that need to be clearly defined. Two library names that I included were Internal Communication and External Communication – why do we need to define these? Well, maybe we could live with one definition, but are we talking about external to the company or external to this function? Another definition was a word we have all seen too many times in business, “stakeholders” – when does someone we do business with become a stakeholder? That’s important because it’s a metadata term used in a lot of places, and if stakeholders are involved, the apparent importance of the document increases.
In our board meetings at the New England Chapter of AIIM, we often describe a documentation task as being necessary “for the children.” In other words, we are taking the time to document something that we figured out, but that future board members shouldn’t have to. That’s the difference between managed content and a bunch of files in a shared folder. That’s why you create information policies and that’s why you pay attention to the definitions, guidelines and clear instructions that people include in that very important document. Of course, the policies can change, so when they do, the document should be revised.#InformationPolicy #design #ECM