As clinics grew, patient messaging turned into a quiet operational fire — inconsistent, costly, and risky. Everyone wanted a bulk-blast tool. I built the opposite: a governed system where every message needs a category and doctors get just 2 SMS a month. The constraint is what made it scale safely. No-shows dropped from 22% to 15%.
The broadcast setup — category first, a live SMS counter, and smart targeting built in.
Everyone was sending. No one was governing.
As clinics scaled, doctors and staff had to handle a flood of patient communication — schedule changes, reminders, follow-ups, closures, festival wishes, offers, health advice. It was all ad-hoc, manual, and uncontrolled. Each person messaged in their own tone, on their own timing, with their own wording. That variance looked harmless. It wasn't.
Discovery made the root cause clear: 8 doctor interviews, 5 with clinic assistants, workflow walkthroughs across 3 clinics, and an analysis of 1,200 appointments over six months. The findings pointed in one direction — the problem was structural, not a missing feature.
75% of doctors prioritized speed over flexibility — "I need quick sends, under two minutes." They didn't want a rich composer. They wanted safe defaults and almost no decisions. Every choice you ask a time-pressed doctor to make is a chance to get tone, timing or compliance wrong.
The instinct was to add capability. Research said subtract it. 80% of assistants made repetitive errors for lack of templates; 30% of sends were already excessive. So the design bet was to limit — locked categories, reusable templates, a hard SMS cap — because constraint is what makes communication safe at scale. Patients proved the point: relevant, timed messages got 65% higher response than generic blasts.
The whole system rests on one rule: no message exists without a category. You can't reach a send button by accident. Every broadcast walks a strict, sequential path — category, then group, then channel, then timing — and each step quietly enforces compliance and relevance before the next unlocks.
Eight locked types — Doctor Advice, Important Alert, Health Tips, Festival, Offer, Out of Office, Seasonal, General. Pick one before anything else. No free-form mass blast is possible.
Segment by ailment (e.g. T2DM), status and adherence level — so the right message reaches only the patients it's relevant to, cutting noise and lifting response.
Two SMS per doctor per month, full stop, with a live counter and a graceful limit-hit state. Push is unlimited. This one constraint controls cost, prevents spam, and forces intentional sends.
Reusable, approved, named templates so assistants stop rewriting the same message — eliminating the repetitive errors that wasted a fifth of their day.
| Before | After |
|---|---|
| Ad-hoc reminders relayed through staff | Predefined templates, set up in seconds |
| Manual texting, error-prone | Smart targeting to precise patient groups |
| Frequent missed follow-ups | Scheduled, automated outreach |
| Inconsistent, unlimited messaging | Controlled frequency via hard limits |
Measured, 3 months post-MVP
And the operational dividend
The team wanted unlimited bulk messaging. I argued for a hard cap — and had to prove that less sending meant more trust.
This was the hard part, and it wasn't a screen. Stakeholders were skeptical of limits — a 2-SMS cap sounds like crippling your own product. The instinct in a growth context is always "give users more power." But the research was unambiguous: 30% of existing sends were already excessive, compliance flags were piling up, and patients were tuning out. An unlimited tool would have scaled every one of those problems.
So I made the case with data, not opinion. I showed that relevant, limited messages outperformed blasts by 65%, that each compliance flag carried real regulatory and cost exposure, and that the cap would protect the engagement the team was trying to grow. The reframe landed: we weren't limiting communication, we were protecting its value. That turned skepticism into buy-in, and the constraint became the MVP's defining strength.
Introduce financial-literacy-style guidance for doctors earlier, so the value of the limit is obvious from day one rather than something they discover. And explore AI-assisted predictive targeting in the next iteration — early modelling suggests another 10–15% adherence lift by sending the right message to the right patient at the right moment.
Domain — Healthcare operations · doctor appointment & broadcast messaging
Role — UX Lead: product strategy, governance architecture
Timeline — 3 weeks, discovery to MVP release · system redesign, not feature design
Team — Me (UX Lead), 1 product designer, 1 product manager, with engineering & compliance stakeholders
What I owned — UX strategy, the patient-communication governance model, research with doctors and staff, information architecture, flow design, and the adoption & safety guardrails. UI detailing went to the designer; testing to the PM.