Usability Tests

Usability Testing Plan

TODO: Detail the procedure we followed for the usability tests

Usability Testing Results - Round 1

Dispatcher Survey Results

Likert Scale Questions (login, load scenario, speed up simulation, assign tasks, re-order tasks):

Dispatcher Task Completion Time Results

TODO

Scenario Admin Survey Results

Likert Scale Questions (usability of scenario editor, helpfulness of error messages):

Open-ended Questions (scenario editor feedback):

Feedback pertaining to the scenario editor:

• Issues due to the use of the JSON format to define the scenarios (clarity, readability, troubleshooting validation issues, too text-heavy) (7 mentions)
  • Alternatives proposed include a different format than JSON, form-based (4), a datetime picker for timestamp fields, map-based (world-builder-esque)
• The scenario editor lacks functionality expected in text editors (tab-friendliness, line numbers, syntax coloring, collapsable fields) (2 mention)
• Difficult to understand what to delete and what not to delete in the json editor (1 mention)
• The scenario doesn't save automatically when pressing Start simulation (1 mention)
• Desire for the ability to drag a JSON file over the editor to import / save it (1 mention)
• The use of red for the selected scenario is confusing since red is usually used to indicate something bad (1 mention)
• The placement of the scenario description field before the scenario content field is unatural (1 mention)

Feedback pertaining to the login page:

• Log in page should allow white-space around the username (1 mention)

Feedback pertaining to the usability test:

• Titles in the task tables should match the json titles (1 mention)
• Instructions could be a little simplified (1 mention)

Bugs discovered:

• Clicking on the current scenario after it has been edited shows a "Unsaved Changes" card (1 mention)

Scenario Admin Task Completion Time Results

TODO

General User Feedback Compilation

TODO

Key Takeaways

TODO

Action Items & Issues Created

TODO