Homeschool Guide: These lesson plans are a guide for parents. Content may contain errors — always cross-reference with official exam board specifications.

problem-solving in engineering

FoundationHigherAll Boards

4 detailed 50-minute lessons with teaching scripts, worked examples, parent guides, and assessment criteria.

Fastmail

Lesson Overview

Total Lessons: 4
Tier: Foundation and Higher
Duration: 50 minutes per lesson (200 minutes total)
Exam Boards: AQA, Edexcel, OCR, Eduqas, CCEA

Learning Objectives

Prerequisites

Materials & Equipment

Lesson 1: Introduction: problem-solving in engineering

Duration: 50 minutes

Starter Activity (5 minutes)

Quick Recall

Write down everything you already know about problem-solving in engineering. Then check against the key terms: key terms from problem-solving in engineering. Use a mini-whiteboard or paper.

Main Content (35 minutes)

Parent/Teacher Guide:
Before lesson: Read the script below. Pre-teach key vocab: key terms from problem-solving in engineering.
If stuck: Re-read the revision notes (link above), then break the content into smaller steps.
Extension: See the Stretch & Challenge ideas in Lesson 4.
Teaching Script (35 mins):
Mins 0-5 - Hook: "Today: problem-solving in engineering. By the end you will be able to answer exam questions on it unaided. It connects to the rest of Engineering because the ideas here recur across the spec."
Mins 5-20 - Direct Instruction: Work through the core ideas below one at a time; after each, ask your student to explain it back in their own words.
Mins 20-30 - Guided Practice: Model the worked example together, then let your student attempt the first practice question with guidance.
Mins 30-35 - Independent Practice: 2-3 practice questions from Lesson 3 below, with immediate feedback.
First Look

Start with the revision notes summary, then attempt: explain the key ideas of problem-solving in engineering

Plenary (5 minutes)

Check Out

Your student states one thing they learned and one question they still have about problem-solving in engineering.

Lesson 2: Core Concepts: problem-solving in engineering

Duration: 50 minutes

Starter Activity (5 minutes)

Review Previous Lesson

Quick recap: write 3 key points from Lesson 1 on problem-solving in engineering. Check them against the notes below.

Main Content (35 minutes)

Key Fact: Engineering problem-solving follows a systematic process: define, research, develop, test, evaluate, iterate.
Key Fact: The design brief defines the problem, requirements, constraints and criteria for success.
Key Fact: A specification translates the brief into measurable technical requirements: dimensions, materials, performance targets.
Key Fact: Research gathers information about existing solutions, materials, processes, user needs and relevant standards.
Key Fact: Ideation generates multiple possible solutions; the best are developed through sketching, modelling and calculation.
Key Fact: Prototyping and testing validate design decisions: physical tests confirm that the solution meets the specification.

Practice (10 minutes)

Q: explain the key ideas of problem-solving in engineering

Answer:

Plenary (5 minutes)

Explain Back

Your student teaches the key points back to you without looking. Fill any gaps immediately.

Lesson 3: Application: problem-solving in engineering

Duration: 50 minutes

Starter Activity (5 minutes)

Quick Recall

Recall the key terms: key terms from problem-solving in engineering. Define each in one sentence.

Main Content (35 minutes)

Parent/Teacher Guide: Let your student attempt each question alone first, then compare with the model answer. Award method marks for correct working even if the final answer is wrong.

Work through the practice questions on the revision notes page for this topic.

Plenary (5 minutes)

Error Review

Review any questions answered incorrectly. Identify whether the error was knowledge, method, or reading the question.

Lesson 4: Exam Practice: problem-solving in engineering

Duration: 50 minutes

Starter Activity (5 minutes)

Command Words

Review what these command words require: state (one point), describe (say what happens), explain (say why), compare (both sides), evaluate (judgement).

Main Content (35 minutes)

Extended Answer

Extended question: Full-Mark Response A company needs a portable tablet stand for site engineers that is stable on uneven ground, folds flat and costs under 15 pounds to manufacture. Describe the problem-solving process from brief to final design. [8 marks] <div class="

The brief: design a portable tablet stand for site engineers, stable on uneven ground, folding flat, costing under 15 pounds. Research investigates existing stands, site conditions, available materials and processes. The specification includes: max weight 500g, folded size under 200x150x20mm, adjustable angle 0-90 degrees, stable on 15-degree inclines, manufacturing cost under 15 pounds, durable outdoors. Ideation generates concepts (tripod, X-frame, kickstand); each is evaluated against the specification. The best concept (likely folding tripod for stability) is modelled in CAD and prototyped using FDM. The prototype is tested for stability, ease of folding, weight and robustness. Evaluation compares results against the specification. Iterations address shortcomings: widening the base, improving the hinge, switching material to meet cost. Final testing confirms all requirements are met.

Exam Tips: In problem-solving questions, follow the systematic process in order. | Always distinguish between the brief (what and why) and the specification (how much and how well). | Iterative design is not failure - it is the expected process of improvement. | Risk assessment: identify the hazard, assess the risk AND specify the control measure. | Fitness for purpose links directly to the specification - if it meets the spec, it is fit for purpose.
Common Errors: ✗ The first design solution should be the final one. ✓ Initial designs rarely meet all requirements; the iterative process is essential to reach an optimal solution. ✗ A specification is the same as a design brief. ✓ A brief is a general problem statement; a specification is a detailed, measurable list of technical requirements. ✗ Risk assessments only need to be done once. ✓ Risk assessments must be reviewed regularly and updated whenever conditions or processes change. ✗ Testing is only needed for the final product. ✓ Testing at prototype stage catches problems early, saving time and money compared to discovering failures in production.
Stretch & Challenge (Grade 8-9):
  • Synoptic links: explain how problem-solving in engineering connects to another Engineering topic you have studied
  • Real-world: research one real-world use or example of problem-solving in engineering
  • Critical: "What are the limitations of the models used in problem-solving in engineering?"

Plenary (5 minutes)

Assessment Criteria
  • Got it: Confident explanation + correct worked examples
  • Getting there: Main points OK, needs support with detail
  • Not yet: Confused on key concepts - re-run Lesson 2

Homework & Consolidation

Recommended Resources

🎓 Smart Lesson (Guided)