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: Boeing Tech Pubs going offshore? (long) From:Mike Stockman <mstockman -at- mac -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 16 Jun 2003 12:01:23 -0400
On 06/16/2003 9:31 AM, Richard Lippincott (richard -dot- lippincott -at- ae -dot- ge -dot- com)
wrote:
>But we can't assume that it's going to catch the
>critical mistakes, even if we -want- to assume it will. In a way, this is
>just a variation of the old "tech writer's don't need to understand the
>content" argument. In this case "Don't worry if the Chilean writers don't
>know anything about aircraft maintenance procedures. Boeing QA will fix the
>mistakes." The problem in the process may be (as I've experienced in other
>places) when the reviewers just glance over the draft, and don't stop to
>think if what is written actually works.
An excellent post, Richard... I'll just agree with everything you wrote,
and will clarify only the part of my message that you responded to above.
I wasn't saying that their documentation quality will be good because of
their quality control. I was saying that they won't *ship* bad manuals,
because of good quality control. The new writing group, wherever they
are, will either write garbage or quality documents... then Boeing's
quality control prcess will either accept the documents or refuse to use
them. I assume this is true of Boeing because I've never heard anything
bad about their manuals, and planes aren't dropping out of the sky
because of lousy documentation.
And, for the record, I'm a big, big believer in writers needing to be
subject matter experts (SMEs) for everything they write. No exceptions...
you can't write good, complete documentation without knowing the subject
very, very well. If Boeing's writers had been mindlessly quoting SMEs and
acting only as publishers of someone else's expertise, we'd have a lot
more crashes because the docs would suck.
I posted originally to stop the scare tactic of planes crashing (dear
Lord, think of the children!) because Boeing is outsourcing its docs.
Outsourcing does not necessarily lead to poor quality docs... that
happens only if the company allows bad docs to ship. There's nothing
about outsourcing that *must* hurt quality, so planes won't automatically
drop out of the sky because of outsourcing unless Boeing lets other
processes fail.
---
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.