Skip to main content
Version: Next

Usability Tests

Introduction

After defining personas and scenarios and understanding the context in which our application operates, we wrote use cases, user stories, and acceptance criteria. Finally, we created a low-fidelity prototype in Figma and needed to evaluate whether the application functioned well from the users' perspective.

We tested the prototype with 11 participants: 6 students and 5 Medicine Tutors. All users signed a consent form and completed a list of tasks within the prototype.


Mockup 1
Mockup 2

Below, you will find the results and possible usability issues that students and tutors encountered while navigating the app. These issues were documented in a final form filled out by users, where they provided suggestions, highlighted problems, pointed out inaccuracies, and recommended areas for improvement. Additionally, they completed a System Usability Scale (SUS) questionnaire.


Usability Testing Tasks

Student Interface

To test the student interface, we selected five key tasks that students are expected to perform:

  1. Perform self-assessment for the next evaluation (USF) with the following autonomy levels:
    • MEC14 - N1
    • MEC15 - N3
    • MEC16 - N3
    • What is the response after submitting the self-assessment?
  2. Check the evaluation obtained in USF4.
    • What was the autonomy level achieved in MEC 3?
  3. View the number of approved MEC points.
    • What is the approved point value?
  4. View the procedure for MEC 1 or "Person-Centered Medical Approach."
    • How many steps does this MEC have?
  5. Request a re-evaluation of MEC 3.
    • What feedback was received?

Tutor Interface

To test the tutor prototype, we selected five key tasks:

  1. Check when the next evaluation is scheduled.
    • What is the date and time of the next evaluation?
  2. Perform an evaluation for USF5 for the student Maria do Mar with the following autonomy levels:
    • MEC14 - N1
    • MEC15 - N2
    • MEC16 - N2
    • What feedback is received after submitting the evaluation?
  3. View the procedure for MEC 1.
    • How many steps does this MEC have?
  4. Check the calendar.
    • On what date is the next evaluation?
  5. Approve a student's request to re-evaluate MECs in the next USF.
    • What feedback was received?

Results

Student Results

TaskDescription
TASK 1Perform self-assessment for the next evaluation (USF) with predefined autonomy levels.
TASK 2Check the evaluation obtained in USF4.
TASK 3View the number of approved MEC points.
TASK 4View the procedure for MEC 1 or "Person-Centered Medical Approach."
TASK 5Request a re-evaluation of MEC 3.
Mockups

Tutor Results

TaskDescription
TASK 1Check when the next evaluation is scheduled.
TASK 2Perform evaluation for USF5 for Maria do Mar with predefined autonomy levels.
TASK 3View the procedure for MEC 1.
TASK 4Check the calendar.
TASK 5Approve a student's request to re-evaluate MECs in the next USF.
Mockups

Problems and Strengths

Tutor Prototype

Usability Problems

ProblemDescription
Task completion color differentiation and text inconsistencyThe homepage should have distinct colors and uniform text sizes for upcoming and past evaluations.
Difficulty finding the re-evaluation request sectionThe "Requests" section should specify request and validation dates.
Calendar is not intuitiveUsers had difficulty finding and understanding evaluation identifiers.
MEC Search ButtonThe search button in the navbar is not intuitive, confusing users.

Strengths

  • Tutors appreciated the statistics feature, finding it particularly useful and engaging.
  • The evaluation forms were quite complete. The colors made the form easy to fill out.

Student Prototype

Usability Problems

ProblemDescription
Highlight key points in evaluationsWhen students need to fill in strengths and weaknesses, they often struggle with the forms and need autocomplete suggestions to make it easier.
Places to request re-evaluationThe re-evaluation request button on the homepage is not intuitive enough, and there should be access points in the evaluation section.

Strengths

  • The statistics feature was also highly appreciated by students.

System Usability Scale (SUS) questionnaire

Average SUS Score: 81

Mockups

User Evaluation Conclusion

Users found the prototype intuitive, easy to use, and well-organized. Initial adaptation was quick, despite some feeling slightly overwhelmed at first.