<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-4220214319596432601</id><updated>2011-07-07T15:16:12.249-07:00</updated><category term='share'/><category term='education'/><category term='information misuse'/><category term='cellphone'/><category term='oversights'/><category term='course'/><category term='free'/><category term='information'/><category term='answering machine'/><category term='retail'/><category term='calling features'/><category term='website'/><category term='customer ser vice'/><category term='correct writing'/><category term='user documentation'/><category term='training'/><category term='clarity'/><category term='telephone'/><title type='text'>The Gift of Information</title><subtitle type='html'>Be kind to humans--give the Gift of Information.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>15</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-7563241839730586577</id><published>2008-12-07T11:16:00.000-08:00</published><updated>2009-12-04T13:05:06.713-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='telephone'/><category scheme='http://www.blogger.com/atom/ns#' term='retail'/><category scheme='http://www.blogger.com/atom/ns#' term='customer ser vice'/><category scheme='http://www.blogger.com/atom/ns#' term='answering machine'/><title type='text'>Retailers: Your Missing Employee</title><content type='html'>Many retailers of all sizes are not taking advantage of an "employee" that will work for almost no wages, and help keep their customers satisfied.&lt;br /&gt;&lt;br /&gt;This employee will work for you when nobody is around.  It will give you a presence in your local community.  It will provide a sense of continuity when your business is closed.&lt;br /&gt;&lt;br /&gt;You can buy this employee for just a one-time cost of a few dollars.&lt;br /&gt;&lt;br /&gt;I cannot understand why businesses do not all hire this employee.   By not having this employee, you anger your customers.  Also by not using this employee correctly, you really anger your customers.&lt;br /&gt;&lt;br /&gt;The employee is NOT a web page.  For many small retailers, a web page might not be a good investment.&lt;br /&gt;&lt;br /&gt;This employee is a &lt;span style="font-style: italic;"&gt;telephone answering machine&lt;/span&gt;.  Not so high tech, and been around for years.  Yet woefully ignored.&lt;br /&gt;&lt;br /&gt;Let me present some examples that hit me today.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;No Information, No Answering Machine&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;We bought a really nice carpet at a local retailer.  In addition, we borrowed a sample of the carpet so we could match it to fabrics.  I wanted to return the sample.  The REALLY simple question is "is the store open at 10:00 AM."  I did not want to look at their website, so I called on the telephone.&lt;br /&gt;&lt;br /&gt;Now this is a big company with several large branches in my town.  Ring, ring, ring, and finally to provide the customer some punishment, the high-pitched whine of a FAX machine came on the line.&lt;br /&gt;&lt;br /&gt;It would have been much more customer friendly if the store had an answering machine that, among other information, provided the hours of the store's operation.  I had to go out (driving in the snow, which I dislike) anyway because another company had an answering machine with incorrect information (see below), so I stopped off there to drop off the carpet sample.  They were closed...boy was I unhappy, as I told to the manager that I spoke with when the store finally opened.&lt;br /&gt;&lt;br /&gt;I think that if I could have found the same carpet elsewhere, I would have returned it, costing the store a $1300 sale.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Nice Answering Machine, Wrong Information&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The local Scandinavian furniture company sells Christmas trees.  I called their line before the store opened to see if they had any trees left.  The answering machine answered.  The message: "Your store has plenty of Christmas trees."&lt;br /&gt;&lt;br /&gt;(I wanted to get there before the store opened so that I did not have to wait on line with all the folks buying furniture.)&lt;br /&gt;&lt;br /&gt;I went over (driving in the driving snow) and lo and behold, the Christmas tree corral was empty.  (Then I drove to the carpet store.)&lt;br /&gt;&lt;br /&gt;I called the Scandinavian furniture company when they opened and mentioned that the message was wrong.  I got some kind of nonsense that they only knew their stock levels when the store had closed for the day...of course the Christmas tree message was a special message (they don't list the stock levels of all their merchandise on the telephone), and anyone looking out at the tree corral could see that it was empty, and that the message should have been changed.&lt;br /&gt;&lt;br /&gt;If it were acceptable to provide wrong information then the message should have said something like: "We're still selling trees.  If you want to know whether or not we have any, then drive by and see."&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;There Was a Third Example&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;A local store had a piece of furniture that my wife spotted as being a good fit in our living room.  I was to see if it was what I wanted (Art Deco style living room).&lt;br /&gt;&lt;br /&gt;Their answering machine told me that if they heard the message, that I was to leave my number and they would call me back.  I don't want them to call me back.  I only wanted to know what time they opened.  The answering machine did provide a bit of an ad for the store, but that was of no interest to me.  The information that I wanted was missing.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Lessons&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;1.  Every retailer should have an answering machine.  If you think one would provoke crank calls, then you are pretty paranoid.&lt;br /&gt;&lt;br /&gt;2.  The answering machine should provide some basic information:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;A Simple Greeting&lt;/li&gt;&lt;li&gt;Name of the Store&lt;/li&gt;&lt;li&gt;Store Hours&lt;/li&gt;&lt;li&gt;Store location (not only "123 First Ave," but also, "Near the intersection of First Avenue and Jones Road.")&lt;/li&gt;&lt;li&gt;Any Special Sale or other Information&lt;/li&gt;&lt;li&gt;Leave a Message and We'll get back to you&lt;/li&gt;&lt;li&gt;Check out our website at www.whatever&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;3.  Work the machine properly.&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Make sure that at closing time, the information on the machine is correct.  Turn the answering machine on.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Turn off the answering machine when the store is open.  Get the messages left by customers, and respond to them.&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;span style="font-weight: bold;"&gt;Finally&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Don't let your store look like it is out of business every evening when it closes.  Provide information that your customers need to do business with you by using an answering machine.&lt;br /&gt;&lt;br /&gt;(I also recommend buying an answering machine, rather than using a service of your telephone provider, which may entail a monthly fee.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-7563241839730586577?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/7563241839730586577/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=7563241839730586577' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/7563241839730586577'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/7563241839730586577'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2008/12/retailers-your-missing-or-stupid.html' title='Retailers: Your Missing Employee'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-6451278443933253965</id><published>2008-02-14T05:12:00.000-08:00</published><updated>2008-02-14T05:15:01.009-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='user documentation'/><category scheme='http://www.blogger.com/atom/ns#' term='education'/><category scheme='http://www.blogger.com/atom/ns#' term='free'/><category scheme='http://www.blogger.com/atom/ns#' term='course'/><category scheme='http://www.blogger.com/atom/ns#' term='training'/><title type='text'>FREE course on creating great User Documents</title><content type='html'>I have made my course on creating great User Documents as a free, no-strings-attached download.  The course guides the student through the creation of an effective User Document.&lt;br /&gt;&lt;br /&gt;You can learn about it here:&lt;br /&gt;&lt;br /&gt;http://www.greatuserdocs.com/DownloadCourse.htm&lt;br /&gt;&lt;br /&gt;Please pass this information on to your friends and loved-ones who are assigned to write User Documentation.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-6451278443933253965?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/6451278443933253965/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=6451278443933253965' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/6451278443933253965'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/6451278443933253965'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2008/02/free-course-on-creating-great-user.html' title='FREE course on creating great User Documents'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-8385403287914733312</id><published>2007-12-28T08:50:00.000-08:00</published><updated>2007-12-28T09:06:25.238-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cellphone'/><category scheme='http://www.blogger.com/atom/ns#' term='telephone'/><category scheme='http://www.blogger.com/atom/ns#' term='calling features'/><title type='text'>New Cellphones Should Do the Phone Stuff</title><content type='html'>This is driving me nuts.  Cellphone makers are thinking of more and more things to put into their phones: cameras, mp3 players, etc.  Why don't they make their phones do what phones should be doing.  Here are three...they might make phone use better for all of us.&lt;br /&gt;&lt;br /&gt;1. &lt;span style="font-weight: bold;"&gt;Visual&lt;/span&gt; &lt;span style="font-weight: bold;"&gt;Voice Menus. &lt;/span&gt;When the user dials into a system that uses voice menus ("press 1 for this, press 2 for that") the voice menu system should provide a text display of the menu items.  The user will not have to wait for the voice to present all of the options.  He/she will be able to see the page of the voice menu options, and press the desired button...or touch the item for a touch-sensitive screen.  &lt;br /&gt;Yes, this requires changes on the voice menu system but it sure would make life easier for all of us.&lt;br /&gt;&lt;br /&gt;2.  &lt;span style="font-weight: bold;"&gt;Pass on a phone number&lt;/span&gt;.  Years ago my son was on a cellphone call to another friend.  My son asked for a third friend's phone number.  My son had to write down the number and re-dial it.  Why can't one phone user send a phone number to another via the phone?  The sender could have it sent from his/her contact list or type it in.  The receiver could use that number to dial his/her phone, or put the number in his/her contact list.&lt;br /&gt;&lt;br /&gt;3.  &lt;span style="font-weight: bold;"&gt;I'm in the car, and I don't want to answer.&lt;/span&gt;  The option to easily enter "I cannot answer" messages.  These might be: "I'm in the car, and I don't want to answer....call me in 10 minutes" "I'm in a meeting".  &lt;br /&gt;Also the user should be able to program his/her phone to accept calls at any time from certain numbers (the phone would vibrate); non-designated numbers would get an "I'm not available" message.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-8385403287914733312?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/8385403287914733312/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=8385403287914733312' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/8385403287914733312'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/8385403287914733312'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/12/new-cellphones-should-do-phone-stuff.html' title='New Cellphones Should Do the Phone Stuff'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-8393992029409697788</id><published>2007-12-05T12:42:00.001-08:00</published><updated>2007-12-05T12:53:18.526-08:00</updated><title type='text'>Tell Us What It Means</title><content type='html'>Recently I received a notice from the City telling me that a building was going to be built that violated some of the current building codes.  The owners of the building-to-be wanted three variances.&lt;br /&gt;&lt;br /&gt;The City was asking me and other residents that might be affected to comment on the requested variances.&lt;br /&gt;&lt;br /&gt;The variances were:&lt;br /&gt;1.  Change of floor loading&lt;br /&gt;2.  No loading dock for the retail stores&lt;br /&gt;3.  Narrowing of the entrance to the parking lot.&lt;br /&gt;&lt;br /&gt;The City wanted the residents to analyze the requests, and voice their opinions at a meeting.&lt;br /&gt;&lt;br /&gt;The only problem is that the City did not even give us a hint of what these three variances meant to us.  We were left to guess, or to contact the City for clarification.&lt;br /&gt;&lt;br /&gt;Had the City estimated what effects these variances might have on the residents, confusion and cost (for calling the City and having its staff respond) would have been reduced.&lt;br /&gt;&lt;br /&gt;(By the way, if a resident waited until the meeting to learn the impact of the variance, it would have been too late to object...submissions had to be made about five days before the meeting.)&lt;br /&gt;&lt;br /&gt;You may argue that the City would be going out on a legal limb telling us how the variances would impact the residents.   Nonsense...if asked, the City would have to give an answer (which would be official) anyway.&lt;br /&gt;&lt;br /&gt;When your organization publishes any information, make sure that the receivers of that information can understand what the information &lt;span style="font-weight: bold;"&gt;means to them&lt;/span&gt;.  Not doing so adds to the confusion, cost, and negative feelings.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-8393992029409697788?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/8393992029409697788/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=8393992029409697788' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/8393992029409697788'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/8393992029409697788'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/12/tell-us-what-it-means.html' title='Tell Us What It Means'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-8618137257687528636</id><published>2007-09-24T05:45:00.000-07:00</published><updated>2007-09-24T05:46:38.217-07:00</updated><title type='text'>Technorati</title><content type='html'>&lt;a href="http://technorati.com/claim/tgrpk5d5t" rel="me"&gt;Technorati Profile&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-8618137257687528636?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/8618137257687528636/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=8618137257687528636' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/8618137257687528636'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/8618137257687528636'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/09/technorati.html' title='Technorati'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-16338018326823852</id><published>2007-09-12T07:52:00.000-07:00</published><updated>2007-09-12T09:01:41.172-07:00</updated><title type='text'>A Tough Programming Question</title><content type='html'>I have a fairly tough (and sarcastic) programming question.  It's in two parts.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Part 1: How Long to Program This? &lt;/span&gt;&lt;span&gt;&lt;span&gt;&lt;br /&gt;&lt;br /&gt;I have a 30 character ASCII (single byte characters) field.  This field will have numbers and other characters, usually spaces or dashes.  I want to remove any non-numeric characters (characters other than 0 through 9) and left-justify the result.&lt;br /&gt;&lt;br /&gt;For example, if the input field is:  1234 523-67890 335&lt;br /&gt;The result should be:  &lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt;123452367890335&lt;br /&gt;&lt;br /&gt;What is your estimate for an average programmer meeting this programming requirement in any &lt;span style="font-weight: bold;"&gt;one&lt;/span&gt; of the following languages:&lt;br /&gt;PERL, C, C++, JAVA, JAVASCRIPT, Micosoft's ACCESS (database programming language)?&lt;br /&gt;&lt;br /&gt;My guess is at most about 1/2 to 1 hour.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Part 2:  The Dangerous Question&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Given your answer to the above question, WHY don't Web forms which ask for input such as a credit card number permit spaces and dashes?&lt;br /&gt;&lt;br /&gt;After all, it's easier for a human to check his/her input if it is of the form:&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt;1234 523 67890 335&lt;br /&gt;&lt;br /&gt;Than the usually-required:&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt;123452367890335.&lt;br /&gt;&lt;br /&gt;Perhaps it's security or execution time...&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;How to Help the World&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Designers:&lt;/span&gt; When you design number input fields on a form, make these fields look and work the same way that the User deals with these numbers in real life. &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Programmers:&lt;/span&gt; If you are asked to program number input fields so that they only permit digits (with no separators), suggest to the designers the more User-oriented way to accept these fields.  Permit User entry of the fields the same way that the User deals with them in real life.  In most cases, to permit the User-oriented entry format(s) requires only the code described in Part 1, above.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;span&gt;&lt;span&gt; &lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-16338018326823852?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/16338018326823852/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=16338018326823852' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/16338018326823852'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/16338018326823852'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/09/tough-programming-question.html' title='A Tough Programming Question'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-4100052807136289031</id><published>2007-08-30T10:18:00.000-07:00</published><updated>2007-08-30T10:38:07.708-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='user documentation'/><category scheme='http://www.blogger.com/atom/ns#' term='clarity'/><category scheme='http://www.blogger.com/atom/ns#' term='website'/><category scheme='http://www.blogger.com/atom/ns#' term='correct writing'/><title type='text'>Write Correct User Documents</title><content type='html'>&lt;span style="font-weight: bold;"&gt;Overview&lt;/span&gt;&lt;br /&gt;Any instructions for a human may be thought of as being User Documentation.  Make sure that your User Documentation is correct.  Correct User Documentation matches the way that the product works.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;A Website Example&lt;br /&gt;&lt;/span&gt;In this example we will call the instructions on the invoice the "User Document".  The "product" is the website itself.&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;&lt;br /&gt;&lt;/span&gt;I subscribe to a gardening magazine.  I recently received an invoice that enabled me to pay on-line.  It said to go their web address, and then follow the '"Subscriptions" link' (these are the exact words on the paper invoice.&lt;br /&gt;&lt;br /&gt;However, when I went to the website, I only found a "Subscribe Now" link.  This name has a very different meaning than "Subscriptions."&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;"Subscriptions" means: deal with your subscription, and possibly create a new one.&lt;/li&gt;&lt;li&gt;"Subscribe Now" means: you don't have a subscription, create one now.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;The correct instructions on the printed form should have been:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Visit www.thesite.ca&lt;/li&gt;&lt;li&gt;Choose the "Subscribe Now" link&lt;/li&gt;&lt;li&gt;On the page that opens choose the "Make a payment" option, at the left of the page&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;etc...&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Bottom Line&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Go over the steps that you present to the User to ensure that they are correct; they match the way that the product works.  Don't force your User to figure out what your instructions mean.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-4100052807136289031?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/4100052807136289031/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=4100052807136289031' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/4100052807136289031'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/4100052807136289031'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/08/write-correct-user-documents.html' title='Write Correct User Documents'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-2643176311710147464</id><published>2007-08-05T14:50:00.003-07:00</published><updated>2007-08-17T13:55:40.749-07:00</updated><title type='text'>More Poor User Documentation</title><content type='html'>I just bought an Acme (fictitious brand but unfortunately a real product) One Touch Backup III external USB 2.0 Drive.&lt;br /&gt;&lt;br /&gt;The documentation fails on several counts.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;It Failed The First Rule of User Documentation: Be Accurate&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The first rule of User Documentation is that the documentation must match the product.  That is, the documentation must accurately reflect how the product and the User interact.  This poor documentation fails this first test; it is not accurate.&lt;br /&gt;&lt;br /&gt;The docs say that to erase the drive you have to enter the password incorrectly five times (I did that over and over) and then you will be able to erase the drive.    All I wanted to do was to erase the drive.&lt;br /&gt;&lt;br /&gt;[As an aside, the software had me enter a question and answer in case I forgot the password.  It NEVER asked me the question when I gave incorrect passwords.   I did not forget the password, I merely wanted to erase the drive.  This failed password method was the only way to get prompted to erase the drive.]&lt;br /&gt;&lt;br /&gt;Well, the system was so nice that it never gave me the option of erasing the drive.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;The Second Failure of Documentation: The User Can Figure It Out&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The company boasts about how clever their online help is.  Nonsense.   I went to their website looking for help.&lt;br /&gt;&lt;br /&gt;When I finally got to the web page where my drive was listed, it showed &lt;span style="font-style: italic;"&gt;two &lt;/span&gt;sets of models of the drive.  However, no place on the drive itself could I find any model numbers.  Thus their website requires that the User figure out for himself/herself what model of drive they had.  To be fair to the company they did show a picture of each drive; unfortunately the two pictures were identical.  No help there.&lt;br /&gt;&lt;br /&gt;The second failing is that the documentation assumes that the User can figure out things for themselves.  If you pair this failing with its sibling -- "everybody knows that" -- then you have a recipe for really poor documentation.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;A Documentation Inconvenience: Leaving Out Important Information&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Tell the Reader what to expect.  For example, how long will the backup take?&lt;br /&gt;&lt;br /&gt;Tell the User what things mean.  For example, "what is a backup?"  Now that sounds stupid, until you consider that there are complete backups, and there are incremental backups (where only things that have changed get backed up into a new area).  What does this system use?  A clever User can figure it out.  I think that the system uses excremental backups.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Formatting Failures (I Usually Don't Care About These)&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The documentation is supplied on a CD in .pdf format (many languages).  Unfortunately the artists who created the layout formatted it so that if the user made the documentation large enough to read, then he/she would have to scroll left and right on each subsequent page to see the text.&lt;br /&gt;&lt;br /&gt;It wasn't multicolumn text (which really stinks for documentation viewed on a computer screen), but it was jogged left and right for each page.  C'mon folks, one nice column down the center of the page would be just fine.  It might not appease a graphic artist's sensibilities, but it would be better for the Reader.&lt;br /&gt;&lt;br /&gt;Also a very clever designer put the CD's in a beautiful cardboard folder, and cleverly hid a startup manual there also.  (I did find it before doing the installation, but it really could have been made more visible.)  All of the colors blended together. &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Grammatical Errors&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;My feeling about grammar is that it should be &lt;span style="font-style: italic;"&gt;third &lt;/span&gt;in importance, after content and access.  Fourth comes flashy presentation.&lt;br /&gt;&lt;br /&gt;This document had flashiness first, then content (poor because it did not match the product), OK access (although in FoxIt Reader 2, the table of contents was not hot linked to the text, but did work as "bookmarks" in Adobe Acrobat Professional 6.0) and somewhere later, grammar.  In at least one place the wording was poor, it had "you" followed by a noun (it meant to say "your").&lt;br /&gt;&lt;br /&gt;Perhaps instead of companies managing their documentation with the snazzy mechanisms such as XML, someone could write an XML spell checker.  One thing it could look for is "you" followed by a noun.  (There probably is one somewhere...)&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Where's Your Attention?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;It seems that that the focus of the current documentation literature is on document management.  Topics such as XML, DITA, Docbook hold the interest of most documenters.  You'd think that they all worked for IBM, Microsoft, Apple, the big auto manufacturers, and others with massive documentation requirements.  They don't.&lt;br /&gt;&lt;br /&gt;I believe, and I hope that most product Users would agree, that the focus of documentation should be to produce User Documents with excellent content and access to that content.  Documentation management systems are keen, but the User will see little benefit in them.  They are fun toys.&lt;br /&gt;&lt;br /&gt;The User is selfish...he/she only wants their questions answered.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Learn More About Content and Access&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;If you are a documentation writer, especially in a small company please look over the articles in the Reading Room of the GreatUserDocs website:  &lt;a href="http://www.greatuserdocs.com/ReadingRoom.htm"&gt;http://www.greatuserdocs.com/ReadingRoom.htm&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-2643176311710147464?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/2643176311710147464/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=2643176311710147464' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/2643176311710147464'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/2643176311710147464'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/08/more-poor-user-documentation.html' title='More Poor User Documentation'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-316506613179542438</id><published>2007-06-27T08:58:00.000-07:00</published><updated>2007-06-27T09:31:23.102-07:00</updated><title type='text'>Use Your Telephone Call Distributor to Save You Money</title><content type='html'>&lt;span style="font-weight: bold;"&gt;Background: Calling for Assistance&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;My credit card is to be renewed this month.  A call to the credit card company last week, indicated that I would receive it on Monday of this week.&lt;br /&gt;&lt;br /&gt;Today is Wednesday, and since the card didn't arrive, I called the company.&lt;br /&gt;&lt;br /&gt;I went through all of the call distributor (router) options (guessing one that would connect to a human).  I was put on hold waiting for the next customer agent.   And on hold...hold... &lt;br /&gt;&lt;br /&gt;(They were experienced heavier-than-usual call volume...no wonder, since all of the June card expiry customers had not received their new cards by the end of June.)&lt;br /&gt;&lt;br /&gt;A while later, my call was answered, and the operator told me that the cards for June renewal were late in mailing.  I wasted both my time and their operator's time to get a (standard, but acceptable)  answer.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;A Bulletin Would Short-Circuit This Process &lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The credit card company already had the call distributor system working.  It is capable of presenting messages to a caller on hold.&lt;br /&gt;&lt;br /&gt;All that is needed is to be able to present a message as soon as a caller dials in to the system.  This message could answer the acute, current problem.&lt;br /&gt;&lt;br /&gt; Some examples:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;"June credit cards are late.  They were mailed out on June xx ."  &lt;/li&gt;&lt;li&gt;"We are aware of the power failure in the Acme surrounding area.  We are working on the problem, and expect it to be fixed by..."&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;These bulletins should be kept current, and should be presented at the beginning of the answer to the call.  It should not require a caller response to hear the message.&lt;br /&gt;&lt;br /&gt;The bulletins should NOT be used for advertising...their use should be limited to handling acute situations.  If there is no relevant acute situation, then do not present a bulletin.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Benefits to All&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;By providing this information you  both reduce your costs (of having a human respond to the call...with the same information each time), and your callers' frustration (in having to wait for the human to answer the call). &lt;br /&gt;&lt;br /&gt;Once again, giving the "Gift of Information" creates a win-win situation all around.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-316506613179542438?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/316506613179542438/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=316506613179542438' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/316506613179542438'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/316506613179542438'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/06/use-your-telephone-call-distributor-to.html' title='Use Your Telephone Call Distributor to Save You Money'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-1269646026087895485</id><published>2007-06-14T14:14:00.000-07:00</published><updated>2007-06-14T14:26:09.696-07:00</updated><title type='text'>Today is Never</title><content type='html'>My favorite sport is sailing...not boat sailing,  but garage sale-ing.  It's my preferred way to shop.&lt;br /&gt;&lt;br /&gt;People will sometimes post low-information signs advertising their sales.  Here's one example:&lt;br /&gt;&lt;br /&gt;Garage Sale Today&lt;br /&gt;9AM to 2 PM&lt;br /&gt;1234 Acme Ave.&lt;br /&gt;Rain or Shine&lt;br /&gt;&lt;br /&gt;The word "today" is the problem.  I don't know what day the author means.  Was this sign put up today, yesterday or last week?&lt;br /&gt;&lt;br /&gt;The result of the ambiguity is that nobody will be attracted by the sign.  (Would you travel to Acme Ave, not knowing the date of the sale?)&lt;br /&gt;&lt;br /&gt;Leaving out the date rendered the sign useless.  It left a question in the reader's mind.&lt;br /&gt;&lt;br /&gt;Whenever you write, read over your stuff and make sure that your words do not leave questions in your readers' minds.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-1269646026087895485?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/1269646026087895485/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=1269646026087895485' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/1269646026087895485'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/1269646026087895485'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/06/today-is-never.html' title='Today is Never'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-5703884027975599555</id><published>2007-06-07T10:12:00.000-07:00</published><updated>2007-06-13T15:12:18.041-07:00</updated><title type='text'>We Don't Even Give Ourselves the Gift of Information</title><content type='html'>&lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;Background&lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;p align="left"&gt;Although Users cry out for good User Documentation, the Users often overlook the need to write their own documentation for the processes that they perform infrequently.  Instead, each time that they have to perform the process, they have to re-learn (re-figure out) the steps involved.&lt;br /&gt;&lt;/p&gt;&lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;My Invoice System&lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;p align="left"&gt;This is a personal story.  I am a one-person consulting  company.  To keep track of my billing and to issue invoices I wrote my own  invoice system, using a package named dBaseIV (this was many years ago).   I used the program for about 20 years.&lt;/p&gt; &lt;p align="left"&gt;Every year, I had to set the system to number the invoices for the new year.  For example, "2001001" for the first invoice for the year 2001.   So this is a once per year situation.  I am the creator and only user of the  system, and have all of the source code and whatever.   I thought I would remember how to do this from one year to the next.  (Do you think that way?)&lt;br /&gt;&lt;/p&gt; &lt;p align="left"&gt;Each new year, I would go out of my mind trying to re-figure out  how to set the invoice counter.  I even had a menu option for that task, but it  took some smarts to make it work.  It was very stressful.&lt;/p&gt; &lt;p align="left"&gt;Finally, I wised up.  I wrote the instructions for doing  this in a simple text file.  I named it something like "NewYearSetup.txt"  and put it in the same directory (folder) as my data files.  Problem  solved.&lt;/p&gt;&lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;Getting Smarter&lt;/span&gt;&lt;br /&gt;&lt;/p&gt; &lt;p align="left"&gt;I wised up even further.  When I created my User  Documentation Course, I had almost 100 Microsoft Word (tm) files that I had to  convert to HTML and adjust all the links.  If I modified any source files, I would have to perform the same conversion on the revised files.  I wrote (and revised) a complete  step-by-step set of instructions for this.  It works beautifully.&lt;/p&gt;&lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;For a Process I Hope Never &lt;/span&gt;&lt;span style="font-size:130%;"&gt;to &lt;/span&gt;&lt;span style="font-size:130%;"&gt;Use&lt;/span&gt;&lt;br /&gt;&lt;/p&gt; &lt;p align="left"&gt;I even created instructions for a procedure that I hope I never  need to use.  I have a Sony Clie (based on the Palm operating system)  Personal Data Assistant that keeps all my passwords.  The password  program I use is called STRIP, and it has no way to print passwords or work outside  the Palm environment.  However there is a Palm desktop simulator that can  run STRIP.  I wrote VERY complete instructions about how to use STRIP and  the desktop simulator to view my passwords if the Clie were lost.&lt;/p&gt; &lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;Give Yourself the  "Gift of Information" &lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;p align="left"&gt;Whenever you run into something that you have to perform infrequently, consider creating careful step-by-step  instructions for performing the procedure.  Modify the instructions as  you learn more about your procedure...make is so the instructions can be  followed easily with a minimal number of decisions to make.&lt;/p&gt;&lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;What's Does "Minimal Number of Decisions" Mean?&lt;/span&gt;&lt;/p&gt;&lt;p align="left"&gt;Part of the conversion of my Course files (see above) involved using a text replacement tool (BK ReplaceEm) on the HTML files.  BK ReplaceEm uses configuration files, and I had generated several for various tasks.  After having to guess which configuration files to use for the Course conversions, I wrote the names of the proper ones into my how-to file.  This revision eliminated a decision...it's now much nicer to perform the conversions.&lt;/p&gt;&lt;p align="left"&gt;&lt;span style="font-size:130%;"&gt;The Bottom Line&lt;/span&gt;&lt;/p&gt;&lt;p align="left"&gt;We have processes that we perform infrequently.  We think that we will remember the steps.  However, in reality, each time we perform the processes, we have to re-learn the steps.&lt;/p&gt;&lt;p align="left"&gt;We give ourselves the "Gift of Information" if we write out those steps as accurately and completely as possible, and store them in a place where we can find them easily.&lt;/p&gt;Give yourself the "Gift of Information" even if you think that you will always remember the steps...you won't.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-5703884027975599555?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/5703884027975599555/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=5703884027975599555' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/5703884027975599555'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/5703884027975599555'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/06/we-dont-even-give-ourselves-gift-of.html' title='We Don&apos;t Even Give Ourselves the Gift of Information'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-5081546248300119252</id><published>2007-05-24T09:20:00.000-07:00</published><updated>2007-05-24T12:01:25.431-07:00</updated><title type='text'>Get Rid Of the Tachometer in Cars</title><content type='html'>&lt;span style="font-family:verdana;"&gt;&lt;span style="font-size:130%;"&gt;The Tachometer is Just a Gadget&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;    Most automobiles have automatic transmission.  Most people drive with their car in the 'D' position and let the automatic transmission do its magic.  The tachometer (which measures Revolutions Per Minute -- RPM -- of the engine) provides little or no information to the driver.  (This is often true even for manual transmission cars.  Experienced drivers shift gears using the sound of the engine as a guide.)&lt;br /&gt;&lt;br /&gt;So for most drivers, the tachometer is just a gadget.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-size:130%;"&gt;Replace the Tachometer with a Valuable Information Source&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-size:100%;"&gt;    People are interested in fuel economy.  They will change (some of) their driving habits to save fuel, hence saving money and the environment.&lt;br /&gt;&lt;br /&gt;A &lt;/span&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-weight: bold;"&gt;fuel consumption display&lt;/span&gt; would provide drivers with the information that they can use to improve their driving behavior.  Such a display could present&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;instantaneous fuel consumption (miles per gallon or litres per 100 km)&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;total fuel used for a trip (especially for short trips)&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;indication of excessive waste (such as long idling periods).&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;&lt;br /&gt;&lt;span style="font-size:130%;"&gt;Everyone Wins&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;ul&gt;&lt;li&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;   Drivers get useful information to help them improve driving efficiency&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;   Manufacturers get a neat gadget to replace the tachometer&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;span style=";font-family:verdana;font-size:100%;"  &gt;   The environment gets more aware drivers&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;span style="font-size:100%;"&gt;&lt;span style="font-family:verdana;"&gt;    For drivers of manual transmission cars, the tachometer could be the default display, with the fuel consumption display as an option.&lt;br /&gt;&lt;br /&gt;For automatic transmission cars, the fuel consumption display could be the default, instead of the useless (for them) tachometer.&lt;br /&gt;&lt;br /&gt;The goal is to provide, as the default,  the most useful information for the user.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-5081546248300119252?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/5081546248300119252/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=5081546248300119252' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/5081546248300119252'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/5081546248300119252'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/05/get-rid-of-tachometer-in-cars.html' title='Get Rid Of the Tachometer in Cars'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-7401708799803651568</id><published>2007-05-22T14:16:00.000-07:00</published><updated>2007-06-19T10:55:17.718-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='information misuse'/><title type='text'>If You're in the Information Business, here's some summer reading</title><content type='html'>The book is a non-fiction paperback titled &lt;span style="font-weight: bold;"&gt;&lt;/span&gt;&lt;span style="font-weight: bold;"&gt;In Harm's Way&lt;/span&gt; (ISBN 0-312-98337-9) by Doug Stanton.   It's a World War II recounting of the sinking of the USS Indianapolis &lt;a href="http://en.wikipedia.org/wiki/USS_Indianapolis_%28CA-35%29" title="USS Indianapolis (CA-35)"&gt;&lt;/a&gt;(CA-35)&lt;br /&gt;&lt;br /&gt;It's a riveting story with two valuable messages for information professionals:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;How the misuse of information can lead to catastrophe.&lt;br /&gt;Assumptions and mishandling of information led to the misery and death of about 300 US sailors.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;How to use in-line definitions to explain terms that your reader might not know.&lt;br /&gt;Rather than assume that your reader knows the meaning of your terminology, explain it.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;Everyone who deals with information can benefit from these two lessons.&lt;br /&gt;&lt;br /&gt;Please be careful with all information entrusted to you.  How you use or misuse it can have far-reaching implications.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-7401708799803651568?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/7401708799803651568/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=7401708799803651568' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/7401708799803651568'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/7401708799803651568'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/05/if-youre-in-information-business-heres.html' title='If You&apos;re in the Information Business, here&apos;s some summer reading'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-1969110034611673700</id><published>2007-05-22T14:07:00.000-07:00</published><updated>2007-05-22T14:14:54.427-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='information'/><title type='text'>Bad News Can Make You Feel Better</title><content type='html'>&lt;p&gt;Here's an example of how receiving bad news can make you feel   better than no news. This is the opposite of the old saying "no news is good   news." This is an adaptation of the road sign example described by Gilbert (Gilbert, Thomas F. &lt;u&gt;Human Competence: Engineering Worthy   Performance&lt;/u&gt;. New York:McGraw-Hill, 1978. ISBN: 0-07-023217-2). &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; It's late at night and I am driving to Springfield. I come to an   &lt;b&gt;unmarked&lt;/b&gt; T in the road. I need to know which way to turn, but the   directional information is missing. This is an Information Oversight. I am   forced to guess at which way to turn. I have to make an assumption as to which   direction was correct. I turn right. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; As I drive along, my discomfort increases. I could be driving further   and further away from my goal. This is not nice, and I am a bit unhappy with the   people who are responsible for marking the roads. (Notice that the unhappiness   is directed toward the enterprise that was responsible for road signs...they   permitted the Information Oversight to exist. Placement of blame is pretty   accurate.) &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; After 10 minutes of driving, I see a sign saying "Shelbyville 10   miles." I had taken the wrong turn. So, unhappily I turn back to head toward   Springfield. (This is the bad news.) &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; I may be unhappy, or angry, but one gnawing emotion is gone: the   anxiety. I was anxious because I did not know if I was going toward or away   from my goal. The sign gave me the bad news, but removed that anxiety. Thus the   bad news, in some way, had made me feel better. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; We had an Information Oversight (the missing sign) at the T junction.   That started the situation, and it should have been avoided in the first place.   The interesting point is that the information that told me I was going in the   wrong direction was not only beneficial (I turned around and went the other   way), but reduced my uncertainty and anxiety. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Eliminating Information Oversights is a major component of giving   the "Gift of Information."  Everyone wins when we give the Gift of Information.&lt;br /&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-1969110034611673700?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/1969110034611673700/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=1969110034611673700' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/1969110034611673700'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/1969110034611673700'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/05/bad-news-can-make-you-feel-better.html' title='Bad News Can Make You Feel Better'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4220214319596432601.post-112452062394500057</id><published>2007-05-16T07:41:00.000-07:00</published><updated>2007-05-16T11:34:36.215-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='oversights'/><category scheme='http://www.blogger.com/atom/ns#' term='share'/><category scheme='http://www.blogger.com/atom/ns#' term='information'/><title type='text'>Your Information Oversights Will Cost You</title><content type='html'>&lt;p&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; In simplest terms, an Information Oversight (which we shall abbreviate   IO) occurs when an enterprise (that's any information publisher -- it may be a   business, government, some other type of organization, or an individual person)   fails to produce -- or produces unclear -- information that its audience needs.   &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; The audience or receiver is a person or group who must &lt;b&gt;use&lt;/b&gt; (or   &lt;b&gt;want&lt;/b&gt;) the information provided by an enterprise. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; IO's most frequently arise when the enterprise &lt;b&gt;fails to produce&lt;/b&gt;   the needed information. Let me present some of my favorite recent examples.   Please pay special note to the reaction of the people in this situation, and   what your reaction would be if you were in the situation. (Your reaction may or may not be typical,   and in fact there may be no single "typical" reaction.) &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;&lt;hr /&gt;    &lt;p&gt;&lt;b&gt;Pool Closed&lt;/b&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;Recently at a fitness center the doors to the swimming pool were locked.   There were quite a few people milling around waiting to get into the pool. They   were angry because the pool was closed, and because of the uncertainty of   knowing when the pool would re-open. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;Had the pool manager merely posted a handwritten sign saying something   like: &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p align="center"&gt;&lt;span style="font-size:130%;"&gt;&lt;i&gt;Pool Closed for Water   Testing&lt;/i&gt;&lt;/span&gt; &lt;/p&gt;    &lt;p align="center"&gt;&lt;span style="font-size:130%;"&gt;&lt;i&gt;Will Re-Open at 8:15PM&lt;/i&gt;&lt;/span&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;The waiting bathers could plan to wait in more comfortable surroundings,   decide to wait outside the door, or choose not to swim at all. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;The information conveyed by the sign would have resolved the bathers'   uncertainty and made them happier. (Not happy, but happier.) In fact one person   remarked that he felt sorry for the fitness center because they had gotten so   many people so angry. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;The pool manager, in not providing information needed by his audience,   committed an Information Oversight. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;&lt;hr /&gt;    &lt;p&gt;&lt;b&gt;The Bank Statement&lt;/b&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;The bank where I have my business account sends me a monthly statement.   This month, the statement showed a Debit Memo (money removed from my account)   for the tune of about $1,600, taken by the taxation branch of the government.   This clearly must be an error, as I do not remember authorizing any such   deduction. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;Question: What is the first thing that you would do, after searching   your documents and memory to verify that you had not given permission for this   access? &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;I bet it would be to call the bank. That was my first reaction. The bank   statement, printed by the computer, indicated the name of my branch. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;BUT, they left out one small piece of information: the phone number of   the branch. I needed that for the next step…to contact them. I was forced   to look the number up in a telephone directory, or search my records or Palm   Pilot. (There was no e-mail address or website address either.) &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;This is an example of a &lt;i&gt;tiny&lt;/i&gt; Information Oversight. Having   printed the phone number along with the branch name would have saved me some   work, in a stressful (why did they take that money?) situation. This IO made me   less happy with the bank than I could have been. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;Please don't take the bank's side on this. If you feel that they   purposely do not print the number in order to reduce unnecessary calls, then   you are thinking like the organization, and not like a customer. The customer   wants the bank's services to be easy, and by leaving out the number, the bank   made its services harder to access. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;Leaving the phone number off the bank statement is an Information   Oversight. &lt;/p&gt;    &lt;p&gt;By the way, someone had made an error; the bank removed the debit. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Information Oversights are not usually major things. Just lots of   little things which, like the so-called Chinese water torture, makes life less   than joyful. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;&lt;hr /&gt;    &lt;p&gt;&lt;b&gt;An Internal Document Yields a Different Kind of Information   Oversight&lt;/b&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; An e-mail was sent to all those managing websites. This mail announced   that there is to be a change to the web development infrastructure. In simple   terms it means that some name changes which refer to your web pages will change   on such a date…. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; The e-mail contained a small list of Frequently Asked Questions. Here   is a goody: &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;&lt;i&gt;4. &lt;/i&gt;Question:&lt;i&gt; Will I need to change any of my content?&lt;/i&gt; &lt;/p&gt;      &lt;p&gt; &lt;/p&gt;    &lt;p&gt;&lt;i&gt; &lt;/i&gt;Answer:&lt;i&gt; Prior to migration, the content will be scanned for   any references to (the current address) as well as any URLs containing ~   (tildes). This will be changed to (new name) and any tildes will be   removed.&lt;/i&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; I replaced the actual names in the above response. Before we continue   this discussion, please note that the question was stated as "Will &lt;b&gt;I&lt;/b&gt;   need…" &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; The response came in the unclear passive voice. (&lt;i&gt;That's&lt;/i&gt; why your   teachers never liked the passive voice.) It is not apparent who will edit your   web content. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; This is an example of an Information Oversight of a second kind. (The   first kind arose when information was not made available.) In this second type   of IO, the author &lt;b&gt;muddied&lt;/b&gt; the answer. The statement was not 100% clear,   and yet it could have been. For no more cost! Here are two possible changes:   &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; "Prior to migration, we at the corporate migration center will scan the   content for any references to…" &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; But that is still not clear enough. The "user" asked the question "Will   &lt;b&gt;I&lt;/b&gt; need to change…". The answer to prevent any IO should have been:   &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; "No, you will not have to change anything. Prior to migration, we at   the corporate migration center will scan the content for any references   to…" &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Oh wait, there is more in this internal memo. Let's discuss it further.   &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; The last item in the list of questions asks whom to contact if I have   problems. The answer gives two names, but &lt;b&gt;no telephone numbers&lt;/b&gt;. I get   the feeling that they have the same writers as my bank. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Wait there's more. The word ASSUME (everyone should hiss and boo) rears   its ugly head. The document ASSUMES that all will go well. It ASSUMEs that you   will test the site, rather than recommending a next step: &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;Next Step: &lt;/p&gt;    &lt;ul&gt;&lt;li&gt; You should test all aspects of your site after the changeover     (date). &lt;/li&gt;&lt;li&gt; If you have problems, contact… &lt;/li&gt;&lt;/ul&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;"Oho," you say, "don't pick on a little techie whose favorite language   is only understood by a few select individuals and perhaps a computer. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;&lt;hr /&gt;    &lt;p&gt;&lt;b&gt;And From a Professional...&lt;/b&gt;&lt;/p&gt;    &lt;p&gt;So, here is one from a professional writer. The Ottawa Citizen "Going   Out" section (L) December 16, 2000, and a nice one. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt;There is a subsection called "Sunday best The top things to see and do."   It's about events happening on Sunday, but presented in Saturday's paper. The   following sentence appeared in a description of a Magic Show: &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; "The family show with four magic acts is today at 2, 5, and 8 p.m., and   tomorrow, at noon, 3 and 6 p.m." &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; This appeared in the Sunday subsection in the Saturday edition of the   "Going Out" section of the paper. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; QUICK, with no assumptions what days were the shows? Saturday and   Sunday, or Sunday and Monday? Yes, your assumptions will fill in the blanks.   And if your assumption is wrong, you can lose big. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Here is a simple rewrite of the IO sentence. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; "The family show with four magic acts is &lt;i&gt;Saturday&lt;/i&gt; at 2, 5, and 8   p.m., and &lt;i&gt;Sunday&lt;/i&gt;, at noon, 3 and 6 p.m." &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; The argument that this wording does not look as good as the previous   one, is unreasonable. Informative writing should first be clear, then it can be   made to look good. But not polished at the expense of clarity. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;&lt;hr /&gt;    &lt;p&gt;&lt;b&gt;Back to Our Discussion&lt;/b&gt;&lt;/p&gt;    &lt;p&gt;Ah, a bit of writing can spawn a career. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Actually a lot of the meat to feed this career came about with the need   to purchase a new VCR. From the merchant's and the manufacturer's websites, to   product manuals, to the ergonomics of the machine itself, the experience   contains a lifetime of Information Oversights. And a beautiful product loses   some of its sparkle in the process. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Notice that I make an assumption here. I am not going to concern us   with the idea of providing incorrect information. I shall assume that your   enterprise will produce information with the validity it should have (I choose   to be ambiguous here). &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; However, one thing is possible. Although we cannot know what skeletons   in an enterprise's closet do not see the light of day, we do know that many   folks are concerned with uncovering the truth as it affects them. There is a   chance that the skeleton might be illuminated sometime in the future. So watch   it! &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; There are other kinds of information mistakes that we could put under   the Information Oversight umbrella. Here are a few: &lt;/p&gt;    &lt;ul&gt;&lt;li&gt;&lt;b&gt;Timing&lt;/b&gt;. Providing information at the wrong time. &lt;/li&gt;&lt;li&gt;&lt;b&gt;Overload&lt;/b&gt;. Providing too much information, not optimized for     access (which includes navigation). I wonder how much the time spent on a     website is reduced if a flashing banner is placed on the page. The information     overload (distraction) of the banner overshadows the content. &lt;/li&gt;&lt;li&gt;&lt;b&gt;Audience&lt;/b&gt;. This, in fact is one of my favorites. Of course it     got me, that's how I know about it. The "audience error" lies in not finding     out or knowing who your audience is. This error is manifest in most, if not     every, government web site. &lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;    &lt;p&gt; &lt;b&gt;Know Your Audience&lt;/b&gt;&lt;/p&gt;    &lt;p&gt; I can think of (at least) two types of people (let's call them "roles"   that a person takes on) who visit a government website: &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;ol&gt;&lt;li&gt;People who need or want to find out something &lt;b&gt;about the     government&lt;/b&gt;. My example here is the student writing a school paper on the     history of the Patent Office. &lt;/li&gt;&lt;li&gt;People who have to do something with the government or &lt;b&gt;want a     service from the government&lt;/b&gt;. My example is the person who wants to patent     her newest invention. &lt;/li&gt;&lt;/ol&gt;    &lt;p&gt; When either of these roles approach the government website, and search   on "patent" they get the same mass of links. Try it and see. The person who   wants to patent her invention is forced to weed through all this stuff to find   the "how to" stuff. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Aha! We have accepted a further assumption, which makes our government   site even a bit more difficult to use. We assumed that the "how to" person knew   the word was "patent." Even though the search produced gobs of useless   information, we made an assumption that she knew where she should look. Silly   us. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; What the "how to" person probably wants to do is to &lt;b&gt;protect&lt;/b&gt; her   creation. She is an inventor, or writer, or whatever. She is not a patent or   trademark lawyer. Thus she knows what she wants to do with her creation   (protect it) but doesn't know the jargon. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; Please don't say, "the inventor should get a lawyer." For if that is   the attitude we take, then we needn't spend the money on the government   websites. Their mandates are to inform and serve (without stepping on anyone's   toes.) &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; While it is easy to slam the governments, we can all be satisfied in   knowing that almost all Internet sellers' and product manufacturers' websites   have the same failings. They don't seem to recognize the &lt;b&gt;dual&lt;/b&gt; roles of   the customer. I will discuss this further in a section on the Users of your   Information. &lt;/p&gt;    &lt;p&gt;Interestingly enough, many governments have websites with "employee   portals." This is a web address which would be known to and used by employees.   It provides quick access to information which employees need about their jobs   with the government.&lt;/p&gt;&lt;hr /&gt;    &lt;p&gt;&lt;b&gt;Now It's Your Turn&lt;/b&gt; &lt;/p&gt;    &lt;p&gt; Take a minute or two (if you haven't already done so) to think   of any kind of Information Oversight that was inflicted on you. &lt;/p&gt;    &lt;ol&gt;&lt;li&gt;Recall what happened.&lt;/li&gt;&lt;li&gt;What piece of information was withheld?&lt;/li&gt;&lt;li&gt;How did you feel about the situation? &lt;/li&gt;&lt;li&gt;Did your feelings towards the "sender" of the (missing) information     change? &lt;/li&gt;&lt;li&gt;And finally, would there have been any problem for the "sender" to     have eliminated the Information Oversight?&lt;/li&gt;&lt;/ol&gt;    &lt;p&gt; Your feelings in the situation (or any range of feelings that you can   imagine for that situation) are the feelings that people experience when they   hit an Information Oversight of yours. &lt;/p&gt; &lt;hr /&gt;    &lt;p&gt;&lt;b&gt;More than Errors!&lt;/b&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; But there is more to it than what I have been presenting. The   underlying concept is that enterprises should always be trying to give the   "Gift of Information." One of the gifts of information is clearing up   Information Oversights. Other gifts go beyond the repair of blunders. These add   product value, greater user skills and knowledge, smoother operations within   your organization, and reduced stress. &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p&gt; &lt;/p&gt;    &lt;p align="center"&gt;&lt;span style=";font-family:Arial;font-size:100%;"  &gt;&lt;br /&gt;&lt;/span&gt; &lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4220214319596432601-112452062394500057?l=infogift.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infogift.blogspot.com/feeds/112452062394500057/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=4220214319596432601&amp;postID=112452062394500057' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/112452062394500057'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4220214319596432601/posts/default/112452062394500057'/><link rel='alternate' type='text/html' href='http://infogift.blogspot.com/2007/05/what-are-information-oversights.html' title='Your Information Oversights Will Cost You'/><author><name>Barry Millman, Ph.D.</name><uri>http://www.blogger.com/profile/09652928158547902626</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://www.greatuserdocs.com/barry.jpg'/></author><thr:total>0</thr:total></entry></feed>
