STC Toronto Logo
STC Communication Times Logo
STC Toronto - Communication Times
March 2005

In the March 2005 Newsletter:

The e-mail part of the newsletter consists of the News and Events section. All links to other articles below will take you to our website.

News and Events:
-Single Sourcing SIG Meeting on March 17
-Nominations wanted for Rennie Charles Award.
-Rochester STC Conference coming in April.
-New Certification in Editing Planned
-CIHR Health Communication Awards
-Important Reminder to Renewing STC Members

February Meeting Report: Selling Technical Communication
Susan Webb reports on Barry Clegg's insightful and funny presentation at this year's Wine & Cheese.

Emphasis on Success
Last month's speaker Barry Clegg offers peculiar insights into the writing of management reports...

A Writer's World: Interviewing and Dating: A Single Source Solution
Andrew Brooke simplifies his business and personal life with Single Sourcing...

Becoming a Technical Writer in Germany
Maj-Brit Mammitzsch, a German technical writer who recently completed an internship in Canada, gives an overview of how technical communication is taught in Germany.

The Wandering Eye: Framescript
Keith Soltys talks about FrameScript, a powerful scripting tool for FrameMaker.

Training the Ones Who Train Us
Lilli Dailide of Front-Runner writes that trainers need training too...

This newsletter is sponsored by
Front Runner Publishing Solutions
Don't miss Lilli Dailide's Training Article in this month's newsletter.



About the STC:

The Society for Technical Communication is an individual membership organization dedicated to advancing the arts and sciences of technical communication. It is the largest organization of its type in the world. Its 25,000 members include technical writers and editors, content developers, documentation specialists, technical illustrators, instructional designers, academics, information architects, usability and human factors professionals, visual designers, Web designers and developers, and translators - anyone whose work makes technical information available to those who need it.

The STC Toronto Chapter was founded in 1959 (then the Society of Technical Writers) and is the largest chapter in Canada.

About this Newsletter:

This newsletter is produced monthly by the STC Toronto Chapter and is sent to all registered members. If you have any feedback or ideas, please e-mail editor Philip Kahn at: newsletter@stctoronto.org

Our mailing list comes directly from the STC, so if you want to receive the newsletter at another address you will need to login to their members profile section and update your information. The STC Toronto Chapter will not share nor sell our address list and will only send e-mails with information we believe to be useful and relevant to our members.


Emphasis on Success
by Barry Clegg

One of the hardiest products to emerge from the long evolution of business practices in the Western world is the Management Report. This is a document widely used to pump periodic accounts of departmental activities outward and upward through the management structure. It serves also to reassure readers that you (the author) are still alive, gainfully employed, and making progress.

Because of the stresses and uncertainties inherent in office life, many senior managers have developed a highly refined appreciation for Good News. As a writer of Management Reports it will be to your advantage to bear this in mind. While admittedly not everything which occurs in the business environment actually works to the general corporate advantage, you will be wise to find a way of making it seem so.

If you suspect your talents for writing Management Reports do not do justice to your other managerial skills, you will be interested in the following guidelines.

  • The events reported, no matter how regrettable in reality, must appear in an encouraging light. For example, rather than admit your computer’s hard disk failed and a month's data was lost, write: A hard disk failure confirmed the importance of our backup procedures. (This incontestable statement says nothing about whether the procedures were followed.)

  • Likewise, projects must not be late. Reschedule them, postpone them, defer them, or cancel them by mutual agreement with the client, but never let them be late.

  • Do not drop into a too simple style, or credibility will suffer. For example, Current work is involved with determination and finalization of the system requirements simply means We're trying to decide what to do - but how much grander it sounds!

  • Change Holding weekly meetings to Continuing ongoing meetings on a weekly basis. Generally speaking, seven words are better than three.

  • Double your value from an event by mentioning it twice - in anticipation (progressing towards scheduled completion), and later as an actual occurrence (completed as planned).

  • Use statistics to advantage: find some numbers to report on, no matter how insignificant, in order to enhance your reputation for precision and attention to detail. Append a bar chart to demonstrate your command of technology.

  • Bad news if inescapable should be presented in the obscurantist style of Pentagon announcements. Again, for the defective hard disk, consider: Electro-mechanical failure of the fixed disk storage medium in our personal computing hardware resulted in logical inaccessibility of the previous period's statistical history. Notice how the barrage of forceful words (electro-mechanical, fixed, hardware, logical, statistical) deflects attention away from failure and inaccessibility.

  • When the events you are reporting on prove irredeemably disappointing, take the opportunity to give a subordinate an enriching experience. Explain first the significance of Management Reports and writing skills; then delegate.

  • Humour: there is no room for humour in a Management Report.

A Professional Engineer with a BA from Cambridge and an MSc in Solid Mechanics from Aston University (don’t ask!), Barry spent 30 years in IT development and management. He now works as a freelance communicator.

Barry has written articles (serious and less than serious) for in-house & external publication - in user manuals, technical documentation, reports, newsletters, websites, conference papers, speeches, skits, poetry, & a coffee-table book.