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.
In my previous posting I mistakenly used
"lossey-gossey" instead of "loosey-goosey". I
--- Tony Markos <ajmarkos -at- yahoo -dot- com> wrote:
> A ways back I asked members of this listserv what
> writing skills are. The general consensus I got was
> that skill in structured writing is the most
> thing. I then did a fair amount of research on
> structured writing and asked the members on this
> listserv what it is. That is were I ran into a big
> Outside of some lossey-gossey sound bites and some
> document formatting considerations (a relatively
> thing), I was unable to identify any specific,
> concrete steps involved in structured writing.
> The best definition of structured writing I got was
> from the man who is generally credited with having
> "invented" it, Charles Horn. On the Infomapping web
> site (Infomapping is just a commercial
> of structured writing), Horn states that, in the
> structured writing is really all about analysis.
> As someone very experienced in structured analysis,
> hearing that structured writing is really all about
> analysis really scrambles my mind. Since it is
> relatively easy to identify the specific, concrete
> steps involved in structured analysis, I conclude
> structured writing is - in the main - some sort of
> less rigorous adaptation of structured analysis.
> If you want your structured writing guidelines to be
> more than formatting standards/guidelines (again, a
> relatively minor thing) and lossey-gossey sound
> then take it from Horn and focus your energies on
> techniques for properly structuring an analysis.
> (Note: Such a focus will also naturally lead you to
> the best flow charting techniques and the best in
> Tony Markos
> --- Nicole Bogdanovic <NICNRADI -at- shaw -dot- ca> wrote:
> > Hello all,
> > I've been asked by our Support Team to help them
> > up a new Knowledge Database and create guidelines
> > for writing/structuring articles.
> > Does anyone have some experience in this area? Can
> > you send me some pointers about what works and
> > doesn't, any recommended reading/resources, tips
> > pitfalls, troubleshooting flowchats, etc?
> > The intended audience is our software end-users
> > (municipal clerical staff mostly, with low to
> > technical knowledge/ability) and our purpose is to
> > help them problem solve on their own.
> > Thanks in advance!
> > ~Nicole.
> Yahoo! DSL ? Something to write home about.
> Just $16.99/mo. or less.
> 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!
> 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
> ajmarkos -at- yahoo -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> Send administrative questions to lisa -at- techwr-l -dot- com -dot-
>http://www.techwr-l.com/techwhirl/ for more
> resources and info.
Yahoo! DSL ? Something to write home about.
Just $16.99/mo. or less.
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