<?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: Having a Design Philosophy</title>
	<atom:link href="http://kshitizanand.com/2008/11/hello-world/feed/" rel="self" type="application/rss+xml" />
	<link>http://kshitizanand.com/2008/11/hello-world/</link>
	<description>User Experience Designer</description>
	<lastBuildDate>Tue, 04 May 2010 13:53:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: vinay</title>
		<link>http://kshitizanand.com/2008/11/hello-world/comment-page-1/#comment-381</link>
		<dc:creator>vinay</dc:creator>
		<pubDate>Wed, 28 Jan 2009 22:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://kshitizanand.com/?p=1#comment-381</guid>
		<description>I loved this ....
&#039;The way I see it, my design philosophy is based on strong design rationale, the ability to enhance user experience and a solid return of investment for the stakeholders.&#039;

Right on the money. I would like to add some more points to the design philosophy
- understanding a problem before jumping to solve it
- building a criteria or set of rules to evaluate design solutions for eg. I have 20 solutions to a problem , then I prioritize and give weights

For e.g.

solution 1 
- good for user 
- but takes time to engineer
- good for business value
- must have as our competitor has it 

- as a designer be open to criticism and play the role of a facilitator, not the owner of a design
- have no sacred rules that can&#039;t be broken... a design rule that is good in a particular context may fail in another...
so have no rules but use frameworks and learn from others</description>
		<content:encoded><![CDATA[<p>I loved this &#8230;.<br />
&#8216;The way I see it, my design philosophy is based on strong design rationale, the ability to enhance user experience and a solid return of investment for the stakeholders.&#8217;</p>
<p>Right on the money. I would like to add some more points to the design philosophy<br />
- understanding a problem before jumping to solve it<br />
- building a criteria or set of rules to evaluate design solutions for eg. I have 20 solutions to a problem , then I prioritize and give weights</p>
<p>For e.g.</p>
<p>solution 1<br />
- good for user<br />
- but takes time to engineer<br />
- good for business value<br />
- must have as our competitor has it </p>
<p>- as a designer be open to criticism and play the role of a facilitator, not the owner of a design<br />
- have no sacred rules that can&#8217;t be broken&#8230; a design rule that is good in a particular context may fail in another&#8230;<br />
so have no rules but use frameworks and learn from others</p>
]]></content:encoded>
	</item>
</channel>
</rss>
