I'm going to do user tests on a Chorded/Chording Keyboard. I would like to know, if there are any guidelines / tips for testing user-input (example sentences to input)?

  • Don't forget to test whether people can figure out how to plug it in / insert the batteries :-)
    – PhillipW
    Apr 15 '12 at 20:51
  • 2
    What are you testing: the keyboard or tasks?
    – dnbrv
    Apr 15 '12 at 21:11
  • I'm also confused, exactly what are you testing for?
    – Ben Brocka
    Apr 16 '12 at 1:32

I'm going to assume your aim is to determine whether a given physical/digital chorded keyboard device has usability issues when used by users who are familiar with using a chorded keyboard (e.g. court stenographers). Your situation might be, for example, a need to evaluate various replacement devices due to obsolescence or usability issues with the current deployed devices.


  1. Research the current situation to determine what factors are more important than others, and typical usage scenarios. Things like speed of entry vs accuracy, short bursty dictation vs sustained endurance-testing transcription, level of ambient distractions, and so on.

  2. Talk to existing users - find out what issues are being reported with any current equipment, find out how they became proficient, how they determine their proficiency level. Compare and contrast the user's comments with comments from managers, stake holders, project sponsors etc - there may be hidden differences in values to be resolved, and there may be usability issues being hidden by workarounds. Find out what class of errors are occurring frequently, and which are causing the most problems.

  3. Decide on the primary purpose of testing. Consider whether you are testing for purposes of discovering as-yet-unknown problems, or testing relative quantitative qualities (speed, accuracy, etc). (aka Formative vs Summative usability testing)

  4. Shape and design your usability tests based on your research. These factors will determine what minimum ratings for accuracy and speed are to be tested, and what relative weightings to assign to any analysis of results. You also want to be sure you'll test relevant scenarios, and not wasting time/effort testing irrelevant scenarios.

  5. Watch out for the Experience Law of Learning if doing repeated tests with the same subjects/participants.

  6. Look to training materials for example texts to test with.

  • I'd differ to that Experience Law of Learning article: some things require a one off 'insight' for users to understand how they work. Once they've gained that insight they don't lose it again - so you can't reuse the participant.
    – PhillipW
    Apr 16 '12 at 9:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.