Reducing weekly friction through reusable meal planning
Mealloop turns everyday meals into a reusable system, replacing memory-based planning with a faster, more reliable weekly workflow.
Meal planning is a repeated task with no system behind it. Users rely on memory, leading to duplicated effort, disconnected grocery lists, and a process that breaks down over time.
Problem
Solution
A system that captures meals once and reuses them, enabling users to build weekly plans through selection and generate grocery lists automatically.
Outcome
9/10 user satisfaction
90% task completion
Role
UX Designer
Timeline
3 weeks
Key Insights from User Research
User research revealed consistent patterns across participants, showing that the challenge isn’t discovering meals, but managing what users already cook.
Meal planning lives entirely in memory
All participants relied on memory to track meals, with no system in place. Each week, they rebuild the same plan, repeating the same mental effort.
A consistent meal rotation already exists
Users reported having a small set of meals they cook on repeat. This validated that users don’t need more options—they need a way to store and reuse what already works.
Grocery shopping is disconnected from meals
Grocery lists are built from memory rather than from a plan, leading to forgotten ingredients and extra effort during shopping.
Translating Insights into Design Direction
Affinity Mapping
I synthesized user research into clear behavioral patterns around how people plan meals today. This surfaced the underlying gaps in the current experience and defined the key themes that shaped Mealloop’s design direction.
No system for capturing and reusing meals
Reliance on mental meal rotation
Disconnected groecry planning
Decision fatigue during weekly planning
Automation with flexibility
User Personas
I developed two personas to reflect how people plan meals today. While their behaviors differ, both rely on memory instead of a system, creating repeated effort and friction over time. The product needed to support both structured routines and flexible decision-making without adding complexity.
Persona Archetype 1: Jordan, the Routine-Based Planner
Persona Archetype 2: Mia, the Spontaneous Rotator
Key Flows Mapped
I mapped key flows to understand how users move from saving meals to planning their week and generating a grocery list. Because the core issue was repetition and disconnected steps, the goal was to design a seamless, end-to-end experience that consolidates fragmented actions into a single, continuous workflow.
User and Task Flows
Exploring Structure
I explored how a saved meal could power both weekly planning and grocery list generation, focusing on how selections translate into a complete, editable list. The goal was to eliminate repetitive planning steps, not repackage them.
Wireframes
3 solutions that address the three core challenges
Each solution was designed as part of a connected system that moves users from passive data consumption to deeper understanding over time.
Turning memory into a reusable system
A personal meal repository allows users to quickly save meals they already make and reuse them when planning their week. This shifts the experience from recalling meals each time to selecting from an existing system.
Competitive analysis insight
Most meal planning tools require manual recipe entry or focus on discovery, rather than supporting the repeat behaviors users rely on daily.
Added feature after user testing
Meal entry was simplified to reduce hesitation, allowing users to save meals with minimal input and edit details later without blocking progress.
View feature
Making planning feel like selection, not decision-making
A weekly planning layer enables users to build their week by selecting from saved meals instead of deciding from scratch. This reduces cognitive load and turns planning into a faster, repeatable action.
Competitive analysis insight
Existing tools often introduce rigid planning structures or require too many decisions upfront, increasing friction and discouraging consistent use.
Added feature after user testing
Category labels and selection states were refined to reduce hesitation and make it clearer how meals are assigned across the week.
View feature
Connecting meals directly to grocery execution
An automated grocery list aggregates ingredients from selected meals, deduplicates items, and organizes them into a usable list. This eliminates the disconnect between planning and shopping.
Competitive analysis insight
Most grocery tools operate independently from meal planning, forcing users to manually translate meals into lists and increasing the risk of missing items.
Added feature after user testing
Grocery list editing was made more flexible and visible, allowing users to quickly adjust items and maintain control without breaking the automated flow.
View feature
Validating what works and revealing what to improve
Usability testing validated that users could move from saving meals to planning their week and generating a grocery list with minimal friction, reinforcing the value of a system that replaces memory with a repeatable workflow.
Add a meal
Plan weekly meals
Generate and review grocery list
Performance metrics
100% task completion - Participants successfully completed core flows, including adding meals and planning their week without assistance.
100% weekly adoption intent - All participants indicated they would use the product as part of their weekly routine.
Improved percieved efficency - Users consistently described the experience as faster than their current process of planning mentally or using notes.
Key Insights That Shaped the Next Iteration
Meal-to-list connection needed reinforcement - Some users did not immediately understand that ingredients entered during meal creation directly power the grocery list. I added supporting copy to clarify how ingredients are used, reinforcing the connection between meals and the generated list.
Grocery list editing needed to be more intuitive and visible - While users understood the list was generated, some struggled to find editing controls and expected a more flexible, checklist-style interaction.