Evaluating Usability with Nielsen's Heuristics: A Step-by-Step Guide for Your CS 2704 Final Project

Introduction: Why Expert Evaluation Matters for Your CS 2704 Final Project

In the CS 2704 final project, you are asked to evaluate an existing app using Nielsen's heuristics. This expert evaluation technique helps you uncover usability issues without needing real users. By following a structured method, you can produce actionable redesign suggestions. This tutorial walks you through each step, from choosing an app to writing your report. Whether you are testing a to-do list app, a note-taking tool, or a simple game, the principles remain the same. Let's dive in.

Step 1: Choosing the Right App for Your Evaluation

Your app must be task-based, free to use, and not require personal information. Consider open-source alternatives like those on osalt.com. For example, you could evaluate Joplin (note-taking), GIMP (image editing), or Audacity (audio editing). These apps are cross-platform and allow intensive use in 30 minutes. Why might your chosen app reveal usability issues? Perhaps its interface is cluttered, or key features are hidden. In your report's Introduction & Background section, you will compare three similar apps (e.g., Evernote, OneNote, and Joplin) and argue why Joplin may have more issues—for instance, its steep learning curve or inconsistent navigation.

Step 2: Understanding Nielsen's 10 Usability Heuristics

Nielsen's heuristics are the backbone of your evaluation. They include:

1. Visibility of system status – Keep users informed about what is happening.
2. Match between system and the real world – Use familiar language and concepts.
3. User control and freedom – Allow undo and redo.
4. Consistency and standards – Follow platform conventions.
5. Error prevention – Prevent problems before they occur.
6. Recognition rather than recall – Minimize memory load.
7. Flexibility and efficiency of use – Provide shortcuts for expert users.
8. Aesthetic and minimalist design – Avoid irrelevant information.
9. Help users recognize, diagnose, and recover from errors – Use clear error messages.
10. Help and documentation – Provide searchable help.

These heuristics are like the rules of a game: they help you spot fouls in the user experience. For example, if an app does not show a loading indicator, it violates heuristic #1. Just as in a popular game like Fortnite, where the health bar keeps you aware of your status, your app should keep users informed.

Step 3: Assembling Your Expert Team

You need three experts: yourself and two classmates. Each expert should independently evaluate the app using the heuristics. To avoid bias, do not discuss findings until after data collection. Provide each expert with a list of tasks (e.g., create a note, edit a photo, export a file). Ensure the tasks can be completed in 30 minutes. Use a dummy account if needed. For remote testing, use screen-sharing via Zoom. Record the sessions (with permission) for later analysis.

Step 4: Conducting the Evaluation and Collecting Data

Each expert performs the tasks while noting any heuristic violations. Create a spreadsheet with columns for: Heuristic, Problem description, Severity (0-4), and Location in app. For example: Heuristic #1: No feedback when saving a file. Severity: 3 (major). Location: File menu. Collect at least 10-15 issues per expert. This is like a sports analyst reviewing game footage—you look for patterns. For instance, if all experts report that the undo function is missing, that is a critical issue.

Step 5: Analysing the Data and Identifying Redesign Suggestions

Combine the issues from all experts. Group similar problems and calculate average severity. Prioritize issues with severity 3 or 4. For each, explain why it violates a heuristic and propose a fix. For example: Problem: The app does not confirm before deleting a note (violates heuristic #5: Error prevention). Fix: Add a confirmation dialog with 'Undo' option. You can illustrate with simple wireframes (hand-drawn or using tools like Balsamiq). In your Findings & Discussion section, present a table of issues and your redesign suggestions. Use bullet points for clarity.

Step 6: Writing Your Report

Your report should follow the structure:

• Introduction & Background (25%): Review three similar apps, compare them, and justify your choice. For instance, compare Joplin, Standard Notes, and Boostnote. Explain that Joplin's sync issues and lack of templates may cause usability problems.
• Method (15%): Describe how you conducted the evaluation, the tasks, the experts, and the data collection process. Mention that you used Nielsen's heuristics and a severity rating scale.
• Findings & Discussion (50%): Present the top 5-7 issues in detail. For each, show a screenshot (if allowed), describe the heuristic violation, and propose a redesign. Discuss how your findings could improve the app's design. For example, adding a search bar would enhance efficiency (heuristic #7).
• Conclusions & References (10%): Summarize the key findings, note limitations (e.g., small sample size, lack of real users), and suggest future work (e.g., user testing). Include references to Nielsen's articles and the apps you reviewed.

Example: Evaluating a Simple To-Do App

Let's say you choose a to-do app like Todoist (free version). Your three experts perform tasks: add a task, set a due date, create a project, and use a filter. You might find:

• Issue 1: No confirmation when deleting a task (heuristic #5). Fix: Show an undo toast.
• Issue 2: The filter syntax is confusing (heuristic #2). Fix: Use natural language like 'today' instead of 'today|overdue'.
• Issue 3: No keyboard shortcuts for power users (heuristic #7). Fix: Add shortcuts like 'Ctrl+N' for new task.

In your discussion, you can relate these to real-world trends: just as AI-powered apps like Notion AI use natural language, your app should too. Or compare the need for shortcuts to how gamers use hotkeys in League of Legends.

Common Pitfalls to Avoid

• Choosing an app that requires login or payment: Stick to free, no-account apps.
• Not defining tasks clearly: Provide a written task list to all experts.
• Ignoring severity ratings: Use them to prioritize fixes.
• Forgetting to reference sources: Cite Nielsen's 10 heuristics and the apps you compare.

Final Tips for a High-Grade Report

To score in the 70-100% range, ensure your explanation of why the chosen app may reveal issues is backed by background research. Use the method rigorously: have each expert work independently, and document everything. Present findings clearly with tables or figures. Discuss limitations thoughtfully—for example, the lack of real users means you might miss issues that only appear in natural use. Suggest future work like A/B testing. Finally, format references consistently (e.g., APA).

Remember, this evaluation is like a health check-up for an app. By following Nielsen's heuristics, you can diagnose problems and prescribe fixes. Good luck with your CS 2704 final project!