Truckee Roundhouse Summer Maker Camp

The problem

A five-day maker camp for ages 9–12 can easily collapse into a single guided kit. That format is tidy to staff, but it skips the actual engineering work: defining a problem, testing under the same constraints, and iterating when the first idea fails. I wanted 10 campers to practice that loop for real, with motors, gearing, and a parts bin that did not reset overnight.

Approach

I structured the week as a new design-and-build challenge each day: cars, boats, gondolas, launchers, and solar-powered builds. Campers reused and built on the same parts bin from the day before. That constraint forced real problem-solving: kids had to diagnose why a gearing or motor setup wasn't working and adapt on the fly, rather than following a fixed set of instructions. Each day followed the same rhythm: setup, a build-test-iterate loop where campers trialed their designs, adjusted, and retested repeatedly, then a share-out and clean-up. A daily winner earned the privilege of picking the color the group wore the next day, which gave the week a light, ongoing thread of motivation. I designed the program against California's NGSS Engineering Design standards (MS-ETS1, grades 6–8) so the daily structure mapped to how schools actually frame engineering learning.

Process

1. 1

   Five challenges, not one kit

   Rather than a single guided kit spanning the week, I wrote a new design-and-build prompt for each day: cars, boats, gondolas, launchers, and solar-powered builds. Skills and creative ownership compounded day over day instead of locking campers into one prescribed outcome.

2. 2

   Carry the parts bin forward

   Campers reused yesterday's parts for today's build. The constraint forced fast prototyping and creative reuse over chasing one perfect object, and it made diagnosis unavoidable when a motor, gear train, or power setup from the day before did not match the new challenge.

3. 3

   Hold a consistent daily rhythm

   Every session followed the same arc: setup, a build-test-iterate loop, then share-out and clean-up. Campers trialed, adjusted, and retested repeatedly within a single day, not as separate sequential steps spread across the week.

4. 4

   Map the week to NGSS Engineering Design

   I designed against California's NGSS MS-ETS1 standards (grades 6–8). Define the problem: each day opened with a clear goal and constraints (materials on hand, time, size). Evaluate solutions: structured heats and trials compared builds under the same test conditions. Analyze and improve: share-outs surfaced what worked on other teams' builds and fed the next day's design. Iterate toward an optimal design: the in-session loop made iteration the default, not an extra.

5. 5

   Keep motivation light and shared

   A daily winner earned the fun privilege of picking the color the group wore the next day. Candy worked well as an end-of-day pickup routine and as an in-the-moment reward. Neither replaced the engineering work; they kept energy up across five intense days.

6. 6

   Facilitate a group of 10

   10 campers was the right size to actively manage and coach through shifting social dynamics. Bringing in other instructors to support campers improved group dynamics. Some campers were more willing to advocate for support than others, so balancing time and attention so everyone got help was an ongoing challenge.

7. 7

   Stock for friction, not a perfect kit

   Motors, gearing, and power did not always match, and some of the best learning of the week came from that friction. Stocking small hardware (axles, batteries, connectors) ahead of time, and building in slack for gearing and motor mismatches, kept momentum up when a design needed a new part instead of a new plan.

8. 8

   What this demonstrated

   Rapid program design: a full week's curriculum from scratch, grounded in real engineering-education standards, sequenced so skills compounded day over day. Hands-on technical instruction: teaching ages 9–12 fabrication and engineering skills (motors, gearing, basic circuits, tool use) in an age-appropriate, safety-first way. Group facilitation and adaptability: managing dynamics across 10 kids and balancing support so everyone got help without anyone coasting. Iteration under real constraints: running a genuine build-test-iterate loop with kids, not just talking about it.

9. 9

   Questions I'm still exploring

   How would this structure change as a semester-long program instead of a single week? What would it look like with more or fewer students? What's the right balance of adult support versus self-discovery for learning? Could this work as a semester-long project instead of 1–2 day builds?

Outcome

Ten campers each designed, built, and tested five different projects. The week showed that a camp can run a genuine engineering loop with kids: diagnose mismatches, reuse yesterday's parts, and iterate inside a single session rather than treating those as separate sequential steps.

Stack & services

• • Program and curriculum design
• • Hands-on STEM instruction
• • Group facilitation
• • Safety-first shop teaching
• • NGSS standards mapping