Middle School NGSS Resource Hub
Three-dimensional breakdowns, phenomenon ideas, misconceptions, and engagement activities for every NGSS middle school standard.
๐ Jump to Your Discipline
-
๐งช
โPhysical ScienceMS-PS1 to MS-PS4 โข 19 standards
-
๐งฌ
โLife ScienceMS-LS1 to MS-LS4 โข 21 standards
-
๐
โEarth & SpaceMS-ESS1 to MS-ESS3 โข 15 standards
-
๐ ๏ธ
โEngineeringMS-ETS1 โข 4 standards
Middle School NGSS Standards
Pick any standard. Each page is your full lesson-planning workspace for that standard.
Defining Design Problems: Turning Vague Goals into Testable Specs
"Define the criteria and constraints of a design problem with sufficient precision to ensure a successful solution, taking into account relevant scientific principles and potential impacts on people and the natural environment that may limit possible solutions."
NGSS does not list an explicit clarification statement for this standard.
"Emphasis is on the situation in which the solution to a societal challenge needs to be designed and evaluated."
The three dimensions packed into this standard
Every standard bundles a DCI (the content), a SEP (the science practice), and a CCC (the crosscutting lens). They run in the same task, not in sequence.
"The more precisely a design task's criteria and constraints can be defined, the more likely it is that the designed solution will be successful. Specification of constraints includes consideration of scientific principles and other relevant knowledge that are likely to limit possible solutions."
Engineering doesn't start with building. It starts with defining the problem precisely. Criteria are what success looks like, written so you can measure it. Constraints are the limits the solution has to live inside. Sloppy criteria and constraints lead to sloppy designs. Tight ones make the work testable.
"Define a design problem that can be solved through the development of an object, tool, process or system and includes multiple criteria and constraints, including scientific knowledge that may limit possible solutions."
Students aren't picking a project and running. They're rewriting a vague problem into a specific one. They name what the solution must do, what it can't do, and what limits the materials, time, safety, or environment put on it. The problem statement is the deliverable.
"All human activity draws on natural resources and has both short and long-term consequences, positive as well as negative, for the health of people and the natural environment."
Every design choice ripples outward. A new product uses resources, affects people, and changes the natural environment. Students consider those impacts up front, not after the prototype is built. The constraints on a real design include "what does this do to the people and the planet around it?"
๐ Where This Standard Fits in the K-12 Progression
Use this to plan the year. Knowing what students should already know and what they're heading toward keeps the lesson focused.
Engineering problems are situations people want to change or fix. A good problem statement says what success looks like and what limits the solution must work within.
Defining Design Problems: Turning Vague Goals into Testable Specs
Real-world design problems usually involve many criteria and constraints at once, including social, cultural, and environmental tradeoffs. Defining the problem well is a research task in itself.
๐ Phenomena for MS-ETS1-1
Anchor the lesson in one puzzling phenomenon kids keep coming back to. Use the two investigative phenomena to sharpen specific facets.
The Mars Rover Design Brief
Before NASA built Perseverance, engineers wrote a design brief that specified every condition the rover had to survive. It had to operate at -100ยฐC. It had to roll over rocks up to 20 cm tall. It had to land within a target zone smaller than a city. It had to carry instruments under tight mass limits because every kilogram costs millions to launch. The brief was hundreds of pages before any hardware was built. Students see the gap between "send a robot to Mars" and the precise spec that made the mission possible.
"Why do real engineers spend so much time writing before they start building?"
- "What happens if a spec misses something the rover encounters on Mars?"
- "Who decided which criteria mattered most?"
- "Could the same rover design work on the Moon, or do the criteria have to change?"
Two Product Listings, Same Product Category
Pull two real spec sheets for similar products. Two water bottles, two flashlights, two backpacks. They look like the same thing on the shelf, but their spec sheets reveal different criteria and constraints. One bottle is rated for boiling water, the other isn't. One flashlight is rated waterproof to 10 meters, the other to splash-resistant. Use this to sharpen the precision lens the anchor is pushing on: tiny spec differences cause real differences in what the product can do.
"Why do two products that look the same end up with such different specs?"
- "Which spec differences matter to me as the user?"
- "Did the cheaper product cut criteria or constraints to lower the cost?"
- "Could I write a spec for the product I actually want?"
The School's Locker Request
A school is replacing the lockers in a hallway and the principal hands out a one-page request: "We need new lockers." Students read it and immediately realize the request is unsolvable as written. How tall? How many? How secure? Compliant with which safety codes? Within what budget? Same kind of vague-to-precise rewrite as the anchor, only the stakes are local instead of interplanetary.
"What would a useful version of the principal's request actually say?"
- "Who are the stakeholders, and what do they each need from the lockers?"
- "What scientific principles limit the design (weight, security, fire safety)?"
- "What impacts on people and the school should be written into the spec?"
โ ๏ธ Misconceptions Your Students Will Walk In With
These come up almost every year. Knowing them in advance lets you head them off in the first lesson.
"Engineering is mostly about building stuff"
Building is the visible part, but defining the problem is at least half the work. Engineers spend days or weeks writing specs before anyone touches materials. A bad spec wastes every hour of building that follows. A clear spec makes the building part faster and the testing part possible.
"More requirements means a better design problem"
Over-constrained problems can't be solved. If a team lists 15 criteria and 12 constraints, some of them will contradict each other. Real engineering specs are tight, not long. A good problem statement has the criteria and constraints that actually matter and leaves room for creative solutions.
"Criteria and constraints are the same thing"
Criteria are goals. They describe what the solution must achieve. "Keeps water above 50ยฐC for 30 minutes" is a criterion. Constraints are limits. They describe what the solution can't do or can't use. "Must cost under $20" is a constraint. Goals tell you when you've succeeded. Limits tell you what's off the table.
"Real engineering doesn't work like a homework problem with a written spec"
Real engineering absolutely works that way. Every car, phone, building, and toy started with a written spec sheet. Mars rovers have hundreds of pages of criteria and constraints written before a single bolt is ordered. The spec sheet is how engineers across companies, countries, and decades stay on the same page.
๐ Common Student Questions and How to Respond
These come up almost every time this standard gets taught. Plan a response and you'll keep the lesson focused.
You can, and people do, but they usually have to start over. A clear spec is the difference between iterating on a design and rebuilding from scratch. It's also how you know whether your prototype actually solved the problem or just produced something interesting. Without criteria, "did it work?" is impossible to answer.
Yes, but flag it. Real engineering specs get revised when teams discover new constraints. The rule is that changes get tracked so everyone knows what changed and why. If you add a constraint mid-project, write it down, date it, and note what prompted the change. That's how engineers communicate.
Only if you can measure it. "Cool-looking" by itself isn't testable, so it can't drive a design. But "must score 7 or higher on a 10-point appearance survey of 20 classmates" is testable. Engineers absolutely care about appearance, but they translate it into something a judge can score the same way twice.
It used to be handled after the fact, and that's how we got products that polluted rivers and tools that broke people's bodies. The shift in modern engineering is to write impacts into the spec from the start. A constraint like "must be non-toxic" or "must be recyclable" is cheaper to design for than to retrofit later.
๐ Vocabulary Students Need for MS-ETS1-1
Twelve terms students need to access this standard. Definitions in plain-English, classroom-ready language.
What a solution must achieve, written specifically enough to measure. "Keeps water above 50ยฐC for 30 minutes" is a criterion. "Works well" is not.
A limit on the solution. Constraints come from budget, materials, time, safety, the laws of physics, or impacts on people and the environment.
The written document that lists all criteria and constraints for a design problem. The spec is the deliverable at this stage of engineering.
A situation someone wants to change, framed precisely enough that a solution can be designed and evaluated.
When meeting one criterion makes another harder to meet. "Cheaper materials cost less but might not last as long." Tradeoffs are normal and have to be named.
A criterion is testable if two different people can measure it and get the same answer. Numbers, thresholds, and yes/no checks are testable. Adjectives usually aren't.
A problem statement that doesn't have measurable criteria or specific constraints. Vague problems lead to designs no one can evaluate.
A problem statement with measurable criteria, specific constraints, and a clear scope. Precise problems can be solved and the solutions can be compared.
A rule from science that limits what a design can do. The laws of heat transfer, gravity, electricity, and chemistry all constrain real designs.
A consequence of a design on people or the environment. Impacts can be positive (a safer car) or negative (more plastic waste). Both count when writing constraints.
Anyone affected by the design problem or its solution. The user, the maker, the community, the environment. Naming stakeholders helps surface impacts that should become constraints.
A short document, usually one page, that states the design problem along with its key criteria and constraints. Used by professional engineering teams to align everyone on the goal.
๐ก Free Engagement Ideas for MS-ETS1-1
Vague-to-Precise Rewrite
Pairs get a vague design problem on a card ("help students who get cold in class," "make recess safer," "reduce cafeteria food waste"). They have 15 minutes to rewrite it as a precise problem with at least 3 measurable criteria and at least 3 constraints. Then pairs swap cards and critique. The critique step is where the learning lands. "Could a stranger measure this criterion?" "Is this constraint a real limit or just a preference?"
Spec Sheet Scavenger Hunt
Students get printed or linked spec sheets from real consumer products. Bike helmets, water filters, LED bulbs, smoke detectors. They highlight every criterion in one color and every constraint in another. They circle one scientific principle the spec relies on and one impact the spec addresses. Reading real specs is how students see that the standard isn't a classroom invention. It's how products actually get made.
Impact Constraint Brainstorm
Teams pick a product they use every day (phone, sneakers, snack wrapper). They brainstorm every impact that product has on people or the environment over its life. Sourcing, manufacturing, daily use, disposal. Then they rewrite three impacts as constraints that could have been on the original design spec. The activity makes the CCC concrete: every constraint has a story about a person or a place.
The Bad Spec Hunt
Students get a packet of four "design briefs" written with intentional problems. One has vague criteria ("must work well"). One has contradictory constraints ("must be lightweight AND made of solid steel"). One ignores safety. One ignores environmental impact. Teams identify what's wrong with each and rewrite the worst one to fix all of its issues. Hunting for bad specs trains them to recognize what a good one looks like.
๐ Assessment Ideas for MS-ETS1-1
Three short tasks that hit all three dimensions. Doable in one class period each.
Students get a vague problem they haven't seen ("reduce noise in the cafeteria," "help younger students find their classroom on the first day"). They write a one-page design brief with at least 3 measurable criteria, at least 3 constraints (including one safety or impact constraint), and one scientific principle that limits possible solutions. They do not propose a solution. The brief itself is the deliverable.
Students get a flawed design brief with at least 5 issues: vague criteria, contradictory constraints, missing scientific principle, missing impact constraint, unmeasurable language. They identify each issue, write a one-sentence explanation of why it's a problem, and rewrite the brief to fix all of them. The rewrite must keep the original intent of the problem.
Students get two real-world spec sheets for similar products (two bike helmets, two water bottles, two flashlights). They list which criteria appear on both, which appear on only one, and which constraints differ. They write a short paragraph explaining how the spec differences would change what each product can do, including at least one impact on people or the environment that the specs address.
๐ฏ What Proficient Student Work Looks Like
Same prompt, three student responses at different proficiency levels. Use as anchor papers when scoring.
"Take the vague problem 'help students who get cold in class' and rewrite it as a precise design problem with criteria, constraints, and one scientific principle that limits the solution."
- A specific claim backed by data, observation, or model
- Use of standard-specific vocabulary in context
- Connection between the visible and the underlying explanation
- A question they're still wondering about (curiosity stays alive)
Students who are cold in class need something to keep them warm. The solution should be warm and easy to use. It should be cheap and safe. The science is about keeping heat in.
Names the goal but doesn't write measurable criteria. Constraints are vague ("cheap," "safe"). The scientific principle is gestured at but not specific. A second team couldn't take this spec and build comparable solutions.
Design a wearable that keeps a seated student at least 2ยฐC warmer than the surrounding air for 30 minutes. Criteria: keeps wearer 2ยฐC warmer than ambient for 30 minutes, fits in a standard backpack, lets the student write and type normally. Constraints: must cost under $5 in materials, must use only classroom-safe materials, must be machine-washable. Scientific principle: insulation slows heat transfer from the body to the air, so the wearable must trap air or use low-conductivity materials.
Criteria are measurable. Constraints are real limits. The scientific principle (heat transfer through insulation) is named and connected to the design. Another team could take this brief and produce a comparable solution. Hits exactly what the standard is targeting.
Design a wearable that keeps a seated middle school student at least 2ยฐC warmer than ambient air for 30 minutes in a classroom set between 18ยฐC and 22ยฐC. Criteria: maintains a 2ยฐC temperature difference for 30 minutes (measured by skin thermometer), fits inside a 30 cm x 40 cm backpack section, does not restrict arm movement below the elbow, scores at least 7/10 on a comfort survey of 10 classmates. Constraints: materials cost under $5 per unit, all materials must be classroom-safe (no open heating elements, no chemical hand-warmers in direct skin contact), must be machine-washable at 40ยฐC, must be recyclable or compostable at end of life. Scientific principle: heat transfers from the body to cooler air through conduction and convection, so the wearable has to use insulating materials that trap air. Impacts considered: material sourcing (the recyclable-or-compostable constraint addresses landfill impact), classroom safety (no heating elements addresses fire risk and student safety).
Criteria include numbers, methods, and a stakeholder survey. Constraints include safety, cost, and end-of-life impact. The scientific principle is specific (conduction and convection, not just "heat transfer"). The student explicitly connects two constraints to impacts on people and the environment. This is exactly the kind of precision-plus-impact reasoning the standard targets.
