Learning Goals
Students will be able to investigate greenhouse crop needs using direct observations, measurements, and community food preferences to define an evidence-based growing plan.
Students will be able to model photosynthesis and cellular respiration in the greenhouse system to explain how light energy becomes stored chemical energy and supports plant growth.
Students will be able to analyze stakeholder feedback from staff, families, and community partners to synthesize user needs into a clear problem statement for greenhouse products and distribution.
Students will be able to design and justify crop, packaging, and distribution choices using criteria and trade-offs related to cost, safety, reliability, aesthetics, and environmental impact.
Students will be able to prototype greenhouse products and communication materials that respond to user needs and can be tested with authentic audiences.
Students will be able to evaluate survey, yield, and sales data to refine planting, harvesting, packaging, and distribution decisions across greenhouse production cycles.
Students will be able to communicate greenhouse design decisions to school and community audiences using labels, flyers, brochures, and presentations that explain how user evidence shaped the final solution.
Products
User Interview Portfolio and Greenhouse Product Prototype
Each student produces a research portfolio with interview notes, observation evidence, and a synthesized user-need statement, then creates one individual low-fidelity prototype for a greenhouse product or communication material. The prototype must show how firsthand evidence shaped design decisions and what would need testing next.
Harvest to Table Expo Problem Statement and Tested Greenhouse Solution
Each team develops a shared, evidence-based problem statement and a higher-fidelity greenhouse product or service solution with packaging, distribution, and presentation materials suitable for authentic stakeholder review. The final expo presentation explains how individual research informed the team solution and how testing led to revisions.
No rubric has been generated yet.