<?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 Dawn Nidy</title>
    <link>http://www.boxesandarrows.com/person/1377</link>
    <pubDate>Fri, 26 Jan 2007 14:53:19 GMT</pubDate>
    <description>Comments by Dawn Nidy</description>
    <item>
      <description>&lt;p&gt;I agree with the author that if you are trying to get early feedback on paper, it&amp;#8217;s generally a good idea to add fidelity and visual cues.  I also like the idea of testing &lt;span class="caps"&gt;HTML&lt;/span&gt; prototypes, but it&amp;#8217;s often much faster to get it out on and tested on paper.  If you&amp;#8217;re using templating in Visio, it will be very easy to drop in navigation, logos, pictures, etc. to make the wireframe more useful.&lt;/p&gt;

	&lt;p&gt;Absolutely you should be collaborating with your visual designers and copywriters before letting anything go out to usability testing.  Interaction design is only one piece of the puzzle and not having those in will skew your results.&lt;/p&gt;

	&lt;p&gt;I am not convinced you need color as part of your wireframes for your internal audience unless the interaction designer is also responsible for the visual design.  Or, if the visual designer is going to add their design to the wireframe to create a common deliverable.  I think this depends on the project, organization and team as to how appropriate this is.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/real_wireframes#content_3654</link>
      <guid>http://www.boxesandarrows.com/view/real_wireframes#content_3654</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:19 GMT</pubDate>
      <author>Dawn Nidy</author>
    </item>
  </channel>
</rss>
