<?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 Maria Cordell</title>
    <link>http://www.boxesandarrows.com/person/1141</link>
    <pubDate>Sat, 01 Dec 2007 13:19:07 GMT</pubDate>
    <description>Comments by Maria Cordell</description>
    <item>
      <description>&lt;p&gt;I&amp;#8217;d also like to explore how to best deploy a team. Are the various roles working together collaboratively from the start?  To what extent? Where does the graphic designer get involved, for example? In my experience these folks don&amp;#8217;t generally read the research materials produced early in the process (user research, market research, etc.) that should directly affect the visual look and feel of the end product. (I don&amp;#8217;t mean to pick on graphic designers; developers, for example, don&amp;#8217;t typically read any documentation, either. This isn&amp;#8217;t always their fault, however, as their jobs often don&amp;#8217;t allow time for this.) Of course, this can also affect how things work within an IA &amp;#8220;team&amp;#8221; and its reporting structure? If an IA team is, say, divided between research and design (with different managers, for example), how does one account for knowledge transfer between the groups? How thoroughly does research have to document in order for design IAs to faithfully carry on the work?&lt;/p&gt;

	&lt;p&gt;Not sure all of this is related to your specific objective for the article, but it&amp;#8217;s something that affects planning (building in time for documentation and knowledge transfer), and it&amp;#8217;s also something I&amp;#8217;m facing as a team manager. Would be very interested to see how you cover it.&lt;/p&gt;

	&lt;p&gt;Regards,&lt;/p&gt;

	&lt;p&gt;Maria&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/13449#content_13797</link>
      <guid>http://www.boxesandarrows.com/idea/view/13449#content_13797</guid>
      <pubDate>Sat, 01 Dec 2007 13:19:07 GMT</pubDate>
      <author>Maria Cordell</author>
    </item>
    <item>
      <description>&lt;p&gt;Thanks for the article, Aaron. I&amp;#8217;ve done a lot of wireframes in Visio and Omnigraffle, and I sketch a lot in my notebook, but I&amp;#8217;ve only recently had a chance to use a sketchy wireframe style in Omnigraffle. It&amp;#8217;s great for communicating concepts and early ideas early on. My client reacted to the &amp;#8220;sketches&amp;#8221; very well when reviewing early concepts for a somewhat complex site content area, and we were able to have a good discussion as a result. There was just enough fidelity to see how things should work, but not so much that one felt too firmly committed to a particular direction. I think it made me more relaxed overall, too, since it didn&amp;#8217;t have to be perfect. I&amp;#8217;ll be doing more of this in the future, that&amp;#8217;s for sure!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/sketchy-wireframes#content_49293</link>
      <guid>http://www.boxesandarrows.com/view/sketchy-wireframes#content_49293</guid>
      <pubDate>Sat, 05 Mar 2011 05:53:21 GMT</pubDate>
      <author>Maria Cordell</author>
    </item>
  </channel>
</rss>

