Lesson 6 of 37 in this sequence

16%

Not completed yet

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

Learning path

Step 6 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 6/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

Find a Problem to Solve · Engineers look around and find a problem that people want to fix. · K-2-ETS1-1

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: 4
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 Engineers Are People Who Solve Everyday Problems; 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/what-is-a-problem
Route source: Fallback route needs owner canonical review
Candidate route: /library/junior/engineering_making/en/lesson/what-is-a-problem

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

Find a Problem to Solve

with Atlas

Atlas the friendly robot guide walks through a busy park, pointing at a wobbly bench and a spilled water cup while kindergartners watch, lean in, and smile.

Define a problem as something that bothers people or does not work well.
Identify real problems by looking around a room or a park.
Explain that engineers find a problem before they try to fix it.
Sort everyday situations into 'a problem' or 'not a problem'.

Key terms

problem: something that bothers people or does not work well
engineer: a person who finds problems and builds or fixes things to solve them
observe: to look and listen carefully to notice what is wrong
needs: the things people want fixed or made better

What Counts as a Problem

A problem is something that bothers people or does not work well right now. A wobbly chair is a problem because it might make someone fall. A jar that is too hard to open is a problem because it stops people from getting what they need. A happy, sunny day is not a problem, because nothing is bothering anyone. To find a real problem, look for something that is hard, broken, or in the way for people today.

Find the Problem Before You Build

Engineers do not start by grabbing tools. First they look around with their eyes and ears and watch how people feel. They ask, what do people want to fix? Only after they find a clear problem do they pick one to solve. Finding the problem first is important, because if you build before you know the problem, you might make something that does not help anyone at all.

Worked examples

You walk into a room and want to find a problem to solve. How do you do it?

Look around with your eyes and listen with your ears.
Notice anything that is broken, messy, or hard to reach.
Ask yourself if that thing bothers people or does not work well.
Pick one thing that truly bugs people as your problem to solve.

Answer: A real problem is something that bothers people right now, like a backpack zipper that keeps getting stuck.

Hi! I am Atlas. Let me tell you a secret about engineers — engineers are people whose job is to find problems and then build or fix things to solve them. Engineers do not start by building. First, they look around. They use their eyes and ears. They watch how people feel. A problem is something that bothers people. It is something that does not work well. A wobbly chair is a problem. A toy that is too hard to open is a problem. A puddle blocking a path is a problem. Engineers ask, 'What do people want to fix?' Then they pick one problem to work on. You can do this too! Look around your room right now. Is something hard to reach? Is something messy? Is something broken? That is a problem you found! Finding the problem is the first big step. If you feel stuck, just point at one thing that bugs you. That is a great start. Good job, problem finder!

Activity

Sort each card into the bin that says 'a problem' or 'not a problem'. Some bins may get more cards than others.

Practice

Look around your room and name one real problem you can find.

Explain why a sunny day at the park is not a problem to fix.

Common mistakes to avoid

Engineers start by building things.Engineers first look around to find a clear problem before they build anything.
Engineers must find a problem in every situation.Some things work fine and bother no one, so they are not problems that need fixing.

Check your understanding

What is the FIRST thing an engineer does?

Which one is a problem an engineer might want to fix?

Is a sunny, happy day at the park a problem to fix?

Recap

A problem is something that bothers people or does not work well right now, like a wobbly chair or a stuck zipper. Engineers do not start by building. First they look around carefully to find a real problem, then pick one to solve. Finding the problem is the first big step in engineering.

Reflect

What is one problem near you that you would like to solve?