<?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: Use Case Briefs</title>
	<atom:link href="http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/</link>
	<description>Software product success.</description>
	<lastBuildDate>Tue, 22 May 2012 20:46:27 +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/24/apr-use-case-briefs/comment-page-1/#comment-91661</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 27 Apr 2007 16:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-91661</guid>
		<description>Maybe we should use my picture :)</description>
		<content:encoded><![CDATA[<p>Maybe we should use my picture :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-91624</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Fri, 27 Apr 2007 15:36:56 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-91624</guid>
		<description>I think Eddy the Editor will come to life as a reincarnation of you, Scott :-D
Seriously maybe there have to be a couple of blokes who do clean-up. Time will tell, I wouldn&#039;t include Eddy as of now.</description>
		<content:encoded><![CDATA[<p>I think Eddy the Editor will come to life as a reincarnation of you, Scott :-D<br />
Seriously maybe there have to be a couple of blokes who do clean-up. Time will tell, I wouldn&#8217;t include Eddy as of now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-91602</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 27 Apr 2007 15:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-91602</guid>
		<description>In reply to Rolf&#039;s suggestions...

On favorites - very cool.  I imagine a &quot;my rated articles&quot; page for users.  This will serve as the first &quot;favorites&quot; page, and will encourage people to rate articles.  Will evolve as it grows (and as people&#039;s lists grow).

Good points about searching.  I think that is the mandatory first thing to implement, and the mashups will improve the &quot;learn something new&quot; use case.

I like Eddie The Editor.  Basically the guy who gets a per-article feed from wikipedia on his topic of expertise and polices the article for errors.  He&#039;s definitely a guy we want here!  The question is, is he a guy we will actually have here?  I don&#039;t know if we should include him as &quot;wishful thinking.&quot;

Also - great point about &quot;dead links.&quot;  I think that will be an nth-order problem to resolve relative to other functionality, but thanks for putting it on the stack.

Rating the reviews/comments does seem to have a lot of support :)  It will definitely happen - maybe not in the first release</description>
		<content:encoded><![CDATA[<p>In reply to Rolf&#8217;s suggestions&#8230;</p>
<p>On favorites &#8211; very cool.  I imagine a &#8220;my rated articles&#8221; page for users.  This will serve as the first &#8220;favorites&#8221; page, and will encourage people to rate articles.  Will evolve as it grows (and as people&#8217;s lists grow).</p>
<p>Good points about searching.  I think that is the mandatory first thing to implement, and the mashups will improve the &#8220;learn something new&#8221; use case.</p>
<p>I like Eddie The Editor.  Basically the guy who gets a per-article feed from wikipedia on his topic of expertise and polices the article for errors.  He&#8217;s definitely a guy we want here!  The question is, is he a guy we will actually have here?  I don&#8217;t know if we should include him as &#8220;wishful thinking.&#8221;</p>
<p>Also &#8211; great point about &#8220;dead links.&#8221;  I think that will be an nth-order problem to resolve relative to other functionality, but thanks for putting it on the stack.</p>
<p>Rating the reviews/comments does seem to have a lot of support :)  It will definitely happen &#8211; maybe not in the first release</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-91600</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 27 Apr 2007 14:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-91600</guid>
		<description>Sorry about the posting problems, Rolf!  Our spam-filter caught you.  I &quot;de-spammed&quot; both of your comments so that it will learn, and not happen in the future.

For anyone else who sees a comment &quot;dissappear&quot; after submitting it - PLEASE send me an email when this happens.  Your comment may have gone into the moderation queue (might be spam), which I will definitely find.  Or it may have gone into Akismet&#039;s spam-bucket, along with a couple hundred spam-comments per day.  I WILL NOT FIND IT in that mess if you don&#039;t let me know.</description>
		<content:encoded><![CDATA[<p>Sorry about the posting problems, Rolf!  Our spam-filter caught you.  I &#8220;de-spammed&#8221; both of your comments so that it will learn, and not happen in the future.</p>
<p>For anyone else who sees a comment &#8220;dissappear&#8221; after submitting it &#8211; PLEASE send me an email when this happens.  Your comment may have gone into the moderation queue (might be spam), which I will definitely find.  Or it may have gone into Akismet&#8217;s spam-bucket, along with a couple hundred spam-comments per day.  I WILL NOT FIND IT in that mess if you don&#8217;t let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-91453</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Fri, 27 Apr 2007 08:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-91453</guid>
		<description>Sorry if this comment appears several times, I have problems posting it.

Browse an Area:
Answer: I don&#039;t think our niche is so dynamic or focused that I need to know about things just after they happened. I can live without a &quot;what&#039;s hot?&quot; feature. I suggest that an 1-click way for individual users to use links to what they need most frequently (&quot;favorites&quot;).

Search for a Topic:
This also concerns the &quot;kind&quot; of article, like &quot;overview&quot;, &quot;10 most helpful hints&quot; or &quot;impact of A on B&quot;. If I was new to a topic, I&#039;d probably start with some overviewish articles.

Rate an Article:
On recategorization: Maybe we have another persona here, Eddy the Editor. He corrects spelling errors, merges synonym categories, and cares about under-categorized articles.
Thought: what happens with changed links or delete articles?

Comment on an Article:
Thought: &quot;Was this comment useful?&quot; helps with sorting the comments for display.

Suggest An Article:
On forcing the users to rate: maybe yes, in order reach a critical mass of idicators for relevance, what would support finding useful articles.</description>
		<content:encoded><![CDATA[<p>Sorry if this comment appears several times, I have problems posting it.</p>
<p>Browse an Area:<br />
Answer: I don&#8217;t think our niche is so dynamic or focused that I need to know about things just after they happened. I can live without a &#8220;what&#8217;s hot?&#8221; feature. I suggest that an 1-click way for individual users to use links to what they need most frequently (&#8220;favorites&#8221;).</p>
<p>Search for a Topic:<br />
This also concerns the &#8220;kind&#8221; of article, like &#8220;overview&#8221;, &#8220;10 most helpful hints&#8221; or &#8220;impact of A on B&#8221;. If I was new to a topic, I&#8217;d probably start with some overviewish articles.</p>
<p>Rate an Article:<br />
On recategorization: Maybe we have another persona here, Eddy the Editor. He corrects spelling errors, merges synonym categories, and cares about under-categorized articles.<br />
Thought: what happens with changed links or delete articles?</p>
<p>Comment on an Article:<br />
Thought: &#8220;Was this comment useful?&#8221; helps with sorting the comments for display.</p>
<p>Suggest An Article:<br />
On forcing the users to rate: maybe yes, in order reach a critical mass of idicators for relevance, what would support finding useful articles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-91450</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Fri, 27 Apr 2007 08:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-91450</guid>
		<description>Browse an Area:
Answer: I don&#039;t think our niche is so dynamic or focused that I need to know about things just after they happened. I can live without a &quot;what&#039;s hot?&quot; feature. I suggest that an 1-click way for individual users to use links to what they need most frequently (&quot;favorites&quot;).

Search for a Topic:
This also concerns the &quot;kind&quot; of article, like &quot;overview&quot;, &quot;10 most helpful hints&quot; or &quot;impact of A on B&quot;. If I was new to a topic, I&#039;d probably start with some overviewish articles.

Rate an Article:
On recategorization: Maybe we have another persona here, Eddy the Editor. He corrects spelling errors, merges synonym categories, and cares about under-categorized articles.
Thought: what happens with changed links or delete articles?

Comment on an Article:
Thought: &quot;Was this comment useful?&quot; helps with sorting the comments for display.

Suggest An Article:
On forcing the users to rate: maybe yes, in order reach a critical mass of idicators for relevance, what would support finding useful articles.</description>
		<content:encoded><![CDATA[<p>Browse an Area:<br />
Answer: I don&#8217;t think our niche is so dynamic or focused that I need to know about things just after they happened. I can live without a &#8220;what&#8217;s hot?&#8221; feature. I suggest that an 1-click way for individual users to use links to what they need most frequently (&#8220;favorites&#8221;).</p>
<p>Search for a Topic:<br />
This also concerns the &#8220;kind&#8221; of article, like &#8220;overview&#8221;, &#8220;10 most helpful hints&#8221; or &#8220;impact of A on B&#8221;. If I was new to a topic, I&#8217;d probably start with some overviewish articles.</p>
<p>Rate an Article:<br />
On recategorization: Maybe we have another persona here, Eddy the Editor. He corrects spelling errors, merges synonym categories, and cares about under-categorized articles.<br />
Thought: what happens with changed links or delete articles?</p>
<p>Comment on an Article:<br />
Thought: &#8220;Was this comment useful?&#8221; helps with sorting the comments for display.</p>
<p>Suggest An Article:<br />
On forcing the users to rate: maybe yes, in order reach a critical mass of idicators for relevance, what would support finding useful articles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-90882</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 25 Apr 2007 20:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-90882</guid>
		<description>Also - I think requiring someone to be logged in to comment should take care of the spam problem.  And down the road, there may even be a way to incorporate Akismet (the spam blocker for comments on this blog) into the site.</description>
		<content:encoded><![CDATA[<p>Also &#8211; I think requiring someone to be logged in to comment should take care of the spam problem.  And down the road, there may even be a way to incorporate Akismet (the spam blocker for comments on this blog) into the site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-90881</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 25 Apr 2007 20:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-90881</guid>
		<description>Hey Chloe, thanks again for helping with the evolution of the ideas for the project!

Great point about not requiring people to rate before commenting.  You&#039;ve convinced me :).  Also - some great suggestions about ways to rate the articles with metrics other than explicit ratings.

I&#039;ve also been thinking about some way to &quot;weight&quot; the ratings people give based on the credibility of the person making the statement about the article - for example, if people tend to make similar ratings as you, your opinion is more credible.  Not sure how to do this so that it doesn&#039;t become a group-think exercise.  Will be a fun math problem.  Or maybe just a presentation challenge - putting stars next to keep contributors or &quot;thought leaders&quot; (whatever that means).</description>
		<content:encoded><![CDATA[<p>Hey Chloe, thanks again for helping with the evolution of the ideas for the project!</p>
<p>Great point about not requiring people to rate before commenting.  You&#8217;ve convinced me :).  Also &#8211; some great suggestions about ways to rate the articles with metrics other than explicit ratings.</p>
<p>I&#8217;ve also been thinking about some way to &#8220;weight&#8221; the ratings people give based on the credibility of the person making the statement about the article &#8211; for example, if people tend to make similar ratings as you, your opinion is more credible.  Not sure how to do this so that it doesn&#8217;t become a group-think exercise.  Will be a fun math problem.  Or maybe just a presentation challenge &#8211; putting stars next to keep contributors or &#8220;thought leaders&#8221; (whatever that means).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chloe Morrow</title>
		<link>http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/comment-page-1/#comment-90864</link>
		<dc:creator>Chloe Morrow</dc:creator>
		<pubDate>Wed, 25 Apr 2007 18:25:30 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/04/24/apr-use-case-briefs/#comment-90864</guid>
		<description>Some thoughts on commenting &amp; rating of articles:

I&#039;m not sure it is in your best interest to require a person to rate an article before commenting. For some people, there is a level of stress associating with &#039;grading&#039; an article. They may feel more comfortable leaving a qualitative comment rather than a rating. If you require someone rate an article first, they may not bother with the commenting, and the site looses a potentially valuable contribution. Alternatively - you could look at some softer kinds of rating systems like ability to flag an article as &#039;tried this and it worked&#039; or &#039;tried this and it didn&#039;t work&#039; or something like that.

To ensure you still have a way to figure out which are the &#039;best&#039; articles if you don&#039;t require rating, you could use a combination of statistics.
For example - how many times the article was read, how many comments, how many ratings (good or bad). I probably would want to read an article that had alot of comments associated with it - even if the comments were negative or mixed, because obviously there is something to be learned (an idea to stay away from for example) if alot of people felt inspired to comment on it.

Finally (sorry for the long ramble) are users rating the article .. or the topic of the Article ? If the article is on some agile development technique, are users rating the article poorly because the article is poorly written and doesn&#039;t help you to understand how to use the technique or because they think the technique itself is a bad idea. Perhaps it doesn&#039;t matter - but maybe something to think about.</description>
		<content:encoded><![CDATA[<p>Some thoughts on commenting &amp; rating of articles:</p>
<p>I&#8217;m not sure it is in your best interest to require a person to rate an article before commenting. For some people, there is a level of stress associating with &#8216;grading&#8217; an article. They may feel more comfortable leaving a qualitative comment rather than a rating. If you require someone rate an article first, they may not bother with the commenting, and the site looses a potentially valuable contribution. Alternatively &#8211; you could look at some softer kinds of rating systems like ability to flag an article as &#8216;tried this and it worked&#8217; or &#8216;tried this and it didn&#8217;t work&#8217; or something like that.</p>
<p>To ensure you still have a way to figure out which are the &#8216;best&#8217; articles if you don&#8217;t require rating, you could use a combination of statistics.<br />
For example &#8211; how many times the article was read, how many comments, how many ratings (good or bad). I probably would want to read an article that had alot of comments associated with it &#8211; even if the comments were negative or mixed, because obviously there is something to be learned (an idea to stay away from for example) if alot of people felt inspired to comment on it.</p>
<p>Finally (sorry for the long ramble) are users rating the article .. or the topic of the Article ? If the article is on some agile development technique, are users rating the article poorly because the article is poorly written and doesn&#8217;t help you to understand how to use the technique or because they think the technique itself is a bad idea. Perhaps it doesn&#8217;t matter &#8211; but maybe something to think about.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

