Week 17: Running the Experiment in the Real World
Try-It Week — Capstone Week 3
You picked one repeat problem. You made a plan. This week you try it in real life.
This is Try-It Week.
You use your plan for seven days and notice what happens. Some parts may work. Some parts may not. That is normal.
The goal is not perfection. The goal is honest information you can use next week.
This week's idea in kid language: "Try the plan. Notice what happens. Learn from it."
- This is the live test. Support tracking, not perfect performance.
- Lead with Try-It Week. Offer deployment, data collection, and real-world test as toolbox phrases.
- The plan will probably not work perfectly. That is expected.
- Track honestly, including partial tries, forgotten moments, and rough days.
Week at a Glance
| Prep time | ~10 minutes |
| Materials | Telemetry Log, the protocol document from Week 16, the baseline data from Week 15, a tracking sheet |
| Key vocabulary | Try-It Week, data collection, observation, real-world test |
| Difficulty | Moderate |
Facilitator Preparation
- Have the protocol document from Week 16 visible.
- Have the baseline data from Week 15's tracker accessible.
- Plan to do a mid-week check-in (Session 2) — ideally midway through the deployment week.
- Decide together with the student whether anyone else needs to know about the protocol. Often, the protocol is fully private (it describes the student's actions only). Sometimes — for example, a protocol with a sibling or parent — it can help to mention it ("I'm trying something new this week; I might say less than usual when you walk into my room around dinner"). Either is fine.
Be a curious lab partner, not a judge. Ask questions like "What happened on Tuesday?" instead of "Why didn't you do it right?"
If the learner gets discouraged, remind them that a partial try is still useful information.
Pause the protocol and get adult support if the test starts creating distress, conflict escalation, pressure, secrecy, or any safety concern.
The point is to gather honest data from a safe experiment. Students should not push through harm just to complete the tracker.
For Younger Learners (Ages 8–9)
Simplest version of the concept: "This week we try the plan and see what happens."
What to shorten or skip:
- Keep the check-in short.
- Use a very simple tracker.
Adapting the activities:
- Use a sticker chart or tally marks.
- Keep the plan card visible.
Journal alternative: yes/no plus a feeling face each day.
What success looks like: The student tries the plan at least once and tracks it.
Guided Session 1
Try It and Track It
Learning Goal
By the end of this session, the student can:
- describe what honest tracking looks like
- set up a tracking sheet for the week
- understand that helpful, mixed, and unhelpful results are all useful
Activities
1. The Daily Tracker
Set up a daily tracking sheet for the week. Use the same kind of structure as the Week 15 baseline so you can compare.
| Day | Trigger happened? | Did I run the protocol? | What happened | Severity 1–10 | Notes |
|---|---|---|---|---|---|
| Mon | |||||
| Tue | |||||
| Wed | |||||
| Thu | |||||
| Fri | |||||
| Sat | |||||
| Sun |
The point is honesty, not success. If the trigger happened and you forgot the plan, write that. If you tried the plan and it only partly helped, write that.
2. Three Honest Tracking Rules
Before the week starts, commit to three rules:
RULE #1: Track every time the trigger happens — whether or not you used the plan. Skipping the "I forgot" entries is exactly how you lose the lesson.
RULE #2: Track what actually happened, not what you hoped would happen. "I lost my temper anyway" is honest data. "It went pretty well I guess" is not data.
RULE #3: Track the same day, not from memory at the end of the week. Memory smooths things out and loses detail. Track within a few hours.
3. One More Walkthrough
Walk through the protocol one more time. Read it aloud. Visualize the trigger happening and the student running the protocol.
Then start. Try-It Week begins today.
Guided Session 2
Midweek Check-In
Learning Goal
By the end of this session, the student can:
- review the first half of the week without judgment
- identify any obvious small fixes needed midweek
- continue tracking through the rest of the week
This session happens mid-week — ideally Wednesday or Thursday. Plan it that way.
Activities
1. The Data Review
Look at the tracking sheet so far together. Ask:
- Did the trigger happen as often as expected? More? Less?
- When the trigger happened, what did you do?
- What surprised you about how the protocol played out in real life?
Do not evaluate. Just look.
2. Small Midweek Fixes
If something is clearly broken — for example, the trigger never actually happens, or the protocol's first step is impossible in real conditions — it's okay to make a small patch mid-week.
Examples of legitimate mid-week patches:
- "I realized the trigger I picked doesn't actually happen — the real trigger is 30 minutes earlier."
- "The first step (long exhale) feels weird to do in front of others. I'm switching it to 'count to 5 silently.'"
- "I forgot the protocol exists. I'm putting a copy on the inside of my bedroom door."
What is NOT a good midweek fix:
- "It's not working, so I am throwing the whole thing away." (No. Keep collecting data. The bigger redesign happens next week.)
- "I want to change the friction point." (No — stay with the project. Even imperfect data is the lesson.)
Update the plan card if you patched it. Keep tracking.
3. Reset the Tone
If the protocol isn't working as well as the student hoped, this is the moment to remind them:
"The point of this week is to find out what happens when you try the plan. Even 'that did not work the way I hoped' is useful information for next week."
Keep going.
The deployment is fully solo — you run YOUR protocol in YOUR life. No partner required. (The protocol may involve other people, but the protocol itself is yours.)
Age-Banded Emotional and Social Learning Goals
- Ages 8-9: Track the plan with stickers, tallies, or feeling faces and keep the reflection short.
- Ages 10-12: Compare what happened, what helped, and what needs revision using the full tracker.
- Ages 11-13 optional extension: Add guided analysis of audience, evidence, digital context, or accessibility if the project will be shared beyond the facilitator.
Independent Practice
Goal
Complete a full Try-It Week with honest tracking so you have something real to look back on next week.
Activities
1. The Full-Week Tracker
Continue tracking every day. The data you collect this week is the input for next week's look-back. Better data means a smarter version 2.0.
If the trigger happens multiple times in a day, log each occurrence separately.
Minimum viable version: daily yes/no plus a feeling face or color.
2. The Notes Capture
In addition to the tracker, jot down any observations that don't fit neatly in the tracker:
- "It works better on days I slept well."
- "It works worse when I have a lot of homework."
- "The protocol is way easier with my mom than with my dad."
- "I noticed the trigger happens 3x on Tuesdays — twice as often as other days."
These observations will help a lot next week. Capture them when you notice them.
Telemetry Log
Add a daily entry every day this week:
Day: ___
Trigger occurred? yes / no
Number of times: ___
Did I run the protocol? yes / partial / no
What happened: ___
Severity (1–10): ___
Note about the day: ___ (sleep, energy, anything else going on)
End of week (Sunday) summary:
- Total triggers this week: ___
- Total times I ran the plan fully: ___
- Times I ran it partially: ___
- Times I forgot or skipped: ___
- Average severity compared to baseline: ___
- One unexpected thing I learned: ___
Sentence starters for younger learners:
- "Today the thing happened. I ___."
- "It went ___ today."
Low-writing options: stickers, tallies, colors, or one-word notes.
Reflection Questions
- Was there a moment this week when the plan surprised you?
- What is the most interesting thing you noticed?
- If you had not made the plan, how do you think the week would have gone?
Check for Understanding
After this week, check whether the learner can:
- Show the tracker: "Show me your tracker from the week."
- Describe what they observed: "What is the most interesting thing you noticed this week?"
- Stay calm about rough moments: "If the plan did not work on Tuesday, what happened?"
If the learner can do at least 2 of these, they are ready for the final week.
Pause and Notice
After the week, ask:
"Did trying the plan feel different from just telling yourself to do better?"
That difference matters. A plan gives the learner something concrete to try instead of just more pressure.
This week's takeaway: Honest information helps more than pretending everything went fine.
Spiral Review
- From Week 1: "Your tracker this week is your Telemetry Log working at full capacity. This is what 17 weeks of practice was building toward."
- From Week 4: "The intervention window — the gap between an early warning and a full hijack — is the place your protocol lives. The more clearly you can read your early warnings, the more often the protocol can fire on time."
- From Week 14: "If the protocol involves another person and didn't go well, run the three diagnostic questions on them too. What might they have been operating under that you didn't see?"
Use a sticker chart or faces. That is enough data for this age.
Have the older learner make a simple chart comparing baseline week and Try-It Week.
Related Tools
- Use the Try-It Week Tracker in Student Tools and Printables for a clean daily log.
- Use the Facilitator Safety Guide if the plan creates pressure, secrecy, or a problem that is bigger than the project.
Try-It Week, deployment (toolbox phrase), data collection, real-world test