<?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: Rethinking the Term &#8220;Users&#8221;</title>
	<atom:link href="http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/</link>
	<description>Technical Communication Blog / Technical Writing Blog</description>
	<lastBuildDate>Thu, 18 Mar 2010 07:56:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: lernundenter &#187; Netgeneration - 4 User-Typen</title>
		<link>http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/comment-page-1/#comment-129308</link>
		<dc:creator>lernundenter &#187; Netgeneration - 4 User-Typen</dc:creator>
		<pubDate>Fri, 04 Apr 2008 20:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/#comment-129308</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] findet die vier Bezeichnungen sympathischer als das Wort &#8249;User&#8250;. Dazu der Beitrag Rethinking the Term &#8249;Users&#8250; von &#8249;I&#039;d Rather Be [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] findet die vier Bezeichnungen sympathischer als das Wort &lsaquo;User&rsaquo;. Dazu der Beitrag Rethinking the Term &lsaquo;Users&rsaquo; von &lsaquo;I&#8217;d Rather Be [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tech Writer: &#8220;Someone who writes as opposed to someone who rides something&#8221; &#124; I'd Rather Be Writing</title>
		<link>http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/comment-page-1/#comment-64089</link>
		<dc:creator>Tech Writer: &#8220;Someone who writes as opposed to someone who rides something&#8221; &#124; I'd Rather Be Writing</dc:creator>
		<pubDate>Sun, 28 Oct 2007 21:43:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/#comment-64089</guid>
		<description>[...] not much clearer; plus I don&#8217;t think of myself as a designer. The term &#8220;user&#8221; is also problematic. Still, at least user help designer or something similar would allow us to more freely move outside [...]</description>
		<content:encoded><![CDATA[<p>[...] not much clearer; plus I don&#8217;t think of myself as a designer. The term &#8220;user&#8221; is also problematic. Still, at least user help designer or something similar would allow us to more freely move outside [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet</title>
		<link>http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/comment-page-1/#comment-38033</link>
		<dc:creator>Janet</dc:creator>
		<pubDate>Fri, 27 Jul 2007 17:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/#comment-38033</guid>
		<description>I had a client whose style guide specifically discouraged the use of &quot;user&quot; for the reasons cited in the initial post. When readers of tech documents are IT people, though, you have to admit that &quot;user&quot; is useful.</description>
		<content:encoded><![CDATA[<p>I had a client whose style guide specifically discouraged the use of &#8220;user&#8221; for the reasons cited in the initial post. When readers of tech documents are IT people, though, you have to admit that &#8220;user&#8221; is useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janet Swisher</title>
		<link>http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/comment-page-1/#comment-38030</link>
		<dc:creator>Janet Swisher</dc:creator>
		<pubDate>Fri, 27 Jul 2007 14:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/07/27/rethinking-the-term-users/#comment-38030</guid>
		<description>I&#039;ve been thinking along similar lines lately, and I totally agree. Nobody uses software because they want to use software. They use software because they want to do something that goes beyond software. Even game-players use software because they want to be engaged and entertained. 

&quot;Users&quot; describes people in terms of their relationship to the product. If we avoid that term, we have to talk about people in terms of their roles or goals that they are using the software for. In order to do that, we have to understand who these people are. So, in a way, calling people &quot;users&quot; reveals our failure or laziness in audience analysis. 

I&#039;m taking this post as inspiration to avoid &quot;user&quot; as much as possible from here out. If all else fails, there is &quot;person&quot;, which at least humanizes the discussion a bit more than &quot;user&quot;.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been thinking along similar lines lately, and I totally agree. Nobody uses software because they want to use software. They use software because they want to do something that goes beyond software. Even game-players use software because they want to be engaged and entertained. </p>
<p>&#8220;Users&#8221; describes people in terms of their relationship to the product. If we avoid that term, we have to talk about people in terms of their roles or goals that they are using the software for. In order to do that, we have to understand who these people are. So, in a way, calling people &#8220;users&#8221; reveals our failure or laziness in audience analysis. </p>
<p>I&#8217;m taking this post as inspiration to avoid &#8220;user&#8221; as much as possible from here out. If all else fails, there is &#8220;person&#8221;, which at least humanizes the discussion a bit more than &#8220;user&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
