Chelsey Wiley
HEALTHCARE · PLATFORM STRATEGY
Unifying a fractured product landscape at Baylor Scott & White Health.
How aligning multiple competing roadmaps into one strategic plan returned 62% Digital ROI and delivered preventative care to 4,500+ patients who would otherwise have missed it.
CLIENT
Baylor Scott & White
ROLE
Senior Product Lead
METHODOLOGY
SAFe Agile
SCOPE
70+ cross-functional contributors
62%
Digital ROI increase across the consolidated product portfolio
4,500+
Patients reached with preventative care, well above target
3
Disconnected workflows unified into one cohesive experience
9 mo
End-to-end rollout managed without disrupting in-flight work
EXECUTIVE SUMMARY
At Baylor Scott & White Health, one of the largest nonprofit health systems in Texas, the digital product organization had fractured into competing roadmaps — each team building toward its own vision, duplicating effort, and degrading the patient experience.
I led the consolidation initiative that brought these efforts into a single strategic plan, aligning teams around shared system architecture, APIs, and a unified product operating model. The outcome: Digital ROI up 62%, staffing overhead reduced, and three previously disconnected workflows consolidated into a single preventative care experience that reached 4,500+ patients above target. The work became the foundation for the health system's formal digital product roadmap practice — a permanent operating-model shift.
THE BUSINESS PROBLEM
Excellent local work, compounding into a globally costly system.
Baylor Scott & White Health serves 3M+ patients across hospitals, clinics, and digital platforms. Its digital product organization had grown faster than its operating model — and the result was a fractured product landscape. Each department maintained its own roadmap. Teams duplicated effort across projects that should have been shared. Patients experienced disjointed workflows that mirrored the org chart instead of their actual care journey.
Investment was high. Visible return was low. And no one had formally requested a consolidated roadmap — the gap was systemic, the kind of problem that doesn't appear on any team's backlog because it lives in the white space between teams.
Before: five teams running independent roadmaps with no shared view of dependencies. After: an ecosystem-mapped system with a unified roadmap acting as the operating layer.
"
The biggest challenge wasn't technical but cultural. I needed to be more than just a manager — I needed to be a bridge.
- REFLECTION · PLATFORM STRATEGY
THE STRATEGIC DECISION
Treat the problem as a leadership intervention, not a planning exercise.
I recognized that the problem wasn't technical and couldn't be solved with a better Jira workflow. It was an operating-model problem: the organization lacked a shared view of how its products fit together, and without that view, every team's optimization was locally rational and globally costly.
The decision was to take ownership of the broader vision — to become the advocate for an org-wide product operating model rather than serve as a manager within one team's roadmap. That meant standing up the governance scaffolding the organization didn't yet have: ecosystem maps, system blueprints, and open roadmap rituals that made the cross-team strategy visible and contestable.
THE SYSTEM INTERVENTION
Build the governance the org didn't yet have.
I worked one-on-one with designers, product managers, and developers across every team to map the actual product ecosystem. We surfaced the hidden interdependencies in an ecosystem diagram — APIs, integrations, shared design systems, overlapping user journeys. For most contributors, this was the first time they had seen how their work intersected with the rest of the organization.
From there, we built the system blueprint that became the basis for the consolidated roadmap: a single map of products, integrations, and dependencies that every team could reference. I established open roadmap meetings as a recurring governance ritual — not status reporting, but a forum where teams co-owned the strategic vision.
The rollout ran over 9 months under SAFe Agile, with deliberate sequencing to avoid disrupting in-flight work. I provided weekly updates to leadership in PowerPoint, facilitated cross-team alignment sessions in Miro, and stayed visible as the primary advocate for the unified approach — not because the org needed convincing once, but because operating-model shifts require sustained leadership presence to land.
OUTCOMES & MEASUREABLE IMPACT
What changed, in numbers.
62%
Digital ROI increase through reduced staffing overhead and elimination of duplicate work across the product portfolio.
3:1
Previously disconnected preventative-care workflows consolidated into a single cohesive experience on the mobile app.
4,500+
Patients reached with critical preventative care through the consolidated mobile workflow — well above the original target.
∞
The consolidation became the foundation of the health system's formal digital product roadmap practice — a permanent operating-model shift.
WHAT THIS DEMONSTRATES
The work that compounds most is rarely on anyone's backlog.
The teams at Baylor Scott & White were each doing excellent work; the system around them was failing them. The leadership move was to see the gap, take ownership of it without being asked, and build the governance scaffolding — diagrams, rituals, shared blueprints — that turned a cultural problem into a measurable operating-model improvement.
That's the pattern I bring to platform and product organizations: see the system, build the operating model, make the outcomes legible to leadership.
It's the same discipline now driving AI orchestration and governance work with Aircon, where the surface is different but the problem is the same — teams need a shared view of how decisions flow through a platform before they can scale.