Week 11: Straight-Line Systems and Loop Systems

Unit 4: Better System Shapes

This Week's Big Question

Why do some systems keep reusing their outputs while others pile things up?

This week children compare two simple shapes: a loop and a line. The shapes do a lot of teaching on their own. A leaf loop keeps cycling. A bottle line keeps moving forward until the material gets stuck somewhere else.

Kid Version in One Sentence

Nature often works in loops, but many human-made systems work in straight lines.

You'll Discover

• how to spot a loop shape and a straight-line shape
• why a missing return path can create a growing pile
• how one product can have a loop in one part and a straight line in another

Grown-up Note

• Lead with the shapes, not the word API.
• Keep the tone neutral. Straight-line systems are not foolish; they are often simpler and cheaper at first.
• Sessions are designed for about 20 minutes. Use the Short Path when you only have 15-20 minutes. Extra Challenge options can stretch closer to 25-30 minutes.

Common Kid Misconceptions

• Misconception: "Straight-line systems are stupid." Response: "They are often easier to build. The missing part is the return path."
• Misconception: "A loop means zero effort forever." Response: "Loops still need space, time, and good design."
• Misconception: "Nature never has leftovers." Response: "Nature usually has return paths that pick those leftovers up."

Week at a Glance

Session length	About 20 minutes
Prep time	About 10 minutes
Materials	Paper, markers, a leaf or plant picture, a bottle or package, Systems Log
Safety	Use clean sample objects only
Core vocabulary	loop, line, return path, pileup, fit
Older learner words	linear, circular, API, externality

Core Vocabulary

Word	Kid-friendly meaning
loop	A path that comes back around
line	A path that keeps going one way
return path	A way for material to come back into use
pileup	A buildup that keeps growing
fit	How well two systems work together

Short Path for Younger Learners

• Draw one nature loop and one human-made straight line.
• Do a simple spot-the-shape sort: loop or line?
• Talk about where the output goes in each case.
• Fill in the Systems Log with a side-by-side drawing.

Success looks like: the child can explain the difference between a loop system and a straight-line system.

Extra Challenge for Older Learners

• Find systems that are partly looped and partly straight-line.
• Discuss why a straight-line system can grow fast at first.
• Notice when another system ends up carrying the hidden cost.

Read-Aloud Opening

"Today we are looking for system shapes. Some systems behave like a circle and keep using the same materials again and again. Some behave like a line and keep taking new stuff in while sending used stuff somewhere else. Once you see the shape, you start noticing it everywhere."

Side-by-Side Comic Diagrams

Leaf loop: tree -> leaf -> soil -> tree

Bottle line: oil -> bottle -> use -> trash

Guided Session 1: Spot the Shape

Time: 20-25 minutes

Materials: paper, markers, leaf or plant picture, bottle or package

Setup: Put the leaf and bottle side by side.

Activity steps:

1. Draw the leaf loop together.
2. Draw the bottle line together.
3. Ask what happens to the output in each case.
4. Circle the place where the straight line gets stuck.

What to ask:

• Which system reuses its outputs?
• Which system needs more new input all the time?
• Where does the line keep going after use?

Draw It: Draw both diagrams side by side as a comic.

Talk About It:

• Which shape looks easier to keep going for a long time?
• Why might people build the straight-line version anyway?
• What is missing from the bottle line if we want it to work more like a loop?

What success looks like: The child can point to the missing return path in the straight-line example.

Guided Session 2: Find Shapes Around You

Time: 20-25 minutes

Materials: paper, pencil, Systems Log

Setup: Make two columns: Loop and Straight Line.

Activity steps:

1. Walk through home, school, library, or community examples.
2. Sort each example into loop or line.
3. Mark any hybrid examples that have both shapes.
4. Pick one straight-line system and sketch a missing return path.

Examples to use:

• compost bin
• library books
• lunch packaging
• refillable bottle
• single-use shampoo bottle

What to ask:

• Which system surprised you?
• Which one has the clearest return path?
• Which one would be easiest to redesign?

Draw It: Draw one straight-line system and add a better return arrow.

Talk About It:

• Can one product be a loop in one way and a line in another?
• What makes a return path hard to build?
• What would help people use the return path?

What success looks like: The child can redesign one straight line to include a return arrow.

Systems Log

Use this simple entry:

What I noticed:
What moved:
Where it came from:
Where it went:
My drawing:
One question I still have:

Helpful prompts for this week:

• What I noticed: "This system looked like a..."
• What moved: "The material moved from... to ..."
• Where it went: "The output ended up..."
• My drawing: leaf loop and bottle line

Systems Thinking Move

An environmental system is made of connected parts. When one part changes, other parts may change too. Some changes are quick. Some changes take time. Some effects are easy to see, and some are hidden.

Learner questions:

• What parts are in this system?
• What moves through the system?
• What changes over time?
• What causes what?
• What happens next?
• What part of the system could we change safely?

Who Is Affected?

Environmental problems and benefits are not always shared equally. Some people or places have easier access to refill systems, return paths, safe disposal, or repair options. Some do not.

• Who is affected when a system sends used materials somewhere else?
• Who benefits from a strong return path?
• Who might be missing from the conversation?
• What would make the system fairer, safer, or easier to use?

Engineer Corner

Older learners and facilitators can place the formal language here.

• Linear and circular are formal names for the two patterns.
• API can stay here as an optional analogy about how system parts connect.
• Externality can also stay here as the idea that someone else bears a hidden cost.