<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Me too - dumping the word user</title>
	<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user</link>
	<description>Information architecture, interaction design and much more</description>
	<pubDate>Tue, 07 Oct 2008 16:18:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Todd</title>
		<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-655</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Fri, 23 Jun 2006 00:16:29 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-655</guid>
		<description>Cheers to reclaiming rather than junking the word, Chris. I think for myself it boils down to the fact that 'user' is often too general for the projects I work on, and rather than define it over and over I just name the roles in play and run with them. For those purposes, 'user' comes in handy when I need to quickly point to a pre-defined set of roles in play.
</description>
		<content:encoded><![CDATA[<p>Cheers to reclaiming rather than junking the word, Chris. I think for myself it boils down to the fact that &#8216;user&#8217; is often too general for the projects I work on, and rather than define it over and over I just name the roles in play and run with them. For those purposes, &#8216;user&#8217; comes in handy when I need to quickly point to a pre-defined set of roles in play.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna Maurer</title>
		<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-654</link>
		<dc:creator>Donna Maurer</dc:creator>
		<pubDate>Thu, 22 Jun 2006 12:30:53 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-654</guid>
		<description>Todd, I could see that member would work well. Clearly defines which person you are about and keeps you focused - member is a much more tightly connected concept than user.

Chris - I had the same trouble with 'staff'. I was going to include it in my list then remembered how tricky it was. Managers don't want to be staff, developers are staff but aren't who we are usually talking about etc etc
</description>
		<content:encoded><![CDATA[<p>Todd, I could see that member would work well. Clearly defines which person you are about and keeps you focused - member is a much more tightly connected concept than user.</p>
<p>Chris - I had the same trouble with &#8217;staff&#8217;. I was going to include it in my list then remembered how tricky it was. Managers don&#8217;t want to be staff, developers are staff but aren&#8217;t who we are usually talking about etc etc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris McLay</title>
		<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-653</link>
		<dc:creator>Chris McLay</dc:creator>
		<pubDate>Thu, 22 Jun 2006 00:27:14 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-653</guid>
		<description>I agree with the sentiment, but I don't think the solution is a new word - there isn't really a new word:

&gt; user noun: customer, consumer, client; operator.

In some cases you can use a more generic term (client, member etc.), but even these are problematic. In a recent project we used "staff member" instead of user, but this then got confusing when trying to differentiate between staff members using the product, and staff members nearby. One question that came up, "Are managers who use the product 'staff members'?". It also implied that *all* staff members were users which they were not. Switching back to the term user made everything make sense again.

I think the solution is broader, and is probably more about how we approach the task of designing, than what terminology we use. Let's reclaim the term rather than make it more obscure...
</description>
		<content:encoded><![CDATA[<p>I agree with the sentiment, but I don&#8217;t think the solution is a new word - there isn&#8217;t really a new word:</p>
<p>> user noun: customer, consumer, client; operator.</p>
<p>In some cases you can use a more generic term (client, member etc.), but even these are problematic. In a recent project we used &#8220;staff member&#8221; instead of user, but this then got confusing when trying to differentiate between staff members using the product, and staff members nearby. One question that came up, &#8220;Are managers who use the product &#8217;staff members&#8217;?&#8221;. It also implied that *all* staff members were users which they were not. Switching back to the term user made everything make sense again.</p>
<p>I think the solution is broader, and is probably more about how we approach the task of designing, than what terminology we use. Let&#8217;s reclaim the term rather than make it more obscure&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-652</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Wed, 21 Jun 2006 17:58:36 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-652</guid>
		<description>For all of our Ma.gnolia spec docs we use the word member (and visitor for non-members using the site). This only works because we use a membership model, but it does remind us that these people use our service at their discretion, and that they can leave at any time. It also reminds us that they took the time to engage with us, to sign up, and so forth, and that we owe them attention as individuals.
</description>
		<content:encoded><![CDATA[<p>For all of our Ma.gnolia spec docs we use the word member (and visitor for non-members using the site). This only works because we use a membership model, but it does remind us that these people use our service at their discretion, and that they can leave at any time. It also reminds us that they took the time to engage with us, to sign up, and so forth, and that we owe them attention as individuals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donna Maurer</title>
		<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-651</link>
		<dc:creator>Donna Maurer</dc:creator>
		<pubDate>Wed, 21 Jun 2006 13:56:23 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-651</guid>
		<description>Yes, that could work &#038; differentiates that person from other persons ;)
</description>
		<content:encoded><![CDATA[<p>Yes, that could work &#038; differentiates that person from other persons <img src='http://maadmob.net/donna/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vanderwal</title>
		<link>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-650</link>
		<dc:creator>vanderwal</dc:creator>
		<pubDate>Wed, 21 Jun 2006 13:54:54 +0000</pubDate>
		<guid>http://maadmob.net/donna/blog/2006/me-too-dumping-the-word-user#comment-650</guid>
		<description>I have been replacing user with "person using".  I is not as nice and neat as user, but it is working much better.
</description>
		<content:encoded><![CDATA[<p>I have been replacing user with &#8220;person using&#8221;.  I is not as nice and neat as user, but it is working much better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
