...
User Test | Critical Incident | Design Learnings/Possible Fixes |
|---|---|---|
User 1 |
|
|
User 2 |
|
|
User 3 |
|
|
Reflection
GR1 - Project Proposal and Analysis
GR2 - Project Proposal and Analysis
GR3 - Project Proposal and Analysis
GR4 - Project Proposal and Analysis
GR5 - Project Proposal and Analysis
...
Going through the design process in a methodical way was very educational, and we could see the design evolving throughout. We reflect on the evolution of this design through each stage.
GR1 - Analysis
During the initial Analysis, it was instructive to think concretely about the tasks we wanted users to be able to complete. We ended up going back to you task list multiple times for updates because the actual tasks necessary to achieve a users goals were simplified over time. We did a good job targeting specific user needs, but perhaps took on too much total scope for the purpose of this class looking back on it.
Also looking back, remembering to focus on very specific user problems and ensuring that our application addresses those is key. We ended up moving the application into different directions and we could have benefited from a simplification effort during implementation to ensure our final application met all of the basic user needs.
GR2 - Design
The design phase went well and we have each member design their own version of the major tasks to be handled. This gave us multiple potential ways to implement the same tasks, and then we were able to directly compare them and discuss which methods would work best in our next prototypes.
At this stage we focused on high level tasks, instead of low level methods to achieve those. f
GR3 - Paper Prototype
The paper prototypes were both fun and informative, as we had not gone through such an exercise before. We learned a lot from having users physically attempt to use the paper version, and vocalizing their thoughts.
GR4 - Computer Prototype
The computer prorotype
GR5 - Implementation
asdasd
GR6 - User Testing
asd