Future of Me

Future of Me

Future of Me

Helping people understand complex diagnostic reports in under 10 minutes.

Helping people understand complex diagnostic reports in under 10 minutes.

Helping people understand complex diagnostic reports in under 10 minutes.

My role

Product Designer

Timeline

1.5 Days (MVP)

1500+ signups on launch day

1500+ signups

1500+ signups 

project-image
project-image
The Challenge

The Challenge

Imagine walking into a beauty store, completing a diagnostic scan, and receiving a 20-page report filled with graphs, percentages and medical terminology.

Most customers don't know what those numbers actually mean or what they're supposed to do next.

Our challenge wasn't to improve the scan itself.

It was to transform complex diagnostic data into a simple, actionable experience that customers could understand within minutes during a live retail launch.

Constraints

Constraints

๐Ÿงฑ

๐Ÿงฑ

Built in 1.5 days

Built in 1.5 days

๐Ÿ›๏ธ

๐Ÿ›๏ธ

Live retail MVP

Live retail MVP

๐Ÿงฉ

๐Ÿงฉ

Complex medical data

Complex medical data

โณ

โณ

Reports to be delivered within 10 mins

Reports to be delivered within 10 mins

๐Ÿ‘ฉ๐Ÿปโ€๐Ÿ’ป

๐Ÿ‘ฉ๐Ÿปโ€๐Ÿ’ป

Dashboard postponed due to engineering constraints

Dashboard postponed due to engineering constraints

Understanding the Problem

Understanding the Problem

Since this was an MVP, we leveraged research from a similar initiative conducted a month earlier. We spoke with existing customers, visited Kaya Skin Clinic to observe their consultation process, and analyzed how people interpreted diagnostic reports.

Rather than validating whether people wanted scans, we wanted to understand where they struggled after recieving the results.

Insight 01

People understood the scan, but not the report.

People understood the scan, but not the report.

Customers relied on staff to explain clinical terms, percentages, and graphs because the reports weren't designed for everyday readers.

Insight 02

Generic recommendations created decision fatigue.

Generic recommendations created decision fatigue.

The beauty market is crowded with products and conflicting advice. Customers wanted confidence that recommendations were specific to them.

Insight 03

Information without action wasn't useful.

Information without action wasn't useful.

People didn't just want to know what was happening with their skin or hair, they wanted clear next steps.

Making Clinical Data Understandable

Making Clinical Data Understandable

The Problem

The Problem

Before designing anything, we had to understand the report ourselves.

The diagnostic machines generated highly technical outputs that even our design team couldn't confidently interpret.

Designing the interface before understanding the science would have meant simplifying information we didn't yet understand.

project-image
project-image
project-image
project-image

What I Did

What I Did

  • Collaborated with the machine vendor.

  • Interviewed doctors and wellness experts.

  • Broke down every parameter into plain language.

  • Prioritized which metrics mattered most for first-time users.

Designing the experience

Designing the experience

Once I understood what the data was actually meant, focus shifted on to how the user experience should be.

How to reduce anxiety?

How might we make it scannable?

How do we help users know what to do next?

#phase_1

#phase_2

project-image
project-image
Scaling an MVP for a Live Launch

Scaling an MVP for a Live Launch

Problem 1.

Problem 1.

Building a dashboard would have delayed the launch and increased engineering effort before we had validated demand.

Since the objective of the MVP was learning, not building a perfect product, we intentionally shipped a PDF experience first.

Problem 2.

Problem 2.

Designing the report was only half the challenge.

Since this experience was happening live inside a retail store, every customer's report had to be generated and delivered within minutes.

A manually populated PDF meant longer wait times, higher chances of human error, and a workflow that wouldn't scale beyond the launch weekend.

Epiphany

Epiphany

While reviewing the scan reports, I noticed that every generated PDF followed the exact same structure. Images always appeared in fixed positions, regardless of the customer.

Instead of treating each report as a unique document, I wondered if those fixed coordinates could become anchors for automation.

Next: Working with Engineering

Next: Working with Engineering

Step 1

Mapped every image placeholder in Figma to fixed coordinates.

Step 2

Worked with engineering to build an extraction plugin that automatically populated the correct visuals.

Step 3

Applied a similar workflow for numerical data using Google Sheets and automation.

Step 4

Tested, debugged, and refined the pipeline until reports generated reliably.

Result

Result

Report generation dropped from roughly 15 minutes of manual effort to around 2-3 minutes, making the live launch operationally feasible.

The MVP

The MVP

One fix at a time.

#phase_2

#phase_2

One concern per page

One concern per page

Reduced cognitive load and allowed users to focus on a single issue before moving to the next.

Visual body mapping

Visual body mapping

Marked facial, hair, and body zones so users could immediately identify where each result applied, reducing the effort of interpreting unfamiliar scan images.

Plain language copy

Plain language copy

Replaced technical terminology with simple explanations while preserving scientific meaning.

project-image
project-image
MVP to Product

MVP to Product

Once the launch validated user interest, the temporary PDF workflow was no longer sufficient.

#phase_3

The first priority after launch was transitioning the experience into a web dashboard, enabling users to access reports digitally while reducing operational overhead.

#phase_3

#phase_3

Aftermath & Learnings

Aftermath & Learnings

User Impact

User Impact

  • 1500+ users during launch weekend

  • 30% had no skincare routine

  • Reports generated excitement and repeat referrals

  • 15% adopted recommended products

Operational Impact

Operational Impact

  • Report generation reduced from ~15 minutes โ†’ 2-3 minutes

  • Dashboard replaced manual workflow after MVP

  • Reduced manual intervention through automation

Business Learning

Business Learning

  • Users wanted alternative product recommendations

  • Retail staff occasionally recommended different products than the report

  • Product availability should eventually sync with recommendations

Reflection

Reflection

Simplifying medical information required understanding the science. Delivering the experience required designing operational workflows alongside engineering.

The biggest takeaway for me was that great product design isn't just about making interfaces intuitive, it's about reducing friction across the entire system.