The Gap Between Website Rebuilds and Patient Adoption
Your health system spent months rebuilding its website. It was a rare strategic investment, the kind most health systems make maybe once a decade. You were excited about the outcome.
Then the data came back.
Patients are still calling instead of scheduling online. Clinical staff didn’t buy into the new site. Stakeholders are frustrated.
This scenario plays out more often than you’d think, and it’s almost never because the design was bad.
At Modea, we work with large health systems on digital strategy and implementation. Through discovery research, we’ve started to see clear patterns in what’s preventing adoption.
The Problem: What the Data Really Reveals
One metric tells us a lot about website rebuilds: online patient scheduling adoption. We’ve worked with health systems where baseline adoption rates were as low as 9%. That’s notably low given that most patients today expect self-service and robust digital capabilities.
We worked with a health system where 73% of patients started the online scheduling process but gave up midway and just called the call center instead.
What we found was telling. Only 20% of providers in that system offered online scheduling. So the website was essentially telling patients they could do something most providers didn’t support. Patients tried, got frustrated, and picked up the phone.
Here’s what really mattered: when we asked how this constraint got missed, nobody could answer. Clinical, operational, and IT teams had never been part of the conversation.
Nobody had asked upfront:
- Do we really support this at scale?
- What are our real constraints?
- Who needs to believe in this for it to work?
The health system had designed a beautiful website. It just couldn’t deliver on what it promised.
This is how website rebuilds can fall short. A rebuild typically starts with one department owning the vision, the budget, and the timeline. Clinical leadership, operations, IT, and patient experience teams often join the conversation only after the work has already been commissioned.
Website rebuilds and replatforming are genuinely complex. They need to handle mobile, where over 65% of traffic comes from mobile devices, perform well, work intuitively, and support multiple functional capabilities. When project teams fail to involve the people who have to operate these systems early, organizational constraints remain invisible.
Then the website launches. Reality hits fast.
Clinical staff think, “This doesn’t represent what we actually do or what we’re known for.” Operations teams realize the workflows don’t fit, and IT discovers the tech stack doesn’t align with what’s been built.
The work has been commissioned. It launches anyway. Patients don’t use it, and the call center is still overwhelmed with scheduling questions.
The rebuild doesn’t fall short because of design quality. It falls short because nobody asked the fundamental questions upfront:
- What can we support operationally?
- What are our real constraints?
- Who needs to be part of this for it to succeed?
The Right Approach: Strategy Before Replatforming
We’ve learned that governance and stakeholder engagement need to be woven into your strategy from the very beginning. It’s not overhead. It’s what makes the rebuild work.
Discovery
You start by understanding what you’re working with. That means conversations with marketing, clinical leadership, IT, operations, and patient experience. What do these groups need? What problems are they trying to solve? What constraints are they operating under?
And you need data: usage patterns, patient drop-off points, mobile vs. desktop behavior, SEO and GEO performance, heuristic reviews, and interviews with patients, referring physicians, and the people who will actually use the site. What’s working? What’s broken? What’s frustrating people?
In the health system we mentioned earlier, discovery revealed a 73% scheduling dropout rate. More importantly, it showed that only certain departments and providers had the infrastructure to support online booking. That one insight completely changed the strategic direction.
Synthesis
Now you take what you learned and build a realistic roadmap. What should the future state look like? What are other health systems doing? What constraints do you need to work around?
For that health system, the strategy shifted entirely. Instead of “rebuild a beautiful website that promotes online scheduling,” it became this:
- Phase 1: Make online scheduling work seamlessly for the providers who already support it, giving patients a great experience with the options available.
- Phase 2: Build organizational support for expanding online scheduling to more providers using the success of Phase 1.
This phased approach ensured continuity while expanding provider participation and increasing self-service adoption.
You’re not building a wishlist. You’re building something that acknowledges the constraints you actually face.
Executive Briefing and Socialization
This is where most website rebuilds fall apart. Stakeholder engagement needs to happen in parallel with discovery and synthesis, not as a separate final step after all the decisions have been made.
A lot of health systems find success by standing up a cross-functional steering committee: a core group of stakeholders from clinical, IT, operations, and business who can speak to their departments’ needs and vision.
Regular steering meetings share progress as discovery findings come in and the strategy develops. Concerns surface early, buy-in builds gradually, and by the time you present the final strategy, there are no surprises because stakeholders have been part of the journey.
Implementation Roadmap
You hand the roadmap off to the team that’s going to build it. It’s built with the implementation team in mind. It’s realistic, phased, accounts for constraints and dependencies, and gives people a clear path to execution.
What This Produces
When you do this right, adoption increases, call volume decreases, stakeholders align around a shared direction, patient satisfaction improves, and implementation timelines hold because you’ve addressed the underlying constraints before launch.
On the flip side, skipping governance and stakeholder engagement leads to siloed decisions, poor patient experiences, and a once-in-a-decade investment that never reaches its potential.
The Bottom Line
Website rebuilds don’t fall short because of design quality. They fall short when strategy doesn’t account for organizational reality.
Do the discovery. Bring the right people into the conversation. Build the roadmap together before you design and build.
Those weeks of strategy work aren’t overhead. They’re what separate a transformation that lands from an expensive rebuild that sits unused.
How We Deliver
We view website replatforming and rebuilds as strategic business initiatives, not design projects. We don’t jump into tool selection or platform decisions until we’ve answered the hard questions: What organizational constraints are we really facing? What’s preventing adoption? Who needs to believe in this?
The most successful rebuilds are grounded in structured discovery. They surface the gaps between what patients need and what your organization can realistically support, bring stakeholders together around a shared understanding of strategy, and build roadmaps that account for real constraints and dependencies.
If you’re planning a website replatforming or rebuild, the real first step isn’t picking a platform. It’s making sure you have the governance structures, organizational alignment, and strategic clarity needed to make it successful.
With Contributions From:
Jagannath Chakravarty | VP of Strategy & Design
Jagannath provided strategic insights and design direction for this article. He leads our product vision, focusing on the intersection of human-centered design and long-term business strategy.
Have questions about your organization’s strategy? Contact the Modea team to start a conversation, or Connect with Jagannath on LinkedIn.