Lean UX Diary: How a Health Startup Used Micro-Experiments to Validate Feature Prioritization

Design · 5 min read

MedLoop, a telehealth startup, faced a common early-stage dilemma: stakeholders proposed many features, from asynchronous messaging to detailed symptom trackers. Instead of building full features, the product team ran micro-experiments — low-fidelity prototypes, concierge workflows, and gated previews — to measure real user interest and impact.

They deployed sixteen experiments over nine weeks, each designed to answer a single question (e.g., 'Will users rebook if we offer a push reminder?'). Examples included an SMS-based pilot for async follow-ups, a clickable prototype for a symptom-check widget, and a limited diary feature rolled out to 5% of users. Each experiment captured one primary metric and short qualitative follow-ups.

The outcome: three features were greenlit for full development because they improved retention or revenue signals, six were re-scoped as lower priority, and seven were shelved — saving roughly 18 person-months of development. The practice reinforced that disciplined micro-learning can prevent feature bloat and align teams around evidence rather than opinion.