Case Studies·01·Consumer health

Designed for restoration, not restriction.

Let's Kill Ed is a mobile app for families in eating disorder recovery. Every food and meal tracker on the market is built to help people eat less. Recovery asks the opposite. I led the research, set the creative direction, led UX, branding, and UI, and shaped the product around how treatment actually works, then built it with Asa Gilmore.

Let's Kill Ed home screen showing today's progress toward a calorie goal and a meal checklist
Let's Kill Ed logo
Today screen · demo data
My role
Co-founder · Principal design lead
UX, branding, UI
Team
Two people
Design + build, with Asa Gilmore
Platform
Mobile · Android beta
Light and dark mode
Grounded in
FBT + Plate-by-Plate
Free, always

01 · Background

Eating disorders are serious, common, and treatable.

Eating disorders are psychiatric illnesses with serious medical consequences, and they often begin in adolescence. For adolescents, research shows that family-based treatment, delivered at home with parents at the center, is among the most effective approaches. Let's Kill Ed is built on two established clinical frameworks rather than inventing its own.

10,200 deaths each year in the U.S. are a direct result of an eating disorder. That's one death every 52 minutes, making eating disorders among the deadliest mental illnesses. STRIPED · Deloitte ↗
Treatment model

Family-Based Treatment (FBT)

Also called the Maudsley approach. Parents temporarily take charge of their child's meals and nutrition, then hand control back in phases as recovery progresses. It's a leading evidence-based outpatient treatment for adolescents. FBT defines who does what, and when.

Nutrition method

The Plate-by-Plate Approach®

A visual method from dietitians Wendy Sterling and Casey Crosbie. Families plate full, balanced meals that include every food group, without measuring or weighing at the table. Plate-by-Plate defines what goes on the plate.

02 · The problem

The tools families had were built for a different goal.

In family-based treatment, parents take responsibility for every meal while their child recovers, and the care team needs to know whether the child is getting enough. In practice, that meant spreadsheets, sticky notes, and diet apps. The diet apps were the worst option: their whole model is a deficit, with red warnings when you go over.

The product serves people with different needs. The parent does the logging, usually exhausted and mid-meal. The child is the patient. Dietitians, therapists, and doctors need a clear picture between appointments.

Typical diet trackerLet's Kill Ed
Goal: a calorie deficit, eat lessGoal: adequate calories, in the range each person needs to recover
Weight loss celebratedWeight restoration charted as recovery
Counting by hand, item by itemSnap a photo; AI and USDA data do the counting, the parent confirms
One user, optimizing themselvesA family, with the caregiver as the primary user
Health data on the company's serversData stays in the family's own Google Drive

03 · Research

Built from the table out, with families and clinicians.

We started as the users. Then we tested what we'd learned against other families and the clinicians who treat them, so the product wasn't built for one household's habits.

01

Lived experience

We supported a loved one through FBT ourselves, logging every meal and weigh-in by hand for two long years. We documented where the work broke down: at the table, at handoffs between caregivers, and before appointments.

LearnedLogging took time away from the meal itself, and the parent needed that time to be present.

02

Conversations with caregiver families

Dozens of interviews with parents and caregivers in FBT, covering their daily routines, the tools they had tried, and what they dreaded about mealtimes.

LearnedFamilies were patching together spreadsheets, notes, and diet apps. The diet apps actively worked against treatment.

03

Sessions with dietitians

Working sessions with a registered dietitian on calorie ranges, Plate-by-Plate, and recovery-safe language, plus ongoing review as the product evolves.

LearnedThe target is a range set by the care team. Clinicians want the trend between visits, not every bite.

04

Care team input

Conversations with therapists, doctors, and the nutrition team about what they need from families between appointments and what they never want a family or patient to see.

LearnedSharing had to be view-only and revocable, and the family had to stay in control of the data.

05

Beta with 4 families

An Android beta with four families using the app at real meals, with feedback gathered through check-ins, interviews, and surveys.

LearnedPending. Still in beta.

04 · Creative direction

Fierce toward Ed. Gentle toward the family.

Recovery tools tend to sound like a clinic or a diet app. I wanted neither. The creative bet was the name itself: Let's Kill Ed. It turns a diagnosis into a shared enemy and gives an exhausted family a rallying cry. Ed is the illness, never the child. Once that's clear, the family stops fighting each other and starts fighting it together.

That one idea set the rules for everything that followed: the mark, the voice, the color, and how the app behaves at the table. Every decision answers to the same tension, and the vision for the product sits in the middle of it.

Every screen should make this meal less challenging.

Toward the illness

Unapologetic, never negotiating.

  • The name says what families feel and rarely get to say out loud.
  • The sword in the mark is the tool to fight with.
  • The voice never bargains with the disorder. Food is fuel for recovery, not a test to pass.
Toward the family

Warm, calm, on their side.

  • The butterfly the mark opens into is hope, and the recovery ahead.
  • Slate and gold lower the temperature, with rounded type that softens every number.
  • The language never blames. A hard day is information, not failure.

The rules that came out of it

01

Enough is the goal

Calorie targets work as a minimum to reach, not a ceiling. Weight is charted as restoration. Nothing in the product rewards eating less.

02

Separate the illness from the person

Naming the disorder "Ed" lets the family face it together, without blame or shame. The voice of the product sits on the family's side.

03

Design for the parent at 6 p.m.

Exhausted, one hand free, mid-meal. A photo replaces typing, primary actions are large and few, and nothing needs a tutorial.

04

Private by design

Recovery data belongs to the family. It lives in their own Google Drive, and they choose who sees it.

05 · Visual craft

Gentle enough for the table, clear enough for the care team.

Clinical tools feel cold, and wellness apps feel like they're selling something. I aimed between them. A calm slate blue carries the interface, and a warm gold marks hope and action. Nunito's rounded forms soften every number on the screen. Generous radii, soft surfaces, and large type are there for tired eyes and small screens.

The mark carries the story. The eyes come from the name our family gave the illness. The sword is the tool to fight it with, and the shape opens into a butterfly, a symbol of recovery.

Brand mark

Let's Kill Ed wordmark lockup

Palette

Slate#3D5A80
Gold#F5B800
Ink#1F2933
Slate light#E8EEF4
Gold wash#FFF8E1
Muted#5A6672

Type · Nunito

Snap a photo. Calories in seconds.
Rounded, warm, and legible at a glance, even on a hard night.
Log mealJoin the betaShare with care team
Logging a meal: a photo of a dinner plate, ready to analyze
CaptureA photo replaces typing. One action, one hand.
The meal itemized automatically with calories per food and a total
AnalyzeAI identifies each food and estimates it against USDA data. Every item stays editable.
Home screen: today's calorie progress toward the goal, a meal checklist, and a daily reminder
TodayProgress toward enough, a meal checklist, and a supportive daily note.
Progress chart of weight and daily calories over a year, with weight recovering
ProgressWeight and nutrition over time, in recovery-focused language.
History: meals and weigh-ins organized by day
HistoryMeals and weigh-ins by day, ready to share with the care team.
Settings: patient profile, treatment goals, light or dark mode, and a helpline
ProfileTreatment goals, light or dark mode, and a helpline one tap away.

Screens show demo data for a fictional user.

06 · Product thinking

Structure the product around the pace of recovery.

Family-based treatment moves in phases, and what a family needs changes with each one. The beta focuses on the heaviest phase, when parents carry every meal. The roadmap follows the arc from there, so guidance stays relevant and responsibility can shift back to the young person when the care team says it's time.

Now

Parents lead meals

Fast logging, progress toward the care team's target, and a clear record to share between appointments.

Next

Hands-on psychoeducation

Working with a dietitian partner on plating exercises and structured guidance for each phase of support.

Later

Control returns gradually

Support for handing choices back, tied to progress the family and clinicians agree on, not to a calendar. The app recedes as the family needs it less.

07 · From system to build

Two people, one standard.

A small team can't afford drift between design and code. I defined the system first in Claude Design, as named colors, type styles, and components, then used Claude for AI-assisted design-to-code so new screens came out on-system by default. That freed our time for the decisions that mattered: tone, edge cases, and the moments when a family is struggling.

The same approach scales up. Clear components and written principles are what let AI tools, and new designers, produce work that meets the bar without a principal reviewing every pixel.

08 · Where it stands

In beta, and free, always.

Beta
Live on Android
4
Beta families
$0
Cost to families, always

09 · What carries forward

How to build a health app people stay with.

Building in health care means building consciously. Every product decision affects someone's health, privacy, and trust. These are the lessons I'd bring to any patient experience.

  • 01
    Clarity, simplicity, and intuitiveness keep people in the app. Patients open a health app on top of everything else they're managing. If it takes effort to understand, they stop opening it. Every extra step is a reason to leave.In LKEA meal log went from typing every item to one photo.
  • 02
    Privacy is a design decision, not just a legal one. HIPAA sets the minimum. Patients notice the rest: what's collected, where it lives, who can see it, and how easily they can take it back. Collect less, explain more, and make consent visible and reversible.In LKEData lives in the family's own Google Drive, with view-only sharing they can revoke and a clear path to delete everything.
  • 03
    Start from the clinical model, not the screen. Most treatments have an arc: onboarding, titration, side effects, plateaus, maintenance. When the product's structure follows that arc, the right guidance shows up at the right moment.In LKEThe roadmap follows FBT's phases.
  • 04
    Treat every number as clinical content. Weight, dose, and calories all carry meaning and risk. Decide with clinicians what to show, when, to whom, and in what words. A number that motivates one patient can derail another.In LKECalorie goals work as a minimum, and weight is framed as restoration.
  • 05
    The patient isn't the only user. Caregivers, clinicians, pharmacists, and support teams all touch the experience. Design the handoffs between them, because that's where care falls apart.In LKEThe caregiver logs and the care team views, each with an experience built for their role.
  • 06
    Design for the hard day, not the happy path. Every patient has a bad week eventually: a missed dose, nausea, a stalled number, a meal that didn't happen. Those states should be calm, free of judgment, and offer one clear next step, including a route to a real person.In LKEA crisis helpline is one tap from every profile.
  • 07
    Keep AI honest and the human in charge. AI can remove real burden, but in health it has to show its work, stay editable, and stay inside its scope. It supports care decisions. It never makes them.In LKEAI estimates every item against USDA data, and the parent can edit any of it. The app is clear that it isn't medical advice.
  • 08
    Codify what works so it scales. Principles, patterns, and components turn one designer's judgment into a standard a whole org, and its AI tools, can meet on every screen.
← All workCase studies Case study 02 →Research is the foundation