Book a strategy call

Interactive · 3 rounds · about 90 seconds

Fewer user errors start as design decisions.

Three small decisions from a health-tracking app. Pick the version you'd ship, then see what we chose and why.

Start round 1 or book a strategy call

Fictional product. Carelog is an invented health-tracking app made for this demo, nothing here is medical advice, and the screens are simplified mock-ups. Each reveal shows the decision we would make and the reasoning behind it, not measured data.

The brief
Product
Carelog, an imaginary mobile app for tracking medication and home health readings.
Users
Adults managing a long-term condition, who log a few things a day and often feel anxious about getting it wrong.
Constraints
Health data must be right, people may be stressed or tired, and the app must never replace medical advice.
Our part
Show how we reason about three moments: entering a wrong value, a missed dose, and reading a week of data.

Your call

Choose the version you would ship in each round. There is no wrong answer, only trade-offs.

  1. 01Entering values
  2. 02Daily doses
  3. 03Reading data

Round 1 of 3 · Undo

The impossible reading

Ana types 1200 instead of 120 for her systolic blood pressure. What should happen?

What decided it for you? (optional)

We chose B: catch the mistake where it happens

  • The error appears next to the field, so there is nothing to remember and nothing to dismiss.
  • A suggested fix (“Did you mean 120?”) turns the error into one tap.
  • A wrong reading never reaches the record, which matters because people may share these numbers with a doctor.

Trade-off: Live checks need sensible ranges, and some real readings are unusual. The message warns without blocking when a value is rare but possible.

How we'd measure it: how often readings are corrected after saving, how long a correction takes, and how many entries are abandoned.

Book a strategy call

Want this thinking on your product? We start with one screen of yours.

Round 2 of 3 · Hidden states

The missed dose

Ana's 08:00 medication is now four hours late. How should the app tell her?

What decided it for you? (optional)

We chose A: say what is safe, and let her choose

  • The card tells her what to do next, including that she should not double up. An alarm only says that something is wrong.
  • Taken, Skip and Remind me are all honest answers, so she doesn't tap “Taken” just to silence the alarm and corrupt her record.
  • A calm tone fits people who feel anxious about their health, and it keeps working in public places.

Trade-off: A quiet card is easier to ignore, so critical medication can also use a follow-up notification. Which medication counts as critical is a clinical decision, not a design one.

How we'd measure it: how many reminders get a real answer, how often “Taken” is later corrected, and how long a missed dose stays unanswered.

Book a strategy call

Want this thinking on your product? We start with one screen of yours.

Round 3 of 3 · Making sense of data

The week in numbers

Ana opens her blood pressure history before her appointment. What should she see?

What decided it for you? (optional)

We chose B: lead with meaning, keep the detail close

  • Most people want to know if things are fine, and a trend answers that faster than a list of numbers.
  • One sentence in plain words tells her what to do, without pretending to be a diagnosis.
  • The exact values stay one tap away for people who want them, and for the doctor.

Trade-off: A summary is a judgement, so the wording needs clinical review and must never claim to diagnose. Showing the table as well keeps the raw data available.

How we'd measure it: whether people understand their trend in a short test, how often they open the details, and how prepared they feel before an appointment.

Book a strategy call

Want this thinking on your product? We start with one screen of yours.

The thinking behind all three

Each round is a decision about a moment where a person might be worried or make a mistake. Design for those moments, and the everyday flow gets calmer too.

  • Catch mistakes where they happenCheck the value in the field, and offer the likely fix.
  • Say what is safe, then let people chooseA calm, honest message beats an alarm.
  • Lead with meaning, keep the detail closeA plain sentence first, the exact numbers one tap away.
Book a strategy call

What we can do for your product

  • Strategy & researchJourney maps and user flows before any screen is drawn.
  • UX & UI designFrom wireframes to high-fidelity UI in dark and light mode.
  • Design-to-dev handoffDesign systems and specs your developers can build from.

Have a screen where users get stuck?

Tell us where it hurts. We'll show you how we would approach it.

Book a strategy call

Or write to contact@zenetic.net