TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Tom Green responded to my note that an information architect should
have the "ability to combine usability skills and an understanding of
cognitive psychology with profound knowledge of access and retrieval
methods": <<In one meeting (STC I might add), it was suggested that we
be called Information Architects as opposed to Technical Writers.>>
It's all part of the ongoing identity/self-respect crisis our
profession seems stuck in. STC has had this debate for many years, but
not because (as the detractors might have it) we're trying to inflate
our job descriptions. As an organization, STC has always recognized
that not all its members are writers; some are marketers, interface
designers, trainers, editors, translators, and many other professions.
(I've worn all of these hats at various times.) Thus, STC is about
communication, not just writing.
<<It may well be a job that is beyond the capabilities of a lowly Tech
Writer (according to Goeff).>>
It certainly wasn't my intent to give that impression. I meant that
this isn't a profession you can do without a bit of training, and that
most writers "out of the box" lacked such training.
<<I would first have to understand what that means in plain english.>>
It means that you have to understand what makes an information
architecture (the structure and content of the information) usable (the
usability skills), which relies on an understanding of how people think
about information (cognitive psychology) and the structures used to
gather information into nice tidy packages. You also have to understand
access and retrieval methods: that's both the technology (e.g.,
database design) and the human aspects (search strategies, interface
design) of how people find and use information.
None of this is rocket science, but it you need to read up on the
subject to be familiar with the "best practices". We get annoyed when
rank amateurs try to claim membership in our profession, and
information architects might be justifiably annoyed when others claim
their title.
<<I do not intend to criticize you Goeff, in fact I agree with you. I
just don't believe it necessary that the Technical Writer title be
changed to Information Architect.>>
We agree fully on that.
--Geoff Hart ghart -at- videotron -dot- ca
(try geoffhart -at- mac -dot- com if you don't get a reply)
ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl
WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
