Level: Middle School and High School
Type of Contest: Team
Composition of Team: 2-4 students per team
(Teams must have 2 to 4 members to enter the competition. It is strongly encouraged to have four team members.)
Number of Entries: One entry per school
Next Generation Science Standards: MS-ETS1-1, MS-ETS1-2, MS-ETS1-3,
MS-ETS1-4, HS-ETS1-1, HS-ETS1-2, HS-ETS1-3, HS-ETS1-4
Simply stated, Designing for Equity means designing to minimize or eliminate barriers to opportunities for success.
According to the World Health Organization, equity is the absence of avoidable or remedial differences. Those differences can be defined socially, physically, physiologically, geographically, economically, or demographically. Given the current state of the world, Designing for Equity has never been more important.
The Creative Reaction Lab explains that “Equity-Centered Community Design is a unique creative problem solving process based on equity, humility-building, integrating history and healing practices, addressing power dynamics, and co-creating with the community. This design process focuses on a community’s culture and needs to create a future with equity for all. …Through Equity-Centered Community Design, we are building and supporting an emerging movement of equity designers who take on systems with self- and systemic-awareness of oppression, creativity, and action. These designers—students, activists, organizers, educators, government staff, hospital workers, and beyond—seek to disrupt and dismantle these challenges in, and with, their communities: school, city, family, culture, and so on.”
The theme for the 2020-21 MESA USA National Engineering Design Competition is: Designing for Equity.
For this project, student teams will identify an individual or group who experiences some type of inequity (i.e., a user). Using a microprocessor as the key component of the design, teams will employ human-centered design practices to engineer a solution. Teams must use at least one of the following microprocessors as the main component of their design: Arduino, Circuit Playground Express, and/or Micro: bit.
Examples of Designing for Equity can be (but are not limited to) projects that address:
A physical or learning disability,
Food scarcity,
Access to healthcare,
Access to clean water or other resources,
Access to employment or education, or
A social inequity.
The final design must:
Use Arduino, Circuit Playground Express, or Micro:bit hardware,
Use at least 2 sensors,
Use at least 2 outputs (motors, servos, LEDs, LCD, etc.),
Not exceed dimensions of 20” x 20” x 20” (50.8 cm x 50.8 cm x 50.8 cm),
Not exceed a weight of 20 lbs. (9.07 kg), and
Be packaged in an aesthetically pleasing and functional form factor.
The components listed below will be used to assess the effective implementation of a human-centered design approach in the context of designing for equity, effective implementation of the engineering design process, and the functionality of the prototype.
High school and middle school teams will complete the following four components:
Design Brief (.pdf file submission): The objective is to provide a brief, non-technical overview of the entire project. Students must use the provided Design Brief template (see Appendix).
Electronic Poster (.pptx file submission): The objective is to provide an overview of the project highlighting key points of the design process including relevant data, present the resulting prototype, and share conclusions and recommendations for further development. Students will prepare an electronic academic poster that will provide an easily understood overview of the project and the prototype. The electronic poster will also be used during the Technical Presentation.
Technical Presentation (video submission): The objective is to provide an overview of the prototype functionality including a technical explanation of the mechanical operations, software operations, and integration of the two. Students will deliver a video-recorded presentation and demonstration of the functionality of the prototype.
Prototype Pitch (video submission): The objective is to convince the audience that the design meets the user’s needs and has value as a product to address an issue of inequity. Students will prepare a creative, engaging video-recorded presentation to pitch their prototype to an audience, including a group of judges. The presentation should define the problem, show how they address the theme of Designing for Equity, provide a detailed description of the users and their needs, discuss current solutions to the problem and their weaknesses, and provide a demonstration of their prototype highlighting its advantages.
At the National Competition, awards will be presented for each component of the competition. Overall ranking will be based on the total score, which is derived by adding the scores for each component. Below is a summary of the point values for each component:
Design Brief 50 points (15%)
Electronic Poster 75 points (23%)
Video-Recorded Technical Presentation with Demonstration 100 points (31%)
Video-Recorded Prototype Pitch 100 points (31%)
Total 325 points
MESA USA recognizes that there is both an interest in and benefit for student teams to continue work on a project started in previous years. However, as this is the start of a new National Engineering Design Competition cycle, all projects must be new and original. Teams cannot continue working on a project started in previous years.
Academic honesty and personal integrity are essential to ensure future success as college students and STEM professionals. As such, MESA USA expects that the work presented as a part of the National Engineering Design Competition will be solely the work of the students. If the work or ideas of another are used to further students’ work, proper credit must be given to the owner. Failure to do so will result in an act of plagiarism. If it is determined that a student committed plagiarism, they will be disqualified from the competition and they will be ineligible to receive any awards. They may also risk further sanctions from MESA USA and/or their MESA state organization.
During the course of this event, MESA students, staff, advisors, and supporting family members will be expected to act in a professional and courteous manner at all times. All judges’ decisions are final. Staff, advisors, and parents shall not engage judges during the event.
Due to the impacts of COVID-19, there will be no in-person MESA competitions for the 2020-21 MESA season. Instead, all projects will be submitted electronically to virtual competitions. Judges will score projects remotely.
For the County Competition, all files must be submitted no later than 11:59 pm on the due date specified by the MESA County Coordinator.
The team that wins the County Competition will progress to the 2021 Maryland MESA State Competition. Like the County Competition, all projects will be submitted electronically no later than 11:59 pm on the specified due date.
OBJECTIVE:
The Design Brief provides a brief, non-technical overview of the entire project. It is a short document that can be used alone or as support during the presentations to provide the reader with enough information about the project to:
understand the target user and the challenges they face that inspired the project,
state the project goals,
provide a general idea of the prototype and its key features,
relay the current status of the project,
convey the expected impact for the user and how perceived inequities are relieved, and
reflect on the team’s experience implementing the Human Centered Design Process.
FORMAT: Teams must use the Design Brief Template (see Appendix).
REQUIRED ELEMENTS:
Problem Statement: Describe the people who will benefit from the project and the challenges they face. Discuss the issues of inequity that the project hopes to address. (100 word maximum)
User Research: Discuss key information about the user gathered through your research, interviews, and ongoing discussion with the user throughout the project. The information shared here should be directly related to the user’s needs, insight, goals, and prototype. (200 word maximum)
User Insight: Discuss your team’s understanding of the experiences, emotions, and motivations of the user. This insight should inform the rest of the project and help the reader have a deeper understanding of the inequity of the user. (200 word maximum)
User Needs: Develop a specific list of the user’s needs produced from the user insight. The needs should be reflected in the project goals. (100 word maximum)
Project Goals: List project goals and describe how they are linked to and will adequately meet the user’s needs and address inequities and/or barriers faced by the user. Meeting these goals should be reflected in the key features and graphic(s) provided. (100 word maximum)
Key Features of Design: List key features, illustrating that the design will adequately meet project goals. (200 word maximum)
Prototype Graphic: Include a graphic that is easy to understand with key features that are adequately labeled. The reader should have a general understanding of how the prototype functions by looking at the graphic.
Status of Project: Describe the current status of the project and discuss potential next steps. (200 word maximum)
Impact: Discuss how the design addresses inequities for the user and/or removes barriers. This impact should reflect how the team met the project goals. (200 word maximum)
Reflection: Show that the team has an increased understanding of human-centered design. Examples of personal growth and insights gained about designing for others and helping them overcome challenges should also be included. (200 word maximum)
Design Brief Submission Instructions:
Complete the Design Brief using the provided template (see Appendix).
Save the Design Brief as a .pdf file.
Make sure the .pdf file name contains the school name and the words “NEDC Brief.”
Submit the .pdf file via the MD MESA website no later than 11:59pm on the specified due date.
Late submissions: If the file is received after the deadline, 10 points will be deducted from the score. Files received more than 48 hours after the deadline will not be scored.
OBJECTIVE:
The objective of the electronic poster is to provide an overview of the project, highlight key points of the design process, discuss relevant testing and data collection, present the resulting prototype, and share recommendations for further development. The electronic poster is an important element that as a stand-alone product should help an observer quickly understand the overall scope of the problem, the resulting solution, and next steps of the project. As a visual aid during the oral presentation, the poster can be a powerful tool providing important graphics and highlights of the solution.
FORMAT:
Each team must create an electronic poster in PowerPoint. The size of the electronic poster must be 48” x 36” (W x H). All information should be contained on one single slide that has been resized to 48” x 36” (W x H).
REQUIRED ELEMENTS:
All sections should use as few words as possible to adequately present the information. Any section requiring written explanation should be succinct. Generally, it is encouraged to use bullet-pointed lists instead of text in paragraph form.
The electronic poster must include the following:
Title: Posters should include a title at the top. This section could include:
a. A take-away for people who read the poster.
b. An identifier for the project.
Team Section: Must be present and include the following:
a. School name.
b. Grade level (Middle School or High School).
c. State (optional at state and local events).
d. Team members’ names.
Logo: An Official MESA logo must be included (contact your state office for an official logo).
Problem Statement: This defines the problem to be addressed. This section could include:
a. Description of problem(s) addressed by prototype.
b. Description of users for whom the prototype is designed.
c. Scope of the project and any priorities in design.
Objective: This defines how the problem is being addressed. This section could include:
a. Primary objectives being addressed.
b. Any secondary objectives being addressed.
User Requirements: This section describes the needs of the user and how the prototype meets those needs. This section could include:
a. Graphic explaining requirements.
b. Bullet-point list of requirements.
c. High School Teams Only: Address any implicit requirements. For example, if your client wants to live in Alaska the entire year, an implicit requirement is that your design needs to work in below-freezing temperatures.
Prototype: A picture/schematic of the prototype. This section could include:
a. Short descriptions of important pieces of the prototype using callouts or short lists.
b. Highlights of the device and labeling of main parts.
c. Unique elements of prototype.
Design Process: A graphic that shows the team’s design process, including specifics. A general Engineering Design Process is NOT allowed. It must be specific to your team's design process. This section could include:
a. Flow chart with steps for the team’s iterative process.
b. Engineering Design Process with specific steps outlined.
Design Iteration: A graphic or list that shows multiple iterations of the design process with changes made in each adaptation of the prototype. This section could include:
a. Flow chart that shows changes for iterations of the prototype after testing.
b. Bullet-pointed list that shows changes for iterations of the prototype after testing.
Testing Process: A graphic or list that describes how the team tested the prototypes. This section could include:
a. Specific tests used.
b. Tests with users.
c. User feedback.
Visual Data (Minimum of 2): The relevant data that helped drive the prototype. This section could include:
a. Line graphs.
b. Circle graphs.
c. Bar graphs.
d. Tables.
e. Descriptions of successes and failures of the prototype.
Visual Element: A graphic that describes any other important factors/elements in your prototype. This section could include:
a. Decision tree.
b. Design matrix.
c. Key elements not addressed in other sections.
Results: The end result of the prototype. This section could include:
a. Summary of results.
b. How the prototype improves the user’s capabilities because of the prototype.
c. Changes to the user’s experience in the world.
Conclusions: Description of the final takeaways for the user. This section could include:
a. Success and/or failure to meet primary and secondary objectives.
b. Next steps for project.
Electronic Poster Submission Instructions:
Complete poster in PowerPoint.
Make sure the .pptx file name contains the school name and the words “NEDC Poster.”
Submit the .pptx file via the MESA website no later than 11:59pm on the specified due date.
Late submissions: If the file is received after the deadline, 10 points will be deducted from the score. Files received more than 48 hours after the deadline will not be scored.
OBJECTIVE:
The video-recorded Technical Presentation allows judges the opportunity to determine student knowledge of their project, gain information about the design process the students used during the project, and determine the viability of the design for the user. A technical presentation has a different focus than a pitch; therefore, this presentation should be different from the Prototype Pitch component of the National Engineering Design Competition.
Students will organize and deliver a focused, coherent video-recorded presentation to provide an overview of the development of their design (including research, experimentation, iterations, and conclusions), the technical components of their design, and the functionality of the prototype. The presentation should provide an overview and demonstration of the prototype functionality as well as include an explanation of the mechanical operations, software operations, and the integration of hardware and software.
FORMAT:
The presentation, including demonstration, can be a maximum of 10 minutes in duration and must be supported with appropriate visual aids. Students can use their choice of materials including, but not limited to, their design brief, electronic poster, prototype, and other relevant materials as support during the presentation. Displays and speeches must be the original work of the students.
REQUIRED ELEMENTS:
The video-recorded technical presentation must include:
Background Information:
a. Who is the user and what are the user’s needs?
b. How does this project fulfill the user’s needs?
c. How does the design address an issue of inequity?
Engineering Design Process:
a. What was your team’s methodology and process?
b. What were any major challenges and any correlating solutions?
c. What were the major design choices and how were they influenced by the user?
d. How did the results of testing inform iterations of the design?
e. How did the iterations of the design evolve during the project?
Description of Design:
a. How does the design function mechanically?
b. How is the selected microprocessor integrated into the design?
c. How does the software function?
d. How does the device receive input and produce output?
e. What is the rationale for selected materials and technology?
Conclusion and Recommendations:
a. What is your final assessment/evaluation of your prototype?
b. What is the potential impact of the product on the user’s life?
c. What are the next steps for the implementation of your project?
d. Are there any suggestions for improvement and/or redesign?
Prototype Demonstration:
a. Teams must have a working prototype. If not, some areas cannot be scored.
b. Teams must be able to adequately discuss their prototype design, including unique features of the design, and demonstrate the function of the device.
c. Teams should demonstrate the usability of the prototype and how it meets the needs of the user.
Video-Recorded Technical Presentation Submission Instructions:
Upload video to YouTube as an unlisted video.
Create a document containing the school name, team member names, MESA School Coordinator name(s), and a link to the video on YouTube.
Make sure the document file name contains the school name and the words “NEDC Tech Presentation.”
Submit the document via the MD MESA website no later than 11:59pm on the specified due date.
Late submissions: If the file is received after the deadline, 10 points will be deducted from the score. Files received more than 48 hours after the deadline will not be scored.
Objective:
The objective of the Prototype Pitch is to convince the audience that the design meets the user’s needs and is equitable in its design. Students will prepare a creative, engaging video-recorded presentation to pitch their prototype to an audience, including a group of judges. The pitch should define the problem; provide a detailed description of their user and their needs; discuss how their product is innovative; and provide a demonstration of their prototype including highlighting its advantages.
Format:
The video-recorded pitch must be between 5 and 7 minutes in duration.
Required Elements:
The video-recorded pitch must include:
User Introduction and Problem Addressed:
Describes the user.
Describes the problem the team is solving and its impact on the user.
Describes how design requirements keep target users in mind.
Discusses how user input supported design choices.
Discusses how user feedback supported design changes.
Product:
Defines the proposed solution through the prototype.
Describes how the solution promotes equity in the user’s lives.
Explains the originality and innovativeness of their design.
Presents the advantages of the prototype.
Demonstration of the Prototype:
Explains key features and functions.
Explains how design meets user’s criteria for look, feel, and functionality.
Explains how a microprocessor is integrated using non-technical terms.
Overall Quality of the Presentation:
Effectiveness of speech organization and delivery.
Audience engagement – ability to hold audience’s attention.
Presentation skills – the team is prepared and their voices can be clearly heard.
Introduction and participation of team members.
Team’s interest – explanation of why the team chose this project and why is it important to them personally.
Closing statement – the speech ends with a final statement that summarizes the user, problem, and solution in a memorable manner.
Video-Recorded Pitch Submission Instructions:
Upload video to YouTube as an unlisted video.
Create a document containing the head coach’s name, team name, team member names, MESA School Coordinator name(s), and a link to the video on YouTube.
Make sure the document file name contains the school name and the words “NEDC Pitch.”
Submit the document via the MD MESA website no later than 11:59pm on the specified due date.
Late submissions: If the file is received after the deadline, 10 points will be deducted from the score. Files received more than 48 hours after the deadline will not be scored.