This gallery contains classic examples of bad technical publications. Who is responsible? We are quick to tar and feather the technical writer, but often there is plenty of blame to go around. The technical writer may have been crippled by an outrageously insufficient budget and a perversely short schedule, or someone may have made a flamboyantly bad decision that the technical writer was powerless to overrule. On the other hand, we should never discount the ability of a truly bad technical writer to make users miserable.
One of the best ways to avoid the Rogues' Gallery is to test your technical publications on real, live users.
Return to Usability Testing page.