<?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 Bobby Foster</title>
    <link>http://www.boxesandarrows.com/person/8790</link>
    <pubDate>Thu, 07 Jun 2007 17:07:37 GMT</pubDate>
    <description>Comments by Bobby Foster</description>
    <item>
      <description>&lt;p&gt;As &lt;span class="caps"&gt;UXA&lt;/span&gt;&amp;#8217;s we preach consistency and adheranec to standards. Black and white wireframes &amp;#8211; in the strictest sense of the word &amp;#8211; are as far from &amp;#8220;familiar&amp;#8221; as can be for most users. If wireframes are going in front of the client and/or end users, taking the extra few minutes to show the design in context of what is familiar to them can be far more effective. I&amp;#8217;ve been designing wireframes this way for some time and am a huge propenent for it.&lt;br /&gt;Sure, there may be some stray comments from the users about colors and images, but asking them to stifle comments about one or two specific elements is far easier than asking them to imagine what they would be seeing in a real implementation when all you&amp;#8217;ve presented them with are minimalistic wireframes.&lt;br /&gt;There are those who note that we, as IA&amp;#8217;s, UX&amp;#8217;s, etc. should do whatever is necessary to adequately communicate ideas and concepts to our clients. One could hardly argue that a classic wireframe does that.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/real_wireframes#content_8754</link>
      <guid>http://www.boxesandarrows.com/view/real_wireframes#content_8754</guid>
      <pubDate>Thu, 07 Jun 2007 17:07:37 GMT</pubDate>
      <author>Bobby Foster</author>
    </item>
    <item>
      <description>&lt;p&gt;I&amp;#8217;ve just recently started a new UX practice in a rather large company and can agree whole-heartedly that there is a great temptation to go wide very fast. Having made a significant impact very early, the desire to have me involved in every new and on-going project is great. There are ways to get involved on a wider spectrum with limited resources, though. What we&amp;#8217;ve done is focus on developing an internal process and create guidelines for future projects to adhere to. There&amp;#8217;s also a recognition internally for the need to increase the resources that are dedicated to UI design and usability. Fortunately, I&amp;#8217;ve benefited from being in an environment where the need is apparent and the company is enthusiastic to adopt the practice.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/pioneering-a-user#content_9417</link>
      <guid>http://www.boxesandarrows.com/view/pioneering-a-user#content_9417</guid>
      <pubDate>Wed, 27 Jun 2007 20:49:40 GMT</pubDate>
      <author>Bobby Foster</author>
    </item>
  </channel>
</rss>
