The short version: a straightforward post about Washington State's long-term care policy revealed that for many employees, eldercare isn't a neutral benefits topic, it's tangled up with identity, family duty, and guilt.

The Post That Divided My Comments

Two weeks ago I posted about the State of Washington's decision to start paying for long-term care for its residents. Not a hot take, a straightforward share of one state's approach to a real problem. It reached nearly 34,000 people. As I reviewed the comments, I realized I wasn't reading a conversation about policy anymore. I was seeing arguments focused on who is allowed, or not, to provide help to their family members.

One camp said care for aging parents is an inside job; family handles it, full stop. Bringing in an outsider from a state program, a company or agency isn't support, it's outsourcing something you owe someone. The other camp said the opposite with just as much conviction. These readers shared that utilizing any available resource is a resource worth taking; refusing help out of pride or guilt is how people end up burned out, broke, or both. I simply brought the state's decision to provide long-term care without advocating any particular outcomes. Yet the reaction in many comments wasn't about the policy. It was about identity.

Why Eldercare Isn't Like Other Benefits

That's the part HR leaders miss, because it's not visible anywhere in a benefits binder. A 401K match doesn't touch anyone's sense of who they are. Dental coverage doesn't collide with what someone's parents taught them about family duty, or what their faith says about caring for elders, or what they personally experienced when their own mother cared for their grandmother twenty years ago.

Eldercare does all three at once. Every employee walks into this topic already carrying a script about what a good son or daughter does, and that script was written long before they ever worked for you.

Why Well-Intentioned Rollouts Backfire

Here's the mechanism: most benefits fail from lack of awareness. This one can fail from the opposite problem, too much visibility, delivered wrong. Roll out an eldercare resource company-wide with a big announcement and a mandatory informational session, and the employee who believes care is a family obligation doesn't feel supported. They feel exposed, maybe even judged in front of colleagues who now see a vulnerability in their home life that was a private, family matter. Meanwhile the employee desperately looking for exactly that resource may have already quietly disengaged, months before you launched anything, because nothing about your culture told them it was safe to ask.

The Real Risk For Employers

So the real risk isn't that your workforce won't want help. It's that you don't actually know which employees even want it, which ones will resent the offer, and which ones are too far into crisis mode to notice you built anything at all. Most HR teams design eldercare support the way they design every other benefit: build it, announce it, hope it lands. That approach assumes neutral territory. This topic has never been neutral territory.

Find Out Before You Build Anything

The employers getting this right aren't guessing. They're finding out, quietly and methodically, what their own workforce actually needs before they build or broadcast a single thing. That's the rationale behind the Workplace Caregiver Needs Survey, a quick, easy and anonymous way to see where your people stand before you spend a dollar or send an email that lands wrong with half the company. Share it with your team through the Workplace Caregiver Needs Survey.