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.
<Do your job to the best of your ability. That's what you are paid
<for. What you AREN'T paid for is to approve/disapprove what
<Why don't you wait until you come up with a reason why it is bad and
<then speak with YOUR management, not just assume it is.
Actually, I have spoke with management about it. They agreed with me, but
the president insists on her approval/proofing. She is a very detailed
person so that is the only positive aspect I can come up with, and, of
course, fresh eyes.
The reason I think it is bad is because it slows down the process of
review. By the time the software is done, the manuals are still in the
hands of the exec. asst. She is very bogged down.
We are in the process of creating a style guide for the company. The first
manual she proofed of mine, she suggested that I change the left
justification to full justification except the text next to graphics. My
boss of our division asked me why I preferred left justification, and is
business correspondence standards separate from technical writing. I
recently submitted a report justifiying (!) my background, my degree, the
opinion of the technical writers in this company as a group, and I also
included references from other sources to prove that I wasn't just picking
style and justification because I think it is pretty.
Yes, you are right - she does represent the vice president. As to what
issues that could come up in the manual that I don't know about, I am not
sure. From what I understand, the vice president and president are more
involved in sales than the technical subject matter of the software?
<jposada01 -at- yahoo -dot- com> To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent by: cc:
bounce-techwr-l-81152 -at- lists -dot- r Subject: Re: Secretary Proofing Manuals?
10/24/2001 04:20 PM
Please respond to John Posada
> In fact, we have to start including her in our style meetings as
> well. Am I just being egotistical?
Yes, you are
> The executive assistant doesn't have any control over the software
> so why
> should she have any control over the manuals? They are products
> just as well.
The executive assistant is the eyes of the executive. She might be
instructed to watch out for issues that you have no interest in and
maybe no uthorization to be aware of.
The executive she represents might be too busy to have his/her hands
in everything, but still want to know about them. Sometimes there are
issues bigger than the document and bigger than you (or I) are
allowed to be in on.
Do your job to the best of your ability. That's what you are paid
for. What you AREN'T paid for is to approve/disapprove what
Why don't you wait until you come up with a reason why it is bad and
then speak with YOUR management, not just assume it is.
Announcing new options for IPCC 01, October 24-27 in Santa Fe,
New Mexico: attend the entire event or select a single day.
For details and online registration, visit http://ieeepcs.org/2001
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.