A 0-to-1 UX Case Study Example, Torn Down (Nuzzle)

A 0 to 1 ux case study is one of the hardest to write well, because there is usually no shipped product and no production data. The temptation is to invent impact. This teardown walks through Nuzzle — a fictional, self-initiated concept — to show how a new-product case study can stay credible by being honest about what it did and did not prove.

Nuzzle is a mobile app that guides first-time pet owners through the overwhelming first 90 days: vaccinations, feeding, training, and vet visits. It is an example portfolio built with Folioverse, so the project is realistic but not a real launch.

Recruiter 30-second scan: What problem was being solved? What did the designer personally do? Which decisions were shaped by evidence? And — for a concept — is the designer honest about results, or inventing them?

Case context

• Project type: 0-to-1, self-initiated concept
• Role: sole product designer, partnered with a founder/PM and one engineer
• Duration: 8 weeks, concept to validated prototype

A good 0-to-1 teardown starts by separating the project from the person’s contribution. Here the boundary is clear: the designer owned product design end to end, with a small team for product and engineering input.

Weak version:

“We built a new app for pet owners.”

Strong version:

“I was the sole product designer on an 8-week concept. I owned research, framing, flows, and the prototype, working with a founder/PM and one engineer.”

The problem this case proves

A 0-to-1 case is strongest when the problem is framed around a real human tension, not a market opportunity.

Weak version:

“There was no good app for new pet owners.”

Strong version:

“New pet owners are anxious and overwhelmed. The knowledge to do it right exists — but it’s scattered across Google, breeder PDFs, and forums — while existing pet apps are feature-bloated marketplaces, not a calm guide for someone who just got their first puppy.”

The strong version gives the design work a target: reduce overwhelm, not add features.

What the designer did — and how they framed it

The case shows real 0-to-1 work: eight interviews with people who had gotten a pet in the last six months, and a competitive scan of five pet apps. The sharpest move is the framing.

The job-to-be-done was written as: “help me not screw up the first months without making me feel like I’m failing.”

That single sentence does a lot of work. It names the functional need (don’t screw up) and the emotional need (don’t feel like a failure) at once — and the emotional half drives most of the later decisions.

Key decision 1: a “This week” home, not a feature menu

Evidence: interviews surfaced overwhelm as the dominant feeling.

Alternative considered: a full feature dashboard, like most pet apps.

Weak version:

“I designed a clean home screen.”

Strong version:

“I made the home a ‘This week’ view that surfaces only what matters right now — not a giant feature menu — because the core problem was overwhelm. Showing less was the point.”

This is the moment the case proves product judgment: the designer removed surface area on purpose.

Key decision 2: a personalized timeline from a 3-question setup

Evidence: guidance only feels trustworthy when it feels made-for-me.

Alternative considered: a generic checklist for all pets.

Weak version:

“I added onboarding to personalize the app.”

Strong version:

“A 3-question setup — pet type, age, and source — generates a personalized care timeline, so the guidance feels specific instead of generic. The onboarding earns the right to give advice.”

Key decision 3: tone as a design decision

Evidence: the user is anxious, not lazy.

Alternative considered: standard, neutral reminder copy.

Weak version:

“I wrote friendly notification copy.”

Strong version:

“For an anxious first-time owner, a non-alarming, warm reminder tone was a design decision, not a copy afterthought. A reminder that says ‘Mango’s second vaccination is coming up Friday — want to add it?’ reduces stress instead of adding it.”

This is the strongest teardown signal: the designer treats voice as part of the experience, tied directly to the user’s emotional state.

Outcome and evidence — the honest part

This is where most 0-to-1 case studies break. Nuzzle does not.

Weak version:

“The app improved user confidence and engagement.”

Strong version:

“This is a concept, so there are no production funnel metrics. I validated direction with a prototype test on six new owners: comprehension was clear and self-rated confidence rose meaningfully. A smoke-test landing page collected early waitlist interest. I’m careful not to claim numbers it doesn’t have.”

A reviewer trusts this more, not less. It shows the designer understands the difference between validation and proof.

What makes this teardown worth studying

• The problem is framed around a human tension, with the emotional need named explicitly.
• Every key decision points back to one insight: the user is overwhelmed, so restraint wins.
• Results are honest. A concept is presented as a concept, with real but limited evidence.
• The hardest 0-to-1 lesson is shown, not stated: for an anxious user, the design problem is restraint and tone, not features.

For the full structure behind a case like this, use the UX case study guide. Browse more UX case study examples, including a B2B logistics dashboard teardown. If this is your first portfolio piece, start with how to write a UX case study with no experience.