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:"Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 27 Dec 2005 13:33:14 -0500
OK, so far we've established that in Bill's experience, analysis and
design are *never* separated, whereas in Tony's experience, they
We might possibly conclude that there is more than one correct way to
get from point A to point B. If so, perhaps the only error here is the
use of the word "inevitably."
-- Dan Goldstein
> -----Original Message-----
> From: Tony Markos
> Sent: Tuesday, December 27, 2005 1:25 PM
> To: Bill Swallow
> Cc: TECHWR-L
> Subject: Re: Don Norman on Manual Writing
> 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 analysis to design is the problem of
> short-circuited analysis, which inevitably happens
> when (true) analysts are under the same management as
> the design folks.
> Tony Markos
> --- Bill Swallow wrote:
> > When would analysis and design be separate?
> > Every company I've worked or consulted for had both
> > efforts within a
> > project team. Spreading them out to separate groups
> > proved to be
> > costly as the analysis work didn't have direct
> > insight into design and
> > vice versa. The results of separate efforts were
> > missed details and
> > detached/disassociated/otherwise less than ideal
> > results.
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
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