<?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: Because?</title>
	<atom:link href="http://commadot.com/because/feed/" rel="self" type="application/rss+xml" />
	<link>http://commadot.com/because/</link>
	<description>Started in 1996, commadot.com has been been randomly publishing about UX, technology, Politics, the Jets and my kids.</description>
	<pubDate>Wed, 19 Nov 2008 17:23:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan Lipka</title>
		<link>http://commadot.com/because/comment-page-1/#comment-192</link>
		<dc:creator>Dan Lipka</dc:creator>
		<pubDate>Wed, 01 Feb 2006 15:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://commadot.com/?p=340#comment-192</guid>
		<description>Intuit should hire me as a consultant to do this for you.  This is exactly the consulting that I am doing for my boss's husband.  Basically creating, administering, and analyzing survey to understand people's perceptions.  It did this at Penn, Schoen, and Berland for some of the biggest companies in the country.  Being objective, instead of subjective, can save companies a ton of money.

Here is the link to my boss’s husband’s site, all of which I could do myself: http://www.bayerconsulting.com/.
Here is Penn, Schoen’s site: http://www.psbresearch.com/</description>
		<content:encoded><![CDATA[<p>Intuit should hire me as a consultant to do this for you.  This is exactly the consulting that I am doing for my boss&#8217;s husband.  Basically creating, administering, and analyzing survey to understand people&#8217;s perceptions.  It did this at Penn, Schoen, and Berland for some of the biggest companies in the country.  Being objective, instead of subjective, can save companies a ton of money.</p>
<p>Here is the link to my boss’s husband’s site, all of which I could do myself: <a href="http://www.bayerconsulting.com/" rel="nofollow">http://www.bayerconsulting.com/</a>.<br />
Here is Penn, Schoen’s site: <a href="http://www.psbresearch.com/" rel="nofollow">http://www.psbresearch.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fiat lux</title>
		<link>http://commadot.com/because/comment-page-1/#comment-191</link>
		<dc:creator>fiat lux</dc:creator>
		<pubDate>Tue, 31 Jan 2006 15:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://commadot.com/?p=340#comment-191</guid>
		<description>In point of fact, unless you have data in front of you that proves your point, you don't actually know what the user is thinking. You're drawing on your experience with similar situations in order to make an educated guess. Presumably, your experience is such that your guess is correct.

And that's normal in the product development &#38; marketing worlds. It's too expensive and time-consuming to do in-depth research, testing, surveys, etc about every single customer-facing question that comes up, so the experience of the people doing the work often becomes a proxy for actually asking the users.

The problems happen when people think their knowledge is so deep that they don't need to ask the users anymore, or when they are unable to navigate the ambiguity of user demands/expectations and make wrong choices.

Whether any of that meta musing applies to your situation, though, I don't know. Maybe the person in question was just being a butthead.</description>
		<content:encoded><![CDATA[<p>In point of fact, unless you have data in front of you that proves your point, you don&#8217;t actually know what the user is thinking. You&#8217;re drawing on your experience with similar situations in order to make an educated guess. Presumably, your experience is such that your guess is correct.</p>
<p>And that&#8217;s normal in the product development &amp; marketing worlds. It&#8217;s too expensive and time-consuming to do in-depth research, testing, surveys, etc about every single customer-facing question that comes up, so the experience of the people doing the work often becomes a proxy for actually asking the users.</p>
<p>The problems happen when people think their knowledge is so deep that they don&#8217;t need to ask the users anymore, or when they are unable to navigate the ambiguity of user demands/expectations and make wrong choices.</p>
<p>Whether any of that meta musing applies to your situation, though, I don&#8217;t know. Maybe the person in question was just being a butthead.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
