Two health systems. One patient journey.

The Situation

 Two hospital systems had just become one, and neither of their technology stacks was built to be the other's. Each brought its own martech platforms, its own IT and marketing teams, and its own vendor relationships, built independently and rarely compatible with each other. Layered on top was the reality of consumer healthcare itself, patients now expect the kind of digital experience they get everywhere else, and a fractured, duplicated technology landscape was the opposite of what that required. 

The Real Problem

On the surface, this looked like a technology and vendor selection decision. The real problem ran deeper. Two teams that had never worked together were now expected to operate as one, each with legitimate ownership over systems they had built and trusted, and neither with an unbiased view of what the new organization actually needed.

Left alone, influence wins over patients, and politics wins over strategy. What the organization needed was not a vendor scorecard. It was one shared standard, how well each option served the patient journey, not which legacy team it came from.

The Work

We started with the patient journey and the business outcomes it needed to support, then worked backward to the technology, rather than starting with the platforms and hoping the experience would follow:

• Evaluated existing platforms, internal teams, and outside vendors across both legacy organizations, and graded each against how it served the evolving consumer healthcare journey
• Evaluated budgeting to ensure every recommendation was financially sound for the newly combined organization
• Evaluated platforms and capabilities against future needs, including planned feature rollouts, so the organization would not outgrow its decision within a year
• Evaluated adjacent technology platforms to protect uninterrupted, bidirectional data feeds, a requirement that carries real weight in healthcare, where broken data continuity affects patient care and compliance alike
• Delivered new workflow recommendations designed for efficiency at scale
• Identified where internal training was needed to sustain the new organization
• Built a phased rollout plan designed to limit disruption, recognizing that a health system cannot pause patient facing operations to change its technology
  
  
  

The Outcome

• An optimized patient journey, built by working backward from the experience patients actually needed rather than forward from whatever technology already existed
• One unified technology recommendation replacing two competing, duplicated stacks, evaluated against patient experience rather than legacy team ownership
• A clear, budgeted roadmap delivered through a phased rollout that protected continuity of care
• New workflows that delivered real efficiencies of scale, enabling the combined organization to do more with the same teams
• Uninterrupted, bidirectional data continuity across every adjacent system, preserving the accuracy and compliance a health system depends on

Why It Worked

A merger does not just combine two technology stacks. It combines two teams, two cultures, and two sets of assumptions about what good looks like, and no vendor comparison can resolve that on its own. Starting with the patient journey and the business outcomes it needed to achieve, then working backward to the platforms and workflows that would deliver it, gave the organization one outside, unbiased standard to evaluate everything against.

We were not brought in to pick a winner between two internal teams. We were brought in to give a newly merged organization a single, coherent technology strategy built around the people it ultimately serves.