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.
Don't you always check your technical accuracy
with an engineer/developer?
>><every time. every single time. but the engineer flamed me because the
quality of the paper was not up to snuff. when DO you check for technical
accuracy? at the end of the project, right before publication, or during the
development of the content? i'm for during development, but...>
Do you always have 100% accuracy or close to
when you do your content review? Or... Is it because you did not check
until the "final" was together and you should have been asking
for content review back when you "scraped together" some information?
>><this is was the intent of the review. we were nowhere near final.>
it was very clear it was a work in progress, with questions and comments in
the rev marks>
If you did not have the time to do the job correctly, why did you
agree to do it in the first place? Why could you not "schedule" some
time for the Marketing group, if you wanted to or were required to
help them with the gathering of the technical content for the white
paper?
>><this was one of the lessons learned. never start without a schedule that
guesstimates how long things will take. it was pitched to me as a "quick
review" which was all i agreed to. turns out much more was needed.>
If that was not possible, then you needed to tell them that you could
not spare the time to do the project correctly, and therefore would
not be able to help them.
>><also on the list of lessons learned. trying to help out is not always the
best solution, if you can't REALLY help.>
If you approach something with a half-*@&# kind of attitude, what else can
you expect to get out of it?
>><indeed. i don't think it was my attitude, which was more like - we'll
pitch what we can to marketing and they'll take it from there... it was that
my primary responsibilities had to take precedence and this project kept
getting shelved.>
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available 4/30/01 at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
---
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.
