Buy Leads , RDP , SMTP , Cpanel
Buy Leads , RDP , SMTP , Cpanel
Buy Leads , RDP , SMTP , Cpanel
Writing better links

Writing better links

color-writing.jpg

Let’s talk links. That’s right, web links. Because most of the links we see on intranets and employee portals just stink. That’s right, stink.

Recent client usability testing efforts resulted in some classic examples of how not to do it.

  1. Avoid using software package titles as links: One client uses “Rosetta Stone” as the link to the language learning modules they offer employees. Problem is, most employees don’t know what Rosetta Stone is. They’d like to find the language learning options, but when asked to, can’t.
  2. Don’t separate what goes together. Notice how employees group and label a topic. For example, one group of employees is inclined to put compensation stuff together with benefits stuff. They can group the compensation stuff together, but they don’t know how to label it and they don’t really think of it as its own separate group. When put with “benefits” it all makes sense to them. So, the link becomes “Benefits & Compensation.”
  3. Don’t use acronyms for navigation. When faced with a bunch of HR navigation such as FMLA, L&D and SPD, most employees just ignored them and hit the search. Heavy use of search means your navigation is failing you.
  4. Don’t use terms that aren’t easily understood in every country. One term may not mean the same thing to employees in different countries. Some terms are far more recognizable to employees in the U.S. than in other parts of the world.

Obviously, links also must be prioritized and well organized. Here is some recent insight from Jakob Nielsen on the use of mega drop-down menus. We think this is a really cool approach for dealing with a lot of descriptive navigation.

But, it still has to be descriptive. Even a great mega drop-down menu won’t work if the link language is vague, unfamiliar and laden with acronyms.

Stacy Wilson, ABC, is president of Eloquor Consulting, Inc., in Lakewood, Colorado

About Us | Contact Us | Terms of Use | Privacy Policy | Copyright Communitelligence 2014-15

Follow us onTwitter.com/Commntelligence Linkedin/Communitelligence YouTube/Communitelligence Facebook/Communitelligence Pinterest/Communitelligence