Info
Looks like you wandered into an interview. Pull up a chair.
— Lemme introduce Emme
How did you design for trust in a product where accuracy really matters?
The experience needed to feel calm, inclusive, and smart by default. Clear signals, plain language, and nothing that felt judgmental or overly technical.

I avoided anything clever or showy and focused on making the system feel steady and predictable.

When a product fades into the background and becomes part of someone’s routine, that’s when trust is real.
How did you balance simplicity with the complexity of tracking missed or late doses?
The complexity lived in the technology, not the experience. The system handled the thinking, timing, and reminders so users didn’t have to.

My role was to wrap that in something that felt approachable and empowering rather than clinical or stressful. Simplicity came from clear language, clean layouts, and interactions that felt friendly without being casual about something important.

The experience was meant to be supportive and confidence-building, easy to understand at a glance, and serious when it needed to be.
How did you validate the core experience before building everything else?
I leaned heavily on prototyping and early testing.

Before building the full platform, I built simple interactive prototypes around the core moments and put them in front of people right away.

That made it easy to see what was unclear or overcomplicated. Fixing those issues early was fast and low risk, and it gave the team confidence that the core experience worked before investing in everything else.
How did you decide what information to surface immediately versus what to keep in the background?
I anchored the interface around the core question, ‘Did I take my pill?’

That drove the information hierarchy.

Status and timing stayed front and center, while history and settings were available through progressive disclosure so they never competed for attention.

The result was a surface that felt simple and calm while still supporting deeper needs.”
How did you design for a subject you were not the target user for?
I leaned heavily on research and direct feedback from the people the product was actually for, using their language, concerns, and habits to guide decisions.

Instead of designing from assumptions, I let the target audience validate the work as it took shape. Their feedback drove adjustments and helped ensure the experience felt relevant, respectful, and genuinely useful to the people it was meant to support.