CASE STUDY 03

Three executive visions, one scheduling product

The CEO, CTO, and Director of Product could circle on patient scheduling for hours without landing anywhere. I anchored them on an artifact, showed them what they were really asking for, and we shipped a simpler model in about six months.

Role
Product Owner / Product Manager
Company
InteliChart
Timeline
2019–2022
Status
Launched, about six months from concept to production
  • Zero to one
  • Executive alignment
  • Configurable workflow
  • EHR integration

The problem

InteliChart needed self-service scheduling that worked for new and established patients and fed each practice's own workflows and EHR.

The CEO, CTO, and Director of Product all wanted a great product, but they had a hard time hearing each other. Each spoke a different language, and as they added requirements, the flows they described kept getting more convoluted. Conversations could go in circles for hours without reaching a decision.

The call

I moved the conversation out of the abstract and onto the table. I mapped what they were describing end to end and printed it, so they could see exactly what they were asking for: every branch, dependency, and exception. Next to it, I laid out my cleaner proposal, which still reached the end states each of them cared about.

Tangled flow versus clean flowTwo scheduling workflows drawn as flowcharts. The first, the flow the executives described, has many steps and decision points, with paths that loop back and cross. The second, the proposal, is a short path with a single decision whose two branches rejoin before the end.The flow they describedEvery branch, dependency, and exceptionThe proposalA short, clean path to bookTangled flow versus clean flowTwo scheduling workflows drawn as flowcharts. The first, the flow the executives described, has many steps and decision points, with paths that loop back and cross. The second, the proposal, is a short path with a single decision whose two branches rejoin before the end.The flow they describedEvery branch, dependency, and exceptionThe proposalA short, clean path to book

That gave us something concrete to react to. Instead of circling, we focused on the few points where their decisions actually mattered, and the visuals did a lot of the convincing.

The model we landed on was configurable decision trees. Practices define their own scheduling rules inside one common product, and patients get a short, clean path to book. In plain terms, the win was not building a convoluted workflow just because the request came from the top.

What we built

I partnered with UX on competitive research, then designed for two audiences: practices that needed control, and patients who needed booking to be easy.

Friendly on the outside. This was public-facing, so practices could configure what patients saw. Internal system language became plain, friendly appointment options.

Easy to put anywhere. The scheduler was simple to embed, and every provider had a unique booking URL. Practices could export all of it and hand it straight to their website admins.

Connected underneath. New and established patients could both book, with established patients matched to their existing records. API integrations fed appointments into each practice's practice management system and EHR.

Many ways in, one schedulerPatients arrive from a practice website, Google, or a provider's own booking URL. All of them lead to one scheduler, which sends appointments to the practice management system and the EHR.Practice websiteGoogleProvider URLsPatient ScheduleOne scheduler,each practice's rulesPM systemEHRMany ways in, one schedulerPatients arrive from a practice website, Google, or a provider's own booking URL. All of them lead to one scheduler, which sends appointments to the practice management system and the EHR.Practice websiteGoogleProvider URLsPatient ScheduleOne scheduler,each practice's rulesPM systemEHR

What changed

Patient Schedule went from concept to production in about six months, and despite the matching, configuration, and integration complexity, the launch went smoothly with no major production issues.

As new practices came on board, things stayed quiet in the best way. For a product that has to fit every practice's scheduling rules, quiet is a good review, and it's where the configurable model paid off.