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.
On Sunday, 14 February 2016, <mbaker -at- analecta -dot- com
> What it should be, though, is neither of these things. In the paper world,
> authors were responsible for the organization and connectivity of
> information within a book and librarians were responsible for finding books
> on shelves. No one was responsible for the overall organization and
> connectivity of an organization's information as a whole because there was
> not effective technological means to organize and connect that much
> information into an integrated and navigable whole.
> In the digital world, the technological means exists, and reader's
> expectations have changed to expect that kind of integration and
> connectivity and the one-stop information shopping that comes with it.
> Unfortunately, our authoring processes and tools, and our traditions of
> information design, have not kept up and largely do not fit with that
> model. Information architecture should be about changing all that. What we
> see too often though is that people create the job title but don't change
> their tools or their design habits to match. Many of the tool changes that
> people are making today are more about doing the old thing for less money
> than about doing the new thing. All of which, I think, contributes to a
> lack of clarity about what the role of an information architect is or
> should be.
> In short, it is not enough to give someone the title of information
> architect. You actually need to build an information architecture. But what
> many organizations are building is not an information architecture, but a
> content assembly line.
> -----Original Message-----
> From: techwr-l-bounces+mbaker=analecta -dot- com -at- lists -dot- techwr-l -dot- com [mailto:
> techwr-l-bounces+mbaker=analecta -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of
> David Farbey
> Sent: Sunday, February 14, 2016 9:37 AM
> To: TechWhirl (techwr-l -at- lists -dot- techwr-l -dot- com)
> Subject: Re: Information Architecture seems quite similar to Technical
> While I've seen Information Architect used as a synonym for the sort of
> planning work that a senior tech writer or a doc manager may do, I have
> also seen it used for the job of designing data structures and other
> back-end features of web sites and systems.
> I've also noticed that information architects appear to be better paid
> than technical writers...
> David Farbey - david -at- farbey -dot- co -dot- uk
> Mobile 07538 420 800
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
> You are currently subscribed to TECHWR-L as dfarbey -at- yahoo -dot- co -dot- uk -dot-
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
Sent from my mobile device
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com