Lesson 5 of 37 in this sequence

14%

Not completed yet

Saved on this device only — not synced to an account yet.

Learning path

Step 5 of 37

Continue the sequence

ResumeReturn to this step ReviewRevisit the core idea RemediateGet repair practice Next stepChoose the next lesson manually

Completion

Review objectives and instruction
Complete the activity with manual learner confirmation
Answer every understanding-check item
Show completion feedback and reward only after the learner finishes the check

Progress

Step 5/37
15 content types
AI help source context available
Auto-advance blocked

Review objectives and instruction

AI help

Available only with source grounding, privacy limits, age controls, and measurement.

AI source context

Engineers Are People Who Solve Everyday Problems · What Making Is · K-2-ETS1-1 · engineering design

Evidence: local lesson AI-help metadata only; source-grounding, privacy, age-safety, and measurement hooks do not prove real model quality, production telemetry, child AI approval, or AI tutor production readiness

Production AI readiness not claimed

AI source context

Assessment shape

Local lesson assessment shape is complete.

Local shape only; production answer-attempt telemetry, live ownership/RLS evidence, mastery interpretation, release, and production readiness are not claimed here.

Objectives: 3
Activity: Prompt ready
Quiz items: 3 items, 3 answer keys, 3 explanations
Reward: Completion reward ready

Assessment progress stays manual: do not auto-advance through uncertain answers, failed writes, consent, media, payment, learner choice, or AI-assisted checks.

Learning-loop evidence: Content-map contract only; persistence and production learner-progress writes require route/API evidence.

Manual policy: assessment, media, consent, payment, learner choice, failed writes, and AI-uncertain help stay under learner control.

Prerequisite: Complete or review Drawing a Plan Before You Build; Use with parent or guardian controls for child learners

AI guardrails

Privacy

Do not send raw child free text without consent
Use source excerpts and non-identifying progress state only
Asset is not registry-gated

Age safety

Apply junior audience controls before AI-help claims
Keep child learner AI paths behind guardian/product review evidence before readiness claims

Measurement

Log AI help usage by surface and asset slug
Evaluate answer quality against source-grounded rubric before production-readiness claims
Tie remediation prompts to completion, retry, or review outcomes

Local AI-help guardrails only; they do not prove guardian approval, production telemetry, model evaluation, release, deployment, or AI tutor production readiness.

Source and rights

Source path: koydo-app/scripts/curriculum-authoring
License: ai-generated-koydo
Attribution: Attribution decision needs owner review
AI provenance: claude-opus-4-8

Source review gates: attribution_missing

Local source evidence only; this does not prove publication rights, attribution approval, AI provenance clearance, release, deployment, or production readiness.

Route review

Current route: /library/junior/engineering_making/en/lesson/engineers-solve-problems
Route source: Fallback route needs owner canonical review
Candidate route: /library/junior/engineering_making/en/lesson/engineers-solve-problems

Local route evidence only; fallback candidates need owner-approved canonical route policy before route writes, production discoverability, or readiness claims.

Content gates: canonical_target_web_missing_uses_library_fallback

lessonslessonslesson objectivesmedia scenesdrillspractice setsquizzesfeedbackcharacterscitationsconcept mapsprogressresumereviewremediationnext steps

Engineers Are People Who Solve Everyday Problems

with Atlas

Atlas stands at a workbench covered with cardboard tubes, tape, and wooden blocks, peering at a soggy paper bridge that has collapsed under the weight of a toy truck, scratching his chin and already reaching for a sturdier piece of cardboard to try a new design.

Identify what an engineer does: spots a problem and designs or builds something to fix it.
Explain the difference between a problem and a solution in a real example.
Identify at least two things engineers might design or build to solve everyday problems.

Key terms

engineer: a person who looks at a problem and designs or builds something to fix it
problem: something that is hard, broken, or bothers people and needs fixing
solution: the thing an engineer designs or builds to fix a problem
design: to plan out how something will work before you build it

What Makes Someone an Engineer

An engineer is not only a person in a hard hat. An engineer is anyone who spots a problem and then designs or builds something to solve it. Engineers notice what is hard or broken in everyday life, like a tippy cup or a wobbly chair. Then they think hard about what could help. They draw it, build it, and test it. That curious, fix-it way of thinking is what makes someone an engineer.

From Problem to Solution

Every solution starts with a problem. First the engineer notices the problem clearly, like a paper bridge that keeps collapsing. Next they imagine an idea that could help. Then they build that idea and try it out. If it works, the new thing is the solution. A solution is always the answer to a problem, which is why finding the problem first matters so much before you start building.

Worked examples

Atlas's paper bridge keeps collapsing under his toy truck. How does he turn this problem into a solution?

Notice the problem clearly: the paper bridge is too weak for the heavy truck.
Think of an idea: fold the cardboard so it is thicker and stronger.
Build the new, stronger bridge using the folded cardboard.
Test it by rolling the truck across to see if it holds.

Answer: The folded, stronger cardboard bridge is the solution that fixes the weak-bridge problem.

Hey, I'm Atlas — and I love figuring things out! Have you ever spilled your water because your cup kept tipping over? Or wished your backpack had a pocket in just the right spot? Those little troubles are called PROBLEMS. An engineer is a person who looks at a problem and designs or builds something to fix it. Engineers look around, notice what is hard or broken, and then think: "What can I make to help?" Let me show you. My toy truck was too heavy for my paper bridge — CRASH! That was my problem. So I tried something new. I folded the cardboard to make it thicker and stronger. Now the truck rolls right across. That new, stronger bridge is my SOLUTION — the thing I designed and built to fix the problem. Engineers design and build all kinds of things: ramps for wheelchairs, waterproof rain boots, safer bicycle helmets, and water filters that make drinking water clean. Every single one started the same way — someone saw a problem and said, "I can design or build something to fix this!" You can be an engineer too. Just look for a problem, think about what might help, and start building!

Activity

Sort each card into the correct box: is it a PROBLEM or a SOLUTION that an engineer designed or built?

Practice

Name one problem you notice at home and describe a solution you could build.

Look around your classroom and point out one problem an engineer could fix.

Common mistakes to avoid

Engineers just buy new things when something breaks.Engineers design and build something new to fix the problem instead of only buying a replacement.
A problem and a solution are the same thing.A problem is the trouble that needs fixing, while a solution is the thing you build to fix it.

Check your understanding

What does an engineer do?

Atlas's paper bridge collapsed under a heavy toy truck. What would an engineer do NEXT?

Which of these is an example of a SOLUTION an engineer might design or build?

Recap

An engineer is a person who spots a problem and then designs or builds a solution to fix it. A problem is something hard or broken, and a solution is the thing you make to solve it. Anyone who notices a problem and builds a fix is thinking like an engineer.

Reflect

What problem would you most like to solve as an engineer?