Week 17: Test Your Plan Like a Friendly Troublemaker
Unit 5: The Redesign Project
This Week's Big Question
What could go wrong with your plan, and how could you make it stronger?
This week teaches critique without meanness. Children start by naming one strength in the plan, then look for weak spots, surprise situations, and people who may be affected by the redesign.
Kid Version in One Sentence
Strong plans get better when you test what could go wrong before you try them.
You'll Discover
- how to find weak spots in a plan without attacking the person who made it
- how to name simple fixes or warnings
- how to notice who else might be affected by the redesign
- Keep emotional safety explicit: critique the plan, not the person.
- Younger learners only need 2-3 possible problems, not a long list.
- 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: "If someone finds a problem, the plan is bad." Response: "Finding problems is how plans improve."
- Misconception: "Testing means trying to make a classmate fail." Response: "We are helping the plan, not hurting the person."
- Misconception: "One fix solves everything." Response: "Most plans still have tricky parts even after they improve."
Week at a Glance
| Session length | About 20 minutes |
| Prep time | About 10 minutes |
| Materials | Week 16 plan card, paper, pencil, Systems Log |
| Safety | Keep critique respectful and specific |
| Core vocabulary | problem, reason, fix, warning, person affected |
| Older learner words | failure mode, edge case, stakeholder, known limitation, second-order effect |
Core Vocabulary
| Word | Kid-friendly meaning |
|---|---|
| problem | Something that could go wrong |
| reason | Why that problem might happen |
| fix | A change that could help |
| warning | Something people should know ahead of time |
| person affected | Someone the plan changes for |
Short Path for Younger Learners
- Start with one plan strength.
- Find 2-3 possible problems.
- Fill in the simple problem table.
- End with one fix or warning for each problem.
Success looks like: the child can improve the plan by naming a few realistic weak spots.
Extra Challenge for Older Learners
- Add surprise situations and second effects.
- Notice people who may like, dislike, or be burdened by the plan.
- Revise the plan card after the stress test.
Read-Aloud Opening
"Today we are testing your plan like a friendly troublemaker. That means we are going to help the plan by looking for weak spots before they become real problems. We are not judging you. We are helping version 2.0 get smarter."
Guided Session 1: Start With a Strength, Then Test It
Time: 20-25 minutes
Materials: plan card, paper, pencil
Setup: Write this sentence at the top of the page: One thing that is strong about my plan is...
Activity steps:
- Name one strong feature.
- Ask what could go wrong.
- Ask why it might happen.
- Add a fix or warning.
Use this simple table:
| Problem | Why it might happen | Fix or warning |
|---|---|---|
What to ask:
- What could go wrong?
- Why might that happen?
- What would make it easier?
- What is one thing you forgot before today?
Draw It: Draw the plan and add sticky-note style warnings to tricky spots.
Talk About It:
- Which problem seems most likely?
- Which one is easiest to fix?
- Which one might need a warning instead of a full redesign?
What success looks like: The child can name a few realistic problems and match them with fixes or warnings.
Guided Session 2: Who Is Affected?
Time: 20-25 minutes
Materials: paper, markers, Systems Log
Setup: Write a short list of people the plan touches.
Activity steps:
- Name the people affected.
- Ask who might like the plan and who might find it annoying, costly, or confusing.
- Revise one part of the plan to make it easier.
- Add one known tricky part that is still not fully solved.
What to ask:
- Who has to help this plan work?
- Who might not like it?
- What would make it easier for them?
- What part is still tricky even after changes?
Draw It: Draw the plan with speech bubbles from two people affected by it.
Talk About It:
- Why is it useful to hear objections early?
- What is the difference between a plan flaw and a person flaw?
- How can version 2.0 improve without becoming too complicated?
What success looks like: The child can revise the plan after thinking about people affected and tricky parts.
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: "One weak spot in my plan was..."
- What moved: "The problem would happen when..."
- Where it went: "My fix would change the path by..."
- My drawing: plan plus warnings
Environmental Checkpoint
This week is a good time to pause before presenting.
- What claim am I making?
- What evidence, observations, data, or examples support it?
- What might be missing or left out?
- Who or what is affected?
- What tradeoff or unintended consequence still needs to be named?
- What should I check before I trust, share, repeat, or act on this idea?
Ethical Communication Note
Strong projects do not need exaggeration, blame, shame, or fear. Learners can say:
- "I do not know yet."
- "This part still needs checking."
- "One limitation is ___."
- "One thing I would revise is ___."
Engineer Corner
Older learners and facilitators can keep the formal stress-test language here.
- Failure mode, edge case, stakeholder, and second-order effect belong here.
- The kid-facing version stays plain: what could go wrong, who is affected, and what change would help.