What Are The 8 Science And Engineering Practices

The 8 Practices, Actually Explained

Most people encounter What Are The 8 Science And Engineering Practices through the NGSS framework, and they walk away confused because the documents read like a government spreadsheet. I've spent years watching teachers and students try to apply these in real classrooms and lab settings, and the gap between the written standards and how they actually work in practice is substantial. The 8 practices come from the 2012 A Framework for K-12 Science Education. They're meant to describe what scientists and engineers actually do, not just what they know. Here is the list:

What Are The 8 Science And Engineering Practices

1. Asking Questions (for science) and Defining Problems (for engineering) This isn't just raising your hand and waiting for a response. In science, asking a testable question requires understanding variables, controls, and measurability. A question like "Why do plants grow?" is useless in a lab context. "How does light wavelength affect the rate of photosynthesis in Elodea?" is something you can actually run with. Engineering problems are framed differently — they require defining constraints, criteria, and success metrics before any design work begins. 2. Developing and Using Models

Models are everywhere in both fields, but students consistently struggle with model limitations. A physical model of the solar system made from styrofoam balls teaches nothing about scale or orbital mechanics unless you explicitly discuss what the model gets wrong. I've seen labs where students treat their diagram as truth rather than a representation, which defeats the entire purpose. 3. Planning and Carrying Out Investigations This is where most instructional time goes, and where most things fall apart. The key detail everyone misses: planning and carrying out are two different cognitive tasks. Students can plan a competent experiment in theory and still fail when executing it because they haven't considered material limitations, timing issues, or measurement error. I once watched a class spend three weeks designing a perfect circuit investigation only to discover halfway through that their resistors had ±20% tolerance, making their data essentially meaningless. We pivoted to qualitative observation of brightness changes instead. That pivot itself was a legitimate exercise in Practice 3.

4. Analyzing and Interpreting Data Data analysis is not the same as making a graph. Students routinely produce graphs without analyzing them. The practice requires identifying patterns, sources of error, correlations versus causation, and statistical significance where applicable. Using a trendline and calling it an analysis is a common failure point. Real analysis asks what the pattern means, whether it's reliable, and what alternative explanations exist. 5. Using Mathematics and Computational Thinking

This practice bridges the gap between qualitative observation and quantitative prediction. The computational thinking piece is often underutilized in science education. Simulation tools, spreadsheet modeling, and basic programming can transform a single lab into an investigation of parameter spaces that would be impossible to test physically. The constraint is time and access, not capability. A ten-minute Python script can model population dynamics across hundreds of parameter combinations in the time it takes to run one actual experiment. 6. Constructing Explanations (for science) and Designing Solutions (for engineering) These are paired because they serve parallel functions in their respective domains. A scientific explanation connects evidence to a claim using reasoning grounded in established principles. An engineering design solution connects constraints, criteria, and test results to a proposed artifact or process. The difference matters. Engineering solutions don't have a single correct answer — they have trade-offs. I've seen students treat engineering design problems as if there's one right answer, which leads to frustration and shallow iteration.

7. Engaging in Argument from Evidence This is the practice that separates rote learning from actual scientific literacy. Argumentation requires stating a claim, citing evidence, and providing reasoning that links the two. It also requires evaluating competing claims. Most classroom discussions never reach this level because students lack the vocabulary and structural scaffolding. The Toulmin model — claim, evidence, warrant, backing, qualifier, rebuttal — is the standard framework, but it's rarely taught explicitly. 8. Obtaining, Evaluating, and Communicating Information

In the pre-internet era this practice meant literature searches and report writing. Now it involves source evaluation at scale. Students encounter misinformation constantly, and the ability to assess credibility, detect bias, and synthesize multiple sources is arguably the most practically useful of the eight. The communicating component hasn't changed — clear technical writing and presentation remain essential.

How These Actually Work Together

The practices are not sequential steps in a recipe. They overlap and recur throughout any investigation. A typical research project might involve practices 1, 3, 4, and 5 in a tight loop, with practice 7 occurring at the end when results are contested. Engineering projects weave practice 2, 6, and 8 together continuously as designs are iterated and documented. Here's a specific problem I ran into repeatedly: when these practices are taught as a checklist, students complete each one mechanically without understanding how they reinforce each other. A student might produce a perfect graph (Practice 4) but fail to use it in an argument (Practice 7) because they were never shown the connection. The workaround I found was to require a single integrated product — a lab report or design portfolio — where every practice had to be visibly present and cross-referenced. This took more class time initially but produced noticeably deeper understanding by the end of the unit. The biggest structural weakness in the framework is that Practices 7 and 8 assume a level of disciplinary vocabulary and argumentation skill that many students haven't developed. The NGSS documents acknowledge this in the progression tables but don't provide enough scaffolding for teachers working with underprepared students. Pairing these practices with explicit vocabulary instruction and sentence-frame supports mitigates the issue, but it requires deliberate curriculum design rather than dropping the standards into an existing course and hoping for the best.

For engineering-specific contexts, Practice 6 (designing solutions) often needs supplementary instruction in design thinking methodologies, failure mode analysis, and prototyping workflows. The science-oriented practices map more directly to lab-based inquiry, but the engineering side benefits from project-based structures that allow for iteration and real-world constraint negotiation. Trying to teach all eight with equal weight in a standard semester schedule is impractical. Focus on the ones most relevant to your specific units and revisit the others in different contexts throughout the year.