<?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 for Brian Hoadley | Digital Optimist</title>
	<atom:link href="http://www.brianhoadley.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brianhoadley.com</link>
	<description>Brian Hoadley, Digital, UX, Writing, Thinking</description>
	<lastBuildDate>Tue, 15 Nov 2011 18:28:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Whatever happened to discovery? by Brian Hoadley</title>
		<link>http://www.brianhoadley.com/2011/11/15/whatever-happened-to-discovery/#comment-79</link>
		<dc:creator>Brian Hoadley</dc:creator>
		<pubDate>Tue, 15 Nov 2011 18:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/?p=870#comment-79</guid>
		<description>Mike - I think content, in many ways, is still king. I do believe search has reduced the potential for discovery. And as far as information being pre-filtered by your network, this may be the case with respect to social sites, but beyond social, people are mostly searching vs. browsing, which goes back to my point of reduced focus on discovery.</description>
		<content:encoded><![CDATA[<p>Mike &#8211; I think content, in many ways, is still king. I do believe search has reduced the potential for discovery. And as far as information being pre-filtered by your network, this may be the case with respect to social sites, but beyond social, people are mostly searching vs. browsing, which goes back to my point of reduced focus on discovery.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Whatever happened to discovery? by Mike</title>
		<link>http://www.brianhoadley.com/2011/11/15/whatever-happened-to-discovery/#comment-78</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 15 Nov 2011 17:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/?p=870#comment-78</guid>
		<description>Perhaps content is still king? I don&#039;t think search has replaced discovery. Discovery happens when information is pre-filtered by your network, you never know what you&#039;re going to stumble across.</description>
		<content:encoded><![CDATA[<p>Perhaps content is still king? I don&#8217;t think search has replaced discovery. Discovery happens when information is pre-filtered by your network, you never know what you&#8217;re going to stumble across.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Prototyping as an ethos by Interesting elsewhere &#8211; 28 September 2011 &#124; Public Strategist</title>
		<link>http://www.brianhoadley.com/2011/09/23/prototyping-as-an-ethos/#comment-57</link>
		<dc:creator>Interesting elsewhere &#8211; 28 September 2011 &#124; Public Strategist</dc:creator>
		<pubDate>Wed, 28 Sep 2011 13:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/blog/?p=660#comment-57</guid>
		<description>[...] Prototyping as an ethos &#124; Brian Hoadley So if we take our responsibility seriously, why don’t our clients? Why do they so often try to cut corners, cut out research and prototyping, shudder at the idea of iteration (which will equal cost now but provide potential benefit later), and railroad us down an agile path that promises iteration, but so often delivers linear, scaled-back development with no opportunity to evolve already built functionality?Prototyping and testing gives you a real opportunity to test, iterate and re-test. It allows teams to incorporate learnings (other than their own) so that the end results more closely resemble the type of result that users might actually find useful. [...] </description>
		<content:encoded><![CDATA[<p>[...] Prototyping as an ethos | Brian Hoadley So if we take our responsibility seriously, why don’t our clients? Why do they so often try to cut corners, cut out research and prototyping, shudder at the idea of iteration (which will equal cost now but provide potential benefit later), and railroad us down an agile path that promises iteration, but so often delivers linear, scaled-back development with no opportunity to evolve already built functionality?Prototyping and testing gives you a real opportunity to test, iterate and re-test. It allows teams to incorporate learnings (other than their own) so that the end results more closely resemble the type of result that users might actually find useful. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on No Virginia… you are NOT the user by Prototyping as an ethos &#124; Brian Hoadley</title>
		<link>http://www.brianhoadley.com/2011/09/04/no-virginia%e2%80%a6-you-are-not-the-user/#comment-56</link>
		<dc:creator>Prototyping as an ethos &#124; Brian Hoadley</dc:creator>
		<pubDate>Fri, 23 Sep 2011 16:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/blog/?p=628#comment-56</guid>
		<description>[...] you a real opportunity to test, iterate and re-test. It allows teams to incorporate learnings (other than their own) so that the end results more closely resemble the type of result that users might actually find [...] </description>
		<content:encoded><![CDATA[<p>[...] you a real opportunity to test, iterate and re-test. It allows teams to incorporate learnings (other than their own) so that the end results more closely resemble the type of result that users might actually find [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile as the process by Prototyping as an ethos &#124; Brian Hoadley</title>
		<link>http://www.brianhoadley.com/2011/05/20/agile-as-the-process/#comment-48</link>
		<dc:creator>Prototyping as an ethos &#124; Brian Hoadley</dc:creator>
		<pubDate>Fri, 23 Sep 2011 10:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://digitaloptimist.com/?p=403#comment-48</guid>
		<description>[...] iteration (which will equal cost now but provide potential benefit later), and railroad us down an agile path that promises iteration, but so often delivers linear, scaled-back development with no opportunity to evolve already built [...] </description>
		<content:encoded><![CDATA[<p>[...] iteration (which will equal cost now but provide potential benefit later), and railroad us down an agile path that promises iteration, but so often delivers linear, scaled-back development with no opportunity to evolve already built [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UX and the Art of Digital Appropriation by Interesting elsewhere &#8211; 8 September 2011 &#124; Public Strategist</title>
		<link>http://www.brianhoadley.com/2011/09/01/ux-and-the-art-of-digital-appropriation/#comment-54</link>
		<dc:creator>Interesting elsewhere &#8211; 8 September 2011 &#124; Public Strategist</dc:creator>
		<pubDate>Thu, 08 Sep 2011 11:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/blog/?p=621#comment-54</guid>
		<description>[...] UX and the Art of Digital Appropriation &#124; Brian Hoadley User experience is pervasive. It is ubiquitous. Companies and agencies need to step back and realise that the concept of user experience will mean change in the way their businesses operate. It’s too big to be owned by any one team, shoved down any one silo. It is too fundamentally important to leave to any one concept, methodology or team. To understand user experience is to create a fundamentally open and collaborative environment with a healthy exchange between and amongst users, businesses, agencies. [...] </description>
		<content:encoded><![CDATA[<p>[...] UX and the Art of Digital Appropriation | Brian Hoadley User experience is pervasive. It is ubiquitous. Companies and agencies need to step back and realise that the concept of user experience will mean change in the way their businesses operate. It’s too big to be owned by any one team, shoved down any one silo. It is too fundamentally important to leave to any one concept, methodology or team. To understand user experience is to create a fundamentally open and collaborative environment with a healthy exchange between and amongst users, businesses, agencies. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UX and the Art of Digital Appropriation by UX and the Art of Digital Appropriation &#124; information architecture &#124; Scoop.it</title>
		<link>http://www.brianhoadley.com/2011/09/01/ux-and-the-art-of-digital-appropriation/#comment-53</link>
		<dc:creator>UX and the Art of Digital Appropriation &#124; information architecture &#124; Scoop.it</dc:creator>
		<pubDate>Wed, 07 Sep 2011 13:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/blog/?p=621#comment-53</guid>
		<description>[...]  UX and the Art of Digital Appropriation  [...] </description>
		<content:encoded><![CDATA[<p>[...]  UX and the Art of Digital Appropriation  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Pervasive UX &#8211; Who is Responsible? by No Virginia… you are NOT the user &#124; Brian Hoadley</title>
		<link>http://www.brianhoadley.com/2011/07/12/pervasive-ux-who-is-responsible/#comment-50</link>
		<dc:creator>No Virginia… you are NOT the user &#124; Brian Hoadley</dc:creator>
		<pubDate>Tue, 06 Sep 2011 09:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://digitaloptimist.com/?p=442#comment-50</guid>
		<description>[...] experiences for users (also see my blog posts on UX and the Art of Digital Appropriation and Pervasive UX &#8211; Who is Responsible?), more Information Architects, with their own values, interests, varied experiences and goals [...] </description>
		<content:encoded><![CDATA[<p>[...] experiences for users (also see my blog posts on UX and the Art of Digital Appropriation and Pervasive UX &#8211; Who is Responsible?), more Information Architects, with their own values, interests, varied experiences and goals [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on No Virginia… you are NOT the user by Cleaning up the user interface &#124; Public Strategist</title>
		<link>http://www.brianhoadley.com/2011/09/04/no-virginia%e2%80%a6-you-are-not-the-user/#comment-55</link>
		<dc:creator>Cleaning up the user interface &#124; Public Strategist</dc:creator>
		<pubDate>Tue, 06 Sep 2011 08:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/blog/?p=628#comment-55</guid>
		<description>[...] need to know. But they are a tiny minority of the people affected. Or as Brian Hoadley has put it in a recent blog post: No Virginia… you are NOT the user. The user is the user. Someday, you may have the opportunity [...] </description>
		<content:encoded><![CDATA[<p>[...] need to know. But they are a tiny minority of the people affected. Or as Brian Hoadley has put it in a recent blog post: No Virginia… you are NOT the user. The user is the user. Someday, you may have the opportunity [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UX and the Art of Digital Appropriation by No Virginia… you are NOT the user &#124; Brian Hoadley</title>
		<link>http://www.brianhoadley.com/2011/09/01/ux-and-the-art-of-digital-appropriation/#comment-52</link>
		<dc:creator>No Virginia… you are NOT the user &#124; Brian Hoadley</dc:creator>
		<pubDate>Sun, 04 Sep 2011 19:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.brianhoadley.com/blog/?p=621#comment-52</guid>
		<description>[...] UX represents a world of ubiquitous experiences for users (also see my blog posts on UX and the Art of Digital Appropriation and Pervasive UX &#8211; Who is Responsible?), more Information Architects, with their own values, [...] </description>
		<content:encoded><![CDATA[<p>[...] UX represents a world of ubiquitous experiences for users (also see my blog posts on UX and the Art of Digital Appropriation and Pervasive UX &#8211; Who is Responsible?), more Information Architects, with their own values, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

