How to Teach Engineering in High School: A 12-Week Crash Course Sequence

High-school engineering works best when students repeatedly do the thinking engineers actually do: define a need, identify constraints, model a system, use evidence, compare tradeoffs, test assumptions, and revise a design. A playlist can provide excellent technical explanations, but a coherent course needs more than a sequence of videos. It needs an instructional spine.

This 12-week sequence uses Crash Course Engineering as the recurring content source while organizing the 46 numbered episodes into a progression from engineering disciplines and physical laws to materials, controls, sustainability, advanced technologies, infrastructure, and design synthesis. The goal is not to turn every student into a specialist. It is to help students recognize the reasoning patterns that connect very different engineering fields.

Start with engineering design, not a list of branches

The NGSS high-school Engineering Design expectations emphasize defining criteria and constraints, breaking complex problems into manageable parts, evaluating solutions using tradeoffs, and using models or simulations to test proposed solutions. That framing is useful even when a course also teaches thermodynamics, materials, electronics, biomedical engineering, or environmental engineering.

A strong recurring routine is to ask students five questions throughout the course:

1. What problem is the design supposed to solve? What counts as success, and what constraints matter?
2. Where is the system boundary? What components, flows, people, environments, and interfaces belong inside the analysis?
3. What physical or process limits control performance? Energy, matter, forces, heat, fluid flow, material properties, information, and time all create constraints.
4. What evidence supports the explanation or design choice? Students should distinguish observations from mechanisms and compare competing explanations.
5. What tradeoff or verification step comes next? Better engineering decisions make uncertainty visible rather than pretending it does not exist.

This approach aligns with the broader practices described in the National Academies' Framework for K–12 Science Education, including developing and using models, analyzing data, using mathematics and computational thinking, constructing explanations and designing solutions, arguing from evidence, and communicating information.

A practical 12-week Crash Course Engineering sequence

The sequence below groups the 46 episodes conceptually rather than treating the commercial bundle boundaries as instructional units.

Week 1 — What Engineers Do

Begin with engineering as a problem-solving discipline, then compare civil, mechanical, and electrical engineering. Students should leave the week seeing disciplines as overlapping toolkits rather than isolated career labels.

Week 2 — Engineering Fields & Conservation

Chemical, biomedical, and industrial engineering expand the range of systems students encounter. Conservation laws then provide a unifying idea: engineers track what enters, leaves, accumulates, transforms, or is lost from a system.

Week 3 — Thermodynamics, Engines & Mechanical Behavior

Move from reversibility and the laws of thermodynamics into heat engines, cycles, stress, strain, viscosity, and flow behavior. This week establishes a critical engineering habit: performance is limited by physical laws, not only by creativity or budget.

Week 4 — Moving Fluids, Heat & Mass

Fluid equipment, heat transfer, combustion-related thermal reasoning, and mass transfer show students how engineers move energy and material through real systems. Ask students to identify driving forces, resistances, and boundary conditions in each example.

Week 5 — Separation & Structural Materials

Mass separation leads into toughness, metals, ceramics, and polymers. Instead of memorizing material categories, have students compare properties against design requirements: strength, stiffness, toughness, temperature tolerance, corrosion behavior, manufacturability, cost, and lifetime.

Week 6 — Electrical, Nano & Biological Materials

Conductors, semiconductors, solar cells, nanomaterials, and biomaterials provide a natural bridge between material structure and function. This is a good point for an optional unit checkpoint because students must integrate electrical, chemical, and biological constraints.

Week 7 — Control, Structures, Ethics & Safety

Process control and structural behavior are paired with engineering ethics and safety. This is intentional: a system that technically “works” can still be a poor design if control logic, failure modes, human consequences, or risk were handled badly.

Week 8 — Environmental & Energy Engineering

Water systems, renewable energy, clean-energy futures, and batteries make tradeoffs unavoidable. Students can compare carbon, reliability, storage, materials, infrastructure, cost, land use, and lifecycle constraints rather than reducing energy choices to a single metric.

Week 9 — Complex Engineered Technologies

Robotics, aerospace, computing, and drug discovery force students to think across subsystems. Ask what happens when mechanical, electrical, software, biological, and human requirements interact—and which interface is most likely to become the bottleneck.

Week 10 — Bioengineering, Food & Structural Problem-Solving

Smart medical technologies, genetic engineering, food engineering, and the Leaning Tower of Pisa create a useful contrast between microscopic design, process-scale manufacturing, and large structures. The recurring question is the same: what evidence tells us the proposed intervention will work under real conditions?

Week 11 — Infrastructure, Communication, Oceans & Design

Transportation, communications, marine corrosion, and desalination emphasize networks, interfaces, maintenance, environment, and scale. By this point, students should be able to move between component-level reasoning and whole-system reasoning.

Week 12 — Becoming an Engineer & Full-Course Synthesis

Finish the numbered playlist with careers and the future of engineering, then shift to two cumulative application lessons: engineering failure analysis and an engineering design review. These lessons ask students to diagnose evidence, compare plausible mechanisms or proposals, identify missing tests, and defend a recommendation before the cumulative final.

Use video as evidence, not as the entire lesson

A simple routine keeps video instruction active without making every class period complicated:

• Before viewing: give students one design question, system question, or prediction to keep in mind.
• During viewing: students record only the evidence needed to answer the assigned question rather than copying every fact.
• After viewing: require application—compare two materials, diagnose a failure, explain a tradeoff, interpret a system boundary, or propose a verification test.

The National Academies' work on Engineering in K–12 Education highlights engineering design, integration with mathematics/science/technology, and habits of mind such as systems thinking, creativity, collaboration, communication, and ethics. Those habits are strengthened when students must use episode content to make a decision, not merely recall it.

Build an assessment rhythm that does not consume the course

For a 60-day implementation, one practical structure is:

• Weeks 1–11: four episode lessons plus one required weekly checkpoint.
• Unit checkpoints: optional/flexible cumulative assessments after Units 1–4, useful for review, intervention, or grading needs.
• Week 12: Episodes 45–46, a failure-analysis lesson, a design-review lesson, and the required cumulative final.
• Optional Week 12 checkpoint: retained as a flexible resource rather than consuming an additional required course day.

This keeps the course at 60 required days while still giving teachers multiple ways to collect evidence of learning.

What should students be able to do by the end?

A coherent high-school engineering course should leave students able to do more than identify engineering disciplines. They should be able to define criteria and constraints, trace energy or material through systems, connect structure to function, compare competing explanations, recognize uncertainty, analyze risk and ethics, evaluate sustainability tradeoffs, and explain what evidence would verify a design before full commitment.

Those competencies transfer across engineering fields—and they are much closer to authentic engineering thinking than a long vocabulary list.

Ready-to-use planning options

If you want the complete 12-week sequence already organized, see the Crash Course Engineering Full Curriculum. It includes the episode resources, weekly and unit assessments, cumulative final, planning documents, and the Week 12 synthesis lessons.

You can also start with the free Engineering Educator Planning Guide to review the course architecture, or try Episode #1: What Is Engineering? free before using a larger set.

Teachers who prefer smaller sections can use the four episode bundles: Episodes #1–12, #13–23, #24–34, and #35–46.

Independent educational resource. Crash Course and YouTube are referenced for instructional compatibility; this resource is not affiliated with or endorsed by Crash Course.