<?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 Deanna Glaze</title>
    <link>http://www.boxesandarrows.com/person/27695</link>
    <pubDate>Fri, 20 Mar 2009 01:50:01 GMT</pubDate>
    <description>Comments by Deanna Glaze</description>
    <item>
      <description>&lt;p&gt;Okay, so my disclaimer is that I am an art director/visual designer who also happens to have interaction design experience. The phrase in this article that furrowed my brow is &amp;#8220;design behind the design.&amp;#8221; I don&amp;#8217;t believe visual design can be separated from interaction design; they are fluid and overlap (or should). The only real solution to this is collaboration. An information architect and visual designer should be working hand in hand from a strategic perspective.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/photos-for#content_35131</link>
      <guid>http://www.boxesandarrows.com/view/photos-for#content_35131</guid>
      <pubDate>Fri, 20 Mar 2009 01:50:01 GMT</pubDate>
      <author>Deanna Glaze</author>
    </item>
    <item>
      <description>&lt;p&gt;I used JotSpot before Google bought it and think Google ruined what worked well and Googleized it into something less.&lt;/p&gt;

	&lt;p&gt;You might look at Microsoft&amp;#8217;s Communication Server software. It creates a framework around tools a team typically uses rather than forcing a team to learn new tools in order to work together.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/wanted-needed-ux#content_46704</link>
      <guid>http://www.boxesandarrows.com/view/wanted-needed-ux#content_46704</guid>
      <pubDate>Sat, 03 Oct 2009 18:00:13 GMT</pubDate>
      <author>Deanna Glaze</author>
    </item>
  </channel>
</rss>

