What We Shipped First, and Why It Was the Dashboard

Founders ask me how to scope an MVP without shipping something embarrassing. With Movement — Ichilov's patient-facing checkup app — the temptation was to launch the whole care journey at once: booking, questionnaires, results, post-visit summaries. I argued for sequencing around the single most load-bearing surface first: the glance-able dashboard. If a user opens the app and instantly sees their purchased checkups, next appointment, and latest results, the product already justifies its place on the home screen — even before every flow is polished. That's the MVP's job: prove the core promise, not catalog every feature. From there, the path to the full version was additive rather than corrective. The experiential self-assessment questionnaires — colorful, conversational, large tap targets — came next, because completion rate is the metric that makes the clinical side work, and that surface needed real craft time, not a rushed first pass. Booking and post-visit summaries layered on after. The lesson I'd give any founder: don't ship a thin slice of everything. Ship the one surface that makes the product worth reopening, get it genuinely right, then expand outward from proven value instead of patching a broad, shallow launch.
Related articles

About
Making complicated into easy for users.
Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.