Skip to main content

Week 18: Patch, Present, Reflect

Iterate and Share What You Learned

The loop is complete.

You had a problem. You analyzed it. You designed a protocol. You tested it. You collected data. Now you patch what didn't work, present what you discovered, and reflect on how 18 weeks of decision literacy has changed the way you think.

This cycle — Identify → Design → Test → Iterate — never truly ends. It's how scientists discover, how engineers build, and how the best decision-makers get better over time.

Facilitator Snapshot
  • This is the finale. Make it feel like a celebration, not a final exam.
  • The presentation can be as simple as a 3-minute conversation with a family member or as elaborate as a poster board.
  • The final journal reflection is deeply personal. Give the student time and space for it.
  • Consider saving the Decision Journal as a keepsake. It's a remarkable record of intellectual growth.
Quick Navigation

Week at a Glance​

Prep time~10 minutes
MaterialsAll tracking data from Weeks 15–17, Decision Journal, presentation materials (paper, poster board, or slides)
Key vocabularyiteration, patch notes, presentation, reflection
DifficultyModerate

Facilitator Preparation​

Before You Begin
  • Have all tracking data from Weeks 15-17 ready
  • Prepare presentation materials (poster board, paper, or digital slides — whatever fits)
  • Have the student's Decision Journal available for the final reflection
  • Consider inviting family members or friends for the showcase in Session 2
  • Prepare a small "graduation" moment (certificate, sticker, special treat, etc.)
Facilitation Mindset

Focus on the process, not whether the protocol worked perfectly. The student identified a real problem, tested a system, collected data, and iterated — that alone is worth celebrating.

For Younger Learners (Ages 8–9)​

Adapting This Week

Simplest version of the concept: "You get to share what you discovered — like a real scientist presenting their findings!"

What to shorten or skip:

  • Skip the formal presentation structure. This should feel like show-and-tell, not a TED talk.
  • Skip self-assessment rubrics. Use simple reflection questions instead.
  • Keep the celebration proportionally big — this is a real accomplishment.
  • Keep sessions to 20 minutes.

Adapting the presentation:

  • The presentation can be as simple as: "My question was ___. I tried ___. I found out ___. The coolest thing I learned was ___."
  • Add one simple patch step: "Next time, I would change ___." This keeps the iteration part of the project visible.
  • Props are encouraged: hold up the tracking chart, show the Decision Poster from Week 15, act out the experiment.
  • Drawing and oral presentation count fully. No written report required.
  • If the learner is shy about presenting, they can present just to the facilitator, a family member, or even a stuffed animal — it's the structured reflection that matters.
  • The facilitator should be an enthusiastic audience.

Journal alternative: "The most important thing I learned in this whole course is ___. One thing I'll do differently now when I make decisions is ___." Spoken is fine.

What success looks like: The learner shares their experiment results in any format and can name at least one decision-making skill they'll keep using.

For Ages 10–12
  • Full structured presentation with introduction, hypothesis, method, results, and conclusion.
  • Written or digital self-assessment reflecting on their growth over the 18 weeks.
  • Peer feedback (if multiple students) or facilitator Q&A.
  • Discuss: "How has your thinking about decisions changed since Week 1?"

Guided Session 1​

The Patch​

Learning Goal​

By the end of this session, the student can:

  • analyze their full experiment data and draw conclusions
  • write specific "patch notes" for protocol improvements
  • explain what they would do differently in version 2.0

Activities​

1. The Full Data Review

Lay out all the data from the experiment:

  • Baseline (before the protocol)
  • Week 16 tracking
  • Week 17 tracking

Answer these questions together:

QuestionAnswer
How often did the friction point happen at baseline?
How often did it happen during the experiment?
Did things improve, stay the same, or get worse?
On days you followed the protocol, what was the average result?
On days you didn't follow it, what happened?
What was the biggest surprise in the data?

Create a simple before/after comparison:

BEFORE (Week 15 Baseline):
  Friction point happened: ___ times in ___ days
  Average severity: ___/10

AFTER (Weeks 16-17):
  Friction point happened: ___ times in ___ days  
  Average severity: ___/10
  Protocol followed: ___% of the time

2. Write the Patch Notes

Software developers write "patch notes" when they update their programs. We'll do the same:

🛠️ DECISION PROTOCOL — PATCH NOTES v2.0

What's New:
  - [Change based on data]
  - [Change based on data]

Bug Fixes:
  - [Something that didn't work, and how you fixed it]
  - [Something that didn't work, and how you fixed it]

Known Issues:
  - [Something you still haven't solved]
  - [Something that needs more testing]

Removed:
  - [Anything from v1.0 that turned out to be unnecessary]

Examples:

v2.0 Patch Notes for "I'm always late for school":

  • NEW: Added a 5-minute "buffer alarm" that goes off before the main alarm
  • BUG FIX: Moved the outfit decision to Sunday evening (picking clothes each morning was too slow)
  • BUG FIX: Added a hook by the door for shoes (the "shoes by the door" rule kept failing because there was no hook)
  • KNOWN ISSUE: Still struggling on rainy days when I need extra gear
  • REMOVED: The "pack backpack at 8pm" rule — turns out packing right after homework works better

3. The Process vs. Outcome Check

Return to the foundational idea from Week 2:

"Let's evaluate your project on PROCESS, not just outcome."

Process QualityYes/No
Did I identify a real, recurring problem?
Did I dig into the root cause (not just the surface)?
Did I design a specific, testable protocol?
Did I collect honest data?
Did I analyze the data and draw conclusions?
Did I iterate based on evidence?

"If you checked most of these boxes, your process was excellent — regardless of whether the protocol 'solved' the problem perfectly. Remember: a good process with a bad outcome (Week 2) is still a good process."

Guided Session 2​

The Showcase​

Learning Goal​

By the end of this session, the student can:

  • present their project clearly to an audience
  • explain their reasoning, data, and conclusions
  • answer questions about their process and findings

Activities​

1. Prepare the Presentation

The student prepares a brief presentation (3-5 minutes) covering:

  1. The Problem: What was your friction point? Why did it matter to you?
  2. The Root Cause: What did the 5 Whys reveal?
  3. The Protocol: What was your plan? (Trigger → Default → Check)
  4. The Data: What happened when you tested it? (Show the numbers!)
  5. The Patch: What did you change for v2.0?
  6. The Lesson: What would you tell someone else facing a similar problem?
  7. The Toolkit Connection: Which concepts from the course showed up in your project? (e.g., Was a bias driving the friction point? Did you use EV thinking? Was it a two-way or one-way door? Did you apply the 100 Times Test or Probability Glasses?)

Format can be:

  • A poster board
  • A few sheets of paper with drawings
  • A verbal walkthrough with the data sheet
  • A digital slide deck (if the student prefers)

Simplified presentation option (younger learners): The learner answers 4 questions with the facilitator's help: (1) "What was my question?" (2) "What did I do?" (3) "What happened?" (4) "What did I learn?" They can draw, speak, or act it out. Take a photo of their work to mark the occasion.

2. Present!

The student presents to:

  • The caregiver/teacher
  • Family members (invited for this session)
  • Siblings or friends
  • Even just a stuffed animal audience is fine!

After the presentation, the audience asks questions:

  • "What was the hardest part?"
  • "What surprised you the most?"
  • "What would you do differently if you started over?"
  • "Do you think you'll keep using your protocol?"

3. The Celebration

This is a genuine accomplishment. Celebrate it:

"Over 18 weeks, you learned about probability, cognitive biases, expected value, game theory, and systems thinking. You applied those tools to a real problem in your life. You designed an experiment, collected data, and iterated. You now understand decision-making better than most adults. That is remarkable."

Optional: Create a simple "certificate of completion" or award.

Independent Practice​

Goal​

Write the final Decision Journal reflection — a letter to yourself about what you've learned.

Activities​

1. The Final Journal Entry

This is the most important journal entry of the course. Take your time with it.

Answer these questions in your Decision Journal:

  1. The Big Takeaway: If you could only remember ONE thing from this entire course, what would it be?

  2. The Most Surprising Lesson: What did you learn that genuinely surprised you about how your brain works?

  3. Your Biggest Brain Bug: Which cognitive bias or shortcut do you think affects you the most in daily life?

  4. The Tool You'll Keep Using: Which decision-making tool or framework do you think you'll actually use going forward?

  5. The Change: How has your thinking about decisions changed since Week 1? Be specific.

  6. Advice to Your Past Self: If you could go back to Week 1 and give yourself one piece of advice, what would it be?

2. Then vs. Now

Open your Decision Journal to the very first entry from Week 1.

Read it. Sit with it for a moment.

Now write:

"When I started this course, I thought a good decision was ________________________." "Now I think a good decision is ________________________."

3. The Decision Literacy Pledge

Write a short personal commitment:

"Going forward, I will ________________________."

Examples:

  • "...ask 'What would happen if I did this 100 times?' before big choices."
  • "...write down my reasoning before seeing the result."
  • "...check for brain shortcuts before making snap judgments."
  • "...look for win-win solutions before assuming it's zero-sum."
  • "...remember that a good process matters more than a lucky outcome."

Decision Journal​

This IS the journal entry for this week. Make it count.

Reflection Questions​

  • If you taught this course to a friend, which week would you start with? Why?
  • Do you think you'll keep using your Decision Journal? Why or why not?
  • What's the next friction point you'd like to optimize?
  • In 5 years, which lesson from this course do you think will matter the most?

Quick Mastery Check​

This is the final check for the entire curriculum. After the presentation and reflections, confirm:

  1. Core concept retention: "Name 3 big ideas from this course." (Looking for any 3 — biases, expected value, reversibility, ripple effects, signal vs. noise, game theory, etc.)
  2. Personal framework: "What's your process for making a tough decision now?" (Looking for: a multi-step approach that draws on course concepts — even a simple 3-step verbal checklist counts.)
  3. Transfer to life: "Can you tell me about a real decision you made differently because of something you learned here?" (Looking for: ANY real example, no matter how small — "I stopped to think about who my choice affected" or "I checked if I was making a sunk cost mistake.")
  4. Growth mindset: "What's something you used to think about decisions that you've changed your mind about?" (Looking for: evidence of intellectual growth — "I used to think gut feelings were bad" or "I didn't know I had biases.")

If the learner can show concept retention, a personal framework, one real-world application, and self-awareness about growth — they've completed the course successfully. Celebrate.

Pause and Notice​

What Matters Here

This is the final Pause and Notice for the course. Make it count.

"Think back to Week 1 — when we first talked about all the decisions you make in a day. How do you feel now compared to then? More confident? More thoughtful? More aware?"

"You've learned tools that most adults don't know. Expected value, cognitive biases, game theory, signal vs. noise — these are powerful ideas. But the most important thing you've learned isn't any single tool. It's the HABIT of pausing before a decision and thinking: 'How should I approach this?'"

Course takeaway: You are a decision-maker. Every day, dozens of times a day. And now you have a toolkit to make those decisions more carefully, more wisely, and more aligned with what you actually care about. That's worth celebrating.

Spiral Review​

Looking Back at the Whole Course

Use this as a facilitated conversation or a written reflection:

Phase 1 — Probability & The Physics of Choice (Weeks 1–4): "What are the building blocks? Decisions are everywhere. Outcomes vs. luck. Prediction and calibration. Hindsight bias."

Phase 2 — Debugging the Hardware (Weeks 5–8): "Your brain takes shortcuts. Some help, some don't. Anchoring, loss aversion, sunk costs, framing, and bias awareness."

Phase 3 — Data & Signal Processing (Weeks 9–11): "Expected value, signal vs. noise, and reversible vs. irreversible choices help you think more clearly under uncertainty."

Phase 4 — Game Theory & Social Systems (Weeks 12–14): "Your choices create ripples. Cooperation, trust, and shared systems change what the best move looks like."

Phase 5 — The Optimization Project (Weeks 15–18): "Build your own framework. Design an experiment. Analyze the data. Patch the plan. Present what you learned."

Ask: "Which phase was your favorite? Which idea surprised you the most? Which tool will you use the most going forward?"

Congratulations! 🎓

You've completed the Decision Literacy for Kids curriculum. You now have five mental models most adults never learn:

  • Probabilistic thinking — the world is uncertain, and that's okay
  • Bias awareness — your brain has defaults, and you can override them
  • Opportunity cost and trade-offs — every "yes" is also a "no"
  • Diminishing returns of information — know when "good enough" is good enough
  • Iterative improvement — design, test, measure, improve, repeat

Plus powerful tools like expected value, game theory, the 100 Times Test, and your Probability Glasses to put them into practice.

Keep your Decision Journal. Keep asking good questions. Keep debugging your brain. The world needs better decision-makers, and now you're one of them.