...
Another design choice was that we did not implement user accounts. While this does limit the amount of social interaction user would have on this site, it does not prevent the user's experience for the main tasks. While many of the possible tasks in the site are social, these are not the primary focus of the site's interface. Our implementation has a single user, and supplies enough scenarios to give that single user the experience of the three defined user types (i.e., tournament administrator, player, and administrator+player).
Describe the internals of your implementation, but keep the discussion on a high level. Discuss important design decisions you made in the implementation. Also discuss how implementation problems may have affected the usability of your interface.
Evaluation
Describe how you conducted your user test. Describe how you found your users and how representative they are of your target user population (but don't identify your users by name). Describe how the users were briefed and what tasks they performed; if you did a demo for them as part of your briefing, justify that decision. List the usability problems you found, and discuss how you might solve them.
...
User | Usability Problems/Points of Confusion | Possible Design Changes |
|---|
User 1 | - Create a Tournament
- Problem locating "Create Tournament" button at the bottom of the page. Thought it should/would be at the top of the page next to the Tournaments label. (Monitor was fairly large resulting in little content at the bottom of the page, so eyes were not drawn to tournament button).
- When inviting members, user expected that pressing "Enter" on the keyboard would result in adding another member. However, the names had to be comma delimited
- Join a Tournament
- Update a Tournament
- Thought that check boxes on the side panel had to be marked to update the players' score, resulting in slight confusion when there was no visible change. Quickly recovered as soon as he hovered over the round-robin matches matrix. No problems with the score input.
- Manage a Tournament (make admin/boot player)
- View a Tournament
| - Create a Tournament
- Re-locate "Create Tournament" button closer to the top of the page.
- Provide clearer instructions for inviting multiple users, such as
- indicating with instructions that names should be comma delimited
- having the site automatically split user input with line breaks
- require manually adding a new input field for each invited member
- Join a Tournament
- Update a Tournament
- Although there was some initial confusion, everything seemed to make sense after a minute, implying that it would be easy to use/remember for the next time.
- Manage a Tournament
- View a Tournament
|
User 2 | - Create a Tournament
- Join a Tournament
- Update a Tournament
- Manage a Tournament (make admin/boot player)
- View a Tournament
- Other
- Was not immediately clear that the tournaments displayed on home page were users' own tournaments. (Missed reading the "Your tournaments" label due to relatively small text size).
| - Create a Tournament
- Re-locate "Create Tournament" button closer to the top of the page.
- indicate with instructions that names must be comma delimited
- Join a Tournament
- Update a Tournament
- Although there was some initial confusion, everything seemed to make sense after a minute, implying that it would be easy to use/remember for the next time.
- Manage a Tournament
- View a Tournament
- Other
- re-format "Your tournaments" label to make more visible.
|
User 3 | - Create a Tournament
- Confusion when inviting participants to the tournament. Thought that both the username and email boxes had to be filled out.
- Also felt that the Invite Member and Create buttons should be larger/more noticeable.
- Join a Tournament
- Update a Tournament
- Initial confusion regarding ability to indicate a winner with a lower score, but realized after a few seconds that it made sense (eg. golf scores).
- Manage a Tournament (make admin/boot player)
- Expected some kind of feedback on the spreadsheet itself, not just the sidebar
- View a Tournament
- Other
- Overall just wanted more feedback for the actions performed.
| - Create a Tournament
- Make it clear that you only need to fill out either usernames or emails box
- Join a Tournament
- Update a Tournament
- Although there was some initial confusion, everything seemed to make sense after a minute, implying that it would be easy to use/remember for the next time.
- Manage a Tournament
- add more visual feedback on the player grid
- View a Tournament
|
User 4 | - Create a Tournament
- Also commented on the ambiguity of usernames/emails.
- Thought the space on the side of the screen was largely wasted (no need for a full page for people's names, etc)
- Join a Tournament
- No problems
- Felt that tournament panels on the home screen should have had more information
- Update a Tournament
- Thought something would happen when clicked on player's names in the grid, but soon figured out how to update scores.
- Thought that Larry's row should stand out from others since that's the name of the user.
- Manage a Tournament (make admin/boot player)
- View a Tournament
| - Create a Tournament
- Make it clear that you only need to fill out either usernames or emails box
- Join a Tournament
- Update a Tournament
- Although there was some initial confusion, everything seemed to make sense after a minute, implying that it would be easy to use/remember for the next time.
- Manage a Tournament
- provide more visual feedback
- View a Tournament
- Overall
- provide more dynamic feedback of actions
|
...
- Problem locating "Create Tournament" button at the bottom of the page. Thought it should/would be at the top of the page next to the Tournaments label. (Monitor was fairly large resulting in little content at the bottom of the page, so eyes were not drawn to tournament button).
- When inviting members, user expected that pressing "Enter" on the keyboard would result in adding another member. However, the names had to be comma delimited
...
...
Reflection
Discuss what you learned over the course of the iterative design process. If you did it again, what would you do differently? Focus in this part not on the specific design decisions of your project (which you already discussed in the Design section), but instead on the meta-level decisions about your design process: your risk assessments, your decisions about what features to prototype and which prototype techniques to use, and how you evaluated the results of your observations.
...