STEAM Camps Review

Suggestions

1. Refine and polish curriculum completely to about 16 one hour lessons with detaled, full curriculum.
2. Before/During/After Unit:
   1. Before: go over all the lessons, so you're practicing during Camp, not seeing material for the first time.
   2. During: Focus on collaborative teaching to make life easy for instructors, all 12 in same or near time zone. Or otherwise work out the collaborative teaching aspect.
   3. After: Incentive Challenge, and 1 hour Design Sprint every Saturday, with 1 hour prep beforehand.
3. Do only 9 day events; other programs could exist, but that is not the STEAM Camp
4. Define clear Product to be developed within the 5 Dev Days, with 144+ people
5. Secure enough Instructors so each prepares a 1 hour lesson. Rationale: the curriculum needs to be refined, and is a full time effort for ~4 people until the curriculum is done. Part time development with about 16 instructors would solve this.
6. Promise clarity on the next event: organizing 12x12 with $72k theoretical budget
   1. $80 COCA for $12k advertising costs
   2. $12k at $4k/month to an Event Planner
   3. $25k allocated to an Incentive Challenge for Product
   4. $23k allocated to OSE infrastructure development (physical and virtual) to get all requisite tools in place.
      1. Registration is posted 10 weeks before the event. Early bird at T-2 months. If 12+ people are not registered 6 weeks prior to event (4 weeks into the publicity cycle), then COCA is quadrupled until people register. Clear tracking metrics are implemented for STEAM Camps.
7. Divide up 16 lessons between future participants for
8. New rules: camp does not run if there are not 12 people signed up for each location. This means marketing must be vetted and effective. COCA+ plan is activated