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: Drafts Back in Time From:Lyn Worthen <Lyn -dot- Worthen -at- caselle -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 30 May 2003 12:02:29 -0600
I work with the product (whatever it is) until I get to the point where I
have specific questions to ask the SME. I work directly with the SME on
these questions (usually passing by his/her desk and asking if they have a
minute to clarify something). When I have the chapter/document/whatever
chunk we've agreed on ready, I give it to the SME to review to verify the
accuracy of my interpretation of what I've experienced/discussed with them.
Most of the "big deal" signoff issues I've run into have been instituted
from above, and consist of the requirement to have Development, Sales,
Support, and QA all agree that the document the SME and I have created is
acceptable to those groups. (This can get really ugly if there are
territorial issues between these departments.) I've usually tried to
generate enough of a relationship with the key people in those departments
that I can address their concerns/head off troubles during the document
writing process (treating them like secondary SMEs). It makes life easier.
From: Mike O.
Sent: Friday, May 30, 2003 9:12 AM
I never understood why people get so uptight about reviews.
I suspect (and I am not pointing at any one in particular, so don't
take this personally) that a lot of writers depend on the review
process because they are unsure about the content. They are using the
review cycle as part of their content development process, instead of
as a final sanity check.
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.