<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Writing&gt;Technical Writing&gt;SMEs</title>	<link>http://tc.eserver.org/dir/Articles/Writing/Technical-Writing/SMEs</link>
	<description>A listing of the most recently indexed works about Articles and Writing and Technical Writing and SMEs in the field of technical communication (and technical writing).</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Writing&gt;Technical Writing&gt;SMEs</title>
		<link>http://tc.eserver.org/dir/Articles/Writing/Technical-Writing/SMEs</link>
	</image>
	<item>
		<title>The Cardinal Rule of Interviewing a Subject Matter Expert (SME) For a Document</title>
		<link>http://tc.eserver.org/34021.html</link>
		<guid>http://tc.eserver.org/34021.html</guid>
		<description>A technical writer will periodically need to interview Subject Matter Experts (SME) to gather information about a technical document.&#xD;&#xD;More often that not, and especially within the context of software development, most SMEs are engineers and software developers. But they can also be mechanical, electrical and other types of engineers, hardware installers, network engineers, testers, site foremen, call center engineers, field technicians, sales or marketing people, local dealers, etc.&#xD;&#xD;One cardinal rule of interviewing an SME is to do your homework well, in advance.</description>
	</item>
	<item>
		<title>Asking Questions is Key</title>
		<link>http://tc.eserver.org/33874.html</link>
		<guid>http://tc.eserver.org/33874.html</guid>
		<description>I think one of the hardest things in technical writing, especially for new hires, is to be assigned to document a product or feature that you know nothing about.</description>
	</item>
	<item>
		<title>Boilerplate</title>
		<link>http://tc.eserver.org/25015.html</link>
		<guid>http://tc.eserver.org/25015.html</guid>
		<description>The SMEs had a choice between two sets of tables they could use to input key product data. If their part of the project used items from the A list, they were supposed to use table A. If their part of the product used items from the B list, they were supposed to use table B. In almost every case, the SMEs used the wrong table, leaving gaps where their information did not conform to the columns of the tables. </description>
	</item>
	<item>
		<title>Technical Writer/Subject Matter Expert Interaction: The Writer&apos;s Perspective, the Organizational Challenge</title>
		<link>http://tc.eserver.org/10415.html</link>
		<guid>http://tc.eserver.org/10415.html</guid>
		<description>Almost a decade ago, Walkowski&apos;s (1991) study of the interaction between subject-matter experts (SMEs) and technical writers focused on the perceptions of software engineers toward technical writers. Her findings gave technical writers insights on how to improve critical relationships with these organizational colleagues. This study partially replicates Walkowski&apos;s (1991) study of technical writer-SME interactions, but instead of collecting data from SMEs, we surveyed technical writers themselves. We report perceptions collected from 31 technical writers and contrast them with Walkowski&apos;s original findings, offering interpersonal and organizational recommendations for addressing tensions between these groups. By examining both the SMEs&apos; and the technical writers&apos; perceptions of their relationship, we are able to provide a two-sided view of a dynamic and complex interaction. We also argue that participants in the SME-technical writer interaction cannot fully alter their relationship without the strategic supp</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Writing/Technical-Writing/SMEs.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>