← Selected work

UX + CONTENT DESIGN / JUNE 2026

DivaFlo

From tracking a cycle
to planning a day.

A menstrual wellness concept that brings cycle information, symptom notes, and everyday food, movement, and rest options into one flow.

Read the design story ↓
MY CONTRIBUTION

Interviews · Empathy & journey maps
UI flow · Prototyping · Usability tests

REFINED PORTFOLIO DEMO
CONCEPT DEMO

Use sample inputs. Entries stay in this visit and disappear on reload.
Illustrative wellness content; no diagnosis or medical recommendations.

A prediction tells you
when. A plan helps
you decide what next.

DivaFlo explores the space between knowing a period is coming and knowing how to prepare for the day.

Cycle tracking, symptom notes, and everyday wellness decisions often live in separate places. The concept brings them into a single flow, with food, movement, and rest options inspired in part by Chinese wellness traditions.

MY CONTRIBUTION

Interviews, empathy & journey maps,
UI flow, prototyping & usability tests

OUTPUT

8-screen course prototype
& a refined portfolio demo

Tracking was already
happening.
Preparation wasn’t.

Early interviews shifted the question from “How might we build another tracker?” to “How might we make tracking useful in everyday life?”

5

interviewees tracked their cycles and described disruption to everyday life.

1/5

regularly tracked symptoms—suggesting logging needed to feel worth the effort.

4/5

wanted proactive guidance beyond cycle predictions.

Five college women, ages 19–20, interviewed in June 2026. These are exploratory findings from a small convenience sample, not population estimates.

A busy day was
the design constraint.

The composite persona, Joanna, needed guidance that fit around a full student schedule. The empathy map separates observed behavior from inferred thoughts; the journey map shows where intentions faded before the next cycle.

The opportunity was to make preparation easier to find, easier to save, and easier to revisit.

  1. Before symptoms: Make a phase update visible without requiring a search.
  2. When plans are disrupted: Put food, movement, and wellness options together.
  3. After choosing an option: Confirm the save and keep the plan accessible.
Explore the original empathy mapComposite persona Joanna: observed and inferred needs organized as Says, Thinks, Does, and Feels
Explore the original journey mapSix-stage concept journey from before symptoms to disruption, coping, recovery, and reflection, with design opportunities

Original course artifacts. The interactive portfolio demo above extends this work with responsive logging, complete recipes, and updating save counts.

One need. Two distinct paths.

01

“Log symptoms” records.

Named symptoms, labeled intensity, and an explicit save action make it clear that this path captures how someone feels.

LESS EXPLICIT

How are you? 😊 😐 😣

MORE EXPLICIT

What are you noticing?
Cramps · Low energy · Bloating

02

“See My Plan” supports action.

A separate, prominent action takes visitors to practical options. Short explanations make the relationship between an input and the sample plan visible.

FROM INFORMATION

Your next period is approaching.

TO A CLEAR NEXT STEP

Explore a gentle movement option.
See My Plan

03

Show what changed.

Logging should visibly update the experience. The demo acknowledges a saved entry, reflects it on Today, and explains the plan’s selection rules.

CONFIRM THE ACTION

Symptoms saved for this visit.

MAKE THE REASON VISIBLE

This lower-effort option appears because you selected low energy.

The copy comparisons above are illustrative rewrites in this portfolio version, not archived screenshots of the original prototype.

Feedback became
a design decision.

Two think-aloud participants immediately understood the concept and chose “See My Plan” first. Their sessions also revealed specific gaps between what the interface promised and what it actually did.

OBSERVATION

Logging did not visibly change the plan.

Observation: One tester looked for the logger under the forecast, then expected a change after saving.
Refinement: Separate “Log Symptoms” from “See My Plan,” confirm the save, and show the logged inputs in the plan.

OBSERVATION

Food tips were missing the next step.

Observation: A tester expected a complete recipe. Another expected named responses rather than emojis.
Refinement: Add ingredients and methods to recipe details and use text labels for symptom selection.

OBSERVATION

Saved progress stayed at “1 of 3.”

Observation: Both testers noticed that progress did not reflect saved recommendations. Peer critique also asked for a clearer saved state.
Refinement: Update the saved count immediately and preserve the selected state on each card.

WHAT I CAN CLAIM

Two think-aloud sessions revealed navigation, feedback, and content gaps. The portfolio refinements have not yet been re-tested, so their effect on usability remains unmeasured. No clinical, retention, or conversion outcome is claimed.

Can someone move
from a feeling to
a useful next step?

The next test should evaluate comprehension and task completion, rather than whether the interface looks finished.

  1. Can someone log low energy without confusing logging with viewing advice?
  2. Can they explain why a sample option appears in their plan?
  3. Can they find a recipe, understand its steps, and save it?
  4. Do they understand the difference between cultural inspiration and evidence-backed medical guidance?
Try those tasks in the demo