# Teaching Engineering & the Design Process (Workshop) > A ready-to-run PD workshop on the engineering design process at every grade level. Run-of-show, handout, follow-up. *A ready-to-run professional learning workshop from K12 Academics. Source page: https://pd.k12academics.com/teaching-engineering-design-workshop.html* Engineering education is not just for future engineers, it teaches a powerful way of solving problems: defining a problem, designing solutions, testing, and improving. The engineering design process engages students in applying science and math to real challenges, and it works at every grade level. The engineering design process, define, design, build, test, improve, teaches a powerful problem-solving approach, applying science and math to real challenges, and works at every grade level, not just for future engineers. ## Why it works Engineering and design education, now part of science standards (the NGSS include engineering design), engages students in a structured yet creative process, defining problems, developing and testing solutions, and iterating to improve, that applies science and math to real-world challenges and builds problem-solving, creativity, and persistence. Research supports engineering design as accessible and valuable across K-12, developing both content understanding and transferable skills, with productive failure and iteration central. **The research:** NGSS engineering design; research on K-12 engineering education. ## The run-of-show ### Staff meeting (15 minutes) A fast introduction to plant one routine. **Goal:** everyone leaves with one thing to try. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 3 min | Hook | Do your build activities include testing and improving, or just building? Name it. | You are surfacing one-shot builds. | | 0:03 | 5 min | Mini-teach | Define, design, test, improve. One slide. | | | 0:08 | 5 min | Plan one | Name a real problem to design for. Turn and talk. | | | 0:13 | 2 min | Commit | Each person names a design challenge. | | ### PLC / team meeting (45 minutes) The standard version. **Goal:** every teacher leaves with something designed for a real upcoming lesson. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 5 min | Hook | One-shot build vs iterate-and-improve. Which is engineering? | Let them see iteration. | | 0:05 | 8 min | Mini-teach | The design process and productive failure. | | | 0:13 | 12 min | See it in action | Plan a design challenge with the full cycle. | Apply science and math. | | 0:25 | 12 min | Design | Run an engineering design challenge. | Protect the full time. | | 0:37 | 5 min | Share | Swap plans in pairs; add a test-and-improve step. | Keep it in pairs. | | 0:42 | 3 min | Commit + follow-up | Lock it in and set the check-in date. | | ### Half-day institute (~3 hours) A deep session for a PD day. **Goal:** built, practiced, and a rollout planned. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | Block 1 | 45 min | Experience + why | One-shot builds, then the design process. | | | | 15 min | Break | | | | Block 2 | 60 min | Design challenges | Teams build design challenges with iteration. | Apply science and math. | | Block 3 | 45 min | Practice | Prototype and iterate a challenge. | Iteration is the heart of it. | | Close | 15 min | Plan the rollout | Adopt the design process; set the check-in. | | ## The core activity: run an engineering design challenge Teachers leave with a design challenge that runs the full process with iteration. - Pick a real problem students could solve. - Plan the design process (define and constrain, design, build, test, improve). - Apply relevant science and math. - Make iteration and productive failure central, not a one-shot build. ## Facilitator notes - Use the full design process, and apply science and math. - Center iteration and productive failure. - It works at every level. ## Adapt it - **Elementary:** simple design challenges, iteration. - **Secondary:** engineering design, constraints, applying science and math. - **All settings:** define, design, test, improve. ## Participant handout One page for every teacher. Print it, or save it as a PDF. ### Engineering & Design: define, design, test, improve **Powerful problem-solving:** the full design process with iteration, applying science and math to a real challenge. - The real problem students could solve: __________ - The design process steps I will use: __________ - The science and math applied: __________ - How I center iteration and productive failure: __________ - Where a one-shot build needs to become iterative: __________ ## Make it stick The full design cycle: - Run the full design process. - Center iteration. - Bring an engineering challenge to the next PLC. ## Common questions **Isn't engineering only for high school or future engineers?** No. The engineering design process, define, design, test, improve, works from elementary up, builds problem-solving for all students, and is part of modern science standards. **What is the engineering design process?** A cyclical approach: define the problem and constraints, brainstorm and design solutions, build and test, then improve based on results. Iteration and productive failure are central. **How is it different from a science experiment?** Science investigates how the world works; engineering designs solutions to problems. Both matter; engineering applies the science to build and improve things. ## Go deeper - [TeachEngineering](https://www.teachengineering.org) ## Build it into a bigger day - [Teaching Science Through Phenomena](https://pd.k12academics.com/teaching-science-phenomena-inquiry-workshop.html) - [Makerspaces & Maker Education](https://pd.k12academics.com/makerspaces-maker-education-workshop.html) - [Productive Struggle](https://pd.k12academics.com/productive-struggle-workshop.html) --- Full workshop page: https://pd.k12academics.com/teaching-engineering-design-workshop.html All workshops: https://pd.k12academics.com/