DEV Community

Cover image for We Built It Right. Nobody Logged In

We Built It Right. Nobody Logged In

There's a special kind of quiet in a launch-week dashboard that isn't moving.

I've seen it happen to genuinely well-built healthcare products. Secure. Compliant. Cleanly engineered. The team did everything "right" — and the people it was built for didn't log in twice.

Nobody wants to hear the diagnosis, because it isn't technical: compliance keeps you out of trouble; it doesn't create adoption. Those are two different jobs, and most healthcare builds are fully resourced for the first and quietly hopeful about the second.

Here's the test that would have saved every one of those launches, and it costs nothing:

Who is the least confident person who has to use this — and does it work for them?

Not the 30-year-old founder demoing on this year's phone. The 74-year-old patient on a five-year-old Android who doesn't especially trust apps with her health information and will give up — permanently, politely — after one confusing screen. Design for her and everyone else finds it easy. Design for yourself and you'll spend launch month refreshing a flat chart.

The second adoption-killer hides on the other side of the counter. Founders spec the patient experience in loving detail — booking, records, messages — and forget that somebody at the clinic has to answer those messages, confirm those bookings, upload those results. The staff side is half the product. It's also the half that decides whether the clinic actually rolls the thing out, because software the front desk hates has a way of never getting mentioned to patients.

So before the feature list, two unglamorous questions: what does the least confident user see in their first sixty seconds, and what does the front desk see all day? Get those right and the fancy features get their chance. Get them wrong and the fancy features launch into silence.

We broke down the full version — what a patient portal actually needs, what it costs, and the adoption problem most builds ignore — here: Patient Portal Development: What to Build, What It Costs, and Why Nobody Logs In

Top comments (0)