The brochure does not have to work a closing shift
An employee benefit can look useful during a presentation and become difficult to use the moment someone needs it. Office hours, unfamiliar instructions and uncertainty about cost all arrive outside the brochure, where the employee has an actual schedule to manage.
Kobby Amoah, CEO of River Health, makes that gap central to his ChatGTM conversation with Michael Beck and Chad Horn. He describes designing around hourly workers: people whose shifts may change, whose free time is limited and whose next available hour may not match a conventional appointment calendar.
The discussion offers a product-design lesson for hospitality employers. Offering a service and making it usable are separate accomplishments. A business that wants employees to experience the value needs to examine the steps between enrollment and a successful first use.
Begin with the person trying to get through the day
Amoah distinguishes the experience of receiving care from the arrangements used to pay for it. They affect each other, but an employee encounters both as practical questions: whom do I contact, when can I reach them and what happens next?
He describes virtual primary care, continuity with a provider and prescription delivery as elements of River Health's approach at the time of the interview. His explanation returns repeatedly to convenience and access. A step that appears minor to a designer can become a real obstacle after a long shift.
For employers assessing any benefit, the useful exercise is to follow an ordinary user journey rather than stop at a feature comparison. Ask a representative to show the first contact, the response path, the instructions and the route to help when someone gets confused. Review the actual plan's scope and limits alongside that demonstration.
The point is to understand the employee's work, not assume technology has removed it. An app can simplify a process, but it can also become one more place where a person has to figure things out alone.
A simpler system can still need an explanation
One of Amoah's most useful observations concerns the payment experience he describes. River Health uses a branded payment card for specified services with participating providers. To someone accustomed to presenting an insurance card, that different interaction can raise immediate questions.
The design may be intended to simplify payment, but familiarity belongs to the older process. Amoah acknowledges the learning curve. Employees need to understand what they have received and how to use it before a new model can feel easier.
That applies well beyond healthcare. Payroll tools, scheduling systems and employee assistance programs often arrive with assumptions about what users will find obvious. A clear demonstration, accessible instructions and a visible support contact can be part of the benefit itself.
Good onboarding should also explain boundaries. Employees should be able to tell what a service includes, what it does not and where to ask questions. Clarity earns more trust than an expansive promise that later requires interpretation.
The employer has a user experience too
Amoah separates the tools built for members from those built for employers. On the employer side, he describes payroll connections, eligibility information and changes when people leave or return. Restaurants do not need another benefit that works only because someone manually reconciles everything behind it.
That administrative experience deserves its own evaluation. Identify where employee information originates, who checks changes and what happens when records disagree. Ask the provider to demonstrate an exception rather than only the clean enrollment path.
This is also where implementation ownership matters. A product can promise reduced administration while still requiring careful setup and ongoing oversight. Knowing who handles each handoff helps the employer avoid discovering an unassigned task when an employee is already waiting for an answer.
Measure use and value without confusing them
Amoah discusses utilization, affordability, retention and missed shifts as different ways his team examines outcomes. He describes quarterly business reviews as moments when employers can look beyond the original sales presentation and examine what employees are actually experiencing.
Those measures should remain distinct. Enrollment shows that someone joined. Utilization shows that a service was used. Satisfaction provides another perspective, while retention also reflects wages, management, schedules and other conditions. A comparison can be informative without establishing that a single benefit caused the entire change.
An employer can ask for clearly defined reporting periods, appropriate aggregate data and an explanation of the comparison being made. Pair that review with employee feedback about the process. The benefit earns its place when the people it was designed to support can understand it and make use of it in the lives they actually have.
