<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Nielsen Norman Group</title>	<link>http://tc.eserver.org/publisher/Nielsen_Norman_Group</link>
	<description>A listing of works published by Nielsen Norman Group in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Nielsen Norman Group</title>
		<link>http://tc.eserver.org/dir/Nielsen_Norman_Group</link>
	</image>
	<item>
		<title>Inclusive Design, Part 2</title>
		<link>http://tc.eserver.org/34868.html</link>
		<guid>http://tc.eserver.org/34868.html</guid>
		<description>Accessibility is not something to be left to specialists hired to clean up our mess at the end. It should be a priority of the entire development team from the beginning. Yes, companies should definitely have accessibility people on-board, but they should act as much as educators and coaches as designers. Everyone on the development team must be aware of and responsive to the full spectrum of identified users if your product is to sell to the widest possible audience. That’s the only way to achieve inclusive design.</description>
	</item>
	<item>
		<title>Inclusive Design, Part 1</title>
		<link>http://tc.eserver.org/34869.html</link>
		<guid>http://tc.eserver.org/34869.html</guid>
		<description>Have you ever thought about what it would be like to be disabled? Well, you better start thinking about it! As my collegue Gregg Vanderheiden is fond of pointing out, &apos;We all will have disabilities eventually, unless we die first.&apos;</description>
	</item>
	<item>
		<title>Manufacturer Sites that Sell</title>
		<link>http://tc.eserver.org/34870.html</link>
		<guid>http://tc.eserver.org/34870.html</guid>
		<description>The job of a retail site is to attract the consumer, sell the product, and deliver it. In the case of a manufacturer site, the only difference when encountering a retail customer is that, instead of delivering the product, the site may deliver the customer—to an authorized retailer.</description>
	</item>
	<item>
		<title>The Worst Interface Ever</title>
		<link>http://tc.eserver.org/34871.html</link>
		<guid>http://tc.eserver.org/34871.html</guid>
		<description>Never, ever, ever let systems-level engineers do human interaction design unless they have displayed a proven secondary talent in that area.</description>
	</item>
	<item>
		<title>Salary Survey: User Experience Professionals 2001</title>
		<link>http://tc.eserver.org/33255.html</link>
		<guid>http://tc.eserver.org/33255.html</guid>
		<description>We asked respondents to state their total annual compensation from salary and bonuses; we did not include stock options and other benefits. Given that most stock options have been under water recently, cash compensation may be the most important number anyway.</description>
	</item>
	<item>
		<title>The High Price of Not Listening</title>
		<link>http://tc.eserver.org/30030.html</link>
		<guid>http://tc.eserver.org/30030.html</guid>
		<description>Ever visited the website of a company with a glaring error either on the site or in their product, only to discover that they have successfully sealed themselves off from the world, so you can&apos;t report it? Sure you have, and it&apos;s not only causing you frustration, it&apos;s costing that company real money.</description>
	</item>
	<item>
		<title>Panic! How it Works and What To Do About It</title>
		<link>http://tc.eserver.org/30031.html</link>
		<guid>http://tc.eserver.org/30031.html</guid>
		<description>When we create technologies that are extremely complex and do not provide comprehensive feedback for each and every possible error, such as a seat belt left unbuckled, people have a tendency to drive their aircraft into garden parties. When we create technologies where similar actions produce dissimilar results, such as placing a brake and accelerator pedal side-by-side, to be actuated in the identical manner by the identical limb, people will periodically die.</description>
	</item>
	<item>
		<title>The Scott Adams Meltdown: Anatomy of a Disaster</title>
		<link>http://tc.eserver.org/30029.html</link>
		<guid>http://tc.eserver.org/30029.html</guid>
		<description>A chain of five errors led to Scott Adams losing his work. Not one of those errors was his. They had been made months and even years before Scott Adams ever started work on his blog. His was an accident waiting to happen, an accident that has almost certainly befallen a large number of other individuals who have had the misfortune to use the same software.</description>
	</item>
	<item>
		<title>Slashing Subjective Time</title>
		<link>http://tc.eserver.org/30028.html</link>
		<guid>http://tc.eserver.org/30028.html</guid>
		<description>Slashing subjective time on your site by 50% is a perfectly reasonable goal. Indolent worker George Costanza once reflected on the time in the shower you wait for the hair conditioner to work as, &apos;a really tough minute.&apos; A minute waiting for hair conditioner to work while getting ready for a date can feel longer than the three subsequent hours you spend with that very special person. Reducing/eliminating boredom points can make the time spent on your website appear to really fly by.</description>
	</item>
	<item>
		<title>Arm-Wrestling the Photoshop Police</title>
		<link>http://tc.eserver.org/21427.html</link>
		<guid>http://tc.eserver.org/21427.html</guid>
		<description>Adobe is shipping a 6.0 upgrade to Photoshop that, for many Mac users, proves unusable. We learned back in the 1980s that when you rake your legitimate users over the coals in the hopes of catching the occasional thief, you end up with a lot of really raked off users. Apparently, someone at Adobe has forgotten.</description>
	</item>
	<item>
		<title>Core Decisions</title>
		<link>http://tc.eserver.org/21424.html</link>
		<guid>http://tc.eserver.org/21424.html</guid>
		<description>Many products are doomed to interaction failure before the design has even begun. Learn just how far your responsibilites as a designer extend.</description>
	</item>
	<item>
		<title>Elephants in the Living Room: The Destructive Role of Denial in Web Design</title>
		<link>http://tc.eserver.org/21430.html</link>
		<guid>http://tc.eserver.org/21430.html</guid>
		<description>Four of your fellow development team members, all trying to do their specific jobs to the best of their abilities, have the power to sink your best effort at interaction design. As an interaction designer, it is your job to see they don&apos;t do so. (If you are not an interaction designer, read on anyway; you may be surprised to learn that you may be part of the problem.)</description>
	</item>
	<item>
		<title>Good Lawyers, Bad Products</title>
		<link>http://tc.eserver.org/21425.html</link>
		<guid>http://tc.eserver.org/21425.html</guid>
		<description>Lawyers may know their way around a courtroom, but they have no business designing products. Too often, in their zealous pursuit of zero liability, they end up damaging products, alienating customers, destroying companies, and killing people. It&apos;s up to you to stop them.</description>
	</item>
	<item>
		<title>How Programmers Stole the Web</title>
		<link>http://tc.eserver.org/21432.html</link>
		<guid>http://tc.eserver.org/21432.html</guid>
		<description>In the late 1970s, a great flood of creative talent, drawn from the ranks of people who had never before touched a computer, took to the keyboards of the early microcomputers and started a revolution. The early programming environments and languages were simple, natural, and accessible. Within five years, that group had been disenfranchised by the advent of &apos;serious&apos; computing environments, such as Pascal and C, and software settled back down to being the business of professionals.&#xD;&#xD;With the advent of the web, another even greater flood of talent was unleashed, but this time the end came sooner. Within two years, the originally simple HTML environment had become clouded with hacks on top of hacks, as the C++ boys moved in and took over. The new talent could only continue to produce pretty pictures, while the traditional priesthood again took up the real work of programming. The web has stagnated ever since.</description>
	</item>
	<item>
		<title>How to Write a Report Without Getting Lynched</title>
		<link>http://tc.eserver.org/21429.html</link>
		<guid>http://tc.eserver.org/21429.html</guid>
		<description>You put forth your best effort to explain to the stupid sods exactly how and where they screwed up, then they have the temerity to not appreciate your fine efforts. Here&apos;s how to write a report that will cause change, instead of uproar.</description>
	</item>
	<item>
		<title>If They Don&apos;t Test, Don&apos;t Hire Them</title>
		<link>http://tc.eserver.org/21431.html</link>
		<guid>http://tc.eserver.org/21431.html</guid>
		<description>The single best indicator as to the overall competence of an interaction design team is their plan for user testing. If you are presented with no plan or a sort of vague &apos;and we&apos;ll eventually do some user testing,&apos; you may want to back off and look at other resources. If, on the other hand, you are given a proposal outlining repeated design and test cycles, you are dealing with people who know exactly what they are doing.</description>
	</item>
	<item>
		<title>Is the Internet Really Collapsing?</title>
		<link>http://tc.eserver.org/21428.html</link>
		<guid>http://tc.eserver.org/21428.html</guid>
		<description>The sky is falling. It has been falling for about a year now, and it feels like it won’t stop falling until every business associated with the Internet is dead, dead, dead.  What is happening now happens with every new explosion of technology. When the sky has finished falling, it will leave behind an industry with far fewer, but much healthier players. And then things will get better than they ever were.</description>
	</item>
	<item>
		<title>Replay TV</title>
		<link>http://tc.eserver.org/21426.html</link>
		<guid>http://tc.eserver.org/21426.html</guid>
		<description>You&apos;ve all heard of TiVo. Sure you have. TiVo is the hard-disk video recorder that automatically records all of your favorite shows. Then there&apos;s ReplayTV, the other leading brand.  Late fall 2001, ReplayTV crossed over a line that should never have been crossed, one that threatened the future of consumer products.</description>
	</item>
	<item>
		<title>When Good Design =&gt; Bad Product</title>
		<link>http://tc.eserver.org/21422.html</link>
		<guid>http://tc.eserver.org/21422.html</guid>
		<description>The prototypes looked great and tested well. The programmers did their usual competent job of implementation. The result was a disaster. What went wrong? Someone forgot the last, critical step.</description>
	</item>
	<item>
		<title>Why We Get No Respect, and What We Can Do About It</title>
		<link>http://tc.eserver.org/21423.html</link>
		<guid>http://tc.eserver.org/21423.html</guid>
		<description>It&apos;s time interface designers, or whatever we&apos;re calling ourselves, get some respect. After 25 years of whining about it, I&apos;ve finally realized we have only ourselves to blame.&#xD;&#xD;Take control. If you look at nothing else of mine this year, please read this, act on it, and pass it on.</description>
	</item>
	<item>
		<title>Panther: The Good, the Bad, and the Ugly</title>
		<link>http://tc.eserver.org/21419.html</link>
		<guid>http://tc.eserver.org/21419.html</guid>
		<description>For a long time, people have been writing me, asking that I do an in depth review of OS X. I held off because I really didn&apos;t think OS X was ready for prime time. That&apos;s all changed. OS X, in the form of the Panther release, is more than ready.</description>
	</item>
	<item>
		<title>Top Ten Nine Reasons the Apple Dock Still Sucks</title>
		<link>http://tc.eserver.org/21418.html</link>
		<guid>http://tc.eserver.org/21418.html</guid>
		<description>Apple Sales is apparently in love with the Dock. You can&apos;t go into an Apple store without seeing it splayed across the bottom of the screen, in the very configuration least conducive to computing on a Macintosh. Why? Because it&apos;s sexy and it sells. Unfortunately, as a productivity device, it just doesn&apos;t work.</description>
	</item>
	<item>
		<title>How to Publish a Great User Manual</title>
		<link>http://tc.eserver.org/19752.html</link>
		<guid>http://tc.eserver.org/19752.html</guid>
		<description>When was the last time you curled up in bed with a really good user-manual just for the sheer joy of reading it? Never? Think that is some immutable law of nature, like the one that dictates all textbooks must be dull as dirt? &apos;Tain&apos;t so, McGee.</description>
	</item>
	<item>
		<title>First Principles</title>
		<link>http://tc.eserver.org/18595.html</link>
		<guid>http://tc.eserver.org/18595.html</guid>
		<description>Principles fundamental to the design and implementation of effective interfaces, whether for traditional GUI environments or the web. Of late, many web applications have reflected a lack of understanding of many of these principles of design, to their great detriment. Because an application or service appears on the web, the principles do not change. If anything, applying these principles become even more important.</description>
	</item>
	<item>
		<title>Is the Slowing Economy Helping or Hurting Usability?</title>
		<link>http://tc.eserver.org/10118.html</link>
		<guid>http://tc.eserver.org/10118.html</guid>
		<description>Seattle attendees felt the slowing economy would underscore the importance of usability practices. They don&apos;t see the slow-down in retail sales negatively affecting the usability field: &apos;In terms of usability, the focus will be the same...If we had to cut something, it wouldn&apos;t be usability.&apos; While the slowing economy will force some companies to implement cutbacks and downsize, they believe that it will also show companies that they need usability in order to remain competitive.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Nielsen_Norman_Group.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>