<?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 User Experience Design Consulting &amp; Training--UX Design Edge</title> <atom:link href="http://www.uxdesignedge.com/comments/feed/" rel="self" type="application/rss+xml" /><link>http://www.uxdesignedge.com</link> <description>User experience interaction design consulting and training</description> <lastBuildDate>Mon, 31 Oct 2011 21:49:19 -0400</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Comment on Icon design for non-designers by Everett McKay</title><link>http://www.uxdesignedge.com/2010/07/icon-design-for-non-designers/comment-page-1/#comment-948</link> <dc:creator>Everett McKay</dc:creator> <pubDate>Mon, 31 Oct 2011 21:49:19 +0000</pubDate> <guid
isPermaLink="false">http://www.uxdesignedge.com/?p=1223#comment-948</guid> <description>Thanks, Melissa! You are making a tradeoff here, but let&#039;s be very clear what that tradeoff is. If you use non-standard icons instead of text, you are exchanging easy-to-comprehend, longer text labels that require localization with difficult-to-comprehend, short iconic labels that don&#039;t require localization. Localization is a lot of work, but so is designing comprehensible icons, do the cost/effort more or less balances out. So the key question is: is it worth the extra space for easy to understand, comprehensible labels that don&#039;t require experimentation, documentation, and memorization to use?
Clearly, my preference is to use concise text labels, but I&#039;m sure there are situations where using icons is clearly the better choice regardless. I expect those situations to be rare though.
It doesn&#039;t have to be all or nothing and that sounds like the approach you are taking. For example, I&#039;m looking at a Canon digital camera that uses very clear icons for most commands, but they still use text labels like MENU, FUNCTION SET, DISPLAY, and ISO. (Not sure why they are upper case.) I find it interesting that they explicitly label the ON/OFF button even though the affordance of that button is very clear.
Putting it all together (without knowledge of your specific labels), I recommend the following:
Use standard icons when you can.
Use icons when their meaning is clear (without thought or experimentation).
Use text for top commands that don&#039;t have good icons.
Use passable icons for rarely used, advanced commands that users are likely to require documentation for anyway.
Use text labels for everything else.
I think this approach will give you the right tradeoff.</description> <content:encoded><![CDATA[<p>Thanks, Melissa! You are making a tradeoff here, but let&#8217;s be very clear what that tradeoff is. If you use non-standard icons instead of text, you are exchanging easy-to-comprehend, longer text labels that require localization with difficult-to-comprehend, short iconic labels that don&#8217;t require localization. Localization is a lot of work, but so is designing comprehensible icons, do the cost/effort more or less balances out. So the key question is: is it worth the extra space for easy to understand, comprehensible labels that don&#8217;t require experimentation, documentation, and memorization to use?</p><p>Clearly, my preference is to use concise text labels, but I&#8217;m sure there are situations where using icons is clearly the better choice regardless. I expect those situations to be rare though.</p><p>It doesn&#8217;t have to be all or nothing and that sounds like the approach you are taking. For example, I&#8217;m looking at a Canon digital camera that uses very clear icons for most commands, but they still use text labels like MENU, FUNCTION SET, DISPLAY, and ISO. (Not sure why they are upper case.) I find it interesting that they explicitly label the ON/OFF button even though the affordance of that button is very clear.</p><p>Putting it all together (without knowledge of your specific labels), I recommend the following:</p><p> Use standard icons when you can.<br
/> Use icons when their meaning is clear (without thought or experimentation).<br
/> Use text for top commands that don&#8217;t have good icons.<br
/> Use passable icons for rarely used, advanced commands that users are likely to require documentation for anyway.<br
/> Use text labels for everything else.</p><p>I think this approach will give you the right tradeoff.</p> ]]></content:encoded> </item> <item><title>Comment on Icon design for non-designers by melissa</title><link>http://www.uxdesignedge.com/2010/07/icon-design-for-non-designers/comment-page-1/#comment-947</link> <dc:creator>melissa</dc:creator> <pubDate>Mon, 31 Oct 2011 21:00:54 +0000</pubDate> <guid
isPermaLink="false">http://www.uxdesignedge.com/?p=1223#comment-947</guid> <description>great article Everett.  I am in a situation where I am working on a site that will need to be translated into many languages, that has limited space.  The Product Manager wants to keep text to a minimum, as the varied length of words like &#039;logout&#039;, &#039;upload to ftp&#039; &#039;edit&#039; oh and especially &#039;refine search&#039;, could take up far too much space if presented as text.  I am finding that the icons confuse even me, but the other option of using text could cause so many  ongoing issues with layout.  Do you have any advice?</description> <content:encoded><![CDATA[<p>great article Everett.  I am in a situation where I am working on a site that will need to be translated into many languages, that has limited space.  The Product Manager wants to keep text to a minimum, as the varied length of words like &#8216;logout&#8217;, &#8216;upload to ftp&#8217; &#8216;edit&#8217; oh and especially &#8216;refine search&#8217;, could take up far too much space if presented as text.  I am finding that the icons confuse even me, but the other option of using text could cause so many  ongoing issues with layout.  Do you have any advice?</p> ]]></content:encoded> </item> <item><title>Comment on Correcting the reality distortion field: Learning the right lessons from Steve Jobs by Correcting the reality distortion field: Learning the ... - UX Design Edge &#124; UX Design &#124; Scoop.it</title><link>http://www.uxdesignedge.com/2011/10/correcting-the-reality-distortion-field-learning-the-right-lessons-from-steve-jobs/comment-page-1/#comment-938</link> <dc:creator>Correcting the reality distortion field: Learning the ... - UX Design Edge &#124; UX Design &#124; Scoop.it</dc:creator> <pubDate>Fri, 28 Oct 2011 16:50:16 +0000</pubDate> <guid
isPermaLink="false">http://www.uxdesignedge.com/?p=3448#comment-938</guid> <description>[...]  Correcting the reality distortion field: Learning the ... - UX Design Edge           Walter Isaacson&#039;s Steve Jobs biography is now the #1 bestseller. From the project management point of view, I fear that Isaacson&#039;s story is too focused on Jobs&#039; character flaws instead of his true brilliance.     Source: www.uxdesignedge.com [...]</description> <content:encoded><![CDATA[<p>[...]  Correcting the reality distortion field: Learning the &#8230; &#8211; UX Design Edge           Walter Isaacson&#039;s Steve Jobs biography is now the #1 bestseller. From the project management point of view, I fear that Isaacson&#039;s story is too focused on Jobs&#039; character flaws instead of his true brilliance.     Source: <a
href="http://www.uxdesignedge.com" rel="nofollow">http://www.uxdesignedge.com</a> [...]</p> ]]></content:encoded> </item> <item><title>Comment on Correcting the reality distortion field: Learning the right lessons from Steve Jobs by Correcting the reality distortion field: Learning the right lessons from &#8230;</title><link>http://www.uxdesignedge.com/2011/10/correcting-the-reality-distortion-field-learning-the-right-lessons-from-steve-jobs/comment-page-1/#comment-936</link> <dc:creator>Correcting the reality distortion field: Learning the right lessons from &#8230;</dc:creator> <pubDate>Fri, 28 Oct 2011 13:15:22 +0000</pubDate> <guid
isPermaLink="false">http://www.uxdesignedge.com/?p=3448#comment-936</guid> <description>[...] hier den Originalbeitrag weiterlesen: Correcting the reality distortion field: Learning the right lessons from &#8230; [...]</description> <content:encoded><![CDATA[<p>[...] hier den Originalbeitrag weiterlesen: Correcting the reality distortion field: Learning the right lessons from &#8230; [...]</p> ]]></content:encoded> </item> <item><title>Comment on A hypothetical Steve Jobs by A hypothetical Steve Jobs &#124; User Experience &#124; Syngu</title><link>http://www.uxdesignedge.com/2011/10/a-hypothetical-steve-jobs/comment-page-1/#comment-914</link> <dc:creator>A hypothetical Steve Jobs &#124; User Experience &#124; Syngu</dc:creator> <pubDate>Thu, 20 Oct 2011 05:39:24 +0000</pubDate> <guid
isPermaLink="false">http://www.uxdesignedge.com/?p=3406#comment-914</guid> <description>[...] Steve Jobs revolutionized the computer, music, and cell phone industries. He led an extraordinary life and founded an extraordinary company. To get an idea of just how extraordinary, I’ve been asking myself some hypothetical questions. Read this post to see how easily things might have been different.     &#160;User Experience  Read the full post on UX Design Edge... [...]</description> <content:encoded><![CDATA[<p>[...] Steve Jobs revolutionized the computer, music, and cell phone industries. He led an extraordinary life and founded an extraordinary company. To get an idea of just how extraordinary, I’ve been asking myself some hypothetical questions. Read this post to see how easily things might have been different.     &nbsp;User Experience  Read the full post on UX Design Edge&#8230; [...]</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Dynamic page generated in 11.295 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-06 16:24:52 -->

