<?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: Ask more questions</title>
	<atom:link href="http://www.sharpenr.net/2008/07/24/ask-more-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sharpenr.net/2008/07/24/ask-more-questions/</link>
	<description>Jaan Orvet - Functional Creativity</description>
	<lastBuildDate>Tue, 11 Oct 2011 06:33:33 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Johan H</title>
		<link>http://www.sharpenr.net/2008/07/24/ask-more-questions/comment-page-1/#comment-25</link>
		<dc:creator>Johan H</dc:creator>
		<pubDate>Mon, 28 Jul 2008 07:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.sharpenr.net/2008/07/24/ask-more-questions/#comment-25</guid>
		<description>I agree, it&#039;s all about trying to drill it down to the actual requirements, and to make sure your and the customer&#039;s vision is the the same.

If they leave you with these open-ended questions you talk about it&#039;s fairly natural that you end up asking lots of questions, since you get triggered automatically by the vagueness of their request, and you&#039;ll eventually get down to something that is workable - using your skill as a professional in the process.

The tricky part can sometimes be when the solution decision process happens before you&#039;re involved, and the customer decides themselves and asks something really straightforward of you, not really triggering the necessary questions.

You end up implementing things, without a clear vision of where the result is heading, which will lead to problems in the end.

So once again, ask more questions, especially the all important one &quot;What do they REALLY want?&quot; - cause the odds are you&#039;re better at guiding the customer than they are guiding themselves.</description>
		<content:encoded><![CDATA[<p>I agree, it&#8217;s all about trying to drill it down to the actual requirements, and to make sure your and the customer&#8217;s vision is the the same.</p>
<p>If they leave you with these open-ended questions you talk about it&#8217;s fairly natural that you end up asking lots of questions, since you get triggered automatically by the vagueness of their request, and you&#8217;ll eventually get down to something that is workable &#8211; using your skill as a professional in the process.</p>
<p>The tricky part can sometimes be when the solution decision process happens before you&#8217;re involved, and the customer decides themselves and asks something really straightforward of you, not really triggering the necessary questions.</p>
<p>You end up implementing things, without a clear vision of where the result is heading, which will lead to problems in the end.</p>
<p>So once again, ask more questions, especially the all important one &#8220;What do they REALLY want?&#8221; &#8211; cause the odds are you&#8217;re better at guiding the customer than they are guiding themselves.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

