<?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 Ben Darlow</title>
    <link>http://www.boxesandarrows.com/person/1338</link>
    <pubDate>Tue, 10 Jul 2007 16:14:38 GMT</pubDate>
    <description>Comments by Ben Darlow</description>
    <item>
      <description>&lt;p&gt;The one reason to use wireframes that isn&amp;#8217;t merely for the benefit of the designer is that of communicating purpose to the client without distractions. It&amp;#8217;s an interesting idea to use colour and make a pseudo-wireframe for usability testing, wireframes still have a very important role in an earlier stage of design, when proposed solutions are still being mooted.&lt;/p&gt;

	&lt;p&gt;This is especially important if the new proposed designs are very different from an existing design, as differences in colour and typography may be sufficiently apparent to the client that they end up becoming a focus, when really they have less significance than the layout of the page and UI elements. Going straight to a prototype means that early decisions about colour, branding and typography have to be made at a stage when really they shouldn&amp;#8217;t be allowed to cloud the subject matter.&lt;/p&gt;

	&lt;p&gt;That all said, I think there is some value in having these chrome parts visible once you get to the user testing stages. Perhaps it would be an acceptable alternative to just use a generic stylesheet at this point?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/real_wireframes#content_3589</link>
      <guid>http://www.boxesandarrows.com/view/real_wireframes#content_3589</guid>
      <pubDate>Tue, 10 Jul 2007 16:14:38 GMT</pubDate>
      <author>Ben Darlow</author>
    </item>
  </channel>
</rss>
