Repositories - Map

The following sections, will address specifically how do you implement the concept of structures in a repository. If you are not part of a similar project, you might want to skip to creativity and innovation.


The first thing you need to do when trying to go from one point to another is to define where the initial point is, or A taking A-B. This means creating an information map to know where everything is, and how much effort and materials will consume the task of migrating.
The green section is about identifying the different systems holding your information. Identify possible conflicts with duplicated documents and/or special needs in processes requiring more than one group that are to be migrated at the same time. It can provide valuable statistical information about the growth trends, habits, and current activity in all your systems.
In this diagram we follow the elements in our framework Data-Processes and eventually Collaboration. It is always recommended to have a cleaning and consolidation phase before designing your repository; it can give you a fresh start instead of trying to do it later down the road.

After many implementations is safe to say you will need a strong mandate for this sections to be carried on by your employees. So do not be afraid of asking for this mandate to your CEO or president because this is where leading the way makes a very important fact for the project to succeed.
What I am recommending in this diagram is to have a repository first and then your business processes. Why? Because many business processes may require you to have the repository at hand prior to implementation plus it makes it easier for you to do it while you are doing the repository design first.

In my experience I have found out that some groups (I wont name anyone) have the expectation that a consultant will come with a magic formula to convert the mess they have into something clean and pristine. I had the sense that for some reason they think "one solution fits all" will work in their company. Another type of thinking is asking consultants who else has the same solution or implementation. In reality, these projects are each very different to implement because each company or institution is different, how? in the way they conduct business, the way they store information, in their culture. What you need is to assess each organization and come up with a plan based on the assessment and not from some past experience that seemed to work which is important but it cannot be assumed will work for everyone.