Prabodham Prasad
Fixing kitchen chaos with simple coordination
Overview
Prabodham Prasad is an app built to help volunteer kitchens handle the chaos of cooking at scale. It handles everything from daily chores to grocery shopping for teams serving over 1,000 meals every week.
I turned a messy system of WhatsApp groups and paper notes into a clean digital hub where everyone knows exactly what their job is.
The Setup
- •Tech: Built for iOS using React Native and Supabase.
- •Team Size: 15-20 volunteers per kitchen location.
- •Scale: Cooking for 200-300 people per meal.
- •Timeline: 8 weeks from idea to working app.
Problem Statement
How do you stop a kitchen from falling into chaos when you're managing 15+ volunteers across multiple locations?
What was going wrong?
- •Info was buried in messy WhatsApp threads.
- •Volunteers lacked a clear daily task list.
- •Manual grocery lists led to missing items.
This "coordination tax" was exhausting for the leaders and confusing for the volunteers.
Role & Constraints
I built this from start to finish: research, UI design, and development.
What I did
- •Found friction points through user interviews.
- •Mapped out the app structure and user flows.
- •Designed the interface and a component library.
- •Built the mobile app and organized the database.
The Constraints
- •No Logins: Simple 'Team Code' for instant access.
- •Low Tech Literacy: Older users who rarely use apps.
- •Kitchen Chaos: Huge buttons and readable text.
- •8-Week Dash: Two months from idea to launch.
User Research
I didn't want to guess what the problems were, so I spent days in the kitchen watching the volunteers work. I talked to everyone from the people chopping veggies to the coordinators ordering the groceries.
How I researched
- •Shadowing: Watching meals prepared start to finish.
- •Interviews: Talking to 11 users about their workflows.
- •Auditing: Finding where info got lost in WhatsApp.
Who are we building for?
- •Leaders: Weekly planning and task coverage.
- •Kitchen Staff: Clear view of today's tasks.
- •Admins: High-level view of all locations.
Insights & Design Strategy
Spending time in the kitchen showed me that the real problem was coordination. Volunteers were getting lost in messy lists and repeat questions, so I focused on making the logistics automatic so they could just focus on cooking.
Info Architecture (IA)
Building the structure for Prabodham Prasad meant turning a web of kitchen data into a linear, easy-to-follow path. I designed a flow where recipes, inventory, and volunteer availability are all interconnected, so when a leader updates the menu, the grocery lists and task queues update automatically. I kept the navigation shallow to ensure that "today's work" is always the priority, making it accessible even for users who aren't tech-savvy. You can see the full map in Figma.
Design Strategy
- •No Auth: Enter a team code and start instantly.
- •Recipe Hub: One source of truth for all instructions.
- •Availability: Fast 'In' or 'Out' toggles for staff.
- •History Log: Transparent list of every update.
Iterations
I tried a few different ways to show the schedule. I even thought about a chat-based app, but that didn't fix the mess. I ended up with a clean, role-based dashboard. I started with simple low-fi sketches to map out the logic.
What I tried
- •Kanban: Too complex for moving cards around.
- •Calendar: Good for the month, slow for daily use.
- •Dashboard: Won by putting 'Today' front and center.
Fixing the details
- •Bigger Text: Oversized task cards for readability.
- •Simpler Nav: Single home screen instead of tabs.
- •Easy Editing: One-tap staff swaps for leaders.
Visual Design System
The app needed to feel warm and community-driven, not like work. I used a lot of orange tones to represent service and warmth.
The rules I followed
- •Glanceable: See your job without scrolling.
- •Warm: Community-first colors like orange.
- •Big Targets: Easy to tap with busy hands.
- •Reliable: Consistent UI that is easy to learn.
Empty State Icons
Even when there's nothing to do, the app should feel friendly. I designed custom illustrations to keep the mood light and guide users on what to do next.
Final Solution
The final design is a mobile-first app that focuses on speed and simplicity. You can explore the complete Figma file here.
Zero-Friction Access
No emails, no passwords. Just a simple team code to get started instantly.
- •Instant setup without complex registration.
- •Team-specific codes for secure, grouped access.
- •Designed for volunteers of all tech levels.
Grocery Lists
No more hand-written lists. The app calculates exactly what you need based on the recipes being cooked.
- •Automatically scales ingredients based on headcounts.
- •Consolidates items from multiple recipes into one list.
- •Real-time updates to prevent double ordering.
Recipe & Inventory
Standardized recipes ensure consistency, while real-time inventory tracking prevents last-minute shortages.
- •Step-by-step instructions for consistent taste.
- •Live inventory tracking to minimize waste.
- •Visual guides for portion control and plating.
Validation & Testing
I gave the app to 15 volunteers for a month to see how it handled real-world use.
What we fixed
- •Font Size: Increased scale to stop users squinting.
- •Alerts: Added push notifications for task reminders.
- •Onboarding: Simplified the first-tap experience.
Impact & Results
The big wins
- •Zero confusion. No more 'What's my job?' calls.
- •Less waste through accurate grocery lists.
- •Leaders save hours on communication weekly.
- •Volunteers feel prepared and ready for shifts.
Reflection & Learnings
This project showed me that in high-stress environments, clarity is everything. People don't want "fancy" features; they want an app that makes their life easier.
Growing as a designer
- •Bring in leaders earlier to co-design core tools.
- •Start with paper to catch navigation issues early.
- •Set up tracking early to see where users get stuck.