Discovery sounds abstract until you walk through it. Imagine a Kathmandu clinic wanting online appointments and patient reminders. Here is how discovery would unfold.

Week 1: Stakeholder interviews

We talk to clinic owner, reception staff, and a few patients. Pain points emerge: phone overload, no-shows, double bookings on paper.

Mapping current workflow

We document how appointments happen today — who calls, how slots are tracked, what happens when doctors run late.

Defining users and roles

Patients book online; reception manages schedule; doctors view daily list; admin handles settings. Each role gets distinct permissions.

Core user flows

Book appointment, reschedule, SMS reminder, staff override, doctor availability — sketched step by step with edge cases like holidays.

MVP vs later

MVP: booking, reminders, admin calendar. Phase two: payments, telemedicine, EHR integration. Explicitly out of scope for v1.

Technical notes

SMS gateway in Nepal, mobile-first UI, HIPAA-minded data handling even if full compliance comes later, hosting choice.

Deliverables at end of discovery

Product brief, wireframes for five core screens, backlog with estimates, risks list, and proposed eight-week MVP timeline.

Why this matters

The clinic sees exactly what they are buying before development starts. Surprises drop; estimates firm up.

The takeaway

Discovery turns a vague "we need an app" into flows, roles, MVP scope, and a credible plan — illustrated here with a clinic, applicable to any domain.

Hedztech runs discovery like this for real clients. See MVP development or book a workshop.