Skip to main content

HealthEdge

Wellframe Ride-Alongs: Care Without a Foundation

Wellframe's care management staff were carrying bigger caseloads every year. Everyone had an opinion on how to fix it. None of it explained what was actually broken.

  • Built the entire ride-along research methodology myself, including HIPAA compliance and customer buy-in materials
  • 60+ hours in the field across 4 health plans, personally leading more than 30 of them
  • Synthesized it all by hand into five themes, then took them directly to senior leadership
  • 60% of the findings shipped as real product within a year
  • Two customers renewed their contracts directly because of the work that followed

No Foundation to Stand On

Screenshot of the Wellframe care management dashboard used by care managers every day.

The Wellframe care management dashboard care managers used every day.

Health care in the US has problems, and everyone working inside it knows it. Care management exists to keep costs down and support the highest-risk members who need more than an annual visit can give them; it's designed to keep people out of the ER. But it's a cost-avoidance function, not a revenue driver: it doesn't bring money in, it keeps money from going out. That makes it exactly the kind of budget line that gets scrutinized hardest when a company is under pressure, and health plans have been under pressure. Medicare Advantage alone posted a $5.7 billion industry-wide underwriting loss in 2024.

Care management staff were managing larger panels every year, across both digital and phone-based outreach, without the training or the tools to do either one well. Patients expected them to be responsive and know their history. Supervisors expected them to carry more cases while staying fully compliant on documentation and fluent in digital tools. Leadership expected them to do more with less, and save money while doing it. Nobody had given them a foundation to stand on for any of it.

What we needed to know

Illustration representing information overload for care management staff — too many inputs, not enough clear signal.

Too much noise, not enough signal: the everyday reality for care management staff.

Our signal-to-noise ratio was off. Frontline staff complained to their supervisors. Supervisors brought it to leadership, who translated it into budget asks and goals. Leadership handed it to Customer Service, who turned it into product idea tickets. Every ticket was actionable. None of them explained the problem underneath it.

And every partner used the system differently to begin with. We had 16 different health plans, each with staff building their own workflows from scratch, nothing coordinated, everyone wanting something different.

The goal wasn't a redesign. It was an honest picture of where digital care management actually broke down for the people using it every day, and a plan specific enough to hold across all 16 of them. That meant going past dashboards and support tickets and watching the actual work happen.

Empathize: The Ride-Alongs

I built the research program from the ground up: the format, the scope, the call script, how notes got taken, how customers needed to be looped in, and the HIPAA compliance work to keep it clean on PII and PHI. I packaged all of it and handed it to our customer partners, who worked any legal questions out with their own teams at the leadership level above me. My job was building the case for the program, not negotiating it.

Over 60 hours of ride-alongs with 18 nurses and staff supervisors across 2023 and 2024, spanning four health plans and roughly a dozen different lines of business — commercial, Medicare, and more, each running the system a little differently. I was the lead researcher on more than 30 of those hours myself, following a care manager through their actual day rather than asking them to describe it to me after the fact. On the rest, I was still in the room: listening, taking notes, and feeding questions to whichever designer or PM was leading that particular session.

Training showed how to use WF but not the process on how WF should be used for caseload. WF should have trained our management, then they could have trained us on WF. I can figure out the rest.

Staff ride-along

Three surveys ran alongside the ride-alongs. Two went to staff, covering onboarding and day-to-day efficiency. The third went to members directly and pulled in the largest pool by far: 2,800 responses. Separately, I ran 25 in-depth interviews and validation sessions with our own internal subject matter experts, to pressure-test what the field research was telling us before it went anywhere near a roadmap.

I owned everything downstream of the research, too: synthesizing all of it into the internal insights deck, running the client readouts, and presenting the findings live at one of our quarterly customer conferences.

Photo of raw categorized notes from an actual ride-along session, member journey pain points and feedback grouped on sticky notes.

Raw categorized notes from an actual ride-along session: member journey pain points, feedback, and follow-up questions.

