Difference between Usability and Information Architecture

Though the terms Usability and Information Architecture are often understood to be the same thing, this is not true.

Usability
This tends to study a person’s ability to do (i.e. use) something, such as reading text on a webpage. Usability is not restricted to the web and is used across many industry sectors. For example, car designers perform usability tests to examine how a driver understands new design modifications.

Information Architecture
This focuses on how to design information. On the web, this involves reading text, labelling items, creating navigation systems, searching for data, using content and so forth.

Web Usability Tests
Usability engineers test websites to see how they suit the user’s needs. To do this, they may test the following:

  • Ability to read text.
  • Ability to use site navigation.
  • Effect of colors and site palette.
  • Ability to use Feedback and Help sections.
  • Length of time to find an article.
  • Locating key contact information.
  • Navigation cues and icons/graphics to see if they assist or hinder the user*.
  • Reaction to ‘innovative’ design elements, such as floating windows.
  • Reaction when lost.

* Users rarely interpret icons as Graphic Designers would expect.

Focus Groups
Focus Group tests are often carried out in one-on-one sessions. Sometimes testing is performed on several test subjects at the same time. However, you need to monitor these sessions as the most active people will influence the more passive participants.

During a test, the moderator asks users to perform certain tasks, gauges their ability to carry out them, and note where/why they encountered any difficulties.

They ask open-ended questions on what was useful, intuitive, difficult, and how to improve things. Large scale focus groups consist of 10 or more individuals. The Usability Engineer may show prototypes in order to isolate specific issues in navigation, process, and usability.

Rules for Usability Testing
When performing usability testing, try to avoid Yes/No questions when interviewing your subjects. These responses will provide little depth and avoid them discussing their experience.

Use open-ended questions, such as, “Why do you like this site?” as this is more productive that the more blunt: “Do you like this site?”

Use chart and diagrams to share feedback with the Graphic Designers—many of whom will be overly enamoured with their own creations.

Objective data may encourage them to improve their design without crushing their feelings. Management also tend to favour charts which show the results and enables them to digest the key points quickly.

Download these templates to start

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan