<?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 Michael Betts</title>
    <link>http://www.boxesandarrows.com/person/3606</link>
    <pubDate>Wed, 18 Apr 2007 00:27:49 GMT</pubDate>
    <description>Comments by Michael Betts</description>
    <item>
      <description>&lt;p&gt;Kudos, Rachel, for tackling an often sticky question. If this business were simply about &amp;#8220;boxes and arrows,&amp;#8221; we&amp;#8217;d be faced with some pretty boring websites. I boil the role down to these three essentials: 1&amp;gt; helping the IA gain a deeper understanding of what&amp;#8217;s actually going to be filling the buckets (because lord knows it&amp;#8217;s not always what they had in mind), 2&amp;gt; translating the experience of wireframes and comps into something a content creator/copywriter can build a narrative around, especially a non-linear one, 3&amp;gt; working with the technical team to create a manageable system for creating, migrating, and maintaining massive amounts of content data.&lt;/p&gt;

	&lt;p&gt;I also must second Robert&amp;#8217;s comment that the IA/CS relationship can vary widely and each project generally benefits from some upfront discussion of who&amp;#8217;s doing what and how you&amp;#8217;re going to work together.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/content-strategy-the#content_5649</link>
      <guid>http://www.boxesandarrows.com/view/content-strategy-the#content_5649</guid>
      <pubDate>Wed, 18 Apr 2007 00:27:49 GMT</pubDate>
      <author>Michael Betts</author>
    </item>
  </channel>
</rss>