60+ hours of ride-alongs. 18 nurses and staff supervisors, four health plans, 2023–2024.

I was lead researcher on 30-plus of those hours myself, following a care manager through their actual day instead of asking them to describe it after the fact.

2,800 member survey responses. Two more surveys covered staff onboarding and efficiency.

Run alongside the ride-alongs, not instead of them. The member survey pulled in the largest pool by far.

25 SME interviews and validation sessions.

Every finding from the field got pressure-tested against our own internal experts before it went near a roadmap.

16 health plans. No two running the system the same way.

The plan had to hold across all of them, not just the easiest one to fix.

Define: Five Themes, One Dead Elephant in the Room

The research collapsed into five themes. Staff had no stable foundation: some were toggling between as many as 9 different systems and spending 20 to 45 minutes just building a member profile before they could make a single call. Retention lived or died on the first day. And staff were still held to telephonic documentation requirements that never adjusted for how differently digital actually worked, so they were quietly doing double the paperwork just to stay compliant.

Onboarding was its own fight, and a different kind of problem than the others. It was sales, even though nobody on staff had been hired or trained to sell anything. Most of these were cold calls: a member picks up the phone, and within two minutes has to hear that they're not healthy, that a stranger wants to help fix that, that it's free, and that step one is downloading an app. That's four reasons to hang up before anyone's said anything reassuring, aimed at clinical staff who'd never needed a sales instinct before. Only half of invited members ever converted.

In spite of all that needed to be overcome to be successful, the fifth theme is where the real story is.

Slide from the roadshow deck showing the five-theme framework (Theme A through E) mapped against the digital care management journey.

The five-theme framework mapped against the digital care management journey, from the roadshow deck shared with SLT and customers.

The Ah-Ha Moment: There Were Two Elephants

I am double documenting messages sent back and forth, which is time consuming.

Staff ride-along

I wish I could be notified when a member has left a message. With my workload I am only able to log in 2x a day.

Staff Efficiency Survey

For years before this research, digital care management's whole premise was built around one target: shorten the time it took staff to actually talk to a member. Telephonic care management could mean over an hour on a single call: understanding a member's medical background, their current conditions, screening for social determinants of health, and working through a 100+ question intake assessment. Then, after hanging up, staff had to remember the conversation and document all of it into the system of record, which usually took another thirty minutes. Staff could be tied up with one member for as much as two hours.

Digital solved that directly, and not just by trimming a phone call. Digital intake assessments let members fill out and submit their own information instead of reciting it live. Secure, encrypted chat let staff and members communicate asynchronously instead of both needing to be on a call at the same time. What used to take the better part of two hours dropped to a couple of minutes of interaction time.

We'd killed the problem we set out to kill. Dead, buried, no remorse.

The ah-ha was what showed up once it was dead. Per touch, the work on either side of the interaction shrank hard too: telephonic prep and documentation together ran close to an hour, digital cut that to ten or twenty minutes. But staff weren't doing eight of these a day anymore. They were doing forty. Ten to twenty minutes, forty times over, adds up to as much daily overhead as the old hour-long version ever did, and at the high end, more. The bottleneck didn't shrink. It moved.

We'd spent years optimizing the middle of the interaction, and we'd won. Now the problem lived at the ends.

Slide showing the pre- and post-interaction time breakdown for telephonic versus digital care management, before and after the bottleneck moved.

The pre-/post-interaction time breakdown from the insights deck: telephonic vs. digital, before and after the bottleneck moved.

I am double documenting messages sent back and forth, which is time consuming.

Staff ride-along

I wish I could be notified when a member has left a message. With my workload I am only able to log in 2x a day.

Staff Efficiency Survey

Ideate: From Themes to a Roadmap

Every theme got broken down into multiple specific design questions, simplifying the problem instead of leaving it as a vague direction. The staff-foundation and onboarding themes became: how might we enrich a member's history so staff aren't rebuilding it from scratch every time, and how might we cut telephonic onboarding down using digital and marketing tools that don't need a live person on the phone. The Day 1 theme became: how might we match a member with genuinely relevant content the moment they onboard, instead of the generic welcome program that was underperforming everywhere. The overhead-and-documentation theme became: how might we take the pre- and post-interaction work off staff entirely, since that's exactly where the cost had moved.

