<?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; mal practices</title>
	<atom:link href="http://usabilitydesign.digitalpractices.com/category/mal-practices/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>The Ecology of Content: Why we can, and should, preserve content on the Web</title>
		<link>http://usabilitydesign.digitalpractices.com/2009/01/01/the-ecology-of-content/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2009/01/01/the-ecology-of-content/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 19:00:58 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[content]]></category>
		<category><![CDATA[digital practices]]></category>
		<category><![CDATA[info management]]></category>
		<category><![CDATA[mal practices]]></category>
		<category><![CDATA[reference]]></category>
		<category><![CDATA[web analytics]]></category>
		<category><![CDATA[web managers]]></category>
		<category><![CDATA[archives]]></category>
		<category><![CDATA[ecology]]></category>
		<category><![CDATA[preserving content]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/04/01/the-ecology-of-content/</guid>
		<description><![CDATA[Why we can, and should, preserve content on the Internet An ocean is never the same body of water because it&#8217;s always moving changing, evaporating and being replenished by new rainwater and runoff. Likewise, Internet content is an ocean of information that with content that is evaporating almost as quickly as new content flows into [...]]]></description>
			<content:encoded><![CDATA[<p align="justify"><strong>Why we can, and should, preserve content on the Internet</strong></p>
<p align="justify">An ocean is never the same body of water because it&#8217;s always moving changing, evaporating and being replenished by new rainwater and runoff. Likewise, Internet content is an ocean of information that with content that is evaporating almost as quickly as new content flows into it.</p>
<p align="justify">We&#8217;ve heard of the <a href="http://www.internettutorials.net/deepweb.html">deep Web</a> and the invisible Web, private or subscriber-based databases that are not accessible to indexing by public search engines (intentionally or unintentionally), but what about millions of links that are broken when content types or entire Web sites are removed from production? Or domain names that expire?</p>
<p align="justify">While we might not miss &#8220;Kyle&#8217;s Frat Party&#8221; site, what about information of value to journalists, researchers and academics? For online journal publishers and academic researchers who cite Internet content in the form of URLs, this is an especially troublesome issue. In 2003, the <a href="http://www.sfgate.com/cgi-bin/article.cgi?file=/c/a/2003/11/30/MNGBD3BLD61.DTL">San Francisco Chronicle reports</a>:</p>
<p align="justify"><em>&#8230;a growing number of scientists and scholars who are nervous about their increasing reliance on a medium that is proving far more ephemeral than archival. In one recent study, one-fifth of the Internet addresses used in a Web-based high school science curriculum disappeared over 12 months. </em><em>Another study, published in January, found that 40 percent to 50 percent of the URLs referenced in articles in two computing journals were inaccessible within four years.</em></p>
<p align="justify"><strong>ArchiveIt 2.0</strong></p>
<p align="justify">One solution offered recently in a July 26, 2006 news release from <a href="http://www.archive.org/">The Internet Archive</a>, a non-profit organization dedicated to preserving the Web and other digital archives, is the <a href="http://www.archive-it.org/">Archive-It 2.0 service</a>, which allows the permanent capture of Web-based information for reference and archival purposes. Existing partners in this effort include the featured collections of the <a href="http://www.archive-it.org/collections/university_of_toronto_web_archives">University of Toronto</a>, <a href="http://www.archive-it.org/collections/indiana_university_web_sites">Indiana University</a> and <a href="http://www.archive-it.org/collections/north_carolina_state_government_web_site_archive">North Carolina State Archives</a>.</p>
<p align="justify"><em>Archive-It 2.0 enables digital archivists, library and museum professionals to create more tailored, relevant and search-friendly collections of up to 10 million URLs based on regular Web crawls across selected websites. Through test crawls, subscribers may see what kind of web material would populate a certain collection before actually archiving them permanently. An optional paid feature within Archive-It 2.0, Archive-It Pro, allows subscribers to not only set caps on how many web documents are collected from a website over time, but also block the collection of materials from specific websites altogether. The digital collections, as a result, are focused and more easily managed, because irrelevant materials do not find their way into an institution&#8217;s archives. </em></p>
<p align="justify">Another issue is <a href="http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html">Web 2.0</a> sites, <a href="http://adaptivepath.com/publications/essays/archives/000385.php">Ajax</a>, Flash, and the increasing number of sites publishing information dynamically. Unlike static pages that can be archived as a hard document, dynamic pages feature content on demand that changes based on what information is requested from a database. Most blog sites offer Permalinks so search engines can index a permanent (or semi-permanent) record of journal entries, but as the Goddard Library Web Project discovered in a <a href="http://www.dlib.org/dlib/november04/hodge/11hodge.html">D-Lib Magazine article published in Nov 2004</a>, the Web is becoming increasingly inaccessible for archival purposes:</p>
<p align="justify"><em>We encountered several problems when performing the crawl on the increasingly complex scientific web sites. The most common problem resulted from the increasingly dynamic nature of those web sites. This includes content that is controlled by Javascript and Flash technologies, and dynamic content driven from database queries or content management systems. The crawling tool is unable to crawl a web page containing a search form that queries a database. </em></p>
<p align="justify"><strong>ISO Standards for publications</strong></p>
<p align="justify">While librarians and Internet archivists try to address the issue of vanishing or inaccessible Internet content, Web site owners and content developers can play a part in helping libraries and archives document and preserve the Web. On Canada&#8217;s national <a href="http://collectionscanada.ca/">Library and Archives site</a>, there&#8217;s an excellent paper on <a href="http://www.collectionscanada.ca/9/13/index-e.html">Electronic Publishing</a> published in 2001. While this was intended for Canadian publishers, the principles can be broadly applied to any electronic publishers on the Web. This matrix explains the scope of what the document means by electronic publishers.</p>
<p align="justify"><strong>Serial publications</strong></p>
<p align="justify">If you publish an online journal, ezine or other serial publication online, applying for an ISSN (International Standard Serial Number) is a way to assign &#8220;<a href="http://www.collectionscanada.ca/issn/index-e.html">a unique code for identifying serial publications, such as periodicals, newspapers, annuals, journals and monographic series</a>&#8221; (Canada&#8217;s ISSN) and &#8220;<a href="http://www.loc.gov/issn/issnbro.html">magazines, newspapers, annuals (such as reports, yearbooks, and directories), journals, memoirs, proceedings, transactions of societies, and monographic series</a>&#8221; (the United States ISSN). For serials distributed on the Internet and World Wide Web, the ISSN should appear on the first screen of the item.</p>
<p align="justify">While publishers are not legally obliged to use an ISSN, the U.S. site lists the <a href="http://www.loc.gov/issn/issnbro.html">benefits of applying for an ISSN</a>:</p>
<p align="justify">The ISSN should be as basic a part of a serial as the title. The advantages of using it are abundant and the more the number is used the more benefits will accrue.</p>
<ul>
<li>
<p align="justify">ISSN provides a useful and economical method of communication between publishers and suppliers, making trade distribution systems faster and more efficient.</p>
</li>
<li>
<p align="justify">The ISSN results in accurate citing of serials by scholars, researchers, abstracters, and librarians.</p>
</li>
<li>
<p align="justify">As a standard numeric identification code, the ISSN is eminently suitable for computer use in fulfilling the need for file update and linkage, retrieval, and transmittal of data.</p>
</li>
<li>
<p align="justify">ISSN is used in libraries for identifying titles, ordering and checking in, and claiming serials.<br />
ISSN simplifies interlibrary loan systems and union catalog reporting and listing.</li>
<li>
<p align="justify">The U.S. Postal Service uses the ISSN to regulate certain publications mailed at second-class and controlled circulation rates.</p>
</li>
<li>
<p align="justify">The ISSN is an integral component of the journal article citation used to monitor payments to the Copyright Clearance Center Inc.</p>
</li>
<li>
<p align="justify">All ISSN registrations are maintained in an international data base and are made available in the ISDS Register, a microfiche publication which is scheduled to cease in the near future, or in &#8220;ISSN Compact,&#8221; a CD-ROM. These products are described in a document maintained by the ISSN International Centre: <a href="http://www.issn.org/products.html">ISSN products</a></p>
</li>
</ul>
<p align="justify"><strong>Individual publications</strong><strong><br />
</strong><br />
For individual publications, publishers should apply for an ISBN number. <a href="http://www.collectionscanada.ca/isbn/index-e.html">International Standard Book Numbers (ISBN)</a> are 10-digit standard numbers for the unique identification of each edition of a book or other monographic publication (e.g. pamphlets, educational kits, etc.), as per this information on the <a href="http://www.lac-bac.gc.ca/isbn/index-e.html">Canadian ISBN site</a>:</p>
<p align="justify">The International Standard Book Number (ISBN) is a system of numerical identification for books, pamphlets, educational kits, microforms, CD-ROM and other digital and electronic publications. Assigning a unique number to each published title, provides that title with its own, unduplicated, internationally recognized identifier.</p>
<p align="justify">As content publishers, our sites become part of the ocean of content online. We have a moral obligation to our current and future users to ensure the content we create becomes part of the Internet&#8217;s official historical record, good and bad, of humankind.</p>
<p align="justify"><strong>Get archived! 7 Ways to Keep Your Content from Vanishing</strong></p>
<p align="justify">Most Web publishers, including me, are guilty of breaking links or removing content and having readers email you to ask &#8220;What happened to that (article/news item/link/download) on your site?&#8221;, but here are some steps you can take to help keep your content online and accessible (assuming you want it to be so!)</p>
<p align="justify"><strong>1. Check your links!</strong> This is a no-brainer, but with all the content management, link verification software and other tools available to Web publishers, it&#8217;s still a stinky issue. You or your Web development staff should establish link-naming conventions (e.g. <a href="http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style_(links)">Wikipedia&#8217;s</a>) to govern the rules of how links are named, which can be followed consistently whether they are being named manually or dynamically.</p>
<p align="justify"><strong>2. Archive your links.</strong> If you really need to remove a link that is still valid, but isn&#8217;t relevant/essential to your site anymore, consider creating a Link Archive page where you can move the links so they can still be indexed by search engines and found by your users. Otherwise, create a redirect for old links so they point to a message indicating they are no longer available, or to new pages/content.</p>
<p align="justify"><strong>3. Archive your old site(s).</strong> Redesigning your site? Replacing it with a new version that has new content. Consider leaving the old site on your server in a Historical Site Archive area. If you don&#8217;t want search engines to index it and return pages of outdated results to your users, try using a robots.txt file that will exclude the historical pages from spidering.</p>
<p align="justify"><strong>4. Let the Internet Archive do the work.</strong> Read <a href="http://www.archive.org/about/faqs.php">How can I get my site included in the Archive</a> on the Internet Archive&#8217;s site. It&#8217;s a blast from the past to see older versions of sites going back to the mid-90s on the Internet Archive, and users can link to these pages, too.</p>
<p align="justify"><strong>5. Let search engines archive your pages.</strong> Find out how to ensure that your site is search engine optimized and that pages are not being published in a way that will cause search engine spiders to exclude them from indexing. <a href="http://searchenginewatch.com/">Search Engine Watch</a> is an excellent resource for SEO, SearchTools.com has some useful information <a href="http://www.searchtools.com/robots/">on indexing robots and spiders</a>, and the all-important Google provides <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=35769">guidelines for Webmasters</a> on how to make your site Google-friendly.</p>
<p align="justify"><strong>6. Open up your content.</strong> Mirroring your content on other sites is another strategy for keeping your content alive and accessible. By licencing your content through a <a href="http://creativecommons.org/">Creative Commons</a> licence and/or offering it for republication or repurposing on the Internet, you can help ensure that your content stays alive and accessible. For more information, visit the <a href="http://www.opencontentalliance.org/index.html">Open Content Alliance</a>, <a href="http://cnx.org/">Connexions</a>, or the University of British Columbia&#8217;s innovative <a href="http://www.pkp.ubc.ca/index.html">Public Knowledge Project</a>.</p>
<p align="justify"><strong>7. Use Universal Design principles.</strong> Last but not least, using <a href="http://www.ap.buffalo.edu/~arced/lifespan00/pud/primer/primer1.html">Universal Design principles</a> to ensure accessibility to the broadest range of users. It&#8217;s not only good from a usability perspective, but also from an archiving perspective.</p>
<p align="justify"><em>Garth A. Buchholz, BA, CUA, is a certified Internet business strategist, usability analyst, researcher and publisher at DigitalPractices</em><em>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2009/01/01/the-ecology-of-content/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>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>Mal Practices</title>
		<link>http://usabilitydesign.digitalpractices.com/2007/05/10/mal-practices/</link>
		<comments>http://usabilitydesign.digitalpractices.com/2007/05/10/mal-practices/#comments</comments>
		<pubDate>Thu, 10 May 2007 20:20:36 +0000</pubDate>
		<dc:creator>Garth A. Buchholz</dc:creator>
				<category><![CDATA[digital practices]]></category>
		<category><![CDATA[mal practices]]></category>
		<category><![CDATA[web managers]]></category>

		<guid isPermaLink="false">http://digitalpractices.com/2007/05/10/mal-practices/</guid>
		<description><![CDATA[Not all sites follow best practices to the letter, but as a usability guy here are some of the peccadillos or minor annoyances I always encounter on the Web:  Down with the Times New Roman empire!  Who the hell uses Time New Roman anymore? Not for Web sites, anyway. Ol&#8217; TNR serif may be popular with [...]]]></description>
			<content:encoded><![CDATA[<p>Not all sites follow best practices to the letter, but as a usability guy here are some of the peccadillos or minor annoyances I always encounter on the Web: </p>
<p><strong>Down with the Times New Roman empire!</strong> </p>
<p>Who the hell uses Time New Roman anymore? Not for Web sites, anyway. Ol&#8217; TNR serif may be popular with the digitally challenged who don&#8217;t know how to change the default font on their Microsoft Word, but it&#8217;s such a dated, hokey-looking font that it doesn&#8217;t belong anywhere on the Web. There&#8217;s a guy who publishes a site called Ban Comic Sans, but I hate TNR even more than I hate Comic Sans.  </p>
<p><strong>The Page Title tag is for, um, a page title.</strong></p>
<p>How many professionally designed sites do I still see with a meaningless page title such as &#8220;default&#8221; or even something embarrassing like &#8220;insert title here.&#8221; Uh, last count was 5, 186, 327. Search engines like page titles. And when people bookmark sites, they like to see something in their Favorites other than &#8220;default&#8221; or &#8220;homepage.&#8221; </p>
<p><strong>Stop using splash pages.</strong> </p>
<p>You heard me. Stop it. Stop it right now! Splash pages were indeed invented by a man named A. Bored Webdesigner in the 1990s so that Web designers could slap an attractive-looking graphic at the front end of the site. You know, that place where everyone is looking for information, links, functionality, etc. Not that users don&#8217;t want to  </p>
<ul>
<li>Stare at a pre-load animation that says &#8220;Page Loading!&#8221; for 15 seconds for their lives;</li>
<li>Gaze in admiration as your Flash splash rolls out its animated images and other bragware about your company for 2 minutes, and</li>
<li>Find the tiny link that says &#8220;Click here to go to homepage&#8221; when they thought they already were going to the homepage, and now have to click one more time to get where they wanted to go to begin with.</li>
</ul>
<p>Some splash pages offer a helpful link that says &#8220;skip&#8221;, which should actually say &#8220;click here to skip this self-indulgent crap that you didn&#8217;t want to see in the first place and make that extra effort to visit our site even though we are trying to frustrate your attempts to do so.&#8221; </p>
<p>Rant over and out. </p>
<p>(<em>more to come!</em>)         </p>
<p><a target="_blank" href="mailto:digitalpractices@gmail.com" title="Digital Practices">Email Garth @ Digital Practices</a></p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitydesign.digitalpractices.com/2007/05/10/mal-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
