Snack'nU
A campus food-redistribution service concept designed to help catering teams surface edible surplus after events and route it to nearby students through time-sensitive pickup flows.
Student-facing pickup surface showing nearby surplus
opportunities and confirmed pickups.
Why this matters
Campus food waste is not only an inventory problem — it is a coordination problem. After events, edible surplus often exists for a short window, but students nearby may never know it is available.
Snack'nU explored whether a lightweight service loop could connect catering staff, surplus food, and students without creating heavy operational overhead.
The Problem
The problem was not demand. Students would take free food if they knew where and when it was available. The harder problem was coordinating surplus quickly enough for it to remain useful while keeping handoff, food safety, and operational responsibility clear. Generic email or team-channel announcements rarely matched how quickly surplus had to move.
- Catering staff needed a fast listing flow that fit post-event cleanup.
- Students needed timely, location-aware alerts before food disappeared.
- Pickup flows had to reduce crowding, ambiguity, and unreliable handoffs.
- Institutional adoption depended on safety, liability, and communication constraints.
Core Insight
Food redistribution on campus is less like a marketplace and more like a time-sensitive service handoff.
The value was not inventory browsing. The value was making surplus visible quickly, routing it to nearby demand, and reducing ambiguity at pickup.
Design Approach
- 1.
Design for the catering staff workflow first.
Why it mattered: If posting surplus takes too long during cleanup, the supply side fails before students ever see the food.
- 2.
Treat pickup timing and location clarity as the core UX.
Why it mattered: The product only works if students can act quickly without creating confusion, crowding, or unreliable handoffs.
- 3.
Keep the student experience lightweight and alert-driven.
Why it mattered: Campus surplus is opportunistic. Students should not need to browse a full marketplace to benefit from nearby availability.
Early service mapping for surplus coordination
and pickup flow.
Service Loop
Stakeholder Reality
The concept moved beyond coursework into conversations with campus dining and wellness stakeholders. Interest existed, but adoption depended on institutional concerns around liability, communication ownership, food safety, and whether existing email-based channels were considered sufficient.
Student event detail view showing menu, pickup window, location,
available servings, and non-guarantee disclaimer.
Impact
- Mapped the full surplus-to-pickup service loop from staff posting to student pickup.
- Identified institutional adoption risks early: liability, ownership, food safety, and communication speed.
- Clarified that reliability mattered more than feature breadth for an initial campus pilot.
- Turned a coursework prompt into a real stakeholder-facing service design exploration.
Reflection
Current limitation:
The hardest challenge was not designing the app flow. It was aligning the operational, legal, and institutional responsibilities required for a real campus pilot.
Next iteration focus:
Define a small controlled pilot with one dining partner, limited pickup windows, clear safety rules, and measurable success criteria around speed, reliability, and food recovered.