We wanted a fairly quick and low-pressure usability test in the form of a lean evaluation before developing the medium-fidelity prototype.
Lean Evaluation & 1st Iteration
The issues identified in the evaluation are below.
• Removed ability to add due dates (Critical Issue): The reliability of crowd sourced due dates was a constant concern of users. We decided to pull that information directly from the university's database.
• Changed functionality of trending screen (Critical Issue): Assignments trending were unclear with the voting system. These trending assignments are now based on the number of comments.
• Changed wordy buttons to icons (Moderate Issue): Awkward wording of buttons caused confusion in functionality.
• Added header for clarification (Minor Issue): Users requested a header above the calendar to clearly indicate what was on the screen.
These changes were implemented into the medium-fidelity prototype, designed in Balsamiq, from the lean evaluation.Download Medium-Fidelity Prototype (Balsamiq file)
Summative Evaluation & 2nd Iteration
Our team’s project ended at the medium-fidelity prototype, but I continued on by performing a summative evaluation myself to develop a higher fidelity prototype.
The feedback from this evaluation prompted some design changes before the last iteration.
• LIKED the ability to view and discuss assignments in one place
• CONFUSED by the “Due Soon” not being specific enough
• CONFUSED by naming of “Trending” feature
• SUGGESTED adding a search feature for assignments
• SUGGESTED improving readability of comments section
• SUGGESTED adding clarity on what the function of each button is
Below is the higher-fidelity prototype where I implemented these changes.