Experience

Mindbloom case study

Designing AI support before and after therapy

I designed AI-assisted intention setting and voice journaling for at-home ketamine therapy. Intention quality rose 23%. Our three-person team shipped both flows in eight weeks.

Mindbloom: three suggested intentions for the next session
Mindbloom: a voice journal prompt after the session

At a glance

Role
Design Lead
Team
Me, one PM, one engineer
Timeline
Jan–Dec 2024 · this project: 8 weeks
Platform
Mobile

About the company At-home ketamine therapy in 35 states and DC, with more than 200,000 sessions delivered.

What my work did

intention quality after release, beating the team’s target
+23%
from brief to two shipped flows
8 weeks
Watch the 34-second version
In this project

Two moments the app wasn’t helping with

Mindbloom’s clinical team had seen two patterns. Clients who set an intention before a session rated the session higher. Clients who journaled afterward were more likely to continue their program.

The app helped with neither. Intention setting was loosely guided, and journaling happened in paper notebooks mailed to new clients. The brief was to bring both into the app and use AI to help.

Both flows in 34 seconds, cut from the shipped screens. Made with Remotion.

Three questions, then three suggestions

Most clients did not know what a good intention looked like. Too open, and they froze. Too prescriptive, and it felt impersonal.

We prototyped in Figma: one long chat or one question at a time, whether clients could ask questions back, and how many questions before it felt like a chore. Three was right. Clients answer by tapping, typing, or speaking. The app then suggests three intentions based on their answers. They choose one or write their own, so the final words are always theirs.

An intention-setting conversation from the design file. The app greets Tom, asks if he has an intention in mind, affirms each answer, asks him to share more, and suggests a theme around resilience.
  1. Personalization
  2. Short direct question
  3. Validation & affirmation
  4. Go deeper – understand
  5. Validation & affirmation
  6. Suggest a theme, but don’t be too prescriptive
  7. Yes / No will fork the experience. Let’s design for the easy path here.
An early conversation design, with my notes: affirm, go one level deeper, then suggest a theme without writing it for them. The client’s answers are in blue.

Design for the person after a session

Research showed memories were most vivid right after a session. Clients who closed the app to journal later rarely came back. So journaling starts the moment the session ends, on the same background, as a continuation rather than a new task.

After a session, some clients have blurred vision or reduced motor control. I doubled the type and button sizes, made the flow voice-only, and asked one question per screen.

Before a session

Intention setting before a session: an affirmation and the next question in regular type, above the keyboard.

After a session

Journaling after a session: one question in large type on the session’s dark background, with a single Tap to talk button.
Same flow, two states of mind. After a session: twice the type size, voice only, one question per screen.

Results, and a lesson about AI

Intention quality improved 23% on the team’s quality measure, beating the target. But a vocal group of clients did not want AI involved in something so personal.

The help itself was not the problem. The label was. We stopped leading with “AI” in the interface and described the feature by what it did: suggestions based on the client’s own answers. Completion rose right away. People wanted the help; they did not want a technology pitch in the middle of therapy.

Journaling missed its first goal. There was no baseline, since it replaced paper notebooks. The team began testing a shorter flow and accepted that some clients would rather journal later.

What I’d do differently

“Journal while it’s fresh” made clinical sense, but it pulled against “don’t jolt someone out of a therapeutic state.” We never fully resolved that. With more time, I would have tested the timing as carefully as the interface.

Next case study · 3 of 4

Making glucose data readable for beginners

I redesigned how Levels shows glucose, so a beginner can read their day without knowing what a good number is. After a restructure, I was the company’s only designer, working directly with the CEO.