Skip to content

Reflection 4

A facilitation guide for the final team debrief. These questions are designed to spark discussion — not every question needs to be covered. Pick the ones that resonate with what you observed during the run and across the full journey.

What You Shipped

  • Your Field Guide is live. What was the moment like when you opened that URL for the first time outside your workspace?
  • What's the feature you're most proud of in the final product? Is it something from Run 1, something you added along the way, or something you built in this final sprint?
  • If a backcountry skier opened your Field Guide right now before heading into the Wasatch, what would they get out of it? What's still missing?

What You Practiced

  • Lift 4 introduced the idea that deployment is "one prompt away." Did it feel that simple in practice? What surprised you about the process of going live?
  • Think about the risks Lift 4 raised — the two-week cliff, the validation gap, the importance of authoritative data sources. Did any of those feel real during this run? Did you catch something that "looked done" but wasn't quite right?
  • Across all four lifts, you learned prompting (Lift 1), file access (Lift 2), context (Lift 3), and deployment (Lift 4). Which of those skills made the biggest difference in what you were able to build?

The Full Journey

  • Think about your first prompt in Run 1 — the very first thing you asked AI to build. Compare that to what's deployed right now. What changed, and what changed in you?
  • Was there a moment across the two days where something clicked — where the way you work with AI shifted from awkward to natural?

What Comes Next

  • Lift 4 made the point that AI lets you produce faster, and the choice is whether to invest that speed into more output or more understanding. Looking back at today, which did your team lean toward? Which would you lean toward on your next project?
  • After today, what's one thing you might build with AI? A tool for your job? Something for your family or community? A side project that's been rattling around in your head?
  • One way to think about what you learned today: your role isn't just "person who tells AI what to build." It's more like a gardener — you set up the environment (context files, rules, user stories, verification habits) and AI grows the software inside those constraints. What would your "garden" look like for your next project?