<?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>Usability Design &#187; information design</title>
	<atom:link href="http://usabilitydesign.digitalpractices.com/category/information-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilitydesign.digitalpractices.com</link>
	<description>by Garth A. Buchholz &#124; DigitalPractices Media Inc.  ISSN 1920-1893</description>
	<lastBuildDate>Tue, 25 May 2010 03:31:33 +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>Usability Differences between Web and Print Media</title>
		<link>http://usabilitydesign.digitalpractices.com/2009/05/14/usability-differences-between-web-and-print-media/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2009/05/14/usability-differences-between-web-and-print-media/#comments</comments>
		<pubDate>Thu, 14 May 2009 19:53:06 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web writing]]></category>
		<category><![CDATA[chart]]></category>
		<category><![CDATA[print content]]></category>
		<category><![CDATA[repurposing]]></category>
		<category><![CDATA[web content]]></category>

		<guid isPermaLink="false">http://digitalpractices.wordpress.com/?p=162</guid>
		<description><![CDATA[Web professionals often talk about the challenges of repurposing content, creating Web-friendly content, and adapting content for the Web. This chart outlines some of the differences in a succinct way. Do you have any other points you&#8217;d add to this chart? Let me know and I&#8217;ll credit your ideas on this blog if you want. Download PDF (72 Kb): [...]]]></description>
			<content:encoded><![CDATA[<p align="justify">Web professionals often talk about the challenges of repurposing content, creating Web-friendly content, and adapting content for the Web. <a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2009/05/usability-differences-between-web-and-print-media.pdf" target="_blank">This chart</a> outlines some of the differences in a succinct way.</p>
<p align="justify">Do you have any other points you&#8217;d add to this chart? <a href="mailto:Garth@DigitalPractices.com" target="_blank">Let me know</a> and I&#8217;ll credit your ideas on this blog if you want.</p>
<p align="justify">Download PDF (72 Kb): <a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2009/05/usability-differences-between-web-and-print-media.pdf" target="_blank">Usability Differences Between Web and Print Media</a></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2009/05/14/usability-differences-between-web-and-print-media/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spinning the Content Wheel</title>
		<link>http://usabilitydesign.digitalpractices.com/2008/11/04/spinning-the-content-wheel/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2008/11/04/spinning-the-content-wheel/#comments</comments>
		<pubDate>Tue, 04 Nov 2008 17:00:19 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web managers]]></category>
		<category><![CDATA[web strategy]]></category>
		<category><![CDATA[web writing]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[chart]]></category>
		<category><![CDATA[content wheel]]></category>
		<category><![CDATA[digital media]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/06/13/spinning-the-content-wheel/</guid>
		<description><![CDATA[When developing content, all design elements must be considered: editorial, interactive, visual and accessible. This chart graphically illustrates and elaborates on each of four elements:]]></description>
			<content:encoded><![CDATA[<p>When developing content, all design elements must be considered: editorial, interactive, visual and accessible. This chart graphically illustrates and elaborates on each of four elements:</p>
<p style="text-align:center;"><a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/06/contentwheel_490w.jpg"><img class="alignleft size-full wp-image-28" title="Content Wheel" src="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/06/contentwheel_490w.jpg" alt="Content Wheel" width="490" height="456" /></a><a title="Content Wheel" href="http://digitalpractices.files.wordpress.com/2007/06/contentwheel_490w.jpg"></a></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2008/11/04/spinning-the-content-wheel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Top 10 Mistakes in Web Design [ Top Ten Mistakes in Web Design ]</title>
		<link>http://usabilitydesign.digitalpractices.com/2008/05/08/top-10-mistakes-in-web-design/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2008/05/08/top-10-mistakes-in-web-design/#comments</comments>
		<pubDate>Thu, 08 May 2008 14:00:55 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[customer experience]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[interaction design]]></category>
		<category><![CDATA[mal practices]]></category>
		<category><![CDATA[navigation design]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[web analytics]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web strategy]]></category>
		<category><![CDATA[information architecture]]></category>
		<category><![CDATA[list]]></category>
		<category><![CDATA[mistakes]]></category>
		<category><![CDATA[top 10]]></category>
		<category><![CDATA[top ten]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/07/14/top-10-mistakes-in-web-design/</guid>
		<description><![CDATA[With apologies to Jakob Nielsen&#8217;s Top Ten, here are the Top 10 Mistakes in Web Design, from someone who has worked as a Web Manager and Web Strategist for many years: 1. The Web Strategy doesn&#8217;t follow the Business Strategy. Whether you&#8217;re designing for a Fortune 1000 corporation, a SOHO business, a government agency or [...]]]></description>
			<content:encoded><![CDATA[<h3><a href="http://digitalpractices.files.wordpress.com/2007/06/digitalpractices_170w.jpg"></a><a href="http://digitalpractices.files.wordpress.com/2008/06/digitalpractices-200h.jpg"></a>With apologies to <a href="http://www.useit.com/alertbox/9605.html" target="_blank">Jakob Nielsen&#8217;s Top Ten</a>, here are the Top 10 Mistakes in Web Design, from someone who has worked as a Web Manager and Web Strategist for many years:</h3>
<p><strong>1. The Web Strategy doesn&#8217;t follow the Business Strategy.</strong></p>
<p>Whether you&#8217;re designing for a Fortune 1000 corporation, a SOHO business, a government agency or a non-profit, your organization has a direction and a purpose, and your Web strategy must reflect and support that purpose. Read <a href="http://digitalpractices.com/tag/web-strategy/page/7/">The Chemistry of Web Strategy</a>.</p>
<p><strong>2. The Web Design doesn&#8217;t follow the Web Strategy.</strong></p>
<p>Assuming your organization has taken the time and effort to develop a documented Web Strategy, your entire Web Design (or redesign) project must be aligned with the objectives of this strategy as it is aligned with your organization&#8217;s Business Strategy (see #1 above).</p>
<p><strong>3. No one has developed a content strategy.</strong></p>
<p>Among all the discussions about the site&#8217;s presentation design (graphic design), its tools and applications, and its navigational structure, has your Web Design team given any thought to developing a <a href="http://digitalpractices.com/tag/etext/">Content Strategy</a>? If your team cannot clearly answers questions such as &#8220;How is all the site content being prioritized?&#8221; or &#8220;What is this content supposed to achieve for us? &#8221; or &#8220;Who are the 2-3 target audiences for this content?&#8221; then you need to write a Content Strategy or a <a href="http://www.digital-web.com/articles/content_or_dis_content/" target="_blank">Content Requirements Plan</a>.</p>
<p><strong>4. Users are not consulted in advance about the Web Design.</strong></p>
<p>Web analytics, surveys, focus groups, use cases, heuristic reviews — these are some of the tools of usability analysis. Often organizations will undertake a major Web Design or redesign project, then afterwards consult their users to try to confirm whether they did a good job designing the site. You can&#8217;t please everyone, but once you know how people want to use your site (task flow) and what content and applications are important to them, then you MUST consider these when developing your prototype Web Design.</p>
<p><strong>5. Users are consulted too much about the Web Design.</strong></p>
<p>Don&#8217;t be held hostage by user feedback or usability studies, either. When you continue to over-research what people want on your site, you can set up expectations on the part of your users that cannot be reasonably met. As well, you cannot possibly offer everything on your site that users want because the site has to align with your Web Strategy, which has to align with your Business Strategy. (See #1 again)</p>
<p><strong>6. The Web Design is confused with &#8220;look and feel&#8221;, &#8220;colors&#8221; and &#8220;branding&#8221;.</strong></p>
<p>Too often, early discussions about Web Design and redesign centre around &#8220;look and feel&#8221;. &#8220;How will our content fit the new design?&#8221; asks the marketing and communications staff. &#8220;Let&#8217;s not talk about Web Design yet,&#8221; say the developers. &#8220;Give us a few possible designs,&#8221; say the senior executives. If you are leading a Web Design project, one of your first tasks should be making the entire organization know that Web Design is not just about what the site will look like, but also how it will be constructed, how it will be used, and how it will be managed. Yes, <a href="http://www.digital-web.com/articles/why_your_intranet_needs_its_own_personality/" target="_blank">branding is a part of Web Design</a>, but it&#8217;s not all about branding, either.</p>
<p><strong>7. The Web Design has no muscle. </strong></p>
<p>Web sites that perform tasks for their users must have muscle to do it. That means not just search engines, payment processing, and other applications and databases that make the site work, but also the static content and how its information design helps users with the task of scanning, reading and interacting with content. Sites should be designed based on task analysis and task flow rather than by gathering heaps of content (focus on <em>how it will be used</em> to tell you <em>what will be used</em>).</p>
<p><strong>8. The Web Design has no brain.</strong></p>
<p>Web sites with muscle also have to have a brain that controls the muscle. The brain is the documented site architecture and interaction design — making the site logical and intuitive to most people through the application of best Web practices as well as a by thoroughly following how people want to use the site. The site&#8217;s critical <a href="http://digitalpractices.com/tag/navigation-design/">navigation design has to be based on task flow </a>so it will make sense to users.</p>
<p><strong>9. The Web Design has no soul.</strong></p>
<p>The soul of Web Design is the collective mass of human beings behind it that may hide behind the &#8220;Browser wall&#8221;, but nevertheless must imbue the site with humanity and human qualities. A Web Design has no soul if it doesn&#8217;t use <a href="http://www.cluetrain.com/" target="_blank">the language of the marketplace</a>. It will also have no soul if it does not provide ample means for users to <a href="http://digitalpractices.com/tag/customer-experience/page/2/">contact the Web site&#8217;s owners and administrators</a>. And a good Web Design also should have some images of the people who are behind that browser wall.</p>
<p><strong>10. The Web Design is not scalable.</strong></p>
<p>If a single generation of a Web Design cannot be sustained because it cannot accommodate new content and applications without distorting or mangling the original design, then it&#8217;s not scalable enough. A Web Design should allow for continuous improvement of the site, a kind of progressive evolution that allows for change as the rule, not the exception. While it&#8217;s common to implement minor site design changes through small variations, and to conduct major site redesign every couple of years or so, Web Designers should always be designing for the unforeseeable, the <a href="http://www.amazon.com/Black-Swan-Impact-Highly-Improbable/dp/1400063515" target="_blank">Black Swans</a>, and should always design two years into the future. Not &#8220;what we are now,&#8221; but &#8220;what we will become.&#8221;</p>
<p><strong>For more information on Web Design Strategy, contact </strong><strong>Garth@DigitalPractices.com</strong><strong>. </strong></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2008/05/08/top-10-mistakes-in-web-design/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Contentology Manifesto Vs. 1.1</title>
		<link>http://usabilitydesign.digitalpractices.com/2008/01/17/contentology-manifesto-vs-11/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2008/01/17/contentology-manifesto-vs-11/#comments</comments>
		<pubDate>Fri, 18 Jan 2008 04:15:54 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[accessibility + ud]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[convergent media]]></category>
		<category><![CDATA[info management]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[information science]]></category>
		<category><![CDATA[information technology]]></category>
		<category><![CDATA[interaction design]]></category>
		<category><![CDATA[multimedia]]></category>
		<category><![CDATA[new media]]></category>
		<category><![CDATA[rich media]]></category>
		<category><![CDATA[static media]]></category>
		<category><![CDATA[manifesto]]></category>
		<category><![CDATA[trends]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://digitalpractices.wordpress.com/2008/01/17/contentology-manifesto-vs-11/</guid>
		<description><![CDATA[ A Manifesto of Contentology, vs 1.1         What does &#8220;Contentology&#8221; mean? In this Manifesto, Contentology is a coined word that, in its strictest etymology, could mean &#8220;the science of content&#8221; or &#8220;the study of content&#8221;. The word &#8220;Contentology&#8221; is supposed to make people stop and think for a moment, and if it sounds absurd, [...]]]></description>
			<content:encoded><![CDATA[<h2> A Manifesto of Contentology, vs 1.1<br />
    </h2>
<p><strong>   What does &#8220;Contentology&#8221; mean?</strong></p>
<hr />
<p align="justify"><em>In this Manifesto, Contentology is a coined word that, in its strictest etymology, could mean &#8220;the science of content&#8221; or &#8220;the study of content&#8221;. The word &#8220;Contentology&#8221; is supposed to make people stop and think for a moment, and if it sounds absurd, then we have to ask ourselves why it sounds absurd.</em></p>
<p align="justify">Most people presume that the word content means ‘something that is within something else.&#8217; Yet this popular definition creates a tautology: &#8220;Content is content that&#8217;s inside something that seems to be content.&#8221;</p>
<p align="justify">Before the Internet became a tool for the masses, &#8220;content&#8221; or &#8220;contents&#8221; were simply vague terms for printed copy in a book or a magazine, or the food products inside a can of soup. The popular meaning usually referred to something that was being packaged for consumers, or something that was simply being stored or moved within containers.</p>
<p align="justify"><a title="Contentology.com" href="http://contentology.com" target="_blank">Visit the Contentology site</a></p>
<p align="justify"><span style="color: #800080;"><a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2008/01/contentology-manifesto.pdf">Dlownload Contentology Manifesto</a></span></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2008/01/17/contentology-manifesto-vs-11/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Usable Web Information Design</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/10/04/scalene-triangle-of-web-information-design/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/10/04/scalene-triangle-of-web-information-design/#comments</comments>
		<pubDate>Fri, 05 Oct 2007 05:33:49 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[best practices]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[customer experience]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user-centred design]]></category>
		<category><![CDATA[web strategy]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/10/04/scalene-triangle-of-web-information-design/</guid>
		<description><![CDATA[(click on thumbnail image above to view full size diagram)]]></description>
			<content:encoded><![CDATA[<p><a title="thm-Scalene-Triangle-Buchholz" href="http://digitalpractices.files.wordpress.com/2007/10/scalene-triangle-web-information-design-buchholz.jpg"></a></p>
<p class="MsoNormal" style="text-align:justify;"><span style="font-size:10pt;font-family:Calibri;"><em><strong><a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/10/scalene-triangle-web-information-design-buchholz.jpg"><img class="size-full wp-image-76 alignnone" title="Scalene-Triangle-Buchholz" src="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/10/2scalene-triangle-web-information-design-buchholz.jpg" alt="thm-Scalene-Triangle-Buchholz" width="516" height="307" /></a></strong></em></span></p>
<p class="MsoNormal" style="text-align:justify;"><span style="font-size:10pt;font-family:Calibri;"><em><strong>(click on thumbn</strong></em></span><span style="font-size:10pt;font-family:Calibri;"><em><strong>ail image above to view full size diagram)</strong></em></span></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/10/04/scalene-triangle-of-web-information-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Riding the Digital Tsunami</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/09/29/riding-the-digital-tsunami/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/09/29/riding-the-digital-tsunami/#comments</comments>
		<pubDate>Sat, 29 Sep 2007 20:00:49 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[HCI]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[info management]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[mal practices]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/09/29/riding-the-digital-tsunami/</guid>
		<description><![CDATA[How to put information overload into information overdrive In 2004, author Lawrence Lessig coined the term &#8220;email bankruptcy.&#8221; After he spent 80 hours in one week sorting through email that had been in his inbox since January 2002, he concluded that &#8220;without extraordinary effort&#8221; he would never be able to catch up. So he sent [...]]]></description>
			<content:encoded><![CDATA[<p><strong>How to put information overload into information overdrive</strong></p>
<p>In 2004, author Lawrence Lessig coined the term &#8220;email bankruptcy.&#8221; After he spent 80 hours in one week sorting through email that had been in his inbox since January 2002, he concluded that &#8220;without extraordinary effort&#8221; he would never be able to catch up. So he sent out an automated message to everyone who wrote him, then deleted all their emails.</p>
<p>Many office workers, and most senior managers and executives, dread email. Just a few years ago, in the late ‘90s, business leaders used to freely give out their email addresses to anyone who asked because it allowed them to reduce phone calls or keep their numbers private. Now email overload has become the biggest wave of the digital tsunami.</p>
<p>Are unmanageable email volumes really the issue, though? A 2005 Intranetjournal.com article cites several behavioral and time-management issues causing information overload at work. &#8220;External causes&#8221; such as constant interruptions by colleagues (either in person, by phone, or email) certainly contributed to employees&#8217; info stress, but there were also other &#8220;internal causes&#8221; for personal unproductivity and information overload, such as:</p>
<ul>
<li>An obsessive need to be &#8220;plugged in&#8221;, such as constantly checking email or voicemail;</li>
<li>Poor attention span and lack of focus;</li>
<li>Rampant multitasking and the inability to prioritize tasks.</li>
</ul>
<p>Email is not the only digital wave overwhelming workers. Ironically, Blackberrys (affectionately called &#8220;crackberries&#8221; by those who have become addicted to them), cellphones, (both voice and text messaging) Facebook sites, blogs and other electronic communications help keep us connected at all times while subversively disconnecting us as well.</p>
<p>The Consumer Research Center of the Conference Board recently released the results of a survey of 1,800 affluent consumers in seven countries. The report found that &#8220;the largest share of luxury consumers (44%) and the largest share of consumers in each country most strongly agree that &#8216;luxury is having enough time to do whatever you want and being able to afford it.&#8217; So, for luxury consumers worldwide, time is the ultimate luxury.&#8221;</p>
<p>One of the leading authorities on conquering information overload is David Allen, whose 2001 book, &#8220;Getting Things Done,&#8221; is a guide to &#8220;the art of stress-free productivity.&#8221; Allen writes about the problem of &#8220;open loops&#8221;: uncompleted tasks, unresolved issues and unanswered emails. His solution is to simplify by channelling all the tasks in our lives into a single &#8220;in box.&#8221;</p>
<p>Most productivity or time-management experts have two basic strategies for handling large volumes of incoming mail: 1) prioritize and organize emails by moving them into sub-folders or by using inbox rules, or 2) simply delete or ignore any emails that don&#8217;t require a response.</p>
<p>Here&#8217;s an example of organizing emails by priority. You can either use inbox rules to move emails from specific people or with specific subject lines to sub-folders. Or if you want to manually sort your email, you can create sub-folders as in the example below, or use coded labels, e.g. UR (Urgent &#8211; response required), IR (Important &#8211; response required), FR (Follow-up required); PR (phone response only), and NR (no response required &#8211; file or delete). This can help you triage your inbox so you respond the most important messages first.</p>
<p><img src="http://digitalpractices.files.wordpress.com/2007/09/inbox.jpg" alt="inbox_screenshot" /></p>
<p>The problem with inbox rules is they don&#8217;t always work as intended, and sometimes they can actually cause us to miss important messages unintentionally. And the problem with manually sorting emails by priority is that this process takes time as well. You have to at least browse a message to sort it by priority, and in the time it takes to browse some of them, you could almost skip the priority sorting and simply reply.</p>
<p>If time is a luxury for you and your employees, here are a few information management strategies to help you save time and turn information overload into information overdrive.</p>
<p><strong>1. EMAIL</strong></p>
<p>If you&#8217;re a busy executive or senior manager, delegate your emails as much as possible. Ask your Executive Assistant to read your email, respond to easy requests, and then send more urgent or time-sensitive emails to your attention. You could even request a second company email address that is private &#8211; available only to a small, select group.</p>
<p>If you don&#8217;t have an assistant, and you can&#8217;t control what email gets sent to you, remember that answering email is an administrative task like managing your budget or attending meetings. Find a quiet time of day when other staff are not around (e.g. 30 minutes before the office opens or 30 minutes before most people get back from lunch), then dedicate that time to checking voicemail and sorting/responding to emails.</p>
<p>It&#8217;s important not to lose productive time by getting the &#8220;email twitch&#8221;: feeling the urge to check your inbox every minute or every time you hear an email notification &#8220;ping.&#8221; Blackberrys are a wonderful to access your email but should be turned off when you&#8217;re at a meeting or working on something. Same thing applies to your personal Webmail accounts, e.g. Gmail or Hotmail. Some organizations allow employees to check their personal Webmail accounts from the office, but if you&#8217;re already feeling overloaded by your email inbox at work, don&#8217;t waste your time checking your personal emails during work hours.</p>
<p>Another email management strategy is to undertake some &#8220;human engineering&#8221; strategies to change the way people send emails to you. You can also use your inbox rules not only to move mail into different folders, but also to create an automated message that is sent to everyone who sends you an email message. For example: &#8220;Thank you for contacting me by email. I receive a large number of communications by email each day, so I can only respond to emails by priority. If your message is of an urgent nature, please call me at XXX-XXXX or drop by my office. If I do not respond to your email immediately, please be assured that I will follow-up on it as soon as possible.&#8221;</p>
<p>Of course, every time someone emails you, they will receive an automated message, and these will fill up the inboxes of chronic emailers &#8211; which should reinforce why you are trying to manage your own email volumes in a productive way!</p>
<p><strong>2. CELLPHONES/BLACKBERRYS</strong></p>
<p>Two things about voice communications devices create information management problems:</p>
<ol>
<li>We have too many devices &#8211; we have a home landline phone, a personal cell, an office landline, a cellphone/Blackberry and sometimes even more.</li>
<li>We have too many voicemails, usually one for each of the devices mentioned above.</li>
</ol>
<p>Make it a personal policy NOT to check your personal voicemail during the workday. At work, limit who has your business cell number to your boss, your assistant, and a few colleagues. If you have a landline, too, forward your landline to the cellphone when you&#8217;re out of the office, or vice versa when you&#8217;re in the office. Avoid having to login to several different voicemails by limiting the number of phones you use. But when you leave the office, leave your business cell and Blackberry at work if you can.</p>
<p><strong>3. WEBSITES/FACEBOOK/MYSPACE/BLOGS</strong></p>
<p>The World Wide Web is a great time-waster for employees and managers when they succumb to the temptation of browsing non-work-related sites during office hours. Well-intentioned Internet usage policies can help a bit, but instead of prohibiting such behavior, why not find ways to redirect your employees&#8217; information explorations and exchanges into something productive? Channel your staff&#8217;s desire to express themselves by allowing them to create their own internal &#8220;homepages&#8221; profiling who they are and what they do, participate in collaborative workspaces (e.g. Sharepoint), or post to company blogs that are semi-moderated. New generations in the workforce will thrive on this, and you may find that this activity pays off in better internal communications, collaboration and knowledge management.</p>
<p><strong><em>Garth A. Buchholz is an author, educator and corporate Web strategist at DigitalPractices. </em></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/09/29/riding-the-digital-tsunami/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Three Filters for eText Design</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/06/23/three-filters-for-etext-design/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/06/23/three-filters-for-etext-design/#comments</comments>
		<pubDate>Sat, 23 Jun 2007 16:50:10 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[eText]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[web writing]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/06/23/three-filters-for-etext-design/</guid>
		<description><![CDATA[View full-size diagram  1. The content strategy determines the function of the etext (how it will be used, read, etc). 2. The function of the text determines how the etext should be designed. 3. The eText design impacts the how the etext can be experienced. (along with other factors such as physical environment, type of [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/06/3-filters-for-etext-design-full.jpg"><img class="size-medium wp-image-47 alignnone" title="3 Filters for eText Design - thumbnail" src="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/06/3-filters-for-etext-design-thumb-300x166.jpg" alt="3 Filters for eText Design - thumbnail" width="300" height="166" /></a></p>
<p><a href="http://usabilitydesign.digitalpractices.com/wp-content/uploads/2007/06/3-filters-for-etext-design-full.jpg" target="_blank">View full-size diagram</a> </p>
<p><strong><em></em></strong></p>
<p style="text-align: left;"><em></em></p>
<p>1. The content strategy determines the function of the etext (how it will be used, read, etc).</p>
<p>2. The function of the text determines how the etext should be designed.</p>
<p>3. The eText design impacts the how the etext can be experienced. (along with other factors such as physical environment, type of screen, etc)</p>
<p>4. The user experience impacts the publisher/user loop and helps determine how content is developed and maintained.</p>
<p style="text-align: center;"><strong><em><span>Copyright 2007-2009 Garth A. Buchholz | DigitalPractices All Rights Reserved</span></em></strong></p>
<p class="MsoNormal" style="text-align:center;margin:0;" align="center"><strong><em><span style="font-size:11pt;font-family:Calibri;">For free reprint permission, contact <span style="color:olive;"><a href="mailto:Garth@DigitalPractices.com" target="_blank"><span style="color:olive;">Garth@DigitalPractices.com</span></a></span></span></em></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/06/23/three-filters-for-etext-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How people navigate by task flow</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/06/14/how-people-navigate-by-task-flow/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/06/14/how-people-navigate-by-task-flow/#comments</comments>
		<pubDate>Thu, 14 Jun 2007 17:00:10 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[interaction design]]></category>
		<category><![CDATA[navigation design]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[task flow]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user-centred design]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web managers]]></category>
		<category><![CDATA[web strategy]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/06/14/how-people-navigate-by-task-flow/</guid>
		<description><![CDATA[In determining site navigation options for Web sites, many Web administrators/developers are satisfied to offer several navigation options to people (e.g. site search + menus + static links) as well as redundant navigation methods (allowing users to choose several ways to arrive at the same content). However, most people use more than one navigation choice [...]]]></description>
			<content:encoded><![CDATA[<p>In determining site navigation options for Web sites, many Web administrators/developers are satisfied to offer several navigation options to people (e.g. site search + menus + static links) as well as redundant navigation methods (allowing users to choose several ways to arrive at the same content).</p>
<p>However, most people use more than one navigation choice during a single session search for content, and each choice during that session is determined, more often than not, by a specific task flow. For example, if you know what you&#8217;re looking for on a retail site, you&#8217;ll want to navigate by the product or service categories, but if you encounter problems, you&#8217;ll want to navigate by organizational structure (e.g. finding which part of the organization is responsible for a product or service) to seek help.</p>
<p>So in the first case, your navigation is driven by a scenario where you are purchasing something, and in the second case it is driven by a scenario where you are wanting to contact someone or some area of responsibility.  </p>
<p>The chart below outlines some general reasons users make navigation choices, although a more refined analysis can be done when one is looking at specific case studies or organizations. Keep in mind that at any stage of the search, depending on the user&#8217; previous experiences, they may give up and abandon their navigation efforts altogether.</p>
<p>Rather than feeling that their own search/navigation methods failed, or are lacking the necessary skills, most people will instead feel frustration, resentment and even anger, and blame the site design or site administrators for their lack of success.</p>
<table border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td width="111" valign="top">
<h5>Method of Navigation</h5>
</td>
<td width="321" valign="top">
<h5>Usability Reason(s) for Choice</h5>
</td>
</tr>
<tr>
<td width="111" valign="top"> </td>
<td width="321" valign="top"> </td>
</tr>
<tr>
<td width="111" valign="top">
<h5>External search engine</h5>
</td>
<td width="321" valign="top">People will use a general search engine to broadly search for specific content within a site when they are not sure which site(s) to search, or when they know which site to search but they are not familiar with it and prefer to search it by keyword. Often this means when they find content, they end up having to backtrack through the site or click through the site to further narrow down their choices.<span style="color:#000000;">Many people don&#8217;t know that you can use advance search features on search engines to restrict your search query to that site alone. Also, many sites are indexed more thoroughly by external search engines than by their own internal site search engine.  </span></td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Internal site search</h5>
</td>
<td width="321" valign="top">People will use site search (a search tool provided by the site itself) when they are broadly searching for specific content within a site. Some people simply prefer to enter a keyword and search for results, hoping the content they want will appear in the top 10 pages returned by the engine. Others use the site search because the navigation on the site&#8217;s homepage is:</p>
<ul>
<li><span style="color:#000000;">unavailable/not offered on the homepage</span></li>
<li><span style="color:#000000;">available, but past user experience with it was negative/unsuccessful</span></li>
<li><span style="color:#000000;">unclear/ambiguous/complicated</span></li>
<li><span style="color:#000000;">lacks &#8220;information scent&#8221; or &#8220;intuitive&#8221; labelling</span></li>
<li><span style="color:#000000;">not offered as a dropdown/flyout/rollover menus)</span></li>
<li><span style="color:#000000;">offered as a menu but users don&#8217;t realize it is a menu</span></li>
<li><span style="color:#000000;">cluttered with too much information</span></li>
</ul>
</td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Global Static Navigation</h5>
</td>
<td width="321" valign="top">People use global (or ‘persistent&#8217;) static or fixed navigation (links that don&#8217;t dropdown or rollout or slideout into menus) when they are looking for general areas of information or high level categories on a site and are willing to go deeper into the site to explore the second level content, scan their navigation options, and gradually narrow their search.</td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Sitemap Navigation</h5>
</td>
<td width="321" valign="top">Sitemaps are usually a global static navigation page that provides a high level structural view (usually using text links and very few graphics) of all of the major categories and subcategories found within a single, or even its subsites as well.<span style="color:#000000;">People will often look for a Sitemap link on a site when they want to quickly get a sense of what a site contains and how it is structured, especially when the site&#8217;s overall structure is not clear, apparent or detailed enough on the homepage or the global menus. Search engines often look for sitemap pages to help them accurately index a site, which I another reason why sitemaps should be kept current and accurate either by manual methods or by a system that updates them dynamically.</span></td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Global Interactive Navigation</h5>
</td>
<td width="321" valign="top">People use global (or ‘persistent&#8217;) interactive navigation (e.g. dropdown or flyout menus) when they want to view high level categories on a site and see what kind of content those areas contain before making a selection and exploring them further at the second level.  </td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Organizational-view navigation</h5>
</td>
<td width="321" valign="top">People use organizational-based navigation links (e.g. links to specific departments, divisions or other formal organization units) when they think that they can find information they are seeking within a particular part of the organization offers. They will also use organizational navigation when they are seeking help from someone in the organization on something relating to a particular product or service, i.e. they are navigating by area of responsibility.</td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Service-view Navigation</h5>
</td>
<td width="321" valign="top">People use service-based navigational links when they are seeking content related to a particular service or product, but are either uncertain which part of the organization offers it, or are simply unfamiliar with the organization&#8217;s products or services and want to find information that is written or structured in a way that they will understand.  </td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Graphical Navigation</h5>
</td>
<td width="321" valign="top">People use graphical navigation (e.g. ads, buttons, icons and other images) when these navigation aids are bright, distinctive, eye-catching and intuitive; also, when text links on a page are confusing, ambiguous, poorly labelled, hard to read or otherwise. However, usability studies have found that text links are still more popular in terms of usage than graphical links, probably because people have a tendency to read text and understand it quickly, while many graphical navigation links can be ambiguous or unclear.</td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Breadcrumb Navigation</h5>
</td>
<td width="321" valign="top">People use forms of breadcrumb navigation when navigation structure on a site is deep and complex, or when they reach a page using another navigation method and realize that they have to go up or down one or more levels to find the content they want. Breadcrumbs do not show as much of a high-level view as sitemaps because they are contextual to where the user is on a site when hey are viewing the chain of breadcrumb links.</td>
</tr>
<tr>
<td width="111" valign="top">
<h5>Contextual Navigation</h5>
</td>
<td width="321" valign="top">People use contextual or local navigation (which can be either static or fixed links or menus or a combination of both) when they reach within a section of a site or within a subsite and want to restrict their continuing navigate efforts to that specific pat of the site to the exclusion of other parts. If this narrowed navigation attempt fails, they will return to broader navigation methods or bailout (abandon their efforts). </p>
<h6>For more information on navigating by task flow, contact: <a href="mailto:Garth@DigitalPractices.com">Garth@DigitalPractices.com</a></h6>
</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/06/14/how-people-navigate-by-task-flow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The 10 Commandments of Information Design</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/06/06/the-10-commandments-of-information-design/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/06/06/the-10-commandments-of-information-design/#comments</comments>
		<pubDate>Thu, 07 Jun 2007 04:25:11 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[meta text]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[style guide]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[web writing]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/06/06/the-10-commandments-of-information-design/</guid>
		<description><![CDATA[1. Print content is structurally and functionally different from online content.  Understand the differences when you write for Web sites. Print is formally written and passively read. It&#8217;s linear, narrative, dated and presents a continuous view. Online content is informally written, chunked out, non-linear, interactive, dynamic and current. One involves reading paper, the other involves [...]]]></description>
			<content:encoded><![CDATA[<p align="justify">1. <strong>Print content is structurally and functionally different from online content.</strong>  Understand the differences when you write for Web sites. Print is formally written and passively read. It&#8217;s linear, narrative, dated and presents a continuous view. Online content is informally written, chunked out, non-linear, interactive, dynamic and current. One involves reading paper, the other involves reading light. For further explanation of the differences, read this article on <a href="http://www.useit.com/alertbox/990124.html">Jakob Nielsen&#8217;s Web site</a>. </p>
<p align="justify">2. <strong>Don&#8217;t just &#8220;repurpose&#8221; documents; write &#8220;Webitorial&#8221; content.</strong> One of the worst things you can do is to simply &#8220;PDF&#8221; everything. &#8220;Repurposing&#8221; or means when you repackage a document created for print and simply attach it to a Web site in Word, Acrobat, Excel or other such popular formats. While sometimes this is necessary, it&#8217;s the laziest, most ineffective way to put content on the Internet. Instead of editorial writing, write &#8220;Webitorial&#8221; by re-thinking how the content can be rewritten, laid out and designed in context with its specific online environment.  Read <a href="http://www.ondemandpublishing.com/EP_Repurposing.html">The Challenges of Repurposing</a> and point #6 in this <a href="http://www.useit.com/alertbox/9706b.html">Jakob Nielsen article</a>.    </p>
<p align="justify">3. <strong>Online content is not just about words.</strong> In Latin, content basically means a wrapper that contains something else. It&#8217;s images, hyperlinks, applications, streaming media, etc. When you write for the Internet, think &#8220;presentation&#8221; and &#8220;interaction.&#8221; Factor in the other content objects that may be part of it. Analyze the environment where the content will be found. If you were writing for a television ad, for example, you wouldn&#8217;t simply write text without knowing what audio and visuals will be part of it.   </p>
<p align="justify">4. <strong>Words are graphical images, too.</strong>  <a href="http://lrs.ed.uiuc.edu/j-levin/gp/">The layout of a Web page</a> impacts its readability. People often notice the font style, the color of the text, the size of the text and how the text appears as a visual block or grouping before they actually extract its meaning. Layout and design are critical in a visual medium like the Web, so learn about typography, too.</p>
<p align="justify">5. <strong>Chunk it out, chunk it down.</strong> Even if you&#8217;re writing an actual content object such as a Word document or a PDF, content on the Internet has to be easily scannable. Partly because of the Internet and broadcast media, people have far less patience and tolerance for large blocks of narrative text. When you create new Webitorial copy, make sure it&#8217;s &#8220;chunked out&#8221; (broken into smaller blocks of text separated by a break) or, if you&#8217;re editing something for the Internet, chunk it down. Another technique is to use bulleted or numbered lists wherever possible rather than embedding this information within a block of text. Remember &#8211; if no one reads it, what value will it have? </p>
<p align="justify">6. <strong>Write strong meta-text</strong> (navigation titles, headlines, subheads, cutlines, labels, etc).  Writing headlines, subheads, cutlines (captions), labels and other &#8220;meta-text&#8221; (also called metacontent or microcontent) is often the most effective way to make your textual content readable on the Internet. Internet readers have a &#8220;search-and-retrieve&#8221; mentality &#8211; they prefer to scan for the information or keywords or links they need, while bypassing the rest.  Good headlines and content labels also help the reader to cognitively understand the organization and navigation of the content. </p>
<p align="justify">7. <strong>Don&#8217;t reinvent the wheel &#8211; just link to it.</strong> How much of your copy could be trimmed down if you simply linked to other Web pages that offered the same information? Here&#8217;s my 100/25 rule of content originality on the Web: If the Web were like 12 people having a meeting in a boardroom:  One person would be saying something original; two people would be commenting on it; and nine people would simply be referencing what the first three had been saying. 100% of the content is created by 25% of the people. Readers like to interact on the Web, so give them links as non-linear &#8220;rabbit trails&#8221; they can follow. </p>
<p align="justify">8. <strong>Use the traditional newspaper structure for &#8220;inverted pyramid&#8221; writing.</strong>  In most cases, good Internet writing is like <a href="http://www.mtsu.edu/~kblake/171/pyramid.htm">newspaper-style writing</a> because, like newspapers, it&#8217;s a fast read, involves a lot of content and has to catch the reader&#8217;s attention. Make sure your five W&#8217;s (who, what, when, where, why, and also how) are close to the top of the text. Details of lesser importance should follow, from general to specific &#8211; that&#8217;s why the pyramid is wide at the top and narrow at the bottom.  The idea is this: If the reader only reads the headline, they should have a good idea of what the article is about. If they read only the first few lines, they should have a very good idea of the main points in the article.</p>
<p align="justify">9. <strong>Make the writing compelling, personal and energetic.</strong> <a href="http://owl.english.purdue.edu/handouts/grammar/g_actpass.html">Active voice writing</a> is always the best. Use consistent style and conventions. Use &#8220;you&#8221; when appropriate to personalize the text. Take a stand. Give your writing attitude. People like to read writing that feels truthful, creative, positive and individual. <a href="http://www.cluetrain.com/">Avoid &#8220;marketese&#8221; or corporate jargon</a>, but do write promotionally, as long as it&#8217;s truthful (if you sound bored about what you&#8217;re writing about, the reader will be bored, too.)  You can use &#8220;plain writing&#8221; style without sounding plain. And most importantly, keep it tight, unpretentious and free of unnecessary verbiage.</p>
<p align="justify">10. <strong>Know your Internet community.</strong> In print, you have to know your readers, and in broadcast, you have to know your audience. On the Internet, it&#8217;s also crucial to know your &#8220;community&#8221; of readers. Are you creating content for a portal? An Intranet site? An opt-in email newsletter? A Web log (blog)? What are their interests? Education? Age range? Biases? And what is their user experience on the Internet site you are writing for? How will they use the information, and how will the other information in that environment be used? When you write for the Internet, you write for a community&#8230;one reader at a time.   </p>
<p align="justify"><strong><em>Copyright 2006-2009 Garth A. Buchholz | DigitalPractices All Rights Reserved</em></strong></p>
<p align="justify"><strong><em>For free reprint permission, contact <a href="mailto:Garth@DigitalPractices.com">Garth@DigitalPractices.com</a></em></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/06/06/the-10-commandments-of-information-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Communications professionals: When it comes to the Web, don&#8217;t be a broken link</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/02/01/communications-professionals-when-it-comes-to-the-web-dont-be-a-broken-link/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/02/01/communications-professionals-when-it-comes-to-the-web-dont-be-a-broken-link/#comments</comments>
		<pubDate>Thu, 01 Feb 2007 20:00:30 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[contentology]]></category>
		<category><![CDATA[eMarketing]]></category>
		<category><![CDATA[eText]]></category>
		<category><![CDATA[information design]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[style guide]]></category>
		<category><![CDATA[web writing]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/03/01/communications-professionals-when-it-comes-to-the-web-dont-be-a-broken-link/</guid>
		<description><![CDATA[No more excuses. If professional communicators want I.T. professionals to give them a little more respect, and quit calling their work &#8220;fluff&#8221;, they need to start adhering to some clear standards and technical rigor. Yes, communications is also a &#8220;technical&#8221; craft, even though it&#8217;s more often included under the heading of &#8220;arts&#8221; rather than &#8220;science&#8221;, and as [...]]]></description>
			<content:encoded><![CDATA[<p><strong>No more excuses.</strong></p>
<p>If professional communicators want I.T. professionals to give them a little more respect, and quit calling their work &#8220;fluff&#8221;, they need to start adhering to some clear standards and technical rigor. Yes, communications is also a &#8220;technical&#8221; craft, even though it&#8217;s more often included under the heading of &#8220;arts&#8221; rather than &#8220;science&#8221;, and as someone who has been a communications professional, I know what kind of discipline, experience and skills it requires.</p>
<p>When I put on my &#8220;Web&#8221; hat, though, I have to say that I am disappointed at how many communications professionals are making excuses about why they don&#8217;t understand the Web, or how they don&#8217;t have the skills to develop content for the Web. Maybe some of our older colleagues (50+ years old) who worked in communications before the Internet era can say they haven&#8217;t developed the skill set to do Web communications, but it seems that many of our younger communicators (even those in their 30s) should be highly skilled in Web communications by now&#8230;yet they are not.</p>
<p>At the risk of offending many of my colleagues in the Communications field, here is an urgent call for the reform of our practices:</p>
<ul>
<li><strong>Don&#8217;t be intimidated by those in information technology roles who hold highly specialized technical skills </strong>- the principles for developing good Web content are the same no matter what technology is used. Learn about what IT people do. Learn the jargon. Keep up on new developments in technology, even if it&#8217;s only at a superficial level. </li>
<li><strong>Don&#8217;t relinquish control of communications work to people who are not communications professionals</strong> &#8211; whether you know it or not, there are standards and techniques for what you do, and if your colleagues or clients aren&#8217;t aware of them, document them and then follow them faithfully. If your communications practice doesn&#8217;t demonstrate rigor and discipline, you will never gain the respect of I.T. professionals or senior managers.</li>
<li><strong>Learn information design. Learn information design</strong>.  Communications has become more than just writing, speaking and presenting &#8211; it&#8217;s also about business, design and technology, all channels for communications. Learn about information design for the Web so that you have a more holistic understanding of everything that impacts Web communications.</li>
<li><strong>Don&#8217;t write for Web the way you write for print. </strong>Above all, learn the differences between print and electronic communications, and demonstrate superior skills in creating communications for both media. There is simply no excuse &#8211; <em>no excuse</em> &#8211; for not having the skills to write for online media. The Web is not a recent phenomenon anymore, it&#8217;s a cultural pillar, a leading arrow for change in the way we live our lives and communicate with each other. When it comes to the Web, don&#8217;t be a broken link. </li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/02/01/communications-professionals-when-it-comes-to-the-web-dont-be-a-broken-link/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
