Closing the Loop

This is where the project closes the loop — the Reflect stage of Session 1's design cycle, run for real, at full scale, over an entire quarter.

A team that missed targets on Field Test Day but can clearly diagnose why demonstrates the same competency as a team that hit all three. Misses are valuable material here, not something to minimize.

A team that hit all three targets doesn't get to skip real reflection either — your model's actual limitations are still worth surfacing, win or lose.

Build

Prepare a short presentation or written defense — check with your instructor which format — covering all four of these:

1. Your Independent Variable

Which one you chose, and why — reference your actual Session 15–16 reasoning, not a retroactive justification that sounds better now.

2. What Your Data Showed

Summarize your calibration model from Sessions 21–23, and how it changed after Sessions 24–25's iteration.

3. Your Field Test Day Performance

State your results honestly, misses included. For any miss, give a specific diagnosis — a model limitation at the edge of your usable range, field conditions, inconsistent execution — not a vague "we were off."

4. Your Notebook's Evolution

Submit your full notebook, showing the model's evolution from your first Session 15–16 entry through today — not just a polished final summary.

Checkpoint

Before you present or submit, confirm:

• Your IV explanation references your actual original reasoning, not a rewritten version
• Every miss (if any) has a specific, named cause — not a vague explanation
• Your notebook is complete from Sessions 15–16 through today, not just a final-state summary

Reflection

Answer the following questions before submitting your work.

1. Looking back across all 27 sessions, which single skill do you think mattered most to your team's actual field test result — measurement, charting, safety discipline, iteration, or something else?
2. If you ran this entire project again from Session 15, what's the one thing you'd do differently, knowing what you know now?
3. This is the last reflection of the course. What's one habit from this class — documentation, testing before trusting, targeted iteration, anything — you think you'll actually keep using outside of it?

Submit

Submit your presentation or written defense, and your complete design notebook.

Project Complete