Versions Compared

Key

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

...

We learned a lot about the design process through this project. We saw how some features that made a lot of sense to us could be confusing or difficult to find for users. We also saw that going from paper prototyping to a computer prototype makes a big difference that would be useful to take into account. If we were to do this project again it would be a good idea to look ahead to the implementation stage earlier to get a more realistic sense of what we would build before planning everything out, since we planned some things that we didn't have time to build.

During the iterative design process, we ended up testing different parts of our design during different iterations of the testing. Understanding what one is testing at a given point in time, figuring out how to craft tests that keep the user from getting distracted by features that will be implemented later on, and knowing what features to test early rather than later seem to be critical skill that would have lead us to make sightly different design and testing choices throughout the project. There is also a balance of known errors going into a user test will deteriorate the efficacy of the test and waste time for the tester and user; however, one only has so much time to implement a design. If I had understood the full scope of the project and what technical skills would be required, I would have prioritized my study in a different manner. I believe our risk assessment and navigation through design iterations went well and I don't believe I would have changed that process significantly.