JKJulián Kondratavicius

doc24 · Healthtech

Designing wellbeing for two clients with different interests 

A B2B2C product where the company pays, the employee uses and a wellbeing team operates. I designed the experience so all three win with the same product.

View project
Wehealthy app home
tokens / color
Button · 7 states
🔒 Your company only sees aggregates
RoleSenior Product Designer
TeamCofounders, Product Owner, functional analysts, engineering team
Timeline2023 — Present
PlatformsWeb app · iOS · Android

In 30 seconds

The challenge

An ecosystem, not an app

What I did

A corporate wellbeing platform with several actors and one product: HR needs to measure, employees need to trust and the wellbeing team needs to operate. I designed the end-to-end experience, from onboarding to reporting, and the design system that holds it together.

Focus
  • Experience Design
  • B2B2C
  • Design System
  • Data-driven UX

01Context

Two clients, two incentives

The company buys; the person uses. One wants proof the investment works, the other wants to feel better without feeling watched.

In between, a wellbeing team has to run the program, and the product has to make all of it feel like a single experience.

02The problem

An ecosystem, not an app

Every actor needed something different from the same product. Designing for just one of them broke it for everyone else.

  • 01HR needs to measure results and justify the investment.
  • 02Employees need to trust the product before answering honestly.
  • 03The wellbeing team needs to run content and follow-up.
  • 04Product has to turn all of that into one coherent experience.

03The ecosystem

Who gives and who gets

I mapped what each actor gives and gets. The platform isn't the center because it's the app: it's where every promise meets.

  1. Company / HRBuys · communicates · gets insights
  2. PlatformOnboarding · assessment · content · recommendations
  3. EmployeeAnswers · gets value · comes back
  4. Wellbeing teamContent · intervention · follow-up
  5. Data / analyticsAggregation · privacy · reporting

04Research

What people say vs. what they do

I cross-referenced self-perception questionnaires with real product usage. The gap between them showed where to intervene.

05The flows

Wellbeing without feeling audited

The challenge wasn't usability, it was trust. Every question gives something back before asking the next, and it's clear what the company can and can't see.

06The system

The design system that made it scale

With several actors across web and mobile, consistency wasn't aesthetics: it was trust. I built the design system so every new flow speaks the same language without re-arguing buttons and states.

  • 01Tokens: color, type, spacing, radii and elevation.
  • 027 states per component, including empty and error.
  • 03One library for web and mobile, no duplicated components.

07Decisions

Decision 01

Build the system alongside features, not before

The roadmap couldn't stop for two months.

Every component was born from a real case, and the system showed value from week one.

Decision 02

Employee privacy over reporting detail

The company wants results; the employee wants not to be identified.

If employees suspect they can be identified, they stop answering honestly and the data loses value for everyone.

08AI in the process

AI to decide faster

I use AI to synthesize questionnaires and research, and to go from an idea to a clickable prototype in hours. That lets us validate flows with users before committing engineering.

  • Claude
  • Figma Make
  • v0

09What I took away

  1. In B2B2C, designing for whoever pays without losing whoever uses is the real product problem.
  2. In healthcare, trust is part of usability.
  3. A Design System is sold with team metrics, not pretty screenshots.
Next case →LetsBitInvesting in crypto without the fear of getting it wrong
Let’s talk