This is one of the 52 terms in The Language of Technical Communication published by XML Press in 2016 and the contributor for this term is Eric Reiss.
What is it?
The degree to which an individual can accomplish specific tasks and achieve broader goals while using a particular tool or service.
Why is it important?
Despite the constant overuse of the term and misuse of the research, industry professionals have long known that good usability often holds the key to business success both on- and off-line.
Why does a technical communicator need to know this?
Usability is traditionally associated with the technical or functional aspects of an interactive product – ease of use. For example, do the buttons work? Are they conveniently placed? Is the server response time fast enough, etc. But technical communicators need to focus on the psychological side of the usability coin: elegance and clarity. We need to communicate in a clear, concise, and understandable manner that creates a shared frame of reference with the reader.
This is the list I give my “Writing for the Web” students:
- Don’t take anything for granted
- Anticipate the questions people might have
- Answer the questions they didn’t think to ask
- Examine your content (words, images, sounds) in the context of your reader’s situation
As always, the communication environment – the time and place surrounding an experience – will affect the nature of the information needed (or provided) at any given time. For example, reading a printed manual when setting up a new smart TV will be very a different experience from that of an engineer looking for troubleshooting tips on a smartphone somewhere out in the field.
And finally (and perhaps most important of all), remember:
- Whatever you say, say it clearly, without resorting to insider terms
- Don’t assume everyone reads as carefully as you write