Patient education, digital information and the path into a practice.
Skip to content
Business & digital growth · Selected project 59
Patient Navigation: The Appointment Began Before the Waiting Room
Patient-facing explanations and a campus navigation strategy reduced missed appointments across a regional healthcare network.
My role
Strategic Positioning Lead & Patient Journey Architect
Project context
Florida Health Systems & Regional Medical Networks
A confirmed appointment does not mean a patient has everything needed to arrive. The person may still be working out which location to visit, what the service involves and how to navigate an unfamiliar campus at a moment when their attention is already under pressure.
For this regional healthcare-network engagement, I worked on strategic positioning and the patient journey. I developed the authority narrative, planned the campus-navigation experience and wrote technical specifications for the web teams. Missed-appointment rates fell across major facilities, alongside a stronger regional reputation.
Authority needs to help the person reading
A healthcare organization can describe its expertise in language that means a great deal internally and very little to a patient trying to decide what happens next. The communication needs to connect the institution's capabilities with the practical questions a person brings to the page.
My role was to shape that explanation. Clinical facts and judgments remained with the clinicians and responsible institutional teams. The story needed to make expertise understandable without making the patient responsible for translating the organization's internal structure.
Arrival is part of the service experience
The campus-navigation plan addressed a stage that marketing can overlook: the period between deciding to attend and reaching the right destination. A digital experience should make the location relationship clear enough that a person can prepare for the visit.
That is a communication problem as well as an interface problem. Terminology, the order of information and the route from a service page to practical directions influence whether the experience feels manageable. A beautiful institutional page can still leave an ordinary question unanswered.
Requirements carried the patient perspective into development
I translated the intended experience into specifications for the web teams. The purpose was to make the patient-facing requirement visible within the build, rather than leave the technical team to infer it from a general request to improve navigation.
Good requirements explain why a piece of information belongs where it does and what the person needs to accomplish. They help connect positioning with use. The institution's public story and its practical journey should support each other, so that the confidence created by one is not immediately weakened by the other.
Fewer missed appointments, a clearer institutional experience
The engagement reduced missed-appointment rates across major clinical facilities. The work also supported the hospital’s reputation as a regional center of excellence.
The focus extended into the campus and the information needed to reach the appointment. A patient's experience with an organization begins well before anyone calls their name in a waiting room.