<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Links of Note, June 2009: Technical Writing and Communication</title>
	<atom:link href="http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/</link>
	<description>Content Strategy, Management, and Development</description>
	<lastBuildDate>Wed, 08 Sep 2010 14:35:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Society of Technical Communication Helps Pay Dues for up to 400 Members (Deadline Extended to January 19th) &#171; Technical and Marketing Communication: Content for a Convergent World</title>
		<link>http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/#comment-141</link>
		<dc:creator>Society of Technical Communication Helps Pay Dues for up to 400 Members (Deadline Extended to January 19th) &#171; Technical and Marketing Communication: Content for a Convergent World</dc:creator>
		<pubDate>Mon, 11 Jan 2010 21:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://pegmulligan.com/?p=3636#comment-141</guid>
		<description>[...] Links of Note, June 2009: Technical Writing and Communication  Possibly related posts: (automatically generated)Ask a straight question: have tenders for the Endeavour Wharf site been reo&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Links of Note, June 2009: Technical Writing and Communication  Possibly related posts: (automatically generated)Ask a straight question: have tenders for the Endeavour Wharf site been reo&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peg Mulligan</title>
		<link>http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/#comment-140</link>
		<dc:creator>Peg Mulligan</dc:creator>
		<pubDate>Fri, 10 Jul 2009 14:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://pegmulligan.com/?p=3636#comment-140</guid>
		<description>Hi Anne, I am eagerly awaitng the mid-summer release of your book:
Conversation and Community: The Social Web for Documentation by Anne Gentle:
http://xmlpress.net/publications/conversation-community/

I, too, share your enthusiasm for the social web and the ways it can provide direct access to our audence. I am even more passionate about the ways the social web can assist product development, in the best spirit of the agile methodology.

