Return Home

HealthEquity: Product Team Reorganization

6 UX designers and 3 product managers quit in 1 year. Leadership thought they needed tougher hires. The problem was the system those hires walked into.

Role
UX Designer and Product Manager, embedded consultant
Scope
Product team structure and organization
Engagement
Outside consultant through SolutionStream

The problem

Leadership told me they needed a product leader with thick enough skin to handle the senior team.

6 UX designers and 3 product managers had walked out in the previous year. Releases missed their deadlines. The products that shipped did not gain traction. Leadership had a theory: the product people they kept hiring were not senior or tough enough to push ideas through a strong-willed executive bench.

They hired me as an embedded consultant through SolutionStream. They wanted someone emotionally tough. They first asked for product work. As I worked, the real problem came into view. The structure around the product team needed to change.

What I started with

I talked to the people who had quit before I talked to the people still there. Each one described the same environment. They were pulled in every direction, and blamed by every department for not featuring its interests prominently enough. One of them put it simply: "It's not worth the battle."

They were not leaving because they were soft. The system was designed to grind them down.

Expertise at the top

Two VPs knew the product line so well they could no longer see it through a member's eyes.

Departments through the product team

Marketing, customer service, claims, and account services each pushed for prominence. None of them fought each other directly. They fought through the product people instead, because they were the connectors.

One executive override

An executive overrode decisions and forced products beyond the understanding of most members.

No way to decide

The company had no functional way to make product decisions. Conflict landed on the product team.

The revolving door was the predictable result of this structure.

Who it serves

Members

HealthEquity is an HSA bank. Plain language and simpler flows mattered most to them.

Departments

Marketing, customer service, claims, and account services each needed the product to serve their goals.

The product team

It needed a way to make decisions without standing alone in the conflict.

The VPs

They needed to see the product through a member's eyes again.

The approach

I restructured the product team and how it worked with sales, the VPs, the call center, the warehouse, marketing, development, project management, product management, and UX. I shaped the work to fit the company's culture rather than replace it.

Step 1: Build cross-functional guilds

Each guild took one product issue and brought the warring department heads, including the VPs, into one conversation. I directed every conversation back to what the user needed.

Step 2: Run discovery in sprints

Research came first, then user story maps, user flows, and wireframes, sketched together. Department heads had their hands on the artifacts. Conflicts surfaced during co-creation where they could be resolved.

Step 3: Put real members in the room

A Voice of Customer group of real HealthEquity members joined regular calls and tested ideas and prototypes at every stage. Member data ended most disputes faster than internal arguments could.

Step 4: Share one roadmap

I built a research repository so teams stopped starting every study from scratch. I set up a scrum of scrums for the product organization, open to department heads, with notes distributed afterward. It pulled the company into one roadmap and shared priorities. Once alignment held, we shortened the meeting.

Step 5: Build research inside customer service

I taught the customer service team discovery tactics and met with them weekly. They gained product influence, and we gained a steady stream of member insight from the people closest to members.

Step 6: Work with each department head

Some learned through explanation. Others learned through real engagements.

The decisions

  • Department heads in the same room

    Options
    Route conflicts through product managers, or bring the department heads together.
    Gave up
    The product team's role as a neutral buffer.
    Why
    Department heads needed to see each other's points of view.
  • Research as the arbiter

    Options
    Argue internally, or test with members.
    Gave up
    Fast internal decisions.
    Why
    Real member data ended most disputes faster than debate.
  • Discovery created together

    Options
    Review finished designs, or create them together.
    Gave up
    The speed of a single product lead.
    Why
    Hands-on artifacts won buy-in, and conflicts surfaced early.
  • Research inside customer service

    Options
    Keep research central, or embed it in customer service.
    Gave up
    Central control of research.
    Why
    Customer service gained product influence in exchange for member insight.

How I worked with the executive team

I sat in the VP meetings. I used what I was learning across the company to shape decisions at the top. I taught the executive team what to expect from product people and how to recognize a good one.

What I would do differently

  • Hire more product people and UX designers sooner

    I could have made the change quicker.

  • Bring key people from each group together earlier

    I kept many of them separate for too long. They collaborated, but more cross-collaboration would have helped, especially with the VPs.

The outcome

The revolving door stopped. The director of UX I hired stayed, and so did the product team I built. I saw several of them still there three years later.

Departments stopped fighting through the product people. They negotiated through the work itself: guilds, sprints, member data, and a research repository everyone could use. The VPs who had blocked decisions sat in rooms with the member's voice. They wanted to build good products, and this helped with direction.

In the final stretch, I hired two UX designers, 2 product managers, and a director of UX. I handed the director the playbook.

Building something that needs a clear map? Let's talk.

Tell me where the route got unclear. We'll find the way together.