<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by rob fitzgibbon</title>
    <link>http://www.boxesandarrows.com/person/17873</link>
    <pubDate>Fri, 07 Jan 2011 19:43:10 GMT</pubDate>
    <description>Comments by rob fitzgibbon</description>
    <item>
      <description>&lt;p&gt;I dunno  &amp;#8211; I agree with the author that the fact that a client will &#8220;grok&#8221;  familiar, designed elements faster; however, I&amp;#8217;m my experience, it just provides the client an opportunity to rathole into issues such as &#8220;that&#8217;s not the right button&#8221; or &#8220;we&#8217;re changing that logo next week&#8221; or &#8220;that grey bar is so ugly.&#8221; When you introduce color and style into the content, be prepared for color &amp;amp; style content issues getting in the way of the usability and informational stuff you want to solve.&lt;/p&gt;

	&lt;p&gt;An equivalent might be forcing a civil engineer to replace his b/w blueprints with color versions, in which the grass is green, the the hay bales that rim the swales a bright yellow (of course with an fluorescent orange line representing the plastic construction fencing) the gravel in bluish gray and the asphalt in brownish black.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/real_wireframes#content_24142</link>
      <guid>http://www.boxesandarrows.com/view/real_wireframes#content_24142</guid>
      <pubDate>Fri, 07 Jan 2011 19:43:10 GMT</pubDate>
      <author>rob fitzgibbon</author>
    </item>
  </channel>
</rss>

