Heuristic Evaluation

Introduction

Medium is a popular online publishing platform with a clean design and a focus on reading experience. This heuristic evaluation analyzes its user interface to identify usability strengths and weaknesses.

Project Objectives

The objective of this heuristic evaluation is to identify potential usability issues within the Medium.com website's interface. The evaluation will utilize Jakob Nielsen's 10 usability heuristics as a framework.

10 Usability heuristic for user interface design

1. Visibility of system status

2. Match between the system and the real world

3. User control and freedom

4. Consistency and standards

5. Error prevention

6. Recognition rather than recall

7. Flexibility and efficiency of use

8. Aesthetic and minimalist design

9. Help users recognize, diagnose, and recover from errors

10. Help and documentation

1. Visibility of system status

Issue: Lack of clear "next step" guidance

Description: Users may not intuitively understand what action they should take after seeing an article excerpt (or preview). The lack of a clear "Read more" call to action could lead to confusion or disengagement.

Suggestion for Improvement: Add a clear "Read more" button or link. Implement a prominent visual element below each article preview to explicitly signal the next step for the user. This should be visually distinct and consistently placed for easy recognition.

Example:

Original: [Article Title]

[Short excerpt from the article...] Improved:

[Article Title]

[Short excerpt from the article...]

[Read more] (Button or visually emphasized link)

Issue: Lack of Persistent Navigation

Description: The lack of a persistent navigation bar or menu has several negative effects:

  • Disorientation: Users might feel lost, especially when deep within the site's content.
  • Reliance on the "Back" Button: This forces users to overly rely on their browser's "Back" button, which isn't always a reliable or efficient way to navigate.
  • Reduced Discoverability: Important sections of the site might be overlooked if users don't stumble upon them organically.

Suggestions for Improvement:

  • Implement a Persistent Navigation Bar: Place a bar (top or side) containing links to core sections of the site:
  • Home
  • Key Topics or Categories
  • User's profile/settings
  • Search functionality
  • Contextual Navigation: Include in-page navigation, such as breadcrumbs (as discussed earlier), especially for content organized hierarchically.


Severity: 4

2. Match between the system and the real world

Issue: Inconsistent Visual Language for "Hiding" Functionality

Description: The button used for "hiding" content deviates from familiar icons or conventions for this action. This inconsistency forces the user to learn a new visual association to understand the button's purpose, potentially leading to hesitation or misinterpretation.

Suggestion for Improvement: Utilize a more common symbol for "hiding," such as:

An eye icon with a slash through it (representing something being hidden from view)


Severity: 2

3. User control and freedom

Issue: Lack of User Control in sorting or filtering the results

Description: Users are unable to customize how search results or lists of content (like on a topic page) are displayed. This limits their ability to efficiently find the information that most closely matches their needs or preferences.

Suggestions for Improvement:

  • Sorting Options: Implement basic sorting controls such as:
  • Date (newest/oldest)
  • Relevance (if search results are involved)
  • Popularity (if applicable, based on claps or views)
  • Filtering: If appropriate, provide filters to narrow the content displayed.


Severity: 3

Issue: Lack of Sorting/Filtering within Topics

Description: Users exploring content within a chosen topic are unable to refine the results. This hinders their ability to quickly find relevant articles, particularly when topics are broad and contain a high volume of content.

Suggestions for Improvement:

  • Implement the previous solutions within a topic context: Add sorting (date, relevance, popularity) and filtering options (article length, author, sub-topics) specifically tailored to the selected topic.
  • Visually clear scoping: Provide a visual indicator to confirm to the user that sorting and filtering are now applied within the boundaries of their selected topic.


Severity: 3

Issue: Lack of Navigational Aids

Description: The absence of a "Back" button and breadcrumbs creates these problems:

  • Users may feel lost or unsure of how they arrived at a specific page.
  • It becomes difficult to move back to a previous section or to higher-level categories.
  • Reliance on the browser's "Back" button can be unreliable, especially in complex browsing scenarios.

Suggestions for Improvement:

  • Implement Breadcrumbs: Add a breadcrumb trail near the top of the page to display the user's navigation path (e.g., Home > UX research > User experience > The new old. Make all elements except the current page clickable links.
  • Consider a "Back" button: If space allows, a simple "Back" button that takes the user to the previous page could provide direct and convenient navigation, especially when they haven't navigated along a clear hierarchical path.


Severity: 3

Issue: Lack of Flexibility and Forgiveness in Clapping Description: The current "clap" system has several drawbacks:

  • Accidental Claps: Users might unintentionally tap the clap button, especially on mobile devices.
  • Changing Evaluation: A user may want to reduce their level of enthusiasm (number of claps) after beginning to read the article, but he can’t.

Suggestions for Improvement:

  • Tap-and-Hold: Change the clap action to require a tap-and-hold gesture, reducing the likelihood of accidental taps.
  • Undo Option: Implement a short time window (e.g., 5 seconds) after clapping where an "Undo" option appears.
  • Integrate an "Undo" or "Edit Claps" function accessible within a short time frame from the clap button itself.


Severity: 2

4. Consistency and standards

Issue: Inconsistent Placement of date and read time

Description: The varying placement of date and read time across different article views (list views, full article, etc.) has these drawbacks:

  • Users waste time scanning to find this essential information
  • It breaks the natural flow of reading, as users might mentally stumble when encountering an unexpected layout
  • It reduces trust in a site's attention to detail

Suggestions for Improvement:

  • Choose a Standard Location:
  • Above the title is a common and effective location.
  • Below the title could also work but risks being less scannable.
  • Apply the Location Consistently: Enforce this placement across all article list views, full article pages, topic pages, etc.
  • Visual Style: Ensure the date and read time visually recede compared to the title, using a smaller font size or reduced color contrast.


Severity: 2

Issue: Inconsistent UI for the Following

Description: The use of multiple button styles for the same purpose can lead to:

  • Confusion: Users may be unsure whether the different buttons all trigger the "Follow" action.
  • Hesitation: Increased cognitive load as the user has to decipher if different buttons have different meanings.
  • Missed Opportunities: Users might fail to notice the option to follow someone if the button isn't visually consistent with their expectations.

Suggestions for Improvement:

Unify the Design: Choose ONE clear and distinct button style for "Follow" actions and use it consistently throughout the entire site. This button should have a clear label ("Follow") and a visual style that makes it immediately recognizable.


Severity: 3

5. Error prevention

Issue: Destructive Action Without Confirmation or Undo Description: This issue introduces a high level of risk for users:

  • Accidental Clicks: Especially on mobile devices, a single tap could lead to the loss of the user's entire history.
  • Lack of Understanding: Users may not fully grasp the severity of the action before clicking the button.
  • No Recourse: Once executed, there's no way to recover the lost history.

Suggestions for Improvement:

  • Confirmation Dialog: Implement a clear confirmation dialog that explicitly states:
  • The action is about to delete the user's ENTIRE history.
  • The action is irreversible.
  • "Undo" Option: If technically feasible, provide a short window (e.g., 10 seconds) where an "Undo" button allows users to reverse the action.
  • Less Destructive Alternative: Explore if a less severe option could achieve a similar purpose:
  • "Clear History for the Past Week/Month"
  • Selective deletion of specific history items


Severity: 3

6. Recognition rather than recall

Issue: Lack of Social Proof on Article Listings

Users would benefit from being able to quickly recognize the popularity of an article rather than having to navigate to the article itself to discover this information. Description: The absence of clap and comment counts on article previews has the following consequences:

  • Reduced Decision-Making Cues: Users lack a key indicator of an article's potential value or relevance based on engagement from other readers.
  • Increased Friction: Users are forced to click through to each article individually to assess its popularity.

Suggestions for Improvement:

  • Display Key Metrics: Include the number of claps and comments directly on the article preview in a visually subtle way (e.g., small icons with accompanying numbers).
  • Selective Display: Consider a threshold where social proof indicators only appear after an article reaches a certain level of engagement (this balances discoverability with maintaining a clean aesthetic).
  • Sorting Option: At the very least, allow users to sort article listings by popularity, even if the metrics aren't immediately visible.


Severity: 3

10. Help and documentation

Issue: Poor Discoverability of "Help" Description:

  • Limited Support: Users are confined to self-help resources, and unable to get direct, personalized help.
  • Potential for Worse Problems: Unresolved user issues could escalate into negative word of mouth or frustration leading to abandoned accounts.

Suggestions for Improvement:

  • Prominent "Help" Placement:
  • Include "Help" in a persistent navigation bar
  • Place a "Help" link in the footer of every page
  • Clear Contact Options:

Provide a "Contact Us" link with either an email form or, ideally, directions on how to connect with live support (chat, phone, etc.), if this service is offered.


Severity: 4