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.
Subject:Re: Don Norman on Manual Writing From:"A" <aurora -at- identicloak -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 27 Dec 2005 16:08:55 -0500 (EST)
It seems to me that specialization is the enemy here. With so many
camps fighting to divide up the product, and then justify the
existence of their department, the whole goal of creating a usable
product is lost. This trend is accelerated when the company is
far-removed from the customer, hidden behind layers of sales and
remarketers and third-parties.
The goal alluded to originally in the article does seem a bit far off,
but it will be embraced by companies who want to survive the
onslsaught of inexpensive products from China and India. Why? It
breeds quality, and quality sells. (Look at the iPod.)
Beth Agnew said:
> My experience has been that design IS a discovery process. Unwanted
> discoveries, sometimes, but always discovery as the design moves from
> imagination to concrete form. BAs and RAs/SAs HAD to be involved in
> design to adjust that design as necessary to meet the requirements.
> Design is the process of implementing the specifications that come out
> of requirements analysis. Each phase is a discovery and learning
> process, especially if you're working on something new. Techwriters,
> specialists in communication, also need to be involved in both phases
> that the thoughts, ideas, plans, and visions can be brought out of
> people's heads into a more universally understood form.
> Tony Markos wrote:
>>Analysis is a discovery process; design is not.
>>Business Analysts and Requirements Analysts are a
>>couple of examples of people who do analysis - but not
>>design. In the organizations that I have worked in,
>>BAs and RAs were not part of the design group.
>>Much more important than missed/dropped details in
>>transfer from analyis to design is the problem of
>>short-circuited analysis, which inevitably happens
>>when (true) analysts are under the same management as
>>the design folks.
> Beth Agnew
> Professor, Technical Communication
> Seneca College of Applied Arts & Technology
> Toronto, ON 416.491.5050 x3133
> Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
> Help. And online anything else. Redesigned interface with a new
> project-based workflow. Try it today! http://www.webworks.com/techwr-l
> Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
> content and configure Help in MS Word or any HTML editor. No
> proprietary editor! *August release.
> You are currently subscribed to TECHWR-L as aurora -at- identicloak -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/techwhirl/ for more resources and info.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l