<?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: APR: Understanding Our Users</title>
	<atom:link href="http://tynerblain.com/blog/2007/04/19/apr-understanding-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-90880</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 25 Apr 2007 20:21:32 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-90880</guid>
		<description>Hey Chloe, thanks for joining in the discussion!

You make a REALLY good point about user goals.  The statement you quibbled with is almost a description of the solution - where the goal is to gain information.  I&#039;ll definitely keep that in the front of my mind when incorporating different types of information sources - maybe books and other things will get combined with the articles.

Thanks!

ps: And thanks for the encouragement!</description>
		<content:encoded><![CDATA[<p>Hey Chloe, thanks for joining in the discussion!</p>
<p>You make a REALLY good point about user goals.  The statement you quibbled with is almost a description of the solution &#8211; where the goal is to gain information.  I&#8217;ll definitely keep that in the front of my mind when incorporating different types of information sources &#8211; maybe books and other things will get combined with the articles.</p>
<p>Thanks!</p>
<p>ps: And thanks for the encouragement!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chloe Morrow</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-90839</link>
		<dc:creator>Chloe Morrow</dc:creator>
		<pubDate>Wed, 25 Apr 2007 17:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-90839</guid>
		<description>Hmm - second part of my comment got cut off .. so to continue,

I don&#039;t think you are always searching different sources for different reasons. I often find myself doing research when I am having some problem at work and need ideas for solutions. For example, perhaps my projects are suffering because of poor estimations. I&#039;m looking for a solution to that problem, and early in my searching I&#039;m open to whether that solution might be an article, a book, training, a product or whatever. 

Keeping this kind of broader problem definition in mind might evolve your user story from &quot;I want to read about X&quot; to &quot;I want to find out information about X&quot;</description>
		<content:encoded><![CDATA[<p>Hmm &#8211; second part of my comment got cut off .. so to continue,</p>
<p>I don&#8217;t think you are always searching different sources for different reasons. I often find myself doing research when I am having some problem at work and need ideas for solutions. For example, perhaps my projects are suffering because of poor estimations. I&#8217;m looking for a solution to that problem, and early in my searching I&#8217;m open to whether that solution might be an article, a book, training, a product or whatever. </p>
<p>Keeping this kind of broader problem definition in mind might evolve your user story from &#8220;I want to read about X&#8221; to &#8220;I want to find out information about X&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chloe Morrow</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-90832</link>
		<dc:creator>Chloe Morrow</dc:creator>
		<pubDate>Wed, 25 Apr 2007 17:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-90832</guid>
		<description>First, I&#039;m loving the idea of blogging your agile journey for this project! I&#039;m looking forward to reading along.

On the topic of what an &#039;article&#039; is ... I agree that you probably need to pick one type of information source first (like articles) and then move on to the other ones in your list (like books or training). However, I quibble with this comment you made:

&gt;&gt; I’m inclined to treat them differently, because people will look for each for different reasons (I want a to read about X, I want training for Y). </description>
		<content:encoded><![CDATA[<p>First, I&#8217;m loving the idea of blogging your agile journey for this project! I&#8217;m looking forward to reading along.</p>
<p>On the topic of what an &#8216;article&#8217; is &#8230; I agree that you probably need to pick one type of information source first (like articles) and then move on to the other ones in your list (like books or training). However, I quibble with this comment you made:</p>
<p>&gt;&gt; I’m inclined to treat them differently, because people will look for each for different reasons (I want a to read about X, I want training for Y).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-89695</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sun, 22 Apr 2007 16:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-89695</guid>
		<description>Cool.</description>
		<content:encoded><![CDATA[<p>Cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-89666</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Sun, 22 Apr 2007 13:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-89666</guid>
		<description>No objections towards starting with articles at all. This is the internet age.

Reading your reply, Scott, I just realized that &quot;find a book&quot;, &quot;find an outsourcer&quot;, &quot;find a great site&quot;, etc. are solutions to the problem &quot;I want to gain knowledge&quot;.</description>
		<content:encoded><![CDATA[<p>No objections towards starting with articles at all. This is the internet age.</p>
<p>Reading your reply, Scott, I just realized that &#8220;find a book&#8221;, &#8220;find an outsourcer&#8221;, &#8220;find a great site&#8221;, etc. are solutions to the problem &#8220;I want to gain knowledge&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-89424</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sat, 21 Apr 2007 19:48:29 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-89424</guid>
		<description>I think readers have to rate it.  Maybe the person who initially posts the article (to the ratings site) suggests where they think it belongs.  Different people will have different opinions on how to classify it.  I think there&#039;s a way to show that effectively, and will look at some design options for presenting that.

But Tyner Blain will definitely not rate it in an autocratic sense.  Once the site is up, I expect to be a user, not super-user.  I like the way Kevin Rose approached things at digg.  He was just another digger.</description>
		<content:encoded><![CDATA[<p>I think readers have to rate it.  Maybe the person who initially posts the article (to the ratings site) suggests where they think it belongs.  Different people will have different opinions on how to classify it.  I think there&#8217;s a way to show that effectively, and will look at some design options for presenting that.</p>
<p>But Tyner Blain will definitely not rate it in an autocratic sense.  Once the site is up, I expect to be a user, not super-user.  I like the way Kevin Rose approached things at digg.  He was just another digger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-89244</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Sat, 21 Apr 2007 06:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-89244</guid>
		<description>What makes an article suitable introductory material versus deep critical thinking for experts?

Will authors pick? Will readers rate it?With the staff at TB assess it?</description>
		<content:encoded><![CDATA[<p>What makes an article suitable introductory material versus deep critical thinking for experts?</p>
<p>Will authors pick? Will readers rate it?With the staff at TB assess it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-89103</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 20 Apr 2007 15:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-89103</guid>
		<description>Wow, great comments, thanks!  Starting with the second one about &quot;articles.&quot;

Up until now, I&#039;ve been thinking about it solely as collections of (immediately) consumable articles.  From a &quot;how do I write at Tyner Blain?&quot; perspective, I believe the best articles are single topic.  But that isn&#039;t always true, and is definitely just my opinion.

There are a lot of great references that are not consumable articles:
&lt;ul&gt;
	&lt;li&gt;Great books to read&lt;/li&gt;
	&lt;li&gt;Great companies to hire for topic X services&lt;/li&gt;
	&lt;li&gt;Great products for working in field Y&lt;/li&gt;
	&lt;li&gt;Great training in domain Z&lt;/li&gt;
&lt;/ul&gt;
And probably others too.  And all of this stuff is important to all of us who will be using the site.

I&#039;m inclined to treat them differently, because people will look for each for different reasons (I want a to read about X, I want training for Y).  I think we could absolutely leverage some of the functionality we will likely build to make it easy for people to &quot;find great books in our niche&quot; etc.

Do you think it would be effective to present these as top-level activities: &quot;find a book&quot;, &quot;find an outsourcer&quot;, etc, and ask people to prioritize them?  I personally want to do articles first, and then add whatever is most-valued second [ed: this assumes that articles is of more value than the others].  But if one of the other areas dwarfs articles in terms of what people want, then we will reconsider.

At some level, this is like the start of Amazon.  Bezos&#039; team proposed &quot;al l things&quot; in a big vision of what Amazon would ultimately become, and Bezos played the dictator card and said &quot;let&#039;s start with books.&quot;  Then they added the other stuff later, once they established critical mass and credibility.

I&#039;m essentially proposing that &quot;articles&quot; is the right place to start, and we should add others as the community evolves.  But I&#039;m happy to be encouraged to rethink that.</description>
		<content:encoded><![CDATA[<p>Wow, great comments, thanks!  Starting with the second one about &#8220;articles.&#8221;</p>
<p>Up until now, I&#8217;ve been thinking about it solely as collections of (immediately) consumable articles.  From a &#8220;how do I write at Tyner Blain?&#8221; perspective, I believe the best articles are single topic.  But that isn&#8217;t always true, and is definitely just my opinion.</p>
<p>There are a lot of great references that are not consumable articles:</p>
<ul>
<li>Great books to read</li>
<li>Great companies to hire for topic X services</li>
<li>Great products for working in field Y</li>
<li>Great training in domain Z</li>
</ul>
<p>And probably others too.  And all of this stuff is important to all of us who will be using the site.</p>
<p>I&#8217;m inclined to treat them differently, because people will look for each for different reasons (I want a to read about X, I want training for Y).  I think we could absolutely leverage some of the functionality we will likely build to make it easy for people to &#8220;find great books in our niche&#8221; etc.</p>
<p>Do you think it would be effective to present these as top-level activities: &#8220;find a book&#8221;, &#8220;find an outsourcer&#8221;, etc, and ask people to prioritize them?  I personally want to do articles first, and then add whatever is most-valued second [ed: this assumes that articles is of more value than the others].  But if one of the other areas dwarfs articles in terms of what people want, then we will reconsider.</p>
<p>At some level, this is like the start of Amazon.  Bezos&#8217; team proposed &#8220;al l things&#8221; in a big vision of what Amazon would ultimately become, and Bezos played the dictator card and said &#8220;let&#8217;s start with books.&#8221;  Then they added the other stuff later, once they established critical mass and credibility.</p>
<p>I&#8217;m essentially proposing that &#8220;articles&#8221; is the right place to start, and we should add others as the community evolves.  But I&#8217;m happy to be encouraged to rethink that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://tynerblain.com/blog/2007/04/19/apr-understanding-users/comment-page-1/#comment-89049</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Fri, 20 Apr 2007 10:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/19/apr-understanding-users/#comment-89049</guid>
		<description>I like to think of where the users are when they use the product. I&#039;d include in their office, in their home, on their way from A to B, on vacation (uh, that&#039;s almost everywhere).

Somewhat off the personas topic: I&#039;m wondering what an &#039;article&#039; is. Does it have characteristics? Is it just some piece of knowledge (I&#039;d say: yes), or even just a reference to a piece of knowledge?
Is it important that an article is readily accessible from the site (that would exclude training courses, books, ...)? My answer: no, even a hint for a good book or a reputed company would be of help to the personas.</description>
		<content:encoded><![CDATA[<p>I like to think of where the users are when they use the product. I&#8217;d include in their office, in their home, on their way from A to B, on vacation (uh, that&#8217;s almost everywhere).</p>
<p>Somewhat off the personas topic: I&#8217;m wondering what an &#8216;article&#8217; is. Does it have characteristics? Is it just some piece of knowledge (I&#8217;d say: yes), or even just a reference to a piece of knowledge?<br />
Is it important that an article is readily accessible from the site (that would exclude training courses, books, &#8230;)? My answer: no, even a hint for a good book or a reputed company would be of help to the personas.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