I&#039;ve already dropped by your excellent blog several times and will continue to read your timely thoughts. Thanks, in the meantime, for dropping by here and for your detailed feedback.  --Peg</description>
		<content:encoded><![CDATA[<p>Hi Anne, I am eagerly awaitng the mid-summer release of your book:<br />
Conversation and Community: The Social Web for Documentation by Anne Gentle:<br />
<a href="http://xmlpress.net/publications/conversation-community/" rel="nofollow">http://xmlpress.net/publications/conversation-community/</a></p>
<p>I, too, share your enthusiasm for the social web and the ways it can provide direct access to our audence. I am even more passionate about the ways the social web can assist product development, in the best spirit of the agile methodology.</p>
<p>I&#8217;ve already dropped by your excellent blog several times and will continue to read your timely thoughts. Thanks, in the meantime, for dropping by here and for your detailed feedback.  &#8211;Peg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: annegentle</title>
		<link>http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/#comment-139</link>
		<dc:creator>annegentle</dc:creator>
		<pubDate>Fri, 10 Jul 2009 05:30:06 +0000</pubDate>
		<guid isPermaLink="false">http://pegmulligan.com/?p=3636#comment-139</guid>
		<description>Thanks Peg, for mentioning my book here. I&#039;d love to hear what you think about whether technical communicators will get the opportunities to get closer to customers after reading my book. One of the premises it builds upon is that for the first time in history we have tools at our disposal that enable us to know our audience better than ever before.

I believe social media can &quot;power up&quot; our efforts to write customer-facing doc, or assist customers in writing doc themselves. This shift likely means tech comm departments will further align with customer support, sales and marketing, or training and education, which may dictate the level of involvement in social media.

What may end up happening is that tech comm&#039;s content will be the most desired and requested content by users. Then, the overarching content strategy will simply have a social media publishing strategy within it.

Who knows what the future holds? It sure is an exciting time to be a technical communicator.</description>
		<content:encoded><![CDATA[<p>Thanks Peg, for mentioning my book here. I&#8217;d love to hear what you think about whether technical communicators will get the opportunities to get closer to customers after reading my book. One of the premises it builds upon is that for the first time in history we have tools at our disposal that enable us to know our audience better than ever before.</p>
<p>I believe social media can &#8220;power up&#8221; our efforts to write customer-facing doc, or assist customers in writing doc themselves. This shift likely means tech comm departments will further align with customer support, sales and marketing, or training and education, which may dictate the level of involvement in social media.</p>
<p>What may end up happening is that tech comm&#8217;s content will be the most desired and requested content by users. Then, the overarching content strategy will simply have a social media publishing strategy within it.</p>
<p>Who knows what the future holds? It sure is an exciting time to be a technical communicator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peg Mulligan</title>
		<link>http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/#comment-138</link>
		<dc:creator>Peg Mulligan</dc:creator>
		<pubDate>Fri, 03 Jul 2009 12:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://pegmulligan.com/?p=3636#comment-138</guid>
		<description>Thanks, Ellis, for the clarification and for the visit here. I respect your thoughts and will revise the inaccuracy in my post.

The hybrid role you mention of trainer, techical support, and editor is already arriving, with the advent of social media. It seems to me that other groups, including marketing, customer support, and professional services, are already starting to use social media to fullfill these merged functions, and that technical communicators, by virtue of where we are placed in the organization (not customer-facing), will lag behind these other disciplines (really as we always have), evolving in this direction.

My view is that technical communicators will continue to write the most technical, back-end docs, for an IT or developer audience, and that the customer-facing doc will more and more be off-loaded to the customer-facing parts of the organization. This has been my experience in small to medium-size companies of late. Larger companies will probably continue to keep some semblance of a centralized technical writing function, even for the customer-facing docs, but to remain viable, technical communicators will need to deliver those docs in formats that users are accustomed to consuming these days (shorter quick reference docs and podcasts, as Tom Johnson suggests, or where applicable, interactive formats).

Part of the reason I am blogging about marketing and technical communication here, is because I see many more of my traditional technical documentation functions in the marketing discipline these days. As far as a hybrid role, I attended a wonderful MarketingProfs webinar on Customer Experience Management, which provides a framework for the kind of merged functions you mention.</description>
		<content:encoded><![CDATA[<p>Thanks, Ellis, for the clarification and for the visit here. I respect your thoughts and will revise the inaccuracy in my post.</p>
<p>The hybrid role you mention of trainer, techical support, and editor is already arriving, with the advent of social media. It seems to me that other groups, including marketing, customer support, and professional services, are already starting to use social media to fullfill these merged functions, and that technical communicators, by virtue of where we are placed in the organization (not customer-facing), will lag behind these other disciplines (really as we always have), evolving in this direction.</p>
<p>My view is that technical communicators will continue to write the most technical, back-end docs, for an IT or developer audience, and that the customer-facing doc will more and more be off-loaded to the customer-facing parts of the organization. This has been my experience in small to medium-size companies of late. Larger companies will probably continue to keep some semblance of a centralized technical writing function, even for the customer-facing docs, but to remain viable, technical communicators will need to deliver those docs in formats that users are accustomed to consuming these days (shorter quick reference docs and podcasts, as Tom Johnson suggests, or where applicable, interactive formats).</p>
<p>Part of the reason I am blogging about marketing and technical communication here, is because I see many more of my traditional technical documentation functions in the marketing discipline these days. As far as a hybrid role, I attended a wonderful MarketingProfs webinar on Customer Experience Management, which provides a framework for the kind of merged functions you mention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellis Pratt</title>
		<link>http://pegmulligan.com/2009/07/02/links-of-note-june-2009-technical-writing-and-communication/#comment-137</link>
		<dc:creator>Ellis Pratt</dc:creator>
		<pubDate>Fri, 03 Jul 2009 08:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://pegmulligan.com/?p=3636#comment-137</guid>
		<description>Actually, I didn&#039;t say technical communicators will be displaced by user-generated content. If technical communicators were to become extinct, I think they would probably be replaced by a new job function - which would be a hybrid of trainer, techical support and editor. Some of the content may well be user generated, but I think there&#039;s still a role for explaining technical stuff to non technical people.
Ellis Pratt, Cherryleaf.</description>
		<content:encoded><![CDATA[<p>Actually, I didn&#8217;t say technical communicators will be displaced by user-generated content. If technical communicators were to become extinct, I think they would probably be replaced by a new job function &#8211; which would be a hybrid of trainer, techical support and editor. Some of the content may well be user generated, but I think there&#8217;s still a role for explaining technical stuff to non technical people.<br />
Ellis Pratt, Cherryleaf.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
