In March and April of 1999, I wrote a two-part column for DM Review regarding the top 10 mistakes to avoid when building a meta data repository. Now that it is 2002, it is time to update this list to reflect the changes that have occurred in the meta data repository market space. This month we will examine the first five mistakes on our list.

1. Not Defining the Tangible Business and Technical Objectives of the Meta Data Repository. This is the top mistake that most companies make. Quite often, the meta data repository team will neglect to clearly define the specific business and technical value that their meta data repository will provide. It is critical to define these objectives up front as they will guide all proceeding project activity. When selling the concept of meta data to your corporation's senior management, there are only two things that they understand: increasing revenues or decreasing costs. If you are not talking about increasing revenues or decreasing expenses, you are the IT version of the schoolteacher on the old Peanuts cartoon: blah, blah, blah, blah, blah.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access