Your morning alarm knows when to scream. The hallway lights at school know when it’s dark. Your game saves know when you hit a checkpoint. None of that is magic — it’s automation: if something happens, then something else happens, often without you clicking every time. In this adventure, you’ll think like a tiny robot designer using Scratch-style ideas — no typing code, just clear logic and big imagination.
What You'll Learn
- What automation means in everyday language — lights, games, reminders, and more.
- How if → then thinking builds reliable mini “machines” in your head and on screen.
- How Scratch blocks (drag-and-drop) represent decisions and loops.
- How to sketch flowcharts so anyone could follow your plan — even a pet (almost).
- How automation connects to how apps and AI helpers seem “smart.”
Concept:
Automation is “when this happens, do that” without clicking every time — like a night light that knows when it’s dark. If → then thinking is how lots of “smart” apps feel magical.
Adventure 1: The Lazy Genius — Why Automate?
Automation = making steps run by rule instead of by you remembering every time.
| Real life | Hidden rule (simple) |
|---|---|
| Night light | If dark → turn on |
| Sprinkler | If soil dry → water |
| Game auto-save | If level ends → save file |
| Birthday reminder | If date matches → buzz phone |
You’re not “lazy” for liking automation — you’re smart. You save brain fuel for harder puzzles.
Fun Fact
Ancient water clocks and windmills were early automation — gears and levers instead of pixels.
Try This!
Morning map: Write your real morning as 5–8 steps. Circle one step you wish happened automatically (within reason!). Draw a cartoon robot doing only that step.
Try This!
Silly automation: Invent “If my dog wags, then ___” three funny then ideas. Share at dinner — vote least practical, most hilarious.
Fun Fact
Escalators are loops — steps keep coming because motors and sensors follow repeat rules. You already ride everyday loops without thinking in code words.
Visual: A Rube Goldberg machine on paper — one real if-then in the middle of the chaos.
| If this happens… | Then the automation… | Try it! |
|---|---|---|
| You finish homework checklist | Plays your victory song (with adult OK) | Write the if and then on two sticky notes |
| Rain in forecast | Reminds you about umbrella | Draw a silly flowchart for your backpack |
| Friend sends “?” in chat | You send a meme (kind one!) | Discuss: is this automation or you being thoughtful? |
Try This!
Robot breakfast: List three if-then rules for a pretend breakfast robot. What’s one bug (forgotten else) that makes cereal explode? Fix it on paper.
Adventure 2: If This, Then That — The Superpower Shape
Every automation has:
- Trigger (the if — what we watch for)
- Action (the then — what we do)
- Sometimes otherwise (what if the if didn’t happen?)
Shape in words:
IF [something we can detect]
THEN [something we can do]
ELSE [backup plan] (optional but powerful)
| If | Then | Else (optional) |
|---|---|---|
| Answer is “pizza” | Play “yum” sound | Say “cool, what topping?” |
| Score > 10 | Show “Level up!” | Show “Try again!” |
| Rain in forecast | Icon shows umbrella | Icon shows sunglasses |
Fun Fact
Computer scientists use fancy words like conditional — you can just say “decision diamond” in a flowchart and sound pro.
Try This!
Card sort: Write 10 events on slips (“doorbell rings,” “bell rings at school,” “low battery”). Sort into good triggers vs bad triggers for a homework reminder bot — discuss why.
Try This!
Human robot: One person is the robot following only spoken if-then rules. Another gives inputs (“I’m hungry”). Does the robot freeze if you forgot an else? Fix the rules together.
Adventure 3: Scratch World — Blocks Instead of Spells
Scratch is free, visual, and made for creators your age. You snap blocks like LEGO.
Blocks to know by story:
| Block idea | Story name you can remember |
|---|---|
| When green flag clicked | “When the show starts” |
| Ask and wait | “The character interviews you” |
| If … then … else | “Choose your own adventure door” |
| Repeat | “Chorus of the song” |
| Broadcast | “Whisper to another sprite” |
Fun Fact
Scratch’s cat mascot has seen more projects than any real cat has naps.
Try This!
Two-sprite play: Sprite A asks a question. Sprite B only reacts if the answer contains a secret word you picked. No secret word? Sprite B shrugs.
Try This!
Sound automation: If key pressed then play drum — else meow. Annoy siblings ethically (volume low, time limits!).
Visual description: Screenshot or redraw your block stack — color-code with crayons: yellow = start, orange = control, purple = looks.
Adventure 4: Chatty Mini-Bot — Design on Paper First
Before pixels, paper prototypes rule.
Chat flow sketch:
- Greeting: “Hi! I’m ___ bot.”
- Question 1 → branch A / B / C
- Each branch → unique reply + maybe second question
- Polite ending: “Thanks for chatting!”
| Design choice | Why it matters |
|---|---|
| Fewer options | Easier to test |
| Clear words | Less confusion |
| Escape hatch | “Type exit anytime” (if using typed bots later) |
Fun Fact
Big AI chatbots are wildly more complex — but deep down, there’s still pattern matching and rules stacked in layers. You’re learning the baby version of big ideas.
Try This!
Emotion bot: Plan a bot that responds if user says “happy,” “sad,” “mad” — three different supportive lines — no mean jokes.
Try This!
Flowchart only: Draw diamonds for decisions, rectangles for messages, arrows for paths. Test with a friend — did they get stuck in a loop? Add an exit.
Adventure 5: Mini-Bots in the Wild — Games & School
| Where | Automation you might notice |
|---|---|
| Games | Enemy aggro when you get close |
| Apps | Badge when streak hits 7 days |
| Classroom tools | Quiz instant feedback on format |
| Smart home | Lights off when everyone leaves |
Connect to ethics: Automation should help, not trick. Dark patterns are rules designed to manipulate — like infinite scroll with no stopping cue. You can notice and take breaks.
Fun Fact
Some speedruns exploit automation glitches in games — players study if-then rules harder than homework (balance, friends!).
Try This!
Good vs sneaky: List two automations that help users and two that pressure users. Star the ones you’d build vs delete.
Try This!
Automation wishlist for good: Invent one school-friendly automation that helps inclusion (e.g., if loud room then captions bigger) — draw the poster.
Adventure 6: Loops, Variables & Events — Big Ideas, Zero Jargon Stress
Loop = “keep doing this until a stop rule.”
Example: Repeat cheer until timer hits zero — then bow.
Variable = a labeled box that holds a value that can change.
Example: Score starts at 0 — if basket then score + 2.
Event = “when something outside happens, wake up the code.”
Example: When space key pressed → jump.
| Idea | Real-life parallel |
|---|---|
| Loop | Chorus of a song repeats |
| Variable | Lives left in a game |
| Event | Doorbell rings → you answer |
Scratch uses orange loops, variables you can name, and events like green flag.
Fun Fact
Airplane autopilot uses loops that read sensors hundreds of times per second — you use the same shape of thinking in games.
Try This!
Variable diary: Track one number for a week (pages read, minutes moved) — automate celebration: if week total > goal then dance party.
Try This!
Loop unplugged: Jumping jacks while someone counts down from 10 — if they say “freeze” mid-loop, stop — that’s an event interrupt.
Try This!
Name your variables silly but clear — livesLeft beats x7 when you read your blocks later.
Visual: Labeled jars on a shelf — score, level, playerName — coins inside change as game goes.
Adventure 7: From Scratch to Real Robots — Same Logic, Different Stage
Factory robots, hospital helpers, and vacuum bots all use sense → decide → act — cousins of if-then.
| Sense (input) | Decide (rule) | Act (output) |
|---|---|---|
| Bump sensor | If bump then back up | Wheels reverse |
| Light sensor | If dark then slow | Motor eases |
| Mic “Hey…” | If wake word then listen | LED glows |
You’re not building factory arms today — but your Scratch cat uses the same story.
Fun Fact
Mars rovers have minutes of delay — they need automation loops because Earth can’t steer live.
Try This!
Robot charades: Act out sense-decide-act for brushing teeth — what input? what rule? what motion?
Try This!
Draw a rover rule: If rock too big → go around; else collect sample. Add one fun failure mode (stuck in sand).
Visual: Mars doodle with speech bubble if-then rules.
Adventure 8: Bug Safari — When Rules Go Hilariously Wrong
Key Takeaway
- Bugs are logic mistakes — infinite loops, missing else, wrong sensor.
- Explaining your flowchart out loud (even to a rubber duck) finds bugs fast.
- Laughing at broken rules helps you patch without shame — real engineers do this!
A bug is not a creepy-crawly here — it is a mistake in the logic. Classic kid examples:
- If homework done then game time — but you forgot else dinner first → chaos.
- Repeat cheer until timer ends — but timer never starts → infinite cheer (loud!).
- If rainy then umbrella — but sensor thinks bright lamp is sun → umbrella indoors (funny sketch).
| Symptom | Likely bug type |
|---|---|
| Same thing forever | Loop missing stop |
| Wrong thing sometimes | If condition too simple |
| Nothing ever happens | Trigger never true |
Fun Fact
The first computer bug (story time) was a real moth in a machine — now we call mistakes bugs anyway. Your Scratch cat prefers digital bugs only.
Try This!
Bug theater: Act out a broken morning routine on purpose — freeze when the “code” loops wrong. Audience shouts “patch!” — you fix one rule.
Try This!
Rubber duck debug: Explain your flowchart to a rubber duck (or apple). If you stumble, that’s where the bug hides.
Adventure 9: Kind Automations — Design for Real Humans
Good designers ask: Who might be left out if the rule is too simple?
| Rule idea | Kind upgrade |
|---|---|
| If loud then mute mic | Also show “raise hand” icon for shy kids |
| If wrong answer then buzz | Else gentle hint first — confidence matters |
| If dark then bright screen | Remember night mode for sleepy eyes |
Fun Fact
Crosswalk buttons sometimes fake a wait sound so humans feel heard — ethics shows up even in tiny automations. Ask: honest or tricky?
Try This!
Inclusive bot sketch: Draw one screen that helps both a kid who reads fast and a kid who needs bigger text — no code, labels only.
Tell Someone — Teach If-Then at Snack Time
Step 1 — Pour a snack — if bowl empty then sad face (joke).
Step 2 — Draw one real if-then from your day on a napkin.
Step 3 — Ask a grown-up for their if-then from work (email alerts, calendar pings).
Step 4 — Together invent one family rule that automates kindness (if someone does dishes then sticker on chart).
Try This!
Chore flowchart: Paper only — if trash full then take out else play one song first — debate if the else is fair.
Activities
- Flowchart your locker: From arrival to open locker — where do people get stuck? Add one if-then fix.
- Scratch debug party: Break something on purpose in a tiny project — trade with a friend to find the bug.
- Physical loop: Jump if someone claps — else spin — repeat 8 times — laugh, hydrate.
- Snack algorithm: Write if-then for building a perfect snack — inputs = what’s in the fridge (pretend).
- Translate to English: Pick a Scratch stack — write the same logic in plain sentences for a kindergartener.
- Morning bot vs evening bot: Two flowcharts — should they share rules or not? Debate.
- Safety check: List three things a bot should never ask a stranger kid — add to your Scratch project notes.
- Recipe if-then: Write if-then for making toast or cereal — where do branches happen? (Out of milk? Burnt toast?)
- Sports replay: Watch one replay moment — narrate it as if ball crosses line then goal — else keep playing.
- Dream house automation: Draw three silly if-then gadgets for your room (e.g., if book falls then pillow catapult — OK, maybe too silly).
- Sister/brother bot: Write five cards your sibling could draw — you must respond exactly as programmed — laugh at literal answers.
Your Challenge
Build one of the following (with adult permission for accounts):
Follow these steps before you say “done”:
- Choose A, B, or C — circle it on paper — no switching midway unless tech really breaks.
- Name your project — funny working titles allowed (“Banana Router 3000”).
- Build the smallest version first — one path that works beats ten paths that glitch.
- Break it on purpose — one bug — fix it — celebrate with a tiny dance.
- Test with two humans — watch where they get stuck — add one else or exit.
- Document — one sentence what it does + who should use it.
Option A — Scratch: A mini chatbot or choose-your-own adventure with at least three branches and one sound or costume change.
Option B — Paper only: A 12-step flowchart poster for a “Homework Helper Bot” that never does homework for you — only organizes steps.
Option C — Role-play kit: A script for two humans acting as bot and user, with if-then cards the bot must follow exactly.
Include: A title, your name, and one sentence: “Automation helps humans by ___.”
What You Learned
- Automation saves effort by rules — from alarms to game AI.
- If → then → (else) is the backbone of decisions.
- Scratch makes logic visible — great training wheels for any future tech.
- Paper flowcharts catch bugs before code — or without code at all.
- Chat flows are stories with branches — same energy as games.
- Ethics matter: good automation supports; sneaky automation tricks.
- Thinking in steps makes you better at everything — sports, music, group projects.
Show Off!
- Screen record your Scratch (permission) — narrate like a nature documentary: “Here we see the wild sprite choosing a path…”
- Tape your flowchart near your desk — teach a parent one diamond decision.
- Host a “bot battle” — whose mini-bot is kindest? Funniest? Most useful?
- Journal one line: Today I automated my thinking by ___.
- Teach loops with jump rope — two friends turn rope, one counts if-then rules for when to enter.
- Dream machine drawing: Label inputs and outputs on a fantasy invention — present 60 seconds.
You’re not just playing games — you’re seeing the gears. That’s engineer vision. Keep snapping blocks and drawing arrows — the future needs people who understand how things decide.
Key Takeaway
- Triggers start workflows; actions do the work; else branches save you from silly loops.
- Scratch (and paper flowcharts) make thinking visible — same ideas as big apps, smaller stage.
- Good automation helps people; sneaky automation tricks them — know the difference.
- Loops, variables, and events are just fancy names for patterns you already know from games and music.
- Debugging is a superpower — patience + clear rules = fewer “spills.”
Imagine if your classroom door had one automation rule — what should it never do? Ask your teacher about one real automation at school (bell, lights, library checkout).