This wasn't a slide deck that sat in a drive. Getting there meant manually synthesizing 60 hours of ride-along observations against three separate surveys and 25 SME interviews, by hand. There was no AI to help find the pattern connecting something a survey respondent wrote in a free-text box to something I'd watched happen on a ride-along weeks earlier; every one of those connections got made manually, until five patterns emerged instead of a hundred scattered anecdotes. Once they were named, this went to our Senior and Executive Leadership Teams directly, and became an ongoing roadmap roadshow across the company.

We took the same roadmap on the road externally too, running sessions with customers to walk them through the shift in direction before any of it shipped. For everyone who'd participated in the original research, we gave back individualized findings of their own: their own workflow gaps, their own change-management opportunities, training tips specific to their team, pain points pulled directly from their own workflows. It resonated. The support that came back was significant.

The features themselves went through their own prototype and test cycle. That's its own story, not this one.

Slide showing the detail view of each of the five themes, with supporting findings listed under each.
Slide mapping each theme to an opportunity area and specific "how might we" design questions for 2024.

Left: the detail view behind each theme. Right: how each theme mapped to specific design questions for 2024.

Results

Twenty distinct opportunity themes came out of the original Ride-Alongs. Sixty percent shipped as real product within a year, roughly sixteen named features. Personalized onboarding links replaced generic invitations. A Day 1 activation flow replaced the old first-touch experience. Members could browse and request enrollment into care programs that actually matched their condition instead of defaulting into the generic welcome track, directly answering the finding that condition-specific programs kept members where generic ones lost them. And the AI staff assistant idea, named explicitly in the original research as something staff wanted, shipped as a GenAI summarizer pilot in about eight weeks, championed personally by our CPO. I stayed on as a stakeholder on that one, weighing in on what design produced and shaping the final look, not running it day to day.

Screenshot of the personalized onboarding links feature, an access code pre-populated for a staff-invited member.
Screenshot of the member self-activation flow, guiding a new member through app setup.
Screenshot of the care manager dashboard showing member states and a status dropdown.
Screenshot of the new dashboard overview page, panel-wide engagement metrics and task completion.

Top: personalized onboarding links and member self-activation. Bottom: member states and the new dashboard overview.

That eight-week pilot didn't stop at eight weeks. It grew into something that now runs across 189,000-plus eligible members, summarizing more than 99% of them without hitting the model's context limit, tested at 3,000 daily active users. It didn't get there overnight. It got there because we stayed on it.

The data backed the shift toward personalization hard, and it showed up everywhere we looked. For example: what members saw when they onboarded played a huge role. Nearly a third of members stopped engaging entirely after the day they onboarded, and the biggest predictor of whether that happened wasn't the health plan or the staff caseload. It was what program they'd been placed in. Members onboarded into the generic Wellness program had a 45% abandonment rate within two weeks and an NPS of 41. Members onboarded into condition-specific programs like maternal health had a 17% abandonment rate and an NPS of 63 over the same window. Same platform, same company, same staff. The only variable was whether the content actually matched the person.

The clearest signal the work mattered wasn't in that data, though. It was that individual customers started asking for their own dedicated ride-along sessions after seeing what the original research turned up for them. I ran several more rounds specifically for two of them, mostly conducting those sessions myself, which pushed total observation time well past 100 hours across the full program.

Two enterprise health plan customers renewed their contracts in 2024 and 2025, directly because of what came out of those extra sessions and the support we built for their care staff. Not a services line under evaluation. Not a projection. A renewal, tied to a specific body of work.

We finally gave them that foundation to stand on.

Illustration of a care manager working at her desk, with member profile thumbnails displayed around her.

A care manager working through her panel, one member at a time.

Yeah, this is one I fixed.

Send a note →