Palo Alto Unified School District in Palo Alto, California took a straightforward approach to knowing what students wanted: they asked, collected the answers in suggestion boxes, and tested new recipes at structured sampling events. That input drove a steady move toward scratch preparation, built around California-grown ingredients.
Listening channels
Physical suggestion boxes in cafeterias captured day-to-day feedback without needing surveys or platforms students wouldn't use. Student food sampling events added a more structured layer: students tried new recipes under development and voted on what should make it to the menu. Together, these gave the district unfiltered input without overengineering it.
Local sourcing as a lever
California's growing season and dense agricultural network made local sourcing viable year-round for many categories. The district built relationships with producers and designed menus around what was in season, rather than forcing out-of-season items through the supply chain.
Chef-led annual recipe development
Child Nutrition Manager Alva Spence and Chef Justin Jatiram collaborate on new recipe development each year. Annual Tasting Day is the public rollout: students, staff, and families sample the year's new offerings. Staff development sessions precede the launch so kitchens can execute the new recipes confidently from the first week.
What made it work
Palo Alto USD didn't reinvent the process. The district committed to making scratch preparation real (not a stated value but not a real one), listened to students in channels they'd actually use, and built a seasonal rhythm of development, training, and launch.