The moment I knew something was broken
During a visit to an Aspen Dental office, before this project was assigned, I asked the Operations Manager about a dashboard widget called “Schedule Care or Refund.”
He didn’t touch it. Not because he didn’t need to, but because he had no idea what it was asking him to do.
Weeks later, leadership in Patient Financing and Revenue Cycle Management (RCM) brought me the same problem. I already knew why.
Operations Managers (OMs) run each Aspen Dental location, so their day rarely slows down. Many are also new to the job.
A system built for experts, used by everyone
When a patient takes out financing, a clock starts. There are three phases, each with its own rules and deadlines.
Miss a deadline in any phase and the lender takes the money back, whether or not anyone meant it to.
The 10-column queue built on top of it had no call to action:
- “Refund date” sounded final, but shifted with OM actions.
- “Care completed” meant Phase 3 of financing, not finished treatment.
- No care totals, so scheduled patients stayed on the list with no explanation.
From a data table to a tool for action
I facilitated a workshop with Patient Financing, its executives, and the territory managers who train OMs. We asked of every column: does an OM need this to do their job? We cut 10 columns to 5.
Cutting alone still didn’t tell an OM what to do, so I proposed a sixth: “Action Needed,” the exact next step to keep each patient’s financing on track, based on their phase and lender.
With RCM, I mapped every phase and lender combination to its instruction, then validated the state table with our PM and engineers so the instruction updates as a patient’s phase changes.
I also moved “Days Until Scheduled Refund” first, so OMs work the list top to bottom by urgency.
Two ideas didn’t make it:
Redesigning the front door
The dashboard widget leading into the queue had the same problem as the table: it put a red dollar figure up front, but not a next step. This was the widget the OM from my office visit never touched.
I replaced the red "Opportunity at risk" figure with a plain count, "6 accounts left to action," and a "2 refunding soon" badge that appears only in the 0–7 day window. I also renamed it from "Schedule Care or Refund" to "Upcoming Patient Financing Refunds," so it couldn't be mistaken for the dashboard's other scheduling widgets.
Round two would prove me half wrong about this.
Testing the language, not just the layout
In moderated sessions with 7 Operations and Regional Managers (3 months to 14 years of experience), 5 read the original date copy as one deadline instead of two.
I invited the SVP of Patient Financing and our product team to observe, so they'd see OMs' reactions firsthand.
“It feels like I have to finish everything by this one date. I don't get why there are two dates here.”
The simplest rewrite worked for all 7. Jargon mattered too: “charge out” confused people, while “provide over $100 worth of care” landed at every experience level.
What changed in three months
After a 50-office pilot, we launched to all 1,100+ locations, then compared refund dollars in the three months before and after rollout. No other process, staffing, or policy changes happened in that window.
“This makes it way easier to keep track of patients who will be refunded and when I should schedule them.”
I disagreed with the SVP, so I tested it
Months later, leadership asked for in-dashboard refund requests and a view of already-scheduled appointments. I disagreed with the second ask: the queue exists to show outstanding work, and a scheduled patient is finished work. Rather than argue from my own assumption, I designed both and tested them with 5 OMs.
“Why does it say ‘Not started’ if I already scheduled them? That’s confusing.”
No OM wanted scheduled patients on the list. I took that to the SVP of Patient Financing. He'd sat in on the first round of sessions, so the case was short: five OMs, none of whom wanted the view he'd asked for. He dropped the ask. The same sessions proved me half wrong on the widget: the dollar figure I’d cut came back.
Refund requestsMaking irreversible actions deliberate
Refunds used to need a separate ServiceNow ticket. I moved them into the queue's status dropdown alongside outreach tracking, with a confirmation step so nothing irreversible is submitted by accident.
Carrying the work into a new design system
Aspen is adopting a new design system, and I redesigned the full Operations Dashboard for it, across every role tab. Each task widget now names the report card metric it moves, so OMs see why a task matters, not only that it’s due. After launch, I’ll track task completion rates alongside the refund rate.
