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: Inaccurate Info from SME From:Laurence Burrows <burrows -at- IBM -dot- NET> Date:Thu, 17 Dec 1998 18:03:25 +1100
My question to the list: What do you do when you suspect or even know that
the sme assigned to your project isn't such an expert? What do you do when
the sme gives you inaccurate information? Do you go around/over him to get
what you need, ignoring possible personal insult and/or office
politics/power plays? I'm wondering how any of you would handle the situation.
Submit your single-sided draft to the junior engineer, with your queries
written in 'your' colored ink (green?). Accept only written responses on
the draft, or attached to the draft.
If you have reached a crisis point on a topic, send the 'evidence' to the
senior engineer and ask for comment / amplification.
All this may sound like covering your backside, but written answers require
more consideration and are usually more likely to elicit real thought
compared to verbal responses. Also, it takes less time than you may think,
especially if you are working on several parallel topics / products at once.