How do you tell which meal kits need work?
Fresh Food Daily's starting design collected feedback through a shared email address. To spot a recurring complaint about a kit or see which new meals customers wanted, the team would have to sort through messages by hand.
Forum
Give customers a place to ask questions and discuss meals with each other.
Reviews
Ask customers to rate each delivered kit on a 5-star scale and invite them to explain what could be improved after a low rating.
Suggestions
Give both customers and prospective customers a way to propose new kits. Keep those submissions distinguishable so the team can see who is asking for what.
Where a low rating goes
What the customer does
After delivery, a customer selects the meal they ordered and gives it a star rating. The requirements call for a follow-up after a low rating that asks what could be improved and invites a new meal idea.
What the team receives
The data-flow diagram shows the rating being stored against the meal and both ratings and suggestions reaching the feedback manager.

Meal ratings are stored for the selected kit. Ratings and suggestions both reach the feedback manager.
How the 3 features fit into 28 days
The plan grouped the work into five phases. The forum, reviews, and suggestions shared an initial design and a final review, with their development scheduled in parallel.
-
2 days
Scope
Agree on what the new page needs to do.
-
2 days
Content
Decide what goes on the page and in what order.
-
7 days
Design
Wireframe the page, then review its layout and behavior.
-
12 days
Development
Build the three features at the same time.
-
5 days
Integration and review
Bring the features onto one page and test by submitting reviews, suggestions, forum posts, and replies.