Usability Week Day 3
Intranet Usability 2
I realized 5 minutes into today’s session that I made the mistake of picking Writing for the Web 2 instead of Intranet Usability 1 yesterday. With each moment I was seriously wishing I had been here for yesterday’s.
Intranet Usability 1 & 2 were taught by Kara Pernice, Managing Director at NN/g. Kara also ran the focus group on webinars I attended on the first day. I found Kara to be very intelligent, personable and knowledgable.
Yesterday they went into detail about the research background so it was only briefly reviewed today. They studied 27 intranets with employees from the companies. They watched the employees complete tasks during their normal work routine. They weren’t able to show us videos today because companies don’t feel comfortable allowing them to she shown.
The top tasks employees need on an intranet:
- find an employee’s phone number or email
- find information about a group
- find information about a high-level manager
- find information about a policy
- make a request or order
- apply for another job (within the company)
- sign up for a training course
- find information for a training course
- find information via search
- update some personal information (HR or status)
- find past news
- login (additional applications)
Kara explained how important it is to understand your users, which is different from web users. Your intranet users are trying to accomplish a task related to their job. Often they are interrupted often or have to share a workstation. A good way to determine their needs is to hold usability studies.
Things to keep intranet use easy, and therefore ensure it is used, include a good web address, a single login and timeouts that are at least 20 minutes. Personalize the intranet whenever possible by having the user’s name and information automatically populated and by showing only the areas accessible by the employee. Allowing staff to customize with a frequently used section that allows them to save pages the use often can be very helpful.
Creating a single forms repository is important because staff don’t often know which department has which form. Enabling this page to be sortable by name and department is important as well. A description should also be included, especially for forms named in a uncommon way, such as a number, that an employee might not remember. It is also important to offer forms in HTML and not PDF, Word or Excel. This can also allow for online submission, creating a faster business process. Instructions should be included in an easy to understand way with a help option.
Text should be written without jargon or company lingo because new employees don’t understand it and it makes it harder to change company culture in the future. Content should be written succuntly and respectfully without chastizing staff. Avoid things like red text and exclamation marks. If the content is written in an easy to understand way this shouldn’t be needed.
Dictionaries should be searchable and offer both commonly used acronymns and definitions. Another good solution is allowing staff to use a wiki to create the dictionary. This both gives them ownership and creates an easy way for staff to keep the information updated.
We reviewed some of the key points of Writing for the Web 1, including scanning, bolding important words, headlines, succinct paragraphs and bulleted lists. All of the information offered in those sessions is applicable to intranets.
Navigation and terminology should be clear, organized by the tasks staff need to accomplish and avoiding branding, catchey phrases and unclear icons. Top-level navigation should be accessible from anywhere on the intranet and users should always know which section they are in. While it is important to have departmental sections, they should be used for the deparment’s staff and common tasks should be available on top-level navigation. For example, HR documents should be easily accessible by everyone. Information should be cross referenced when possible.
The Intranet design should be consistent across all departments, including all applications. Employees should always know they are on the company’s intranet and not suddenly feel as though they’ve been redirected somewhere else. This brings more credibility to the intranet.
Search results should repeat the query and allow users to easily access the results after they’ve selected an option. They should also include a description of the result. A new search field should be included on the results page as well. When there are no results a statement should appear so the users knows the search is complete.
Staff directories should be searchable and should include title, phone number (and extention), email and location. A short bio is also nice to include, as well as accomplishments, repsonsibilities, photo, hours, supervisor and administrative assitant.
News is important to feature on the site and should be available on the home page. It must be accurate, new and valuable. It’s nice for employees to see updates about projects they may have heard of but are not a part of.
Training sessions are important to offer to staff and should include the title, a description, instructor, who can/should take the class, date, time and location. Allowing staff to sign up online, with a notice going to the staff’s supervisor for approval, speeds up the process.
Help Desks can use the intranet to lessen the number of calls by offering commonly requested problems and solutions. These should be offered in clear, common language and not in technological jargon. Manuals can be posted online and wiki’s can be set up for self-help.
Kara finished by offering tips on conducting an intranet usability study. She suggested holding regular evaluations and recruiting users from various departments. She said to allow an employee to work as they normally would and stay for the entire day, if possible, or ask when they usually use the intranet and visit then. She said you should observe without offering tips or solutions and sit behind the person so they won’t talk to you. Do not allow their supervisor to watch and make it clear it is not a test – in fact, if possible, don’t even tell the person you are coming so they won’t “study” beforehand. You want as natural a setting as possible. Watch users in their own environment, noticing interupptions and other workflow stoppages as they normally occur. Finally, be very respectful of employees and their time.
Overall, I found today to be very useful. I was able to purchase the book from Intranet Usability 1 and I hope to gain some good information from it. Kara was wonderfully articulate and engaging as she offered many opportunities for us to participate. It was very educational and I regreat missing the first session.
I enjoyed the entire experience at Usability Week 2009 immensley. I had lunch with the group of friends I met at the social networking event last night and I feel like I left with a better understanding of my industry and where it is going. I am armed with some wonderful tools that will serve me well. Thanks to the Nielsen Norman Group for putting on a this event.