A more serious topic of discussion was the concern that data management has become a profession (job, role or set of activities) of older people. I tried to point out that young people such as myself were entering the profession. They were quick to point out that 50 didn't count as young. Who knew!
While I share that concern, I think that there are aspects of the profession that will always skew the age of practitioners toward the "experienced" end of the scale. That would include a focus on:
- data, not on the computers and applications
- an enterprise view of the organization, not an operational view
- semantics, categorizations, meanings and definitions
- specialized jobs (traditionally found only in larger organizations and consulting firms)
- planning and coordination
Look, experience need not be synonymous with age, so if we want to bring younger practitioners into the field then we have got to do a few things different.
First we must teach the core competencies that serve as the foundation for data management training later. It parallels the effort to teach computational thinking skills like numbering systems or sorting algorithms without using computers at a young age so they are prepared to learn computer programming later, if they wish. These competencies - things like classification, abstract thinking, information literacy, computer literacy and set theory - ensures students are prepared to learn data management at a more appropriate time. Wax on, Wax off.
Second we must build awareness of data management as an area of study, as a set of skills and as a profession. Most of you are probably thinking database administration when I speak of data management. Fair enough, database administration is certainly part of data management, but so are data modeling, data warehousing, data security and any number of other jobs or roles. Our biggest challenge in this area, as Karen pointed out on numerous occasions at the conference, is to be visible to younger professionals by participating in the communication channels they use. This means we need to be talking data management in blogs (or this one), on Twitter, on LinkedIn, in discussion forums and on wikis.
Finally we must develop, or at least help to develop, curriculum to support the needs of new entrants into the field as well as the ongoing professional development of those who have already chosen data management as a career path. DAMA International made a huge leap in this area last week with the release of The DAMA Guide to the Data Management Body of Knowledge (DM-BOK). The challenge now is for data management professionals to carry this information to local colleges and universities. Additionally, we need to push beyond the basic database training to teach a broader range of data management activities. As Peter pointed out on several occasions, we teach students how to build new databases, but how often do we really do that in our professional lives.
Let me leave you with one final thought. Data management is both a set of activities and a profession. Many people who do the former don't consider themselves the latter. They are, nevertheless, contributing to the body of knowledge, for better or worse, and we need to connect with them just as much as an up-and-coming metadata analyst. Consider the outcomes that Mrs. AdvisoryBored identified in her original proposal for the Business Information Management class (MGMT 215) at Edmonds Community College (see the end of page two). There is no guarantee that the students, particularly those from the Business department, will embrace those data management principles and/or the profession, but she has at least had the opportunity to introduce the concept of data as a managed enterprise resource.
Tags: Enterprise Data World, DAMA, DM-BOK, Data Management