Facilitating human interoperability
Apr 4th, 2005 by Aaron Louie
[Yes, it's been almost 2 months. Yes, I know, I'm a terrible blogger. Work gets in the way.]
Pursuant to my previous post “On Systems Librarianship“, I will be moderating a session at the annual meeting of the ASIS&T PNC on the role of Systems Librarians and Information Architects in getting people to work together. You see, the theme of the conference is “Building Bridges: Overcoming the Barriers To Data Interoperability,” and the call for proposals asked for research and reports on how information professionals were enabling the smooth transformation of data from one system to another.
In my opinion, that’s mostly a solved problem, given the wide variety of computer programs and routines that are all tuned specifically for processing data — text, numbers, images, binaries, and so on — but what is NOT solved is how to transmit meaning from one context to another. You could have the best data-sharing protocol or content management system in the world and still fail in the end due to miscommunication between the techies and… well, everyone else. For instance, look at the word “groupware”. To some, it means videoconferencing, shared drawing, collaborative VR, MUDs and MOOs, and other fancy technologies that are “virtual” analogues of real-life interactions. To others (particularly IT departments), “groupware” means shared calendaring, email, and discussion boards. Now, say the CEO or library director passes down an edict to the IT department that they need to support “groupware” ASAP. Imagine the derisive snorts and invective each camp will direct at the other when they finally realize, after weeks of confusion, what the other really means. Think of the irreparable damage to human relations between the administrators and developers that will cripple progress for years to come. Who would care then if MARC records could be seamlessly converted to XML-RDF?
It’s a human problem that requires a human solution. And it’s precisely where people like IAs and IT librarians come in. We need people who have a systems1 view, who can see the big picture, and who are bilingual (or multilingual!) in the jargon of technology AND business. Who better to fill that gap than those who are skilled in discovering user needs and translating those needs into designs and guiding those designs through to development and implementation?
This is the topic of the panel I’ll be moderating at ASIS&T PNC 2005. The abstract follows:
Session Title: Lingua Franca: How do we facilitate human interoperability?
Session Abstract: The barriers to data interoperability between information systems are nothing compared to the barriers people associated with those systems build between themselves. This is especially true between non-technical stakeholders and the technical staff who must implement and maintain the information systems. What is the role of information professionals in bridging this gap?Session will include a panel of 4-6 systems librarians and information architects. Panelists will be invited to discuss how information professionals (especially systems librarians and information architects) can act as translators between non-technical stakeholders, end users, and technical staff throughout the lifecycle of an information system. Focus will be on practical strategies and tools of the trade: visual language (eg. concept maps, flowcharts, ERDs, UML, IA diagrams, wireframes, etc.), documents (eg. prospectuses, business cases, paper prototypes, technical specifications, etc.), and communications technology (eg. groupware, content management systems, etc.).
[If you're an IA or Systems Librarian, can be in Seattle on May 14, and would like to be on the panel, let me know. ASIS&T can't afford to pay travel expenses, and I don't know if you can get any kind of discount on registration. I'll post an update when I know for sure, though...]
[UPDATE: Yep, your registration fee for the conference will be covered. Here's the link to the chapter web site again.]
1By “systems” I mean it in the sense of holistic “systems science” or “ecosystem” or “systemic”, not “IT Systems”.