Element K: Reflection on the Design Project

Reflection

Due 

Insert a copy of the self-reflection rubric here.  You can find it by click here:  self-reflection rubric.

https://docs.google.com/document/d/13BQ2N6OADLZMHXDMBOiczwntsb8MmXqZoEP0Ci89P5c/copy 

Response

Isaiah Johnson

After giving our presentation, we got a lot of helpful feedback from the audience. Many people asked great questions that made us think more deeply about our project and how we could make it better in the future. The comments helped us understand what we did well and what we could improve.

One important question someone asked was how our problem statement connected to the rest of the project. We gave a short answer at the time, but later we realized this was something we could have explained better. This helped us see how important it is to make sure the problem statement matches the goal of the project.

Another good question was about how we powered the sensor and LED light. In our prototype, we used batteries, but someone suggested using the power from the outlet itself. This idea made us think about how other products work and how we could make our design more practical. We also learned that even though our current solution works, it’s not the best option for a final product.

We were also asked if the sensor might go off by accident and wake someone up. We said this was unlikely because most outlets are close to the ground, but the question made us realize we should test it more and make sure it doesn’t cause problems like that.

Sam talked about how the feedback showed that people liked our project and understood the work we put into it. Even the negative comments were helpful because they were meant to help us improve. It felt good to know people were interested in our project and thought we did a good job presenting it.

Many people said they enjoyed our presentation. They could see that our project worked well and that we explained it in a way that kept them interested. That was important to us because we wanted to show not just our design, but also our thinking and teamwork.

Most of the questions people asked came from curiosity, not criticism. They wanted to learn more about our project, not just point out what was wrong. For example, when someone said the problem statement didn’t fully connect to the rest of the project, it confirmed something we already noticed. That helped us know what to fix for next time.

Ultimately, the feedback showed us what was strong about our project and what we could improve. It reminded us that building a working model is only part of the job—how we explain and improve it matters too. We’re proud of what we did, and we’re excited to keep making it better.