top of page

Usability Research Questions



Usability research is an important aspect of design, and it's especially crucial for intranet platforms, which are often used as a central hub for communication and information within an organization. When designing an intranet platform, it's essential to consider the user experience and ensure that the platform is easy to use and navigate.

One way to gather feedback on the usability of an intranet platform is to conduct a usability research study. This type of study allows you to collect valuable insights from users about their experience with the platform and identify areas for improvement.

Here are some potential questions you could ask in a usability research study for an intranet platform design:

  1. How easy is it to navigate the intranet platform?

  2. Can you easily find the information you are looking for?

  3. How useful are the search results?

  4. Are there any features that are particularly useful or confusing?

  5. How does the intranet platform compare to similar tools you have used in the past?

  6. What, if anything, would you like to see added or changed on the platform?

  7. Is the platform easy to use on different devices (e.g. desktop, laptop, tablet, phone)?

  8. How much time do you typically spend on the platform in a given session?

  9. How often do you use the platform?

  10. Do you have any suggestions for improving the platform's usability?

Asking these types of questions during a usability research study can help you gather valuable insights into the user experience of your intranet platform. By considering the feedback you receive, you can make necessary changes to improve the platform's usability and ensure that it meets the needs of your organization.


Usability principles refer to guidelines for designing user-friendly products. These principles can help designers create products that are easy to learn, efficient to use, and satisfying for the users. Here are some examples of usability principles:

  1. Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within a reasonable time.

  2. Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

  3. User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

  4. Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

  5. Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

  6. Recognition rather than recall: Minimize the user's memory load by making objects, actions,