Engineering Design
The Air Jordan 1 started as a rough prototype. The PlayStation began as a clunky gray box bolted to a CD player. How does a first draft become an icon?
What You'll Be Able to Do
By the end of this lesson, you will be able to:
- Tell students the target outcomes before they meet the content.
- Frame the lesson around distinguishing criteria from constraints and explaining why engineers iterate.
- Goal setting
- Advance organizer
- Understand to Analyze
- DOK 1 to 3 (the "explain why engineers iterate instead of building the final product first" goal reaches cause-and-effect reasoning)
- Each goal paired with an icon and a standard code
- Short, plain-language statements
- One card per goal, no crowding
Words You'll Meet
Choose a card to see what each word means.
- Pre-teach the six terms students will reuse throughout the lesson.
- Separate criteria from constraints early, since the two are the most confused pair in this unit.
- Pre-teaching vocabulary
- Reduced extraneous load
- Remember to Understand
- DOK 1
- Click to reveal, no hover
- One card open at a time
- Plain, short definitions
Famous Products. Rough First Drafts.
Some of the most famous products in the world did not start out looking famous. They started as clumsy, unfinished first attempts. Click each card to look closer.
- Open with familiar products that hide a rough first version, creating a question students want answered.
- Surface the misconception that famous designs arrive perfect on the first try.
- Curiosity gap
- Phenomenon-based learning
- Prior knowledge activation
- Understand
- DOK 2
- Click to reveal, no hover
- Large card targets with icon and label
- Short observation text per card
Two Words That Build the World
Before we follow a design from sketch to store shelf, we need two key ideas. They sound similar, but they play different roles.
Engineering is a field that applies scientific principles to designing and constructing. Engineers use what scientists discover about forces, materials, electricity, and energy to build things that work in the real world.
Design is the process of planning and building that solves a problem or meets a need. Design always starts with a problem: shoes wear out, games are boring, backpacks hurt your shoulders. The design is the answer.
Engineers design solutions everywhere you look:
Engineers have special names for those two lists. Let's meet them.
- Define engineering and design as distinct but linked ideas before the process is introduced.
- Anchor abstract terms in everyday designed objects students already use.
- Concrete to abstract
- Worked examples
- Elaboration
- Understand
- DOK 2
- Key terms defined in place
- Icon-labeled example chips
- Color coding introduced and reused later
Criteria vs. Constraints
Every design problem begins with the same question: what are the criteria and constraints? Compare the two cards below. The colors will follow these ideas through the whole lesson.
- The specific requirements that a design must meet
- They describe success: if the design meets the criteria, it works
- Ask: "What does it have to do?"
- Example: a basketball shoe must grip the court and support the ankle
- The limitations that affect the design process
- They set boundaries: money, time, materials, size, safety rules
- Ask: "What holds the design back?"
- Example: the shoe must cost under $100 to make and be ready by fall
Your design team is building a new school backpack. The client sent over six notes. For each one, decide: is it a criterion (something the backpack must do) or a constraint (a limit on the design)?
- Make the criteria-versus-constraint distinction concrete with a side-by-side contrast.
- Have students classify real design notes, the exact skill 6.MS-ETS1-1 asks for.
- Comparison and contrast
- Generation effect
- Immediate feedback
- Understand to Analyze
- DOK 2 (sorting each statement into criterion or constraint is classification, not recall)
- Side-by-side comparison cards
- Large button targets with keyboard focus styles
- Feedback explains each answer in place
The Engineering Design Process
Engineers everywhere follow the same seven-step cycle, from sneaker designers to NASA. Click each step to reveal what happens there. Open all seven to complete the cycle.
The steps below got scrambled. Click them in the correct order, starting with the step where you define the problem.
- Lay out the seven-step cycle and stress that test and improve form a loop, not a dead end.
- Counter the idea that engineers try one solution and stop.
- Dual coding
- Productive struggle
- Misconception checking
- Understand to Analyze
- DOK 2 (reordering the scrambled steps requires reasoning about sequence, not just naming them)
- Click to reveal each step, no hover
- Steps numbered, icon-labeled, and color-coded
- Order builder gives keyboard focus and clear feedback
Prototypes and Iterations
Remember the rough Air Jordan and the gray 1991 test console from the start of the lesson? Now you can name what they were.
A prototype is an early model of a design that is tested and refined. The Air Jordan 1, 2, and 3 each had prototypes: rough versions built to answer questions like "does it grip?", "does it last?", and "does it look right?" before millions of pairs were made.
Iterations are the repeated cycles of designing, testing, and refining. Each trip around the design cycle is one iteration, and each iteration makes the design a little better.
Seven versions and counting: that's iteration. Each console was designed, tested by millions of players, and refined into the next one. The cycle never really ends.
- Name the rough early versions from the hook as prototypes and iterations.
- Reframe a failed test as useful data, directly addressing "failure means the project failed."
- Predict before reveal
- Dual coding
- Misconception checking
- Understand to Analyze
- DOK 2
- Prediction gates the timeline so students commit first
- Labeled timeline paired with text caption
- Short, parallel callout cards
A Worked Example: The Locker Organizer
Here's the whole process applied to a problem you might actually have: a messy school locker. Read each chunk one at a time and watch how criteria, constraints, prototypes, and iterations all show up.
- Walk the full cycle through one relatable problem so every term appears together in context.
- Show a test failing one criterion, then a redesign that fixes it, modeling evidence-based improvement.
- Worked example
- Chunking
- Transfer
- Understand to Analyze
- DOK 2
- Process broken into three numbered chunks
- Criteria and constraints color-coded in the text
- Closing prompt invites a low-stakes personal example
Brain Check
Two quick questions before we put it all together. These are not graded. Pulling answers from memory now will help them stick.
- Give a low-stakes retrieval check before the synthesis section.
- Target the two ideas most worth strengthening: looping back after a failed test and why prototypes come first.
- Retrieval practice
- Feedback loops
- Remember to Apply
- DOK 1 to 2
- Ungraded and low stakes
- Answer explanations provided
- Retry option with keyboard-accessible radios
Pulling It All Together
Three beats to remember, then every key term in one table.
| Term | What It Means | Example |
|---|---|---|
| Engineering | A field that applies scientific principles to designing and constructing. | Using physics about forces to design a bridge. |
| Design | The process of planning and building that solves a problem or meets a need. | Creating a backpack that stops shoulder pain. |
| Criteria | The specific requirements that a design must meet. | The shoe must grip the court and support the ankle. |
| Constraints | The limitations that affect the design process. | Budget under $15, must fit a 12-inch locker. |
| Prototype | An early model of a design that is tested and refined. | The 1991 gray PlayStation test console. |
| Iterations | The repeated cycles of designing, testing, and refining. | PS1 → PS2 → PS3 → PS4 → PS5, each one improved. |
| Design Process | The seven-step cycle engineers follow to solve problems. | ASK → IMAGINE → PLAN → CREATE → TEST → IMPROVE → SHARE |
- Consolidate the lesson into three big beats and one term-by-term table.
- Resolve the opening mystery so the phenomenon and the vocabulary close together.
- Schema building
- Coherent narrative
- Dual coding
- Understand to Analyze
- DOK 2 to 3 (students connect prototype, criteria, constraints, and iteration into one explanation)
- Three short beats before the reference table
- Summary table pairs each term with a meaning and example
- Consistent color coding from earlier sections
Check Your Understanding
Ten questions covering everything you discovered, including brand new design problems to solve. Answer every question, then submit.
Engineers don't just pick a design. They defend the choice.
Write your own explanation first. Then submit your work to compare your thinking with a model answer.
A team is designing a phone case. Its criterion: survive a 2-meter drop. Its constraint: cost under $5 to make. Their first prototype survives the drop, but it costs $9. A teammate says, "It passed the drop test, so let's sell it." Make a claim about what the team should do next, back it with evidence from the design, and explain your reasoning. Use the word iterate.
- Measure understanding with ten items, including new design problems students have not seen.
- Offer practice mode for self-check and classroom mode for teacher reporting.
- Retrieval practice
- Transfer
- Feedback loops
- Understand to Apply
- DOK 1 to 2 (mix of recall and applying criteria-versus-constraint reasoning to fresh scenarios)
- Practice mode works independently with no submission
- Plausible, evenly placed options
- Progress bar and required fields before classroom submit
More Learning
Engineering design connects to everything you build and test in science class. Extension challenges: redesign your own backpack on paper. List 3 criteria and 3 constraints, sketch a prototype, and trade with a partner to "test" each other's designs. Or pick a product you use daily and research how many iterations it went through before the version you own.
- Offer hands-on extensions where students run their own design cycle and peer-test a partner.
- Link forward to lessons that deepen the test, materials, and measurement steps.
- Transfer
- Interest-driven extension
- Metacognition
- Apply to Analyze
- DOK 2 to 3 (the backpack challenge asks students to set criteria and constraints, prototype, and revise from a partner's test)
- Optional and self-paced
- No penalty for skipping
- Linked cards are clearly categorized and color-coded
Connections
Strong designs are built on evidence. Here is where these skills carry over.