Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Time selection widget unnatural (moderate)
    • Remove the widget and just specify a format for user to type time
  • The user asked about the politician's office hours (minor)
    • We could gray out the unavailable hours in the date and time selection widgets
  • The "View Scheduled Calls" link in the menu bar was not immediately visible (minor)
    • Provide visual distinctions for buttons (colored boxes, perhaps)
    The voicemail record button has a microphone icon while external consistency calls for a red circle (cosmetic)
    • Change the icon to a red circle
  • The now button on the time entry widget confused the user because she had already entered a future date, and now does not make sense in that regard (mild)
    • Remove the now button when the date is not set to today
  • The time entry widget is not intuitively mapped (mild)
    • Use a more intutive time selector widget
  • it did not affect the date, only time (minor)
    • Have the now button apply to dates too
  • Possible safety issue for accidentally canceling scheduled calls (minor)
    • Add a confirmation dialogue
    The header buttons are not obviously buttons (cosmetic)
    • Change the background color and edges of the header hrefs to be more button like

User 3

Reflection

The iterative design process was useful, because it allowed us to make changes rapidly and then get feedback to double check that we had actually made an improvement with that change. If we were to do this again, we would probably investigate which technologies to use more carefully. For all of us this was our first time using css, javascript, or php, and while we got the work done, we had to spend more time learning the technology than we would have liked. However, now that we know the technology better, it would be useful to run more high fidelity tests, because we believe the feedback from testing phases that actually involved a computer (heuristic evaluation and final user testing) to be the most valuable and actionable. For example, even though our paper prototype had radio buttons on the filter tab, none of our test subjects commented on them, and this was likely due to the low fidelity of paper. Again, web prototyping is so quick, that we think it might have been more useful to test a wire-frame prototype a little earlier on.