<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PixelMEDIA &#187; Content strategy</title>
	<atom:link href="http://www.pixelmedia.com/blog/tag/content-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pixelmedia.com/blog</link>
	<description>The official staff chatter blox</description>
	<lastBuildDate>Mon, 14 Jun 2010 17:44:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Small Victories Can Add Up to Customer Loyalty</title>
		<link>http://www.pixelmedia.com/blog/small-victories/</link>
		<comments>http://www.pixelmedia.com/blog/small-victories/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 15:20:06 +0000</pubDate>
		<pxlAuthorId>29</pxlAuthorId>
		<dc:creator>kanderson</dc:creator>
				<category><![CDATA[Hosting and support]]></category>
		<category><![CDATA[Content strategy]]></category>
		<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[Experience Design]]></category>
		<category><![CDATA[Information Architecture]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[search engine optimization]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[webdev]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[Website design]]></category>

		<guid isPermaLink="false">http://www.pixelmedia.com/blog/?p=1117</guid>
		<description><![CDATA[The goal of any good web firm should be to provide clients with the best possible online face to the world.  Notice, however, that I use the term “best possible”.  The reality is that we as developers, designers, information architects, content strategists, account managers and project managers, are often limited by the budget, particularly in [...]]]></description>
			<content:encoded><![CDATA[<p>The goal of any good web firm should be to provide clients with the best possible online face to the world.  Notice, however, that I use the term “best possible”.  The reality is that we as developers, designers, information architects, content strategists, account managers and project managers, are often limited by the budget, particularly in this difficult economy.  While a $100,000 website redesign might be off the table during tough times, “small victories” in key places can happen as part of the regular support and maintenance of your website, and often have a big impact.</p>
<p><span id="more-1117"></span></p>
<p>In the support &amp; maintenance division, edits are often purely functional and extremely urgent.  One thing I try to do with my clients is suggest small improvements above and beyond the standard maintenance requests, and emphasize how easy it is to keep the request affordable.  Almost everyone wants to “do it right,” but clients often have a boss ready to veto 30 hours to redesign and rebuild the entire products section.  However, customers may not realize that significant improvements can be made despite limited time and budget:</p>
<ul>
<li>1-2 hours for an information architect look at a problematic page that frequently elicit customer complaints</li>
<li>½ hour for a copywriter to punch up the language on a flat homepage promotion</li>
<li>2-3 hours for a designer to restyle a confusing chart so that users can get critical product information “at a glance”</li>
<li>3-4 hours for a developer to automate a task that normally takes the client 1-2 hours to accomplish using a content management system (CMS) several times weekly</li>
<li>15 minutes to create a Google Analytics account and add the code to a landing page to make sure a search engine optimization (SEO) campaign is effective</li>
</ul>
<p>Affordable suggestions like these introduce clients to expertise that normally only get tapped during large-scale projects. They also remind them that we really do have their best interest in mind and that we are as frustrated by the “bubble gum and duct tape” add-ons to their website as they are. It’s important for everyone to remember that while a full-scale website redesign might not be possible during tough times, these “small victories” in key places (i.e., where customers often identify difficulty) can happen on a regular basis, and often have a big impact. The focus and frequency of these changes can draw attention to improvements that might have otherwise gotten lost during an overwhelming, large-scale redesign, and show users that your company strives to be responsive.  Innovation, intelligence, and creativity in small doses can still be enough to inspire customer involvement and loyalty.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/small-victories/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My top 10 writing reminders.</title>
		<link>http://www.pixelmedia.com/blog/my-top-10-writing-reminders/</link>
		<comments>http://www.pixelmedia.com/blog/my-top-10-writing-reminders/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 22:27:01 +0000</pubDate>
		<pxlAuthorId>11</pxlAuthorId>
		<dc:creator>Luke Michel</dc:creator>
				<category><![CDATA[Website design]]></category>
		<category><![CDATA[Content strategy]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=664</guid>
		<description><![CDATA[Even after all these years, I check off a handful of reminders whenever I sit down to write or edit a web page. It's not about being creative and using big words, it's about respecting the time and intelligence of the reader. ]]></description>
			<content:encoded><![CDATA[<p><strong></strong>Even after all these years, a handful of reminders help me get off to a good start whenever I sit down to write or edit a web page. It&#8217;s not about being creative and using big words, it&#8217;s about respecting the time and intelligence of the reader. By the way, most of these apply equally well when writing for print, direct mail, and everyday email.</p>
<p><strong><span id="more-664"></span>1.  Be brief.</strong></p>
<p>Most visitors come to your website to accomplish a specific task, and they do not want to spend a lot of time reading irrelevant copy. Write clearly, concisely, and assertively. Use better nouns and fewer adjectives.</p>
<p><strong>2.  Make your content easy to scan.</strong></p>
<p>To help impatient or hurried readers grasp what you’re trying to say, make your page easy to scan by breaking long copy into paragraphs of 150 to 200 words each, defined by meaningful subheadings (and don’t try to be cute or clever). The goal is to tell the essence of the story using only the subheadings, supported by the body copy.</p>
<p>Bulleted lists and the judicious use of <strong>bolded text</strong> can help readers scan the content.  Be sure bolding does not conflict with established standards for links and visited links.</p>
<p><strong>3.  Use the inverted pyramid.</strong></p>
<p>The “inverted pyramid” format presents a summary at the beginning of a story with subsequent paragraphs revealing more detail. It’s used in news and press releases to help readers grasp the important idea by reading the first paragraph. The readers can then decide whether the topic is of sufficient interest for them to read further.</p>
<p><strong>4.  Use keywords to stay on topic.</strong></p>
<p>Focusing on keywords and phrases can help you stay “on topic” and use terms that customers care about. If the list of keywords you want to include in the page copy is excessively long or diverse, consider creating separate pages. Using keywords and phrases in standard HTML headlines and subheadings (H1, H2, etc.) gives added weight in search engine rankings <em>and</em> makes the page easier to scan (see number 2).</p>
<p><strong>5.  Consider page length.</strong></p>
<p>To scroll or not to scroll? It depends on the page level and depth of information. On higher-level pages, which tend to guide users to more detailed pages, less scrolling is usually better. At the lower-level detail pages with longer content, assume the reader is interested in the subject matter. Scrolling is preferable to breaking the content into multiple pages.</p>
<p><strong>6.  Avoid excessive cross-linking.</strong></p>
<p>Too many highlighted links can distract the reader and clutter your content with multicolored links. Avoid linking to pages that are not related to the main topic.  If you want to cross-sell, make it clear that you are leading the reader to a different topic, for example, “You may also be interested in &#8230;&#8221;</p>
<p><strong>7.  Use technical terms consistently.</strong></p>
<p>Establish a guide to branded terms and industry terms and use them correctly and consistently to avoid confusion. Define any terms, abbreviations, and acronyms that are not familiar to the reader. If you use acronyms to save space, be sure to spell out the full name the first time it appears on each page.</p>
<p><strong>8.  Write for an international audience.</strong></p>
<p>Remember that your audience may come from non-English speaking countries. Keep the following guidelines in mind:</p>
<ul>
<li>Always      include the country in mailing addresses, and format it appropriately.</li>
<li>Do      not refer to toll-free telephone numbers that cannot be accessed      internationally; make sure you provide a means of making contact from      outside your country.</li>
<li>Avoid      references to politics, race, nationality, religion, or lifestyle.</li>
<li>Do      not use the term &#8220;domestic&#8221; to refer to your local country, or      “foreign” to refer to the rest of the world.</li>
<li>Avoid      cultural references, e.g., “American spirit,” or “German engineering.”</li>
<li>Avoid      abbreviations; they rarely translate correctly.</li>
<li>Avoid      jargon, slang, and idioms that are meaningless to other nationalities.</li>
<li>For      measurements, include both metric and American units if possible.</li>
<li>Do      not use #, `, or &#8220;to indicate pound, foot, or inch in American      measurements.</li>
</ul>
<p><strong>9.  Avoid overly self-referential copy.</strong></p>
<p>It’s good to imagine your web page as a “first date.” Limit &#8220;we&#8221; or &#8220;our&#8221; statements to a bare minimum (keep count).  Companies that talk about themselves a lot are often compensating for a lack of insight into what their customers want and need.</p>
<p><strong>10. Don’t forget the call to action.</strong></p>
<p>It’s amazing how many times this is forgotten. Most people come to your website to accomplish a task, so be sure to give them something to do. Better yet, give them a range of choices. Don’t rely on the general “Contact Us” link on every web page.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/my-top-10-writing-reminders/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Content Strategy: The Brief</title>
		<link>http://www.pixelmedia.com/blog/content-strategy-the-brief/</link>
		<comments>http://www.pixelmedia.com/blog/content-strategy-the-brief/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 19:09:25 +0000</pubDate>
		<pxlAuthorId>11</pxlAuthorId>
		<dc:creator>Luke Michel</dc:creator>
				<category><![CDATA[Brand identity]]></category>
		<category><![CDATA[Strategic planning]]></category>
		<category><![CDATA[Branding]]></category>
		<category><![CDATA[Content strategy]]></category>
		<category><![CDATA[Experience Brief]]></category>
		<category><![CDATA[Interbrand]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=13</guid>
		<description><![CDATA[Exploring the “what ifs&#8230;?” of the user experience is the best way to avoid the “if onlys…” once the project is completed. And working with the client to prepare and approve an experience brief is the best opportunity to ask important questions about the fundamental underpinnings of a project, including audience, message, and purpose. Here’s [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">Exploring the “what ifs&#8230;?” of the user experience is the best way to avoid the “if onlys…” once the project is completed. And working with the client to prepare and approve an experience brief is the best opportunity to ask important questions about the fundamental underpinnings of a project, including audience, message, and <a title="The only content question that matters" href="http://blog.pixelmedia.com/content-strategy-popping-the-question/" target="_blank">purpose</a>.</p>
<p class="MsoNormal">Here’s a quick look at other people’s briefs. No jokes, please.</p>
<p><span id="more-13"></span></p>
<p class="MsoNormal"><strong>The Creative Brief</strong><br />
Ad agencies produce a <a href="http://en.wikipedia.org/wiki/Creative_brief">Creative Brief</a> at the earliest possible point in the project. The brief serves as an important internal document that helps the agency’s account teams and creative teams work together more effectively. It’s important to note that the creative brief doesn’t propose any creative approaches. In fact, the creative team is usually not involved in the drafting of the creative brief. The purpose of the creative brief is to give the creative team a reference point for developing a solution.</p>
<p class="MsoNormal"><strong>The Organizational Brief</strong><br />
I came across this <a href="http://mjbraide.com/mjblog/get-more-from-brand-strategy-part-one-the-organizational-brief/#more-15">post</a> recently and thought it offered a lot of valuable insight. The author, MJ Braide, has developed (and trademarked) the Organizational Brief as a method for companies to align their organizations to their brand strategies. A website redesign can trigger a lot of questions about an organization’s core business models, product lines, and go-to-market strategies. This is especially true for companies that have experienced a recent merger or acquisition: <a title="What an RFQ can tell you" href="http://blog.pixelmedia.com/content-strategy-the-story-behind-the-rfq/" target="_blank">the pressure is on</a> to upgrade the website, even if the organization is still be taking shape (or shaking out).</p>
<p class="MsoNormal"><strong>The Experience Brief<br />
</strong>Braide follows up with another good <a href="http://mjbraide.com/mjblog/get-more-from-brand-strategy-part-two-the-experience-brief%e2%84%a2/">post</a> about the Experience Brief as a tool for effective brand management. Like a Creative Brief, an Experience Brief can foster a better working relationship between client, agency, and team members. In our business, I think a tool like this could help our clients think in terms of “designing a user experience” rather than “designing a website.”</p>
<p class="MsoNormal">We can tailor an Experience Brief to inform all aspects of Experience Design, including Information Architecture, Content Strategy, User Research, Nomenclature, Visual Design, and Application Design. Because so many disciplines are involved in designing the user experience, there has to be a common point of reference for everyone. Having a brief in hand can prevent the gradual drift away from the original goals as individual interpretations and small variations build one upon the other. <strong></strong></p>
<p class="MsoNormal">Brand Agencies (and consultants like Braide) usually equate “User Experience” with “Brand Experience” and rely on brand attributes and messaging to define the user experience. From the <a href="http://www.interbrand.com/home.asp">Interbrand</a> Brand Glossary:</p>
<p class="MsoNormal" style="margin: 0in 0.5in 10pt;"><strong>Experience</strong>: This is when consumers have been exposed to various brand attributes. A successful brand experience happens with exposure to a brand’s most positive aspects, and this can happen in a store, through advertising and websites, or through word of mouth. The critical aspect is to have the experience match or exceed the customer’s expectations based on promises made in communications.</p>
<p class="MsoNormal">Messages set expectations; content satisfies expectations. <em>At a strategic level, the Experience Brief balances the user’s needs and expectations with the company’s messages and brand attributes. </em>It also provides a tactical framework for making decisions about content, navigation, and design at every phase of the project and serves as a benchmark for evaluating the outcome.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/content-strategy-the-brief/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Content Strategy: The Story Behind the RFQ</title>
		<link>http://www.pixelmedia.com/blog/content-strategy-the-story-behind-the-rfq/</link>
		<comments>http://www.pixelmedia.com/blog/content-strategy-the-story-behind-the-rfq/#comments</comments>
		<pubDate>Thu, 26 Jun 2008 21:27:02 +0000</pubDate>
		<pxlAuthorId>11</pxlAuthorId>
		<dc:creator>Luke Michel</dc:creator>
				<category><![CDATA[Website design]]></category>
		<category><![CDATA[business model]]></category>
		<category><![CDATA[Client Services]]></category>
		<category><![CDATA[Content strategy]]></category>
		<category><![CDATA[RFP]]></category>
		<category><![CDATA[RFQ]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=19</guid>
		<description><![CDATA[When we receive a Request for Quote/Proposal (RFQ/RFP) from a client, it marks the beginning of the process for us. But it’s the end of what was possibly a long and difficult process for the client. They’re relieved that it’s done; we’re anxious to start asking questions. They want to get going right away; we’re [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">When we receive a Request for Quote/Proposal (RFQ/RFP) from a client, it marks the beginning of the process for us. But it’s the end of what was possibly a long and difficult process for the client. They’re relieved that it’s done; we’re anxious to start asking questions. They want to get going right away; we’re saying, “Not so fast.”</p>
<p><span id="more-19"></span></p>
<p class="MsoNormal">So it shouldn’t be a surprise if a client grows impatient during the discovery phase of a project. To make matters worse, we may ask questions that reveal shortcomings in the client’s strategy or expose internal rifts between players and organizations. Even if the client understands the need to revisit the strategy or organization, he or she may have a sense of moving backward, not forward.</p>
<p class="MsoNormal">Getting the story behind the RFQ can help us learn more about the client’s needs and objectives before the discovery process, and help us ask better questions about the <a title="The one content question that matters" href="http://blog.pixelmedia.com/content-strategy-popping-the-question/" target="_blank">purpose </a>of the website and the content that will serve that purpose.</p>
<p class="MsoNormal" style="0.5in;">Here are some questions I’d ask:<em></em></p>
<p class="MsoNormal" style="0.5in;"><em>How long has the RFQ been in development?</em></p>
<p class="MsoNormal">The answer (a few days, a few weeks, or a few months) could indicate the degrees of urgency and difficulty in putting the RFQ together.</p>
<p class="MsoNormal"><em>Were there any organizational/business model changes that factored into the RFQ?</em></p>
<p class="MsoNormal" style="0.5in;">In the event of an organizational change, a merger or acquisition, or shift in the market dynamics, the company website is likely to be seen as a key indicator of a stable transition by customers, shareholders, press, and employees. That makes it a priority project even if all the pieces are not in place or details worked out.</p>
<p class="MsoNormal" style="0.5in;">Depending on the answer to the first question, a short timeframe may indicate that the company is under pressure to revise their site; a long timeframe could signal difficulty and frustration in getting all the players (old and new) to agree on the details of the redesign. In either case, there may be lingering confusion on the client side regarding project ownership, content ownership, and internal reviews.<em></em></p>
<p class="MsoNormal" style="0.5in;">
<p><em>Who has had direct input into the RFQ? </em></p>
<p class="MsoNormal" style="0.5in;">
<p class="MsoNormal" style="0.5in;">Many RFQs list the reviewers and approvers that will be involved during the project. There may be a one-to-one correlation between that list and those involved in shaping the RFQ. Learn about any “uninvolved” reviewers (their roles and responsibilities) and how, and when, they will be brought in to comment—they could be key to staying on track. If there has been a merger, ask who is “new,” either to the company or to the role. Your direct client may still be learning about some stakeholders.</p>
<p class="MsoListParagraph" style="0in;">The bottom line is to be sensitive to our client’s position and the effort involved in putting together the RFQ. <span> </span>Organizational change can add a level of stress and uncertainty to a project—no matter how solid the RFQ may seem. Asking some background questions and letting the client talk at length about the circumstances behind the RFQ can get the project—and the relationship—off on the right foot.</p>
<p class="MsoNormal">
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/content-strategy-the-story-behind-the-rfq/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Content Strategy: Popping the Question</title>
		<link>http://www.pixelmedia.com/blog/content-strategy-popping-the-question/</link>
		<comments>http://www.pixelmedia.com/blog/content-strategy-popping-the-question/#comments</comments>
		<pubDate>Thu, 19 Jun 2008 21:32:23 +0000</pubDate>
		<pxlAuthorId>11</pxlAuthorId>
		<dc:creator>Luke Michel</dc:creator>
				<category><![CDATA[Website design]]></category>
		<category><![CDATA[Content]]></category>
		<category><![CDATA[Content strategy]]></category>
		<category><![CDATA[Information Architecture]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=18</guid>
		<description><![CDATA[I admit it: I’m not much for theories and strategies about content. I’m inclined to grab a shovel and start digging in right off the bat. So I’m sometimes tongue-tied when I try to explain what a content strategist actually does. Unlike IA, content strategists don’t have a consistent set of practices and deliverables. We [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">I admit it: I’m not much for theories and strategies about content. I’m inclined to grab a shovel and start digging in right off the bat. So I’m sometimes tongue-tied when I try to explain what a content strategist actually does.</p>
<p><span id="more-18"></span></p>
<p>Unlike IA, content strategists don’t have a consistent set of practices and deliverables. We don’t produce site maps, or organizational models, or clickable wireframes, or any of that cool stuff. And we don’t create beautiful page layouts that finally—<em>finally</em>—look like a real website.</p>
<p class="MsoNormal">But—Lo!—I think I’ve found the answer.</p>
<p class="MsoNormal">The Content Strategist’s job is to ask a simple question: “What’s the point?”</p>
<p class="MsoNormal">We have to ask it about the website itself. We have to ask it about every bit of content. We have to ask it throughout the project. We have to ask it without looking like we don’t know what’s happening. And we have to ask it in such a way that our clients and colleagues don’t take offense.</p>
<p class="MsoNormal">Or perhaps we shouldn’t worry if anyone takes offense. “What’s the point?” isn’t a good question—it’s a great question. Maybe the only question.</p>
<p class="MsoNormal">OK, OK. Here’s <em>my</em> point: <strong>Content = Purpose</strong></p>
<p class="MsoNormal">Most clients are quite accommodating when we ask for content. We usually get a lot more that we ask for—and a lot less of what we actually need. If we don’t ask the question, “What’s the point?”at the very beginning, it’s a lot harder (and time consuming and expensive) to extract the content that <em>serves the purpose</em>.</p>
<p class="MsoNormal">So we should stop asking FOR the content and start asking ABOUT the content. Right after we pop the big question.</p>
<p class="MsoNormal">Join the discussion: <a title="Check out the whiteboard discussion" href="http://blog.pixelmedia.com/information-and-content-whats-the-difference/" target="_blank">What’s the difference between “content” and “information?”</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/content-strategy-popping-the-question/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Information and Content: What&#8217;s the Difference?</title>
		<link>http://www.pixelmedia.com/blog/information-and-content-whats-the-difference/</link>
		<comments>http://www.pixelmedia.com/blog/information-and-content-whats-the-difference/#comments</comments>
		<pubDate>Thu, 12 Jun 2008 21:14:51 +0000</pubDate>
		<pxlAuthorId>11</pxlAuthorId>
		<dc:creator>Luke Michel</dc:creator>
				<category><![CDATA[Website design]]></category>
		<category><![CDATA[Content]]></category>
		<category><![CDATA[Content strategy]]></category>
		<category><![CDATA[Experience Design]]></category>
		<category><![CDATA[Information Architecture]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=17</guid>
		<description><![CDATA[A few weeks ago, I posted a question on the whiteboard outside of the Experience Design Cubes: What’s the difference between ‘information” and “content?” I wasn’t looking for answers, just ideas and maybe a spirited discussion. Heck, the best I could do was. “I know it when I see it.” Check out some of the [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">A few weeks ago, I posted a question on the whiteboard outside of the Experience Design Cubes:</p>
<p class="MsoNormal" style="1in;"><strong>What’s the difference between ‘information” and “content?”</strong></p>
<p class="MsoNormal">I wasn’t looking for answers, just ideas and maybe a spirited discussion. Heck, the best I could do was. “I know it when I see it.” Check out some of the responses from the whiteboard.</p>
<p><span id="more-17"></span></p>
<ul>
<li><!--[if !supportLists]--><span style="Symbol;"><span><span style="normal;"> </span></span></span>You can have “too much information” but you can never have too much content.</li>
<li><!--[if !supportLists]--><!--[endif]-->To be information, you add value. To be content, you are happy.</li>
<li><!--[if !supportLists]--><!--[endif]-->Good content is information:<br />
Data = 48<span>°</span>, 52<span>°</span>, 67<span>°</span>, 55<span>°</span>, 58<span>°</span><br />
Information = 67<span>°</span>F<br />
Knowledge = “67<span>°</span>F is warm. I’ll wear shorts.”<br />
Wisdom = “However, I’m going to work, and shorts aren’t allowed there.”</li>
<li><!--[if !supportLists]-->Content is information that is contained.</li>
<li><!--[if !supportLists]--><!--[endif]-->Information = “short-twitch muscles” = power<br />
Content = “long-twitch muscles” = endurance</li>
<li><!--[if !supportLists]-->Content is contextually appropriate information.</li>
</ul>
<p class="MsoNormal" style="0.5in;">I posed the question when I heard the two terms used in close proximity and sometimes interchangeably. More questions followed. How does my role as Content Strategist intersect with that of the Information Architect? Does the IA turn content into information? Do I turn information into content? Why should a client pay for a Content Strategist <em>and</em> an Information Architect?</p>
<p class="MsoNormal" style="0.5in;">Is the distinction important? If not, why make the distinction?</p>
<p class="MsoNormal" style="0.5in;">Maybe I’m veering into Zen <a title="Wikipedia definition of Koan" href="http://en.wikipedia.org/wiki/Koan" target="_blank">koan</a> territory here, but I’d love to get perspectives from everyone who handles content—and that’s a lot of people. While there are several disciplines associated with Information (e.g., Information Architect, Information Designer, Information Analyst), there are few identified with Content. Is Content Strategy an emerging field, a clever re-naming of another discipline, or a made-up term?</p>
<p class="MsoNormal" style="0.5in;">Put another way: Everyone agrees that content is king. The Big Kahuna. The Holy Grail. But there seems to be some uncertainty as to what it is, where it comes from, and who is responsible for it.</p>
<p class="MsoNormal" style="0.5in;">And there has to be a better answer than, “I know it when I see it.”</p>
<p class="MsoNormal">
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/information-and-content-whats-the-difference/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Boston-based law firm motions for a more personable, dynamic website</title>
		<link>http://www.pixelmedia.com/blog/boston-based-law-firm-motions-for-a-more-personable-dynamic-website/</link>
		<comments>http://www.pixelmedia.com/blog/boston-based-law-firm-motions-for-a-more-personable-dynamic-website/#comments</comments>
		<pubDate>Wed, 07 Feb 2007 16:45:24 +0000</pubDate>
		<pxlAuthorId>1</pxlAuthorId>
		<dc:creator>PixelMEDIA</dc:creator>
				<category><![CDATA[Case studies]]></category>
		<category><![CDATA[Content strategy]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[Website design]]></category>

		<guid isPermaLink="false">http://blog.pixelmedia.com/?p=999</guid>
		<description><![CDATA[Business Challenge Burns &#38; Levinson LLP is a leading law firm headquartered in Boston with additional offices in Washington, D.C. and Providence, RI. Specializing in corporate litigation, intellectual property rights, real estate services, and private client services, the firm takes a unique approach to business by focusing on its people more than its might. It [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Business Challenge</strong><br />
Burns &amp; Levinson LLP is a leading law firm headquartered in Boston with additional offices in Washington, D.C. and Providence, RI. Specializing in corporate litigation, intellectual property rights, real estate services, and private client services, the firm takes a unique approach to business by focusing on its people more than its might. It drives success through long-term client relationships and individual entrepreneurship. As such, it required a website that captured this spirit and invited visitors to learn about the firm through navigable content, rich photography, and intuitive interactive design.<span id="more-999"></span></p>
<p><strong>PixelMEDIA Solution</strong><br />
To get a real feel for Burns &amp; Levinson—its people, practices, and philosophy—PixelMEDIA worked closely with the firm conducting a series of workshops, brainstorms, and interviews. PixelMEDIA’s User Experience and Creative Services teams spent time getting to know key principles who personified the firm’s deep-rooted commitment to client service. The knowledge gained from these sessions helped PixelMEDIA develop a professional, yet welcoming website that projects both credibility and partnership. Balancing custom photography and animation with revealing testimonials and rich content, the new site extends a warm, inviting presence to existing and prospective clients.</p>
<p>On the back end, PixelMEDIA built powerful, data-driven Flash® tools and DHTML scrolling menus of attorneys and their practices, which are easily scalable to support a growing firm. Custom tools enable Burns &amp; Levinson content owners to update the site quickly and efficiently.</p>
<blockquote>
<p class="MsoNormal">The team at PixelMEDIA really listened to us to help us develop a great product. It really shows the firm’s personality. —Angeline Mistretta, Director of Marketing, Burns &#038; Levinson LLP</p>
</blockquote>
<p><strong>The Impact</strong><br />
The Burns &amp; Levinson website has quickly become a popular site for a wide range of visitors. The site was a 2006 MITX award finalist in the Professional Services category, after having already won the Legal Marketing Association’s award for best website for a mid-sized law firm.</p>
<p>More importantly, the website meets several targeted objectives:</p>
<ul>
<li> Effectively communicates the firm’s breadth of services</li>
<li> Reinforces the firm’s personable, “client-first” approach to business</li>
<li> Scales seamlessly to support new areas of expertise in a growing firm</li>
<li> Offers helpful tools to connect visitors with attorneys</li>
</ul>
<p><strong>For this initiative, PixelMEDIA provided</strong></p>
<ul>
<li> User experience strategy and design</li>
<li> Content strategy and messaging architecture</li>
<li> Information architecture</li>
<li> Custom photography and visual design</li>
<li> Site design and development</li>
<li> Custom application development and content management tools</li>
<li> Search engine strategy</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.pixelmedia.com/blog/boston-based-law-firm-motions-for-a-more-personable-dynamic-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
