YourDOST · Sr Product Designer assignment

Show less, and make what’s shown explain itself.

Two products on opposite ends of the same business: the tool a Customer Success Manager uses to keep a client healthy, and the app a person in therapy uses to keep going.

RoleSole designer, research to build
ScopeWeb dashboard · iOS app, 5 screens
OutputCoded, clickable prototype
WorkflowFigma → Claude → Claude Code
Summary

One business, two people, one idea.

YourDOST sells care to companies and colleges, and earns its renewal when people actually use it. Usage breaks in two places: the CSM doesn’t notice a client slipping in time, and the user doesn’t come back after a hard week. I designed for both breaks.

Task 01 · CSM dashboard
A ranked to-do list, not a data wall.

Every account is scored by the cost of waiting a day. The CSM sees three things to do first, each with one reason and one action.

Task 02 · Client iOS app
A mirror of progress, not a ledger of misses.

History becomes “your Journey”: what’s next first, chapters of how far you’ve come, and gentle patterns of what seems to help.

Task 01 · Internal tool

My Accounts Today

The problem

A CSM looks after about 30 accounts. The signals that one of them is slipping are spread across the CRM, usage dashboards, campaign sheets and email. Mornings go on assembling the picture, and by the time a pattern is obvious the renewal conversation is already hard.

What I learned

Rank every account by the cost of waiting one more day, and show the reason, never the score.
Priority
=
Cost of delayDeadline ≤ 72h · renewal ≤ 30 days
×
Account weightMembers · contract value
×
ChangeSince yesterday

Decisions and trade-offs

DecisionRejected alternativeWhy
Cap “Do first” at threeShow every flagged accountIf everything is urgent, nothing is. Overflow drops into “Also today” with an Urgent tag, so nothing is hidden.
Why → evidence → action on every cardA health score and a chartIt follows the order a CSM thinks in. Actions are verbs (“Send assets to Dean”), never “View”.
Evidence matched to the signalThe same line chart everywhereA late follow-up gets a 14-day strip, a campaign gets progress to goal. A rising 12% stays neutral, not green, because it’s still far below target.
One merged queueSeparate Risk, Engagement, Follow-up and Campaign viewsType becomes a tag, not a place to navigate to. One list answers “where do I start?”.
Snooze needs a reasonA plain snooze button“Waiting on client” and “Tomorrow” mean different things to the team and to the ranking.
Show the ranking rulesA black-box model“How is this ranked?” and “Not relevant?” build trust, and feed the model better data.
 My Accounts Today · live prototypeOpen full screen ↗

How I’d know it works

Time from login to first action. Share of “Do first” items actioned the same day. Renewal saves on accounts that were flagged. And the “Not relevant?” rate, which tells us whether CSMs trust the ranking.

Task 02 · Client iOS app

your Journey

The problem

Today’s History tab lists sessions and logs in date order. For someone in therapy it reads like a record of how often they didn’t show up, and it is usually opened right after a gap, at the worst possible moment.

3.3%

Median 30-day retention of mental-health apps. Most people try once and drift.Baumel et al., Journal of Medical Internet Research, 2019

The YourDOST companion

What I learned

Answer three questions in order: what’s next for me, how far I’ve come, and what seems to help.
ScreenWhat it holdsQuestion
01 HomeCompanion, “Day 24”, the next session, today’s reflection, the week in facesWhat’s next for me?
02 Check-inA sheet, once a day, only if you haven’t checked inHow am I right now?
03 TimelineNamed chapters with summaries, grouped by dayHow far have I come?
04 PatternsThe week chart, opt-in insights, moments reachedWhat seems to help?
05 MomentYour own takeaway, a next step, who can see itWhat did I take from this?

Decisions and trade-offs

DecisionRejected alternativeWhy
Chapters with summariesAn infinite feedA narrative (“Finding a rhythm”) is easier to reflect on than 200 rows, and older chapters fold away.
“Day 24”, days since startingA streak counterA gap never resets anything. Coming back is celebrated: “You came back, and that counts.”
Check-in as a once-a-day sheetA mood card on HomeA card with a face already selected reads like a record, not a question. “Not now” silences it until tomorrow.
Faces from Heavy to GreatGreat firstIt reads like a scale, matches the chart, and removes the pull to tap “Great” just to get through.
A seven-bar week, faces on topDot matrix, gauge and spectrum (my first version)Four encodings were too much on a heavy day. Taller is lighter, and the face says how it felt.
Insights say “seems to help”Confident recommendations“3 of 4 times · from your check-ins” is honest evidence, not a diagnosis, and can be switched off.
Journal entries locked and blurredOpen titlesSafe to open over a shoulder. Employers and colleges only ever see anonymous totals, and the app says so.

One iteration, start to finish: the mood chart

V1Dot matrix + gauge + spectrumRich, but four encodings to decode at once.
V2Two weeks of facesFamiliar, but no clear takeaway.
V3One number, one split barClear, but lost the shape of the week.
SHIPPEDSeven bars, faces on topReadable in a glance, with one headline.
 your Journey · live prototypeOpen full screen ↗

How I’d know it works

Return rate after a gap of a week or more. Tap-through on the next session and today’s reflection. The insight opt-out rate, where a high number means the tone is wrong. And one interview question: “did anything here make you feel judged?”

How I worked

Figma to think, Claude to iterate, Claude Code to ship.

01
Figma

Moodboards, early layouts and the core pieces: the face set, cards and colour roles.

02
Claude

A sparring partner. I pressure-tested UX decisions, critiqued screens against the brief and explored many variations fast.

03
Claude Code

The prototype is real HTML, CSS and JS: working sheets, live states, 60fps motion and reduced-motion support.

Working AI-native changed the economics of iteration. The mood chart went through four complete, clickable versions in one sitting, judged on a real screen rather than in a description. Before submitting I ran a UX and brief-coverage audit with Claude, which caught details such as session counts that didn’t add up across screens. The speed came from AI; the decisions, and the reasons behind them, are mine.

What’s next

What I’d do with another two weeks.

Left out on purpose

Streaks, badges and leaderboards, because care shouldn’t feel like performance. Numeric mood scores on the timeline, because assessments belong with a professional. Guilt-driven push nudges. Sharing, until there’s a consent-first way to share a chapter with your own therapist.

About me

Let’s talk.

Chaitanya Sai

Chaitanya Sai

I’m Chaitanya Sai, a Senior Product Designer at Equal AI, and previously Product Designer 2 at Jio Fynd. I’m a CS graduate turned designer with 4+ years of experience. I design in Figma, iterate in Claude and ship working prototypes with Claude Code, turning messy, human problems into calm, clear products.