Increasingly Im hearing from my clients that they want to create a position designed to manage the database. In the old days, they called them database administrators (DBA), which was a mostly technical job focused on keeping the database running (think auto mechanic). But what most associations really need is a database manager (DBM).
Simply put, this comes down to documentation and training. Ive written scads about this over the years; my most successful clients are those organizations that have taken the time to document their business processes and to provide association-specific training to their staff. The DBM is a key player in this process. The DBM should work with staff to create the documentation and training that will be used throughout the life of the database. A very skilled DBM can also provide that training.
One of the biggest challenges any organization faces is ensuring that staff use the central database for all of the data being managed at the organization. (Even the most successful associations struggle with this, as I outlined in my white paper on the Nine Keys to Long Term Success of Your AMS, which you can find here.) The DBMs job is to sniff out rogue databases (e.g., Outlook distribution lists, stand alone databases in Excel or Access, or even Word documents), find out how this information is being used, and work with the staff to get that information back into the central system.
This is probably the most critical skill. Successfully managing the database cannot be done in a vacuum. That is, your DBM needs to know what your organizations mission is and how the data is being used to support that mission. For example, many associations have, as part of their strategic mission, increasing engagement among the members and the broader public. Given that mission, the DBM will ask How can we use the database and the data we have to address that objective?
Did you like this article? If you’d like to receive notice of articles like these as they are posted in the future, click here.