Project Narrative


The final design’s assembly.

The final design’s assembly.

The final physical design.

The final physical design.

Duration of Project: March 4 - April 10

Project Summary: An open-ended project with a client. They have Spina Bifida, a condition where they cannot feel their lower body. The client described their daily life and various incidents and inconveniences. It was up to our team to decide to design anything we saw fit best. Our team decided to design a mechanism that supported her non-dominant hand, since she has limited mobility with it.

Main Objectives:

Problem Statement: Create a design that supports the client’s non-dominant hand that is lightweight, easy to use, compact, comfortable, and inexpensive.

Constraints:

Functions:

Outcome: Overall, the project was a success! The design was able to carry out all its basic necessary functions. Although, minimal revisions would be needed to ensure its practical for day-to-day use.


Skills Learned

Team’s Work and Personal Contributions

Here discuss the work conducted as a team as well as your personal contributions to the project, any calculations conducted, etc. You should distinguish your work from your other team members’ contribution to the project. Also include pictures that solidify your work. The layout of your pictures can be personalized and is not an official part of this template due to its customizable nature.

The collapsed/folded up version of the final product

The collapsed/folded up version of the final product

When the client bends their hand forward, the mechanism’s ‘fingers’ close, this way the client does not need full mobility of their hand and fingers, but instead the general movement of their hand and wrist.

When the client bends their hand forward, the mechanism’s ‘fingers’ close, this way the client does not need full mobility of their hand and fingers, but instead the general movement of their hand and wrist.

Design Process

  1. Data collection from client meetings
  2. Each team member lists their strengths and past experiences
  3. Create project timeline
  4. Problem framing and develop testing plan
  5. Each team member makes 2 initial sketches for a total of 8, then choose the current top design
  6. Conduct functional analysis
  7. Each team member create a low-fidelity prototype
  8. Decide best prototype using weighted matrix and design considerations
  9. Create mid-fidelity prototype
  10. Revise design and note necessary changes and plan of action
  11. Refine prototype
  12. Conduct testing plan
  13. Repeat steps 10-12 until design is finalized
  14. Create and present product pitch

Reflection

<aside> ❓ An event that occurred during the project was that our team was struggling a battle against time. There was so much to do but not that much time to actually get it done.

</aside>

<aside> ❓ This may have happened for a couple of reasons. First off, we chose a design that was too complicated with the time given. It would have been completely doable and would not need any revisions if we either had more time or if we chose to scrap a feature. However, if we had gotten rid of any of those features, the solution might have been rendered inconvenient. What would be the point of an item meant for daily use if it was a bother to use?

</aside>

<aside> ❓ I wonder if this was a legitimate project in the real world, would I have been able to negotiate the deadline if I knew the deadlines were too tight or if it failed, would I have been able to refuse the project? As there was a chance it could have harmed the client as there were parts and wires sticking out which imposed a danger of getting caught in the clients wheelchair or parts could have came off during use. Next time, I would be more realistic by setting doable deadlines and if it was not possible, then either make it simpler or choose another idea.

</aside>