Chelsey Wiley
PLATFORM · GOVERNANCE
Governance as a product surface: turning a high-stakes rebrand into a routine release.
MyBSWHealth is one of the highest-rated patient apps in the country. A business-wide rebrand couldn't afford to break its usability, accessibility, or performance. The strategic move was to stop treating the design system as a deliverable and start treating it as a governance surface.
30%
reduction in rework across the rebrand cycle through governance-led design system strategy
Top
Rated
patient app in the U.S. — rating maintained through a full visual rebrand
On-Time
delivery across multiple sprints and multiple development teams
Permanent
wireframe library became the team's ongoing governance source
CLIENT
Baylor Scott & White
ROLE
Senior Product Lead
SCOPE
Multi-platform design governance
APPROACH
Agile audits
Figma library
EXECUTIVE SUMMARY
MyBSWHealth is one of the highest-rated patient apps in the country — integrating MyChart, pharmacy, same-day care, and behavioral-science-driven engagement. When Baylor Scott & White Health rebranded across the business, the app couldn't afford a tactical rework cycle. Usability, accessibility, and performance were non-negotiable.
I led the design system strategy that turned the rebrand into a governance discipline rather than a redesign sprint. By auditing the existing system, separating functional governance from visual style, and instituting a Figma wireframe library that operated as a working document across active sprints, rework dropped by 30%. The work also surfaced inconsistencies that had accumulated quietly over years — accessibility and usability improvements that compounded long after the rebrand shipped.
THE BUSINESS PROBLEM
A top-rated app, a hard deadline, and no margin for rework.
The MyBSWHealth app's rating wasn't an aesthetic achievement — it was an operational outcome of accessibility, performance, and interaction design that thousands of patients depended on daily. Any change to the app was high-risk.
The business rebrand was a forcing function: the app had to reflect the new identity within months. But the traditional approach — design in hi-fi, ship to dev, fix in production — was guaranteed to fail. Time was too short, the cost of rework too high, and the surface area of "what could break" too broad.
"
A wireframe library, on its surface, is a deliverable. As an operating-model decision, it's what turned a high-risk rebrand into a routine release.
REFLECTION · BSW WIREFRAME LIBRARY
THE STRATEGIC DECISION
Separate functional governance from visual style.
I made the call to treat the design system not as a deliverable but as a governance surface. The question wasn't "what does the new brand look like?" — it was: "what does the team need to be able to test, decide, and ship without breaking the app?"
That reframe moved the project from a redesign sprint into an operating-model investment. The strategic decision was to build a wireframe library that locked down behavior, accessibility, and component logic so the visual team could iterate on brand expression without rediscovering interaction patterns for every screen.
THE SYSTEM INTERVENTION
Insert a governance layer between design and implementation.
I led a cross-functional audit of the existing design system with designers, developers, and product owners. We documented every component, classified it by functional role rather than visual treatment, and consolidated redundant elements. Components that varied only by color became single wireframe entries with documented variant rules.
The wireframe library was implemented in Figma as a living document that ran alongside active sprints. We instituted controlled checkpoints — updates rolled out at fixed intervals so they wouldn't disrupt in-flight work — and built a publishing-and-review discipline that made the library a trusted source rather than a noisy one.
A three-layer governance architecture: visual design iterates above, product implementation ships below, and the wireframe library sits between them as the contract both sides agree to. The middle layer is the strategic intervention.
OUTCOMES & MEASUREABLE IMPACT
What changed, in numbers and in operating model.
30%
Rework reduced across the rebrand cycle — design team tested designs more rapidly and consistently against governed components.
∞
Permanent practice: the wireframe library remained in use as the team's ongoing governance source long after the rebrand shipped.
0
Broken accessibility, performance, or UX targets. The app's top patient-app rating held through the full visual rebrand.
↑
Hidden technical debt — accumulated inconsistencies across years of releases — surfaced during the audit and was systematically retired.
WHAT THIS DEMONSTRATES
Treat governance as a product, not a constraint.
A wireframe library, on its surface, is a deliverable. As an operating-model decision, it's what turned a high-risk rebrand into a routine release. The pattern is the same whether the system being governed is a design library, an API platform, or an AI orchestration layer: insert the governance where humans need to trust the system, and make the path of least resistance the safe path.
That's the discipline now driving the work at Aircon. AI doesn't deliver value as raw capability — it delivers value as a governed surface that operators can trust. Decision systems need the same separation the wireframe library introduced here: the substrate is stable, the expression on top can iterate, and the surface between them is the product.