Domain: Healthcare · Mental Health

https://getzant.com/

I designed an MVP for a mental health platform in three weeks, from idea to shipped product.

UX Metrics

First-Week Activation +12% Users who pay +1.5% No-Show -30% Rebook +40%

Impact

• Reduced time-to-care from months to same-week availability (often within 24-72 hours)
• Removed insurance barriers with affordable, low-cost sessions
• Gave providers a steady client pipeline and simplified admin (scheduling, messaging, payouts)
• Lowered confusion and booking drop-offs in testing through clear IA, progressive booking/payment, and one-tap return to active sessions

My Activities

Requirements workshop Competitor analysis CJM User scenario User flow UI kit Visual accessibility Developer handoff

Context

Zant was a New York–based startup with a deeply personal origin.

The founder lost a close friend to suicide and struggled to find help for herself. The process felt fragmented, slow, and overwhelming. She decided to build what she couldn’t find: a simple, human way to connect people with psychologists and coaches.

When I joined, there was no product.

Only an idea, a few rough sketches, and a lot of emotional weight.

The reality

There was no product team, no UX process, no roadmap.

Just urgency and trust.

The goal was simple and heavy at the same time:

build something real, fast - so people could start getting help.

The challenge

People come to mental health products already tired, stressed, and overloaded.

Sometimes they are not okay.

The interface could not feel clinical.

It could not feel busy.

And it could not feel confusing.

At the same time, this was an MVP.

We didn’t have months. We had weeks.

The balance was delicate:

move fast without being careless.

Shaping the product

I started from zero.

I mapped the core journey: how someone finds help, how they choose a provider, how they book, how they pay, how they join. I defined the basic architecture, created user stories, and built the MVP logic.

This was not about designing screens.

It was about answering one question:

“What does someone need to see first when they are not okay?”

Designing for emotional load

Because users might arrive already overwhelmed, I kept everything intentionally simple.

<aside> <img src="/icons/language_gray.svg" alt="/icons/language_gray.svg" width="40px" />

Soft language.

</aside>

<aside> <img src="/icons/watch-analog_gray.svg" alt="/icons/watch-analog_gray.svg" width="40px" />

Short steps.

</aside>

<aside> <img src="/icons/geography_gray.svg" alt="/icons/geography_gray.svg" width="40px" />

Minimal choices.

</aside>

<aside> <img src="/icons/view_gray.svg" alt="/icons/view_gray.svg" width="40px" />

Low visual noise.

</aside>

The goal was to reduce cognitive load, not add to it.

This wasn’t a marketplace. It was an entry point to support.

Speed over perfection

We didn’t have time to design everything from scratch.

I made a conscious decision to use a design system and UI kit so I could move faster and focus on flows, clarity, and edge cases rather than pixels.

This allowed me to design the full MVP in about three weeks — from onboarding to booking, messaging, payments, and rescheduling — and hand it cleanly to development.

The product was shipped and later appeared in the App Store.

It wasn’t perfect.

But it was real.

Client journey

Provider journey