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.
Geoff;
I agree whole-heartedly with you on dealing with engineers, although I
would like to add this:
I have found through experience that a large porportion of engineers
have difficulty in taking technical writers and technical writing seriously
at first. Whether this is as a result of the abbreviated and somewhat
incomplete technical writing courses that are a part of their curriculum or
whether they just don't believe that the average technical writer has the
experience or the education to understand what they do.
However, I have also found that being thoughtful in my approach to an
engineer, by taking the time to ask intelligent questions and by taking
their answers seriously helps to alleviate their uncertainties about me.
They are naturally hesitant to grant that someone who is not an engineer
will understand something that isn't finished and that the engineer doesn't
properly understand yet, either. Generally I find that after only a few
weeks of dealing with an engineer this way results in the engineer placing
faith in my skills to understand what he/she is doing, why he/she is doing
it and just what he/she is doing will do. If we take care to make sure that
we understand what the engineer has designed to by asking thoughtful,
intelligent and relevant questions, they begin to place a little faith in
our abilities, and that makes our job that much more difficult.
The worst thing we can do in give the engineer the impression that we
don't know what we're doing and that we're not willing to learn.
Best Regards
Paul Cheverie
paul -dot- cheverie -at- canada -dot- cdev -dot- com