...
Our team learned some valuable lessons from the iterative design process. At the beginning of our brainstorming
process, we were maybe too confident in what we wanted our final project to look like. We believed that our mental
concept of the website was very solid and would be simple to use and aethestically pleasing, but in the end, we
realized that some of our ideas were still premature and vague.
Sometimes, our users provided us comments about very obvious problems with our interface, which we were blind to
becuase we would find ourselves focusing on specific aspects becuase they are in front of us. Users wondered how
they could create parties using our application. We didn't have a very clear way for them to do this, so we added
an option to create parties on the homepage.
If we started the project over, we would try to focus even more on usability. One of the faults that affected our
final project was the fact that we realized there were alot more actions than we originally planned. We didn't
intend for users to change their event once they created it. We created an interface that allowed a user to change
their event, but it was not as well integrated becuase the idea to remodify events was not introduced early enough
in the brainstorming process. We would also focus more time on even more usability features like suggestions for
search, tooltips for form completion, and better error prevention.
Our team learned some valuable lessons from the iterative design process. At the beginning of our brainstorming process, we were maybe too confident in what we wanted our final project to look like. We believed that our mental concept of the website was very solid and would be simple to use and aethestically pleasing, but in the end, we realized that some of our ideas were still premature and vague.
...