The Portfolio Process
Post-TAP
Going through the TAP process was difficult because I am a very social person by nature. I like to interact with the person giving me feedback, and going more in depth to what they're saying. I think that's actually a more valuable exercise in this case because of how simple my layout is. There's no sweeping changes that need to be made, so discussing the minutiae requires dialogue. I find TAP to be more useful for larger scale projects or applications that explicitly rely on their usability to function successfully.
Even so, I gained some valuable tips from the exercise. For larger document artifacts, I moved the annotation above the document viewer so that participants knew what they were looking at. I also added subpages in my overview page so that people could more easily identify where certain parts came from. Finally, I added additional navigation at the bottom of the page to make more clear the path from first to second to third (and so on) year.
Going through the TAP process was difficult because I am a very social person by nature. I like to interact with the person giving me feedback, and going more in depth to what they're saying. I think that's actually a more valuable exercise in this case because of how simple my layout is. There's no sweeping changes that need to be made, so discussing the minutiae requires dialogue. I find TAP to be more useful for larger scale projects or applications that explicitly rely on their usability to function successfully.
Even so, I gained some valuable tips from the exercise. For larger document artifacts, I moved the annotation above the document viewer so that participants knew what they were looking at. I also added subpages in my overview page so that people could more easily identify where certain parts came from. Finally, I added additional navigation at the bottom of the page to make more clear the path from first to second to third (and so on) year.