Skip to main content

Observe What Happened

Short summary: After you try something, look carefully at what happened. Results are information.

Big idea​

"It worked" and "it failed" are just starting points, not the whole story. Looking closely at what changed, what stayed the same, and what surprised you turns any result into something you can learn from.

Why it matters​

People often glance at a result, decide "good" or "bad," and miss the useful part. A result can teach you a lot even when it is not the result you wanted. Careful observation is what makes the next try better.

Kid-friendly explanation​

Think of a paper airplane that nose-dives. "It failed" tells you nothing useful. But "it dropped fast and tilted left" tells you to fix the nose weight and the left wing. The crash was full of information — you just had to look.

Tool: observation questions​

After a try, ask:

  • What did I try?
  • What happened?
  • What changed?
  • What stayed the same?
  • What surprised me?
  • What did I learn?

Activity: Test Report​

Run a small test at home or in class, then write a short test report using the questions above. Pick one:

  • a paper airplane design
  • a memory strategy for a spelling list
  • a plant watering schedule
  • a code or debugging step
  • an organization method for your stuff

Discussion questions​

  • Why is "it worked" or "it failed" not enough information?
  • What can a result that "failed" still teach you?
  • What is the difference between a result you wanted and a result you learned from?
  • Why is it useful to notice what surprised you?

Try it this week​

After you try to fix something, write or say one thing that changed and one thing that surprised you.

Adult note​

Avoid "See, I told you so." That turns data into shame and teaches kids to hide results. Keep results neutral: "Interesting — what did that tell us?" Observation works best when it feels safe.