...
All in all, we would like to keep the main UI of our group task organizing web app as simple and straight to the point as possible. It will always keep what is important in view to the user at all times.
Design 3
Analysis of Design 3
Learnability:
This design is very easy to learn. Since there are not a lot of features, there aren't many areas which can introduce confusion to the user. In addition, each page is very simple, as each page has a very specific function (add a task, add a bucket, etc).
Visibility:
Once concern with this design is the lack of visibility. For example, when editing a task, the user cannot see what other tasks need to be completed. In some situations, this might not matter, but other times it might be nice to see reminders of what else is going on while editing / adding tasks. This design tracks modes well, and always displays the logged-in user's name, and shows who else is collaborating on tasks.
Efficiency:
Adding tasks is relatively easy, however it requires navigating away from the main page. This introduces some efficiency concerns, as there is a lot of time spent navigating through pages before simple tasks can be accomplished. However, since each action requires very little sub-steps, the overall efficiency of the system is still ok.
Errors:
It is possible to easily remove / add users, or edit bucket / task details, therefore any error is easily correctable. In addition, since there are lots of intermediate steps when adding information (navigating to new pages and clicking 'ok'), errors will likely be more rare in this design.
Overall:
Overall, this design is easy to use and individual pages are very simple, but the overall it is more complicated than the other two designs. Having multiple pages to navigate through makes the layout of the individual pages less complex, but the website as a whole becomes more complicated to navigate through / learn, and there are more sub-steps to complete for each action the user takes.