Role
Research-led Product/UX Designer
Platforms
iOS / Android
Timeline
12.2024–04.2025
Status
Prototype
Pivot
I pivoted from a supplement helper to a learning-by-doing habit companion.
The strategy shifted toward repeatable meal actions, not “perfect choices.”
Framing
Supplements felt like a practical entry — until interviews flipped the assumption.
Key finding:
When people talked about “getting healthier,” they meant Food + Movement — not supplement shopping.
What changed
From purchase optimization to repeatable momentum.
For who
Built for people who want to get healthier, but need a doable next step when tired.
Evidence & Insight
Supplements weren’t the foundation for health — food and movement were.
Design implication:
To fit real routines, start with daily eating, then makes the next step small enough to repeat. (Meal Planner → Mission preview)
Strategy / Positioning Decision
What if healthy-eating felt enjoyable — and earned?
Enjoyment is a core goal for healthy eating. Keep progress lightweight, so meals stay enjoyable.
Earned = small wins worth repeating.
Evidence:
Tracking made meals less enjoyable for 2/5 (unprompted).
Boundary:
Not a medical app.
Small note
Meals are designed to make the same portions feel satisfying through technique and creativity — at home or eating out.
Habit Loop & MVP
The smallest entry loop that makes action feel doable.
Plan → Try →Earn a win → Repeat
Small note
This is a habit companion. Cooking is one controllable start, not the product.
Validation highlights
Case 2 → Make it doable (core flow friction)
Case 3 → Make it meaningful (motivation triggers)
Takeaway
I pivoted to a learning-by-doing habit companion—designed for enjoyable, repeatable eating.
What this project taught me:
• Supplements were occasional support. Daily food + movement drove real change. • Repeatable actions — not perfect plans — became the core strategy.
Positioning guardrail:
A healthy-eating habit companion, not a cooking app or a medical diagnosis tool.
Next (early roadmap):
Validate the MVP core path: Meal Planner → Mission preview, so users can decide the next step in minutes. (Validation lives in Case 2 + Case 3.)
Update (after Case 3): How the concept evolved
Later, Case 3 suggested sustain needs post-action feedback, so Food Diary should become a milestone signal inside a progression system — not a standalone record.
Case Study 1 - Evidence pack
Optional deep dive below.
Deep Dive