When a wellbeing benefit has low usage, the easiest conclusion is that employees are not interested. That conclusion is usually too simple.
People care about their health. They also have limited time, different needs and varying levels of trust in anything connected to their employer. If support is hidden behind a benefits portal, explained once during onboarding or presented as a long list of services, low engagement is a predictable outcome.
The benefit is difficult to discover
Employees often learn about support when they join, then forget it exists. Months later, when sleep, stress, caring responsibilities or low mood become harder to manage, they may not remember the provider name or know where to start.
Discovery should not depend on memory. The system should surface relevant support in context, while still allowing the individual to choose what they use.
The support arrives at the wrong time
A lunchtime webinar can be useful, but it rarely meets the employee at the exact moment they need help. Wellbeing is continuous. Workload, sleep, movement, connection and confidence change across the week.
The most useful intervention is often small and timely: a lighter plan after poor sleep, a reminder to close the workday, a clear route to coaching or a prompt to use an existing service before the situation becomes urgent.
The offer is generic
A single wellbeing campaign cannot feel relevant to everyone. One employee may be managing a long term condition. Another may be returning from parental leave. Another may be physically well but disconnected from their work and team.
Personalisation does not need to mean diagnosis. It can mean asking what matters, learning from voluntary signals and adjusting guidance around the person's goals and circumstances.
Employees do not trust the boundary
People will hold back if they think personal wellbeing data could affect performance review, promotion or job security. Trust therefore has to be designed into the product and the programme.
Employers should see aggregate patterns above a clear reporting threshold. They should not receive individual health profiles or productivity scores. Employees should know what is collected, why it is used and what remains private.
Measure usefulness, not sign ups
A launch spike can make a programme look successful while saying little about whether it helped. Better questions include: Did people return? Did they complete a useful action? Did they find support faster? Did the programme reach different parts of the workforce? Did employees report that the support was relevant?
Engagement grows when the programme becomes easier to trust, easier to find and more useful in everyday life. That is a product and service design problem, not an employee motivation problem.
Whole is the daily layer that sits alongside the support your organisation already offers. Explore Whole for Teams.
