Skip to content
Illustrative Case Study

The data was honest. It just read like bad news.

SkinSync's routine builder and tracking logic already worked. The sessions found exactly why an honest, well-built product still didn't feel trustworthy, and what a skincare app needs to do differently in the weeks before any real progress shows.

The brief

A product that asked before it gave anything back.

SkinSync's core habit loop was genuinely well-considered. None of that mattered to a user opening the app for the first time and being asked to configure a routine before understanding what it was for. The brief was to find out why a functionally sound product still left people uncertain, and what it would take to make the honesty already built into the data feel like care instead of a verdict.

01
Trust opened at 2 out of 5. Not because anything had gone wrong, but because the product asked users to set up before it had given them anything at all.
02
Weeks two and three, when skin genuinely hasn't changed yet, is where most users quietly stopped opening the app. The product had no way to acknowledge that stretch honestly.
03
Confusion scored higher than anxiety, 4 out of 5, anchored by ingredient conflict warnings with no way to tell "stop now" from "worth monitoring."
The process

Thirteen sessions. The same two weeks, every time.

The Aspiration Gap and the Anti-Principles sessions, run independently, both landed on the same moment: a user opens their progress photo two weeks in, sees almost nothing, and quietly starts to doubt the routine is working. The Heartbreak Scale put numbers against it, trust at 2 out of 5, anxiety at 3, confusion at 4, delight at 2.

Core PrinciplesThe Heartbreak Scale™75 min
DiscoveryThe Aspiration Gap™60 min
DiscoveryThe Identity Shift™45 min
DiscoveryThe First 60 Seconds™30 min
Brand PersonalityThe Dinner Party™15 min
Brand PersonalityThe Rejection Letter™30 min
Brand PersonalityThe Funeral Speech™20 min
Design PrinciplesDesign Principles Builder™60 min
Design PrinciplesThe Anti-Principles™40 min
Visual DirectionOpposite Ends™10 min
Visual DirectionMoodboard Speed Dating™15 min
Tone & CopyThe Voice Sort™40 min
Tone & CopyRead It Aloud™30 min
"Transform." "Glow up." "Flawless." "Instant." Every one of these landed on the Voice Sort's wrong pile. The words that belonged here were smaller: calm, clear, steady, honest.
Output 01: Strategy & Research

From is this going to judge me to I know my own skin.

The Feel Factor mapped three layers, first impression, the journey, identity transformation, and found the product asking something of the user at every one before it had given anything back. Visual Direction turned that into a specific, ownable register: calm authority built through restraint, neither clinical nor decorative.

The Feel Factor®
The Feel Factor

The Feel Factor®

Three layers, first impression, the journey, identity transformation, mapping a product with a sound habit loop that had not yet been designed to make anyone feel anything.

Trust measured at 2/5 on entry, not because the product had done anything wrong, but because it hadn't yet done anything to earn it.
Every layer was tested against one question: does this make the user feel more capable and more knowledgeable about their own skin, or simply like someone who followed instructions?
The desired shift isn't a better complexion. It's the quiet, earned belief: "my skin isn't a mystery, I can actually understand what it needs."
Download document →
User Personas
Discovery & Strategy

User Personas

Four personas, each carrying a distinct relationship with the product, grounding the emotional landmines named across the discovery sessions in specific people rather than an abstract user.

Priya Nair, the Anxious Experimenter: "I've spent so much money trying to fix my skin and I still don't actually know what's wrong with it."
Rachel Osei, the Methodical Tracker, captures the whole document's thesis in one line: "I don't want to be told my skin is doing well, I want to see why."
All four, independently, name the same two-week moment: opening a progress photo, seeing almost nothing, and starting to doubt whether the app or the routine is working.
Download document →
Visual Direction
Brand

Visual Direction

Calm authority built through restraint. Six words that held up under pressure across every session: calm, clear, steady, informed, gentle, honest, and everything each one rules out.

Opposite Ends placed SkinSync at the low end of information density and the high end of breathing room, a structural decision, not a stylistic one.
Explicitly ruled out: glossy "after" photography, gamified badges and confetti, dense dashboards, and conventional red alert colours for anything health-related.
A single muted accent colour, used sparingly enough that it never appears in more than one place at once.
Download document →
Plus 7 more documents in the full engagement
04
Research & Strategy
Research & Insights Report
05
Research & Strategy
The Aspiration Gap
06
Design
Design Principles
07
Brand
Copy Handbook
08
Brand
Tone & Copy
09
Design
Interaction Principles
10
Design
Animation and Interaction Guide
Output 02: The Design

Six screens, one honest timeline.

From the first question through to the four-week comparison that doesn't need to flatter anyone. Tap through the screens below.

Original
WAA
Output 03: Technology

A build order shaped by trust, not convenience.

Every phase in the roadmap follows the same rule as the design work: emotional dependencies come first, structure before surface, and the highest-risk assumptions get tested earliest. The stack was chosen to support a data model that has to hold up honestly for months, not just at launch.

Tech Stack Recommendations
Technical

Tech Stack Recommendations

React Native via Expo for a twice-daily habit product, NestJS and PostgreSQL for a data model that has to stay relationally sound as insights, patterns, and streaks accumulate over months.

PostHog self-hosted over a managed analytics service, since SkinSync handles personal health data and keeping behavioural analytics in infrastructure the team controls is the right privacy posture from day one.
TypeScript strict mode is non-negotiable, not a style preference, given how much of the data model, routines, products, ingredients, skin logs, depends on relationships that matter.
NestJS's enforced structure costs a little speed at the start and pays back once more than one engineer is working in a codebase built for Phase 2 features.
Download document →
Implementation Roadmap
Delivery

Implementation Roadmap

Four phases across sixteen weeks, sequenced by emotional dependency rather than conventional sprint logic: Emotional Foundation, Journey Architecture, Identity Layer, then Polish and Pre-Launch.

Phase 1 builds the onboarding and the full data model before a single insight or streak celebration is designed, since surface work on unresolved emotional architecture tends to look fine and feel wrong.
Ingredient conflict warnings are explicitly out of scope until the contextualisation layer exists. Shipping the flag without the explanation was named as a critical failure mode.
Success criteria include a specific, uncomfortable one: no user-reported confusion or support query mentions feeling pressured to sign up before trying the product.
Download document →
Plus 2 more documents in the full engagement
03
Technical
Technical Architecture
04
Technical
Build Cost Reference Guide
The result

A product judged on whether a user feels informed, not just whether the data is correct.

Trust at 2 out of 5 and confusion at 4 out of 5 pointed at the same root cause: honest information delivered without the context that makes it bearable. The response was a sequencing discipline specific enough to hold under delivery pressure, in the design work and in the sixteen-week build plan that protects it.

Give first, ask later
Skin type, then a pre-filled routine, then a single "today" screen. Account creation moves to after the first routine is logged, not before it.
A design for the difficult middle
Weeks two and three now have a job: surface small honest signals before the big ones arrive, and reframe a missed day as information rather than a broken streak.
No data point stands alone
Every observation, a breakout flag, a flat week, an ingredient conflict, ships with the context that makes it mean something, never just a number or a warning icon.
A build order that protects trust before speed
Emotional dependencies first, structure before surface, the riskiest assumptions tested earliest. The roadmap makes that order a constraint, not a suggestion.
More work

Other case studies