<aside>

Problem Statement:

Design a solution to help the client to be more independent when partaking in his hobbies, specifically helping him water his plants.

</aside>

<aside>

<aside>

Image 1.0: Final design

Image 1.0: Final design

</aside>

<aside>

Design Functions:

<aside>

Design Objectives:

<aside>

Design Constraints:

</aside>

<aside>

Some Assigned Tasks Include:

<aside> πŸ‘·πŸ½

<aside> πŸ§ͺ

<aside> πŸ“

</aside>

<aside>

Overall Accomplishments

</aside>

<aside>

Design Process

</aside>

<aside>

Reflection

My group’s design process revolved our making many iterations and learning from them after testing. After we printed our upscaled model and went through our final testing plan, we received feedback on the comfort and ease of use. One piece of feedback we received was the placement of the strap, as having it so the vent hole which allowed water to exit the can, to be covered by the thumb felt awkward. It often caused the can to slip away from the hand because there was less grip when removing the thumb, and the PLA was smooth. Instead, many suggested that we put it onto the other side so then an index finger could be used. I believe that this made our design better since there are more grip and the motion felt natural and not clunky. However, I wish that we had conducted our testing earlier to have more time to implement all of the feedback, rather than choosing which ones would be possible to given the remaining time.

Receiving feedback about our final prototype was important and I learned a lot about the design process. I think feedback from final prototype was helpful due to it being unbiased, as we met people outside of design studio and they had experience working with people who have serve arthritis in their wrist and fingers. However, due to the feedback being received near the end of the allocated work periods, not every change could be done as printing time exceeded 2 hours. This experience taught me the importance of early development and testing, as it gives more time to make iterations and further improve the design. Although I was able to create multiple iterations of the solution, our testing plan was executed late, and getting this feedback late made me realize that not only is it important to do multiple iterations, executing your testing is just as important.

From this experience, I learn the important of conducting testing plans early. This is important as iterations are done based off what you learn from testing, rather than blindly making iterations. Moving forward, not only will I ensure multiple iterations are done, but testing plans are executed early to receive important feedback that will improve designs.

</aside>