<?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 Stoy Solutions blog</title>
	<atom:link href="http://blog.stoysolutions.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.stoysolutions.com</link>
	<description>Sharing thoughts on new ideas in the world of software and web media</description>
	<lastBuildDate>Thu, 11 Jun 2009 19:08:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Mobile design guidelines by aaaaa@a.com</title>
		<link>http://blog.stoysolutions.com/mobile-design-guidelines/comment-page-/#comment-577</link>
		<dc:creator>aaaaa@a.com</dc:creator>
		<pubDate>Thu, 11 Jun 2009 19:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=15#comment-577</guid>
		<description>aaaaa@a.com </description>
		<content:encoded><![CDATA[<p><a href="mailto:aaaaa@a.com">aaaaa@a.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another look at usability by Anton Stoyanov</title>
		<link>http://blog.stoysolutions.com/another-look-at-usability/comment-page-1/#comment-469</link>
		<dc:creator>Anton Stoyanov</dc:creator>
		<pubDate>Tue, 28 Apr 2009 09:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=13#comment-469</guid>
		<description>Thanks for the comment Steve, I have some more posts on UX coming </description>
		<content:encoded><![CDATA[<p>Thanks for the comment Steve, I have some more posts on UX coming</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risks of CRM systems implementation by Steve Reeves</title>
		<link>http://blog.stoysolutions.com/risks-of-crm-systems-implementation/comment-page-1/#comment-468</link>
		<dc:creator>Steve Reeves</dc:creator>
		<pubDate>Tue, 28 Apr 2009 08:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://dev.stoysolutions.com/blog/?p=10#comment-468</guid>
		<description>Nice to see you differentiating between business models and application requirements. 
 
Unfortunately, the world&#039;s been led to believe that CRM is a one size fits all type of software solution, and it isn&#039;t of course.  This explains the horrific failure rate for CRM implementation which even salesforce suggests is 70% (not for salesforce of course- my guess is it&#039;s higher for them). 
 
CRM isn&#039;t a software package, it&#039;s a philosophy and can only work when it enables the competitive advantage of the company. 
 
Since that&#039;s different for every company the very concept of a standard software package is crazy.  There are only two ways of offering something to fit a wide range of business needs 1) stuff it full of features most people won&#039;t use, and suffer the adoption problems caused by the complexity and 2) net the app down to generic functions so people can use it however they like, and suffer the adoption problems that come from them not knowing how they want to run their business. 
 
Alternatively of course there&#039;s the custom solution, which is bound to be expensive, not because of the coding, but because of the consulting on how to add CRM to the business model. 
 
Steve </description>
		<content:encoded><![CDATA[<p>Nice to see you differentiating between business models and application requirements. </p>
<p>Unfortunately, the world&#039;s been led to believe that CRM is a one size fits all type of software solution, and it isn&#039;t of course.  This explains the horrific failure rate for CRM implementation which even salesforce suggests is 70% (not for salesforce of course- my guess is it&#039;s higher for them). </p>
<p>CRM isn&#039;t a software package, it&#039;s a philosophy and can only work when it enables the competitive advantage of the company. </p>
<p>Since that&#039;s different for every company the very concept of a standard software package is crazy.  There are only two ways of offering something to fit a wide range of business needs 1) stuff it full of features most people won&#039;t use, and suffer the adoption problems caused by the complexity and 2) net the app down to generic functions so people can use it however they like, and suffer the adoption problems that come from them not knowing how they want to run their business. </p>
<p>Alternatively of course there&#039;s the custom solution, which is bound to be expensive, not because of the coding, but because of the consulting on how to add CRM to the business model. </p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another look at usability by Steve Reeves</title>
		<link>http://blog.stoysolutions.com/another-look-at-usability/comment-page-1/#comment-467</link>
		<dc:creator>Steve Reeves</dc:creator>
		<pubDate>Tue, 28 Apr 2009 08:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=13#comment-467</guid>
		<description>Hi Anton 
 
I&#039;m just pleased everybody bringing web apps to market doesn&#039;t understand your points here. 
 
They are great points, very well expressed. 
 
Ultimately every software product stands or falls on how good it feels to the user.  Adoption is now being recognized as the main issue for software makers, of all descriptions. 
 
Our bet is usability will become the point of competition, as opposed to features - the good old &quot;less is more&quot; argument. </description>
		<content:encoded><![CDATA[<p>Hi Anton </p>
<p>I&#039;m just pleased everybody bringing web apps to market doesn&#039;t understand your points here. </p>
<p>They are great points, very well expressed. </p>
<p>Ultimately every software product stands or falls on how good it feels to the user.  Adoption is now being recognized as the main issue for software makers, of all descriptions. </p>
<p>Our bet is usability will become the point of competition, as opposed to features &#8211; the good old &quot;less is more&quot; argument.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mobile design guidelines by Catherine</title>
		<link>http://blog.stoysolutions.com/mobile-design-guidelines/comment-page-1/#comment-301</link>
		<dc:creator>Catherine</dc:creator>
		<pubDate>Wed, 22 Apr 2009 21:42:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=15#comment-301</guid>
		<description>Keep up the good work.</description>
		<content:encoded><![CDATA[<p>Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another look at usability by stoysolutions</title>
		<link>http://blog.stoysolutions.com/another-look-at-usability/comment-page-1/#comment-56</link>
		<dc:creator>stoysolutions</dc:creator>
		<pubDate>Mon, 13 Apr 2009 15:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=13#comment-56</guid>
		<description>Hi Ann, 
 
Great to see you here. We&#039;ll link to you :) 
 
We&#039;ve actually split this monster in 4 articles (so far, at least). Next post will be on international usability standards and what they are, then the third post would be on cost-effective usability implementation, including testing as well as a few concrete hints/ rules. 
 
Axure looks great - I will check it out. We tend to use Omnigraffle to quickly sketch things with clients, while talking to them, then redefine it in a report.  
 
Anton 
 </description>
		<content:encoded><![CDATA[<p>Hi Ann, </p>
<p>Great to see you here. We&#039;ll link to you <img src='http://blog.stoysolutions.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>We&#039;ve actually split this monster in 4 articles (so far, at least). Next post will be on international usability standards and what they are, then the third post would be on cost-effective usability implementation, including testing as well as a few concrete hints/ rules. </p>
<p>Axure looks great &#8211; I will check it out. We tend to use Omnigraffle to quickly sketch things with clients, while talking to them, then redefine it in a report.  </p>
<p>Anton</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another look at usability by Ann Krause</title>
		<link>http://blog.stoysolutions.com/another-look-at-usability/comment-page-1/#comment-55</link>
		<dc:creator>Ann Krause</dc:creator>
		<pubDate>Mon, 13 Apr 2009 14:23:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=13#comment-55</guid>
		<description>It&#039;s great to see you blogging about usability! Absolutely, prototyping./wireframing in the early stages of design is very useful, but even more useful if you perform some usability tests on the prototypes. Are you going to talk about usability testing in your next post (I hope?) 
 
Personally, I like to use Axure for wireframing--I haven&#039;t tried Omnigraffle and would be curious to hear more about how you use it for prototyping and what you like and don&#039;t like about it.  </description>
		<content:encoded><![CDATA[<p>It&#039;s great to see you blogging about usability! Absolutely, prototyping./wireframing in the early stages of design is very useful, but even more useful if you perform some usability tests on the prototypes. Are you going to talk about usability testing in your next post (I hope?) </p>
<p>Personally, I like to use Axure for wireframing&#8211;I haven&#039;t tried Omnigraffle and would be curious to hear more about how you use it for prototyping and what you like and don&#039;t like about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Another look at usability by Dan</title>
		<link>http://blog.stoysolutions.com/another-look-at-usability/comment-page-1/#comment-14</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 12 Apr 2009 12:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=13#comment-14</guid>
		<description>Useful information, every designer should read it. Please let me know when you post the next part. 

Dan</description>
		<content:encoded><![CDATA[<p>Useful information, every designer should read it. Please let me know when you post the next part. </p>
<p>Dan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
