Dental Care · Florence, KYHealthcare Product Design
I led the end-to-end design and development of a scalable dental care discovery platform that improved patient trust, treatment discoverability, local SEO, appointment conversion, and long-term content scalability.
The practice needed more than a visual refresh. Patients arrived with different levels of urgency and confidence: routine care, cosmetic research, emergency needs, sleep/TMJ education, and financing questions.
The old experience was service-first and brochure-like. The new platform needed to support discovery, trust-building, education, local search, and appointment conversion while remaining maintainable as the practice grows.
The problem lived across three layers: patient comprehension, business growth, and platform scalability.
The redesign was guided by four product principles that shaped navigation, service pages, homepage hierarchy, CTAs, content depth, and implementation.
Provider credibility, reviews, years in practice, local relevance, and payment context appear before high-commitment actions.
Navigation and service cards use symptoms, goals, and care categories instead of long dental treatment lists.
Florence, Northern Kentucky, Boone County, and Greater Cincinnati are treated as decision context, not footer-only metadata.
Reusable service, local SEO, article, trust, and contact modules support growth without rebuilding page-by-page.
Discovery was framed around insight and implication, not activity count.
Local dentists, cosmetic practices, emergency pages, and specialty service pages compete on trust, speed, and clarity more than visual novelty.
Lead with credible local context, clear care categories, reviews, and direct pathways instead of generic “beautiful smile” messaging.
Users search by urgency, symptom, service, city, and confidence level. A routine patient and emergency patient should not receive the same pathway.
Create distinct pathways for family dentistry, cosmetic dentistry, emergency care, sleep/TMJ, financing, and patient resources.
Provider story, reviews, FAQs, awards, service explanations, and payment context are conversion infrastructure, not supporting content.
Repeat trust signals and practical next-step context throughout high-intent sections and service detail pages.
Florence, Northern Kentucky, Boone County, and Greater Cincinnati search intent needed a scalable structure for current and future pages.
Design reusable local SEO templates with service-specific metadata, city relevance, FAQs, and region-aware copy.
These archetypes translated search intent, urgency, and confidence level into product decisions.
“I need a reliable dentist for my family without making this complicated.”
Find routine care, scheduling clarity, insurance/payment context, and family-friendly reassurance.
Surface family dentistry, appointment options, insurance/payment content, and calm trust markers early.
“I want to compare options before I commit to changing my smile.”
Compare whitening, veneers, bonding, Invisalign, outcomes, cost, and provider credibility.
Organize cosmetic services as comparison-friendly pathways with outcome-focused education and credibility cues.
“I need to know if you can help me now.”
Find immediate reassurance, phone visibility, hours, location confidence, and clear next steps.
Make emergency pathways phone-first, direct, and location-aware with minimal navigation friction.
“I need to understand whether these symptoms connect to dental care.”
Learn symptoms, treatment credibility, and whether the practice handles specialized needs.
Build education-led pages that explain symptoms, treatment relevance, and next steps without forcing immediate conversion.
“I need to understand payment options before I feel comfortable reaching out.”
Find transparent payment options, insurance context, financing information, and low-pressure next steps.
Treat financing as a primary care-discovery pathway instead of burying it near the end of the experience.
The journey was redesigned as a decision-making flow from search intent to conversion.
User question: Can this practice help with my city, symptom, service, or “near me” need?
Design response: Location-aware metadata, service landing paths, and local relevance signals.
User question: Am I in the right place, and does this provider feel credible?
Design response: Hero hierarchy, provider credibility, reviews, service scope, and Florence/NKY context.
User question: What are my options, what does this involve, and what will it cost?
Design response: Service explanations, FAQs, testimonials, payment context, and patient-language content.
User question: Should I call, request an appointment, read more, or compare services?
Design response: CTA hierarchy, article pathways, service cards, and low-pressure contact options.
User question: What happens after I reach out?
Design response: Appointment/contact flows, phone-first emergency actions, and expectation-setting copy.
Navigation moved from clinic-first to patient-intent-first.
Home → About → Services → Contact
Home → Family Dentistry → Cosmetic Dentistry → Emergency Care → Sleep & TMJ → Financing → Patient Resources → Contact
Service pathways were clarified around patient goals instead of long clinical lists, making the site easier to scan and easier to scale.
The system exists to make trust, conversion, local SEO, and content scalability repeatable.
Instead of presenting pixels, the case study is organized around product capabilities.
Patients needed to find care by goal, symptom, urgency, and confidence level instead of interpreting long treatment lists.
Create service pathways, homepage sections, symptom-led content, and scannable service cards.
Family, cosmetic, emergency, sleep/TMJ, financing, and resource paths guide users into the right depth of content.
Clearer service discovery and more understandable treatment pathways.
Trust signals were too easy to miss before users were asked to take action.
Repeat provider story, reviews, awards, years in practice, local relevance, and credibility modules across the experience.
Trust cards and provider modules support both homepage scanning and deeper service evaluation.
Stronger confidence before conversion and better support for healthcare decision-making.
Routine, cosmetic, emergency, and cost-conscious patients needed different action paths.
Design CTA hierarchy around intent, with phone-first emergency routes and lower-friction contact options.
Appointment/contact modules, persistent action points, emergency phone visibility, and expectation-setting copy.
Clearer appointment conversion paths without forcing every user into the same CTA.
The practice needed stronger discoverability across Florence, Northern Kentucky, Boone County, and Greater Cincinnati.
Make local relevance part of the UX and content architecture, not only metadata.
City-specific content patterns, service-specific metadata, nearby-region targeting, and reusable page templates.
Stronger local search foundation and future-ready service expansion.
Future services, articles, FAQs, and local pages needed to scale without one-off page builds.
Define reusable service and article structures with CMS-ready content relationships.
Service templates, article layouts, FAQ modules, provider credibility blocks, and local page structures.
Scalable content model and easier long-term maintenance.
The experience needed healthcare credibility, accessible interaction patterns, and consistent page composition.
Build reusable UI components, typography rules, CTA hierarchy, form patterns, and accessibility standards.
Service cards, trust cards, contact modules, article layouts, local templates, and mobile-first responsive patterns.
Reusable component system and responsive production implementation.
Audit, competitive research, patient intent mapping, and local SEO review.
Problem framing, archetypes, success criteria, IA, and content model.
Wireframes, visual system, component library, page templates, and CTA hierarchy.
Next.js implementation, responsive layouts, SEO metadata, reusable components, and production deployment.
Accessibility checks, responsive testing, content QA, browser review, and performance review.
Production site shipped at drronelliott.com.
Foundation supports future services, city pages, educational content, and conversion improvements.
Patients needed scannable pathways by goal and urgency.
Created service cards for family, cosmetic, emergency, sleep/TMJ, financing, and resources.
Less exhaustive on first scan, but much easier to understand.
Improved service discovery and self-selection.
Trust often appeared too late in competitor experiences.
Distributed reviews, provider credibility, years in practice, and local relevance across key sections.
More repetition, but better confidence-building.
Supported conversion before high-friction CTAs.
Nearby-city and service-intent pages would not scale as hard-coded one-offs.
Defined reusable local page structure, metadata, FAQs, and service relationships.
Requires stronger content governance.
Future-ready local search foundation.
Users search by need, symptom, and confidence level.
Reframed navigation and content around patient goals.
Some clinical precision moves deeper into detail pages.
Reduced interpretation burden for patients.
Healthcare users need reassurance more than spectacle.
Used restrained surfaces, clear hierarchy, and steady CTA patterns.
Less visually loud, more trust-focused.
Better fit for dental care discovery.
High-intent and emergency users may act from mobile search.
Prioritized phone visibility, sticky action logic, and short contact paths.
Requires careful CTA hierarchy.
Improved mobile action clarity.
The outcome was a live product foundation for patient discovery, trust, conversion, content scalability, local SEO, and implementation quality.
This project reinforced that healthcare product design is not about making a site look modern. It is about reducing uncertainty, building trust before conversion, and creating scalable systems that allow the business to grow without increasing operational complexity.
The strongest work happened at the intersection of research, architecture, content, visual system design, and production implementation. I translated patient uncertainty into service pathways, business goals into local SEO and conversion systems, and design decisions into reusable Next.js components.
AI helped accelerate synthesis, content exploration, and documentation, but final judgment stayed grounded in patient confidence, accessibility, healthcare credibility, and technical feasibility.
The site is live at drronelliott.com for patients across Florence, Northern Kentucky, and Greater Cincinnati.
