<?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 Ken Whaler</title>
    <link>http://www.boxesandarrows.com/person/21035</link>
    <pubDate>Tue, 16 Dec 2008 15:22:16 GMT</pubDate>
    <description>Comments by Ken Whaler</description>
    <item>
      <description>&lt;p&gt;This is a very interesting topic indeed. My job (UX Strategist) is to show a design/interaction concepts&amp;#8230; a balancing act of detail and concept.&lt;/p&gt;

	&lt;p&gt;My main problem here is that interaction design / UX is not just layout out a page of boxes (or DIVs), its about explaining what the purpose of the boxes are  and what experience they are intended for- to explain why the layout is better because its usable or will allow the target user to use the site that its intended to. This can be summed up in one word: documentation. I agree that its handy to use html to align boxes. But what about the other typical deliverables of a UX professional: sitemaps, user journeys, etc.? The one real solution is a drawing program that can be exported out as a Hi/Lo fidelity prototype and integrates notes and specifications (and everything else under the sun).&lt;/p&gt;

	&lt;p&gt;I have used: &lt;span class="caps"&gt;HTML&lt;/span&gt;, iRise, Protoshare, &lt;span class="caps"&gt;AXURE&lt;/span&gt;, Visio, Paper and pen, OmniGraffle, Illustrator, Fireworks, the list goes on&amp;#8230; All have their strengths and weaknesses. The search continues&amp;#8230;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/prototyping-with#content_31362</link>
      <guid>http://www.boxesandarrows.com/view/prototyping-with#content_31362</guid>
      <pubDate>Tue, 16 Dec 2008 15:22:16 GMT</pubDate>
      <author>Ken Whaler</author>
    </item>
  </channel>
</rss>

