Usability Notes - by Chris Baker

Notes on usability and related things by a project manager who manages electronic publishing projects.

About

My Photo

Twitter Updates

    follow me on Twitter

    Recent Posts

    • The internet and the older user
    • Thrashing numbers and the thirteenth task
    • SEO and SEM vendors and consultants appreciate me too much
    • Introduce new software testers, reveal Goldovsky errors
    • How to print a list of files from a Windows Directory (without needing to buy software)
    • Memories of the dotcom bubble
    • How Annals of Botany has made use of social media
    • Many social media services (Ethnority's lovely taxonomy)
    • Don't be a Hiro
    • van Gogh stops the Machine -- a paradox of virtual experience

    Most popular posts

    • kanban
    • "Oh, you just click the TV?" The journey of a metaphor
    • Security question difficulties
    • The NLM DTD
    • Poka-yoke
    • web colours
    • Requirements analysis
    • Shopping cart abaondonment benchmarks

    The internet and the older user

    I have been thinking about research from Nielsen Norman Group about the usability issues faced by over -65s

    The over-65s are demographically the last group to be spending time online, and if they behave like the other age-groups, sending time will evolve into spending money.

    We are all on a journey to poorer eyesight, poorer motor control and worse memory - for some people over 65, these have become significant barriers to web use. In addition, the over-65s Nielsen Norman studied showed more willingness to blame difficulties in using websites on themselves, and so more inclination to give it up as something for younger folks only. Anecdotally, becoming less confident about new experiences is another common issue about aging (though of course individuals vary hugely).

    With each year that passes, however, there are more people in the over-65 age group for whom the Internet is not so new. I think that is an important point. To illustrate it, here is a table (pdf file) showing how old you'd be now if you turned 65 in the year of some events from Internet history. The table also shows the approximate percentage of the world population online that year. For example, you're 71 now if you were 65 the year the first iPhones came out. If you retired at 65 and got yourself one of the first Android phones, you must now be 70. If you are 85 now, you were 65 the year the Mosaic browser came out (arguably the ancestor of all modern browsers). But if you used it age 65, you were highly unusual - among less that 0.4% of the worlds' population online back then.

    Download The Internet in the year you turned 65.

    It's easy to see how specialised and niche the Internet was at the time current members of the over-65s joined that cohort. There's nothing magic about the number 65, of course - people don't necessarily start behaving differently, or suddenly lack confidence with new technology. But I think it is worth remembering how comparatively recently everything has happened.


    May 28, 2013 | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    Thrashing numbers and the thirteenth task

    Some tasks fit into an awkward sort of "squeezed middle". If something is quick and simple to do and doesn't disrupt the rest of life too much, you might as well get on and do it. Urgent tasks are usually not too hard to remember to do and to get on with, and long tasks are readily handled by putting the into your diary. In the middle are tasks that you need to do, but can't do easily find time to get around to. So they build up. That in itself starts to cause a problem - it's much more bother to have twelve 10-minute tasks than one 2-hour task. That's because there is an invisble 13th task ("keep track of all of the 12 tasks"). The mental pressure of feeling there is a lot to do can be very unpleasant - even  if it's "a large number of tasks to think about" as opposed to "many hours of work"  

    Somebody once told me that old-time mainframe computers had a problem like this. They had to cope with prioritizing tasks for many different users. So the computer would run a program which would decide the best order in which to do the tasks. But of course that choosing program itself needed some of the computer's resources. As more and more tasks piled up in the queue, the computer could get stuck allocating more and more of its resources into deciding what to do. Endgame is that ALL the computer's resoures are going into trying to decide what to do next, and the computer has had a sort of digital nervous breakdown. The number of tasks that would cause this was known as the "thrashing number", I was told. To prevent this from actually happening, the computer would be programmed to change its behaviour as it felt the thrashing number approach - move from doing the tasks in the most efficient order to just doing them: get the length of the queue down any old how, until the situation improves enough to think about efficiency instead of survival again. 

    Something similar can help for people too, I think. If you normally take some care over prioritizing but have ended up "thrashing", it can be helpful just to let that go sometimes and reduce the queue: do the thing that is bothering you first. Or, do the small things first; or just do things in any order to get life more simple again so you can think straight.

    To avoid things getting that bad, it's helpful to set aside a fairly regular "thrashing hour" in which you work through as many of those inconvenient-sized tasks as you can. OK, it's something of a misnomer as the idea is to prevent the kind of behaviour which was "thrashing" for a computer. But "2pm Friday - thrashing hour" is such a satisfying thing to write in the diary.

    May 10, 2013 in ideas parking space | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    SEO and SEM vendors and consultants appreciate me too much

    I like getting comments. I don't always get around to moderating them quickly, but do like to see things that contribute to the discussion. I quickly learned that I did have to moderate the comments, because so many of them are nothing about me or my site - there is usually a lot of spam advertising to weed out.

    Another thing I've noticed is that a  great way to get a lot of brief, generic statements of thanks is to post something about Search Engine Optimization (SEO) or Search Engine marketing (SEM), or about social media strategy. Its nice to see an industry that is so eager to educate the public about how to do this yourself (at least at a basic level), rather then to engage some of the many consultancies that can offer help. Or wait - would it be just too cynical  to think that some of these comments aren't about me at all, but are about getting a comment which bears an inbound link back to the writer's SEO or SEM site? The number of links you have into your site from relevant, reputable sources has a big effect on how you rank on search engines such as Google, Yahoo and their competitors, so the temptation is clearly there. Nah, surely not....

    Let's see. From my recent comments:

    "This is a good post. This post gives truly quality information. I’m definitely going to look into it. Really very useful tips are provided here. thank you so much. Keep up the good works..."

    This exact quote is found 186,000 times by Google, with the same author. "Allen", you are one generous guy. OK, let's face it, you're a robot, aren't you...

    Now of course, lets not damn everyone - the SEO and SEM industry has very professional and honourable people in it. But it's not necessarily easy for clients to sort the sheep from the goats. I'm very glad to publish comments from SEO, SEM and social media consultants, if I feel it's intended as a contribution to my site, not just to yours.

    It will be interesting to see what, if any, comments this post gets...

    December 04, 2012 in e-marketing and e-commerce, Pet hates, social media | Permalink | Comments (2) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    Introduce new software testers, reveal Goldovsky errors

    Its amazing how often new software bugs are reported when you introduce new testers to the testing process. Its quite likely that some of these are not new breakages in the latest software release. What is happening is usually that the new guys:

    • read the test script differently. It is very difficult to write unambiguous instructions, and it would be unconventional to test the test script on a lot of testers until any editorial problems were fixed - usually that would be a poor use of resources. Or;
    • they read it carefully and take it literally. By contrast, your established testers have long got used to skimming the instructions to remind themselves what to do, but rely mostly on their experience and memory of previous tests. It's the trade-off you make for their faster progress through the tests. It's very difficult to make yourself read a long, boring test script for the umpteenth time as if you'd never seen it before (at least, I find this so). In this case the testers, new and old, are making an interesting kind of error (if it is an error)- a Goldovsky error

    This phenomenon of new tester-related bug reports can go on for a long time if the test script is long and complicated or gets updated over time (or both).

    Usually this is seen as a nuisance - after some effort, it's discovered that the bugs aren't real things going wrong with the software, they are artifacts of the test case and tester. It's easy to feel that the tester (or the test script author) "should have got it right in the first place". That would be a fair criticism if lots of time and resources were allowed to get the test script exactly right and train up the testers. But how often do you see that? More usually the team  decided on a trade-off (faster preparation for testing in return for lower-quality script) and now someone is moaning about the downside of it. Or, we didn't decide on a trade-off as such, we just didn't allow enough time to prepare the script, and the test-script errors coming through are how we are learning this uncomfortable truth.

    You could see Goldovsky errors as a blessing. Just occasionally the new guy discovers something that is important and was overlooked by the specific way things were done before. You could argue that, for best bug discovery, you ought to rotate people on and off the team of testers to take advantage of this. Hmm, I'm not sure. On long projects, or systems being regression tested each release, staff turnover or other change tends to make this happen anyway without having to do it as a matter of policy.

    Conversely, training your testers extensively teaches them to use the system just like you do and risks missing out on all the unexpected and creative things people do when they work from instructions, and the discoveries that might come from that.

    Anyway, your customers don't have the benefit of a script, probably won't read the instructions and will certainly do a whole pile of things you won't ever think of until you either do usability tests or launch the product and get customer feedback.

    November 30, 2012 in project management, website testing | Permalink | Comments (3) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    How to print a list of files from a Windows Directory (without needing to buy software)

    Sometimes I have a batch of files in a Windows Directory and I want to either print a list of what I've got to a file, or copy data into Excel or similar to do some more complex analysis. If I want to do something more complex than simply taking a screenshot of the directory, I do this using DOS, the granddaddy of Microsoft systems.(Then I don't need to do this for some time, and next time I have to go looking for my notes. No longer! I'll be able to find them on this site!)

    The following ought to work on any Windows system up to Windows 8 (I've yet to try Windows 8 so don't know what would happen there).

    When the directory is on C:

    1. Click the Start button in Windows (bottom left corner of windows toolbar, the button that is now the 4-coloured Microsoft flag, but used to be a button called Start in earlier versions of Windows)
    2. The start menu opens - In the “Search programs and files” box, type CMD
    3. This opens cmd.exe, (a black window with white text)
    4. Have a note of the file path to the folder you want. Lets say you want to print a list of what you have in your downloads folder (C:\users\chris\downloads in my case)
    5. The black window has a prompt (probably C:\users\chris) telling you which directory it is currently pointing to. You need to get it to point to a different directory within C: So you type "CD \users\chris\downloads" (or the name of the directory you want to reach)
    6. DOS replies "CD \users\chris\downloads" (or the name of the directory you want to reach), and you type dir>listing.txt (or another filename if you don't like "listing")
    7. If you navigate to  \users\chris\downloads, you will now find your text file listing.txt, which you can print or import into Word or Excel etc for further fun

    Here's what the DOS box will look like when you've reached step 6:

    screenshot showing what the dos box looks like after steps 1-7 above

    Here's a version of that screenshot in which I've boxed in yellow text which I typed (as opposed to what DOS "replied"):

    Dos2with highlight

    When the directory is on another drive, e.g. V: or G:

    Sometimes you want to get a listing of files that are not on your C: drive (you are on a network, or the files are on a portable drive). Let's say you want a listing of "G:\packaging script output tars20120719"

    The process is the same as the above except that you need to get DOS to point at a different drive

    1. Click the Start button in Windows (bottom left corner of windows toolbar, the button that is now the 4-coloured Microsoft flag, but used to be a button called Start in earlier versions of Windows)
    2. The start menu opens - In the “Search programs and files” box, type CMD
    3. This opens cmd.exe, (a black window with white text)
    4. Have a note of the file path to the folder you want. "G:\packaging script output tars20120719"
    5. The black window has a prompt (in my case C:\users\chris) telling you which directory it is currently pointing to. You need to get it to point to a different DRIVE this time. So instead of typing CD \..., you type "CD /DG:\packaging script output tars20120719". The "/D" command tells DOS that you want to change drive
    6. DOS replies G:\packaging script output tars20120719 (or the name of the directory you want to reach), and you type dir>listing.txt (or another filename if you don't like "listing")
    7. If you navigate to  G:\packaging script output tars20120719, you will now find your text file listing.txt, which you can print or import into Word or Excel etc for further fun.

    Here's what it looks like (note that my first go at reaching G: did not work because I "forgot" to add the "/D" command. DOS stubbornly gives you a prompt that is the original directory again and leaves you to figure out what you did wrong. Ah, computing in the 80's!):

    Dos screen

    And here is a version of that screenshot where I've highlighted in yellow things I typed myself:

    Dos screen G with highlight

    What the txt file looks like

    Here is what I get in my listings.txt file - you can see I get the modification date and time, file size and file name ("data.2012-06-18.tar" etc). The listing also tells me the number of files and their total size:

    my txt file reads:


    Volume in drive G is Expansion Drive
     Volume Serial Number is 1CDC-DAB8

     Directory of G:\packaging script output tars20120719

    08/11/2012  13:39    <DIR>          .
    08/11/2012  13:39    <DIR>          ..
    18/06/2012  03:23       363,796,480 data.2012-06-18.tar
    19/06/2012  03:09       105,881,600 data.2012-06-19.tar
    20/06/2012  05:55     3,205,591,040 data.2012-06-20.tar
    21/06/2012  03:47       483,563,520 data.2012-06-21.tar
    22/06/2012  03:16       196,956,160 data.2012-06-22.tar
    25/06/2012  03:17       238,018,560 data.2012-06-25.tar
    26/06/2012  03:15       216,565,760 data.2012-06-26.tar
    27/06/2012  03:03        27,166,720 data.2012-06-27.tar
    28/06/2012  05:15     2,556,620,800 data.2012-06-28.tar
    29/06/2012  03:04        65,392,640 data.2012-06-29.tar
    02/07/2012  03:09        91,504,640 data.2012-07-02.tar
    03/07/2012  03:17       228,884,480 data.2012-07-03.tar
    04/07/2012  03:28       511,948,800 data.2012-07-04.tar
    05/07/2012  04:12     1,353,256,960 data.2012-07-05.tar
    06/07/2012  03:08       111,656,960 data.2012-07-06.tar
    09/07/2012  03:53       942,039,040 data.2012-07-09.tar
    10/07/2012  03:23       388,392,960 data.2012-07-10.tar
    11/07/2012  03:17       249,477,120 data.2012-07-11.tar
    12/07/2012  03:28       518,000,640 data.2012-07-12.tar
    13/07/2012  03:06        72,632,320 data.2012-07-13.tar
    16/07/2012  03:39       679,424,000 data.2012-07-16.tar
    17/07/2012  03:20       358,225,920 data.2012-07-17.tar
    18/07/2012  03:17       275,865,600 data.2012-07-18.tar
    19/07/2012  03:28       424,181,760 data.2012-07-19.tar
    08/11/2012  13:39                 0 tarlist.txt
    11/10/2012  16:58    <DIR>          temp unpacked
                  25 File(s) 13,665,044,480 bytes
                   3 Dir(s)  144,890,527,744 bytes free

    November 08, 2012 | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    Memories of the dotcom bubble

    I've recently been reading the excellent Totally Wired - on the trail of the great dotcom swindle by Andrew Smith (Bloomsbury 2012).

    The dotcom bubble ran (arguably) from the IPO of Netscape in 1995 to the stock market collapse of 2001/2001. Remember that 1995 was the PC iron age. In 1995, a PC computer with 8MB RAM was high-end, and would probably cost you about £1,000. Your new PC would run Windows 95 . Your older computer could theoretically run Windows 95 if it met the minimum spec of "an Intel 80386 DX CPU of any speed, 4 MB of system RAM, and 50–55 MB of hard drive space", but performance was poor with such a machine, leading to moaning about how unreasonable it was to need 8MB RAM.

    Internet conections were mostly slow, unreliable and expensive (and metered). To get around you might have Netscape (launched 1993), revolutionary for the time, the direct ancestor of modern browsers. To find anything you might use Yahoo! (founded as Yahoo! in 1994) or, like me, you might have deserted to Alta Vista (1995). Google was not around until 1998.  Flash appeared in 1996, Shopping on very basic websites, if you were in the US, you could buy a book from Amazon (founded 1995).   Sean McManus has a nice History of the Internet page, if you want to find more time points.

    The Internet Archive has some lovely captured pages from websites of that era: they had to be simple to work with slow connections and primitive browsers. Here is Microsoft's from 1996. Or IBM from 1995.

    Yes, it's hard to remember how primitive things were, compared with today...

    Nonethless, the Internet was clearly coming, and for a few years newly-minted companies could be rushed to the stockmarket in an Initial Public Offering (IPO) and appear to be worth crazy fortunes. Totally Wired discusses a factor that I had not considered - the IPOs usually included a big price rise during the first morning of trading, and while staff of the dotcom company were "locked in", unable to sell their shares, typically for 12 or 18 months, their bankers were able to sell that morning and turn a nice profit ontop of the fees and commissions. Hard though it may be to believe that banks would ever mis-sell anything, I suspect that Andrew Smith is right in thinking that the profitability of the IPOs for the banks really helped stoke the bubble.

    STM Journals publishers were already seeing demand (there was an online edition of the Current Biology Journals when I worked there in 1993), but other publishers, such as my employer at the time, Oxford University Press (not the Journals bit), were initially cautious about the Internet. One reason was that several of them had financial hangovers from the CD-ROM bubble earlier in the '90s. The CD-ROM had been going to be the great thing in those days, but turning books into databases or multimedia experiences had proved expensive, and the mass market elusive. So my dotcom experiences were mostly of being involved in preparing data form OUP copyrights and working on licensing it to the dotcommers. Quite a profitable line of business if you insisted on a non-exclusive licence, payment on data delivery, and cashed the cheque fast before the company ran out of money.

    To begin with, we met very sincere-seeming folks who (as far as I could tell) truly believed that the Internet would be a great commercial opportunity (they were of course right about that). Also they believed that there would be a huge "First-mover advantage" such that it was essential to get into the market before it became big (they were not right about that -  those who waited and entered later often did well). Later, when it all tended to be seen as an abberation or a swindle, I wondered with Andrew Smith:

    "Did the kids [the often youthful dotcommers] dupe the establishment by drawing them into fake companies, or did the establishment dupe the kids by introducing them to Mammon and charging a commission for it?"

    (He seems to come to the conclusion that there was a lot of the latter).

    Certianly a lot of the action became speculating in dotcom stocks, well ahead of any sniff of profitability. Writing in 1997, Jakob Nielsen said:

    "The two classic errors in predicting the future of a technology shift are to over-estimate its short-term impact and under-estimate its long-term impact. The Web has been hyped to such an extent that people overestimate what it can do the next year or two: most websites are not going to turn a profit any time soon. But please don't underestimate what will happen once we reach the goal ofeveryone, everywhere; connected. The impact of networks grows by at least the square of the number of connections, and the true value of the Web will be only be seen after extensive business process reengineering."

    From the periphery, there were interesting signs that things were getting out of hand.  We began to get swamped with requests to meet us and developed a policy that we'd have no more meetings at which the vistor's dotcom plan would be unveiled as a surprise for us (with the flourish of a fountain pen with which to sign a non-disclosure agreement). Instead, potential partners had to write outlining their plans first, in confidence if they wished. We also indicated that we tended to like cash in return for licensing data. These steps were just a precaution against completely pointless meetings. Well, pointless to us:, I think there was value in dotcoms being able to claim to investors that "they were in negotiations with Oxford University Press", even if, as per Qui-Gon Jinn, "The negotiations will be short.". But we were rather surprised at the number of requests that went no further once we asked to know in advance roughly what the meeting was about, and that we didn't plan on giving copyrights away. Which I suspect meant that at the end the market was being flooded with people with very little idea of how to do business, but with the conception that it should be terribly easy.

    When it all collapsed, the nay sayers (who had put up with a lot of "you old-business types just don't get it" from the dotcommers in their pomp) were loud in their derision.  But, as an Economist article the dotcoms come of age  in May 2004 notes:

    "Back in 1999, at the height of the internet frenzy, Forrester, a research company, forecast that online retail sales in America could reach $100 billion by 2002. When the bubble burst a year later, lots of crazy predictions went the same way as many dotcom firms. But if online sales of cars, food and travel are added to the official figures, then Forrester's forecast, which once looked so wild, has turned out to be only about a year late. The growth continues."

    And, interviewed in Andrew Smith's book, Fred Wilson (a venture capitalist) describes the long-term legacy of the bubble as follows:

    "A friend of mine has a great line. He says 'Nothing important has ever been built without irrational exuberance'. Meaning that you need some of this mania to cause investors to open up their pocketbooks and finance the building of the railroads or the automobile or aerospace industry or whatever. And in this case, much of the capital invested was lost, but also much of it was invested in a very high throughput backbone for the Internet, and lots of software that works, and databases and server structure. All that stuff has allowed what we have today, which has changed all our lives....that's what all this speculative mania built."

     

    October 16, 2012 in writing about others' writings | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    How Annals of Botany has made use of social media

    Social tools and academic publishing - How Annals of Botany has made use of social media

     

    July 04, 2012 | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    Many social media services (Ethnority's lovely taxonomy)

    The good people at ethnority have made this lovely diagram showing a classification of the many social media services available. This is the "German" version (with nearly all services recognisable to soemone in, say,  the UK or US).Social media flower_medium
    - they also have one for the Internet as seen from behind the Great Firewall of China Not shown).

     

    June 28, 2012 | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    Don't be a Hiro

    The TV show Heroes had a character, Hiro Nakamura, who could teleport in time and space. To do so he had to concentrate awsomely. Actor Masi Oka portrayed this with wonderful physicality (part of a superb performance, which made the earnest yet puppyish Hiro a treat to watch). It looks as if he is trying some barely manageable feat of strength or stamina.

    Hiro1

    It reminded me of something. As an inexperienced project manager I would sometimes try to force my projects along by sheer willpower. It doesn't work of course - once you are relying on others to do parts of the work rather than doing it personally, you lose the option of advancing things by, say, personally working late. So there are times when the project is temporarily beyond your control because you're up to date with your contribution and the rest of the team are working on theirs with all reasonable speed and care. It took me a while to get used to using the time to work on something else, instead of straining Hiro-like to teleport my project closer to its goals. I never did achieve teleportation or time travel, it just made me tired.

    June 21, 2012 | Permalink | Comments (2) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    van Gogh stops the Machine -- a paradox of virtual experience

    The Machine Stops is a well-known science fiction story by E M Forster, written in 1909. Forster imagines a world where people live in solitary rooms; technology meets all their wants and needs well, and travelling or meeting anyone face to face is seen as inconvenient and tedious. Of course, then things start to go wrong... Its a really good story, as well as being of interest as classic dystopian story raising worries about over-dependence upon technology and the substitution of direct experience for virtual ones.

    For some time now it has been possible to live as a cyber-hermit if you want - in 2000-2001 DotComGuy (born Mitch Maddox) lived for a year without venturing outside his backyard - ("The experiment was supported by corporate sponsors who wanted to persuade more customers to shop on the internet"). Such an existence would be massively easier and more convenient now, 11 years later.

    But I also notice another trend. Bands from every decade of my life are reforming and touring (unless, like  the Rolling Stones, they never left the road) and tickets  can cost far more than buying the artists' entire discography. There seems to be no shortage of people who want to go to other bug events, or to travel to exotic holiday destinations. And when they get there, the emphasis seems to be as much (or more) than ever about the direct experience you can have.

    So I wonder whether there is something going on a bit like "the paradox of automation". "The more efficient the automated system, the more crucial the human contribution of the operators. Humans are less involved, but their involvement becomes more critical." (Because if things start to go wrong, the machine which normally turns out 100 perfect components a minute will start turning out 100 pieces of junk per minute until the humans intervene). My thought is that, the more experiences can become virtual, the more important or valuable become those experiences we choose to have directly.

    I was thinking about this because of a recent family trip to Amsterdam to see the van Gogh museum. That was something we all enjoyed, even though it is easy enough to see most of Vincent's work in books or online at a fraction of the cost and time of a trip to Holland. True, you can't yet get reproductions that show you all the details (such as the texture caused by brush-strokes or a palette knife), but even if, as I expect, complete VR facsimile is possible before too long, I think we'd still have wanted to have gone in person.

     

    June 08, 2012 in ideas parking space | Permalink | Comments (0) | TrackBack (0)

    | Digg This | Save to del.icio.us |

    »

    google box

    • google box
      Google

      all Google
      this blog only

    Adsense

    Subscribe in a reader
    Subscribe to Usability Notes - by Chris Baker by Email

    Archives

    • May 2013
    • December 2012
    • November 2012
    • October 2012
    • July 2012
    • June 2012
    • May 2012
    • April 2012
    • January 2012
    • December 2011

    More...

    Categories

    • Accessibility
    • Announcements
    • Books
    • Case Studies
    • Current Affairs
    • Customer behaviour
    • e-marketing and e-commerce
    • Email marketing
    • Games usability
    • ideas parking space
    • mobile
    • My usability experiences
    • Nice usability ideas
    • Pet hates
    • project management
    • Publishing
    • requirements analysis
    • Soapbox
    • social media
    • statistics and data
    • Tools
    • Usability and children
    • usage statistics
    • Useful usability resources
    • Web/Tech
    • Weblogs
    • website testing
    • Weird user interfaces
    • writing about others' writings
    • XML
    • Usability Notes - by Chris Baker
    • Powered by TypePad