Cindy Alvarez (email@example.com) writes:
As one of the projects underway at info-arch.org, I'm trying to do some brainstorming about a "Pragmatic IA/Experience Discussion" area.
This is not the same thing as the deliverables archive; the idea comes more from the IA cocktail hours I've been to. Basically, the most valuable resource I've gotten from the IA community are the "war stories" - real, practical, get-the-job-done discussion.
The main question that arises is: Why should this area be different from a mailing list thread?
A few of my thoughts:
David Heller writes:
I have noticed that the bulk of Information Architects, Interaction Designers, and Experience Designers of all sorts feel that the existing tools fall short. There are people who have created fixes privately, but nothing that can really be used ubiquitously throughout the industry.
Like any community, we encounter the same questions over and over again. Is it time to start an FAQ?
Well, just that has happened on the IAwiki, courtesy of John Paul Fullerton. Is this the place to do it? I'm wondering if we can tie the FAQ to the SIGIA-L discussion a little more closely. What else would an IA FAQ be? And how would you like to be involved?permalink | Comments (4)
Another great idea from Jess McMullin. Jess says:
"I'd like to see a place where everyone can work to create IA deliverables
This seems like it wouldn't be that hard to develop, and rumor has it that Jess is working on a blog to do just that. Rumor also has it that Michael Angeles of IA Slash fame might also be involved. ;-)
Of course, if it's going to happen, we need your help. And it looks like there are already some really smart people involved, so you won't be alone.permalink | Comments (14)
Here are Jess' words:
"Something I've been kicking around offlist is creating an IA site network.
OK, so why pursue an IA site network? [more on site networks in general
1. Good ROI
Lou asked me if we wouldn't need some kind of resolution on scope for the
Of course those sites would have to *want* to be involved. But assuming they
Any reactions? Would this help you? Want to get involved?permalink | Comments (46)
Mailing List Archive: Leveraging What's Been Said
The SIGIA-L mailing list, sponsored by ASIS&T, is a valuable resource to the community. However ASIS&T doesn't have the ability to effectively support the list's ongoing maintenance of SIGIA-L. A new archive could be created that could initially address basic problems we're currently encountering.
Creating archives for these lists could draw much interest from those not currently focused on IA but who work in related fields. Of course, a potentially thorny intellectual property issue could arise here: would we have the right to host this content?
A possible related project would be the creation of an FAQ directed toward new members of the SIGIA-L mailing list.
permalink | Comments (31)
Directory of Professionals: Connecting Us to Each Other
Community functions could be enhanced by a well-designed and well-populated directory of IA professionals, supporting access by geography, skill set, and other attributes. A good information architecture, combined with ideas from such related fields as social network design and economics (a la Slashdot), might result in a high-value resource that showcases our field's skills.
Should content addition and maintenance be self-serve? Or perhaps to have your entry added, you should be required to classify and/or QC one other person's entry already in a queue?permalink | Comments (52)
Employment Area: Resumes and Job Postings
Job postings and resumes could be posted for information architecture and (possibly) related positions. This could be a huge improvement over such services as Monster.com, which have different definitions of information architecture, and which don't distinguish types of information architecture.
The resumes could potentially be tied to the Directory of Professionals. Some database technology, not to mention classification scheme design and content maintenance procedures, would be need to be implemented to support such a system. Also, some decisions would need to be made regarding whether or not to charge (and whom) for such a service.
Additional content could include:
Promoting the Field: Creating and Getting the Word Out
Information architects need, as a group, to make a better case that their services are valuable and necessary to the operations of just about every complex organization in existence. To do so, two things must happen:
Each of these areas could ultimately be developed as specialized content areas in and of themselves.
Perhaps an argument for a more formalized IA association is that such an entity might be necessary to list as the contact for any press releases we might send out...
Anyone out there with PR experience willing to contribute?permalink | Comments (9)
The Library: Building a Resource Collection for the
These efforts are often doomed due to issues of scalability. Could the IA community be enlisted to identify, evaluate, and classify IA resources? The solution might lie in using an active "economic" model, like Slashdot's, or a passive one, similar to Amazon.com's reader-reviewers, to channel volunteer effort into maintaining such an ambitious collection.
This might also be an opportunity to create a model content development policy for use by a distributed community. Which would be cool.
So, the $64,000 question: is there a scalable model for a distributed library of IA resources?permalink | Comments (19)
The News: Pushing "What's New" Out to the Field
Working hand-in-hand with The Library, this tool could aggregate news and events information from IA-related blogs that use RSS to support content syndication. The goal would not be to replace those blogs, but to aggregate them to allow users to access those blogs' content in one place.
Isn't someone doing this already?permalink | Comments (7)