All articles
Employee Benefits

Employer Questions About Most Valued Employee Benefits

WHIA Team 12 min read
Washington employer and HR leader reviewing employee benefits options together

For Washington employers, finding the most valued employee benefits is not a matter of copying another company’s package. The right mix depends on who works for you, what employees need, what your organization can sustain, and how clearly people understand the benefits already offered. A deliberate review can help HR and leadership make those choices with better information.

Talk with a benefits advisor about your priorities

What Do Employees Mean When They Say a Benefit Is Valuable?

A benefit can be valuable because it helps an employee pay for care, makes a difficult life event easier, protects a family, or offers flexibility. Value is not identical for every person. An employee with recurring prescriptions may focus on drug coverage and provider access. A caregiver may care more about leave and schedule flexibility. A new hire may first need help understanding how to enroll and use the benefits.

For employers, “most valued” should mean more than the items employees mention first. Consider whether a benefit:

  • Addresses a real need among your workforce or a clearly defined employee group.
  • Is understandable and usable, not just listed in a handbook.
  • Fits the organization’s budget and operating needs over time.
  • Supports recruitment, retention, employee wellbeing, or another stated business goal.
  • Can be administered consistently and explained accurately.

That definition keeps the conversation grounded. A popular feature may not be affordable at the level employees expect. A less visible benefit may be important to employees who rely on it. Your goal is to see both the needs and tradeoffs before making changes. It can help to separate perceived value from actual use: low enrollment could mean a benefit is unnecessary, but it could also mean employees do not know about it, cannot afford their share, or find the rules confusing.

Which Benefit Categories Should Washington Employers Review?

Start with the core health plan, then look at the broader package. Do not treat every benefit as interchangeable. Medical coverage, employer-designed lifestyle benefits, HRAs, and voluntary benefits serve different purposes and have distinct plan and administrative considerations.

Benefit areaWhat it may addressQuestions for employers
Group medical coverageAccess to covered health services, subject to plan terms, provider networks, and cost sharingDo employees understand the network, deductible, prescriptions, and likely out-of-pocket costs?
Dental and vision coverageDental and vision services under the selected plan termsAre covered services and employee contributions clear? Do the options reflect employee interest?
Employer-designed lifestyle benefitsSupplemental perks selected by the employer to support defined workforce prioritiesWhat purpose does each perk serve, who can use it, and how will the employer explain its limits?
Health reimbursement arrangements (HRAs)Employer-funded reimbursement of eligible expenses under the arrangement’s rulesWhich HRA design fits the employer’s goals, and what setup, eligibility, and administration rules apply?
Voluntary benefitsOptional insurance products employees may choose, often with employee-paid costsDo employees understand what is optional, what it costs, and how it relates to the core health plan?
Leave, flexibility, and supportTime, schedule flexibility, or resources that may support employees’ circumstancesCan the organization offer the policy consistently, and does it meet applicable requirements?

This is a review framework, not a ranking. A benefit’s usefulness depends on its terms, employee circumstances, employer contributions, and how it fits with the rest of the package. For an overview of employer arrangements, see WHIA’s guides to how an HRA works and HRA health benefits. These resources can help frame questions, but the specific terms of any arrangement need to be confirmed before employees rely on them.

How Can You Find Out What Your Employees Value?

Use more than one way to hear from employees. A short survey can reveal broad patterns, while small-group conversations can help explain why a benefit matters. One-on-one conversations may make it easier for employees to raise a personal concern, but participation should be voluntary and privacy respected.

  1. Set a focused purpose. Explain that you are assessing benefit needs and understanding, not promising a particular change. State who will review responses and how the information will be used.
  2. Ask about needs before products. Invite employees to describe what is hard to manage today: affordability, finding care, understanding coverage, family needs, or enrollment steps. This reduces the risk of steering people toward a particular product.
  3. Ask everyone the same core questions. Examples include: Which current benefit do you rely on most, and why? Which benefit is hardest to understand? What situation do you wish the current package helped with? What would make enrollment or using coverage easier?
  4. Offer a way to respond privately. Some employees may not want to discuss health or family matters in a group. Avoid asking for diagnoses or other sensitive details when they are not needed for the decision.
  5. Look for patterns, not anecdotes alone. A vivid comment can be useful, but it does not automatically represent the whole workforce. Compare feedback across roles, locations, work schedules, and eligibility groups without exposing individual responses.
  6. Report back. Summarize what you heard, what you can investigate, and what is outside the current decision. Closing the loop builds trust even when the answer is not an immediate plan change.

Keep the survey short enough that employees can complete it without needing benefits expertise. Include an “I’m not sure” response so a lack of familiarity does not look like lack of interest. If you ask employees to rank priorities, distinguish between benefits they currently use and benefits they would like to learn about; these answers reveal different things. Share broad themes rather than raw comments when reporting results, and avoid slicing the data into groups so small that people could be identified. If several employees raise the same question about a plan feature, first confirm whether the issue is a communication gap, a service problem, or a plan-design concern. Those distinctions help you respond to the cause instead of assuming that adding another benefit is the answer.

Structured employee input is one part of an engagement review. The University of Minnesota’s employee engagement self-reflection questions offer a related example of using questions to examine workplace drivers; they are not a ranking of health benefits.

HR leader listening to employees discuss which workplace benefits matter to them

How Should You Turn Feedback Into a Benefits Priority List?

After gathering input, organize what you heard into needs rather than jumping straight to products. For example, “employees cannot find in-network care near their worksite” is a different issue from “employees want a lower deductible.” “People are unsure when coverage begins” may point to a communication or onboarding gap rather than a need to change the health plan.

A practical prioritization exercise can use four tests:

  • Reach: How many employees or eligible families appear to share the need? Note whether the issue is concentrated in a group that still needs attention.
  • Impact: What happens when the need is not met? Consider access, affordability, time, and employee experience without assuming one benefit solves every problem.
  • Fit: Does the proposed response match the need? Separate a coverage issue from a communication problem, a leave-policy question, or a request for a supplemental perk.
  • Feasibility: What are the employer cost, employee cost, plan rules, implementation work, and ongoing administration? Identify what must be confirmed before a decision.

Then label each item as a current strength, a known gap, a question requiring more information, or a future possibility. This makes the decision record more useful than a list of requested benefits. It also helps leadership see where a low-cost communication improvement may matter more than adding another offering.

For a concrete example, suppose employees ask for easier access to care and lower costs. Do not immediately interpret both comments as a request for a richer plan. First ask whether staff can locate in-network providers, whether the network serves each worksite, and whether cost sharing is understood. If providers are difficult to find, verify directory details and discuss network options. If employees can find care but are concerned about deductibles, compare plan designs and employee contributions. If the issue is uncertainty about the plan, improve the explanation and show where employees can confirm coverage. The same phrase—“healthcare is expensive”—can point to very different actions.

How Can You Compare Options Without Losing Sight of Total Value?

When the review involves health coverage, compare options on consistent terms. A monthly premium alone does not tell employees what care may cost or whether their providers and prescriptions are covered. Ask for a clear comparison of employer and employee contributions, plan design, network access, deductibles and other cost-sharing features, prescription terms, and the service employees will receive.

For each proposal, record what is known, what is estimated, and what requires confirmation. Look at both typical use and less predictable needs. Do not present an example as a promise of an employee’s personal cost. Plan documents, carrier information, eligibility rules, and individual circumstances determine actual coverage.

Funding design can also affect the conversation. Fully insured, level-funded, and self-funded arrangements differ in how costs and risk are structured. They are not automatically suitable for every employer. A proposal should explain assumptions, potential variability, and protections in a way leadership can evaluate. WHIA provides background on what a level-funded health plan is and how level-funded plans relate to spending volatility.

Also distinguish a plan change from an added perk. Lifestyle benefits are supplemental employer-designed offerings; they are not substitutes for core medical coverage, an HRA, or voluntary insurance. If you are considering an HRA, identify the arrangement type, eligibility, eligible expenses, administration, and employee communication requirements. WHIA’s QSEHRA and HRA overview can help frame the distinction, while the specific arrangement needs review for your circumstances.

Consider using a comparison worksheet with one row per proposal and the same columns for each: employee contribution, employer contribution, network, cost-sharing structure, prescription terms, implementation effort, and open questions. Avoid comparing a fully explained option with a sketch of another. If one proposal lacks detail, mark the gap and request clarification rather than filling it with assumptions. For a funding approach, include how costs are determined, what could vary, what protection is included, and how any end-of-period accounting works. A useful comparison lets leadership see both the best-case appeal and the practical obligations involved.

What Should HR and Finance Check Before Making a Change?

Before selecting a benefit, HR and finance should test the proposal against actual operating conditions. Confirm how eligibility will work for different employee classes and schedules. Map key dates for decisions, enrollment, implementation, and employee notices. Decide who will answer questions and how the organization will handle billing, enrollment changes, and claims concerns.

Ask for an explanation of ongoing work as well as initial setup. A benefit may look straightforward in a presentation but involve payroll coordination, employee education, vendor administration, or additional tracking. Document the person responsible for each step, what information they need, and where employees should go for help.

For the medical plan itself, review the experience employees will encounter: locating providers, checking prescriptions, understanding cost sharing, and asking for help when something goes wrong. WHIA’s provider search resource is one practical topic employers can consider when assessing network access. Do not infer that a provider is covered solely from a general directory; confirm details with the carrier and plan.

Finally, look at how the package connects to the rest of the organization’s goals. Are you trying to make costs more predictable, improve the employee experience, support hiring, or simplify administration? Choose a small set of measures you can review later, such as employee understanding, participation where applicable, recurring questions, administrative issues, and renewal feedback. Avoid claiming a benefit caused a retention or recruiting result unless you have evidence that supports that conclusion.

A decision log can make the review repeatable. Record the issue employees raised, the evidence considered, the options reviewed, the reason for the decision, and the date to revisit it. If a benefit is postponed, note what would need to change before reopening the question, such as a budget cycle, better utilization information, or a clearer administrative process. This prevents the same discussion from restarting without context and gives HR a transparent way to explain why a request was not adopted immediately.

How Can You Explain the Package So Employees Can Use It?

Even a carefully selected benefit can have little practical value if employees do not know it exists or cannot tell how it works. Use plain language to describe what is included, what is optional, who is eligible, when an employee can enroll, what the employee may pay, and where to find plan-specific details. Explain limits and exclusions without hiding them in fine print.

Provide information in more than one format when possible: a concise comparison, a live or recorded orientation, and a place to ask follow-up questions. Use examples to explain concepts, but mark them as illustrations rather than guarantees. Give employees enough time and a clear path to confirm their own provider, prescription, or coverage questions with the appropriate carrier or plan resource.

When the package includes several distinct benefit types, explain how they relate without blending their rules. State clearly whether an offering is core medical coverage, an HRA, a voluntary product, or a supplemental lifestyle benefit. This helps employees make informed choices and reduces mistaken assumptions about what a benefit will pay for.

A simple communication test is to ask a new employee to explain the basics back in their own words: what the benefit does, who is eligible, what they may pay, and where to ask questions. Treat confusion as useful feedback about the materials, not as a failure by the employee. Update the explanation when the plan or process changes, and keep a current version easy to find. If the answer depends on individual circumstances, direct the employee to the carrier or plan administrator rather than guessing.

Frequently Asked Questions

What are the most valued employee benefits for a small business?

There is no single list that applies to every small business. Employees may value medical coverage, dental or vision options, flexibility, leave, or other support differently depending on their needs and the plan terms. Ask your own workforce, then weigh the feedback against affordability, eligibility, administration, and your organization’s goals.

How often should an employer ask employees about benefits?

Review priorities as part of the benefits planning and renewal cycle, and listen when a meaningful workplace change occurs. Avoid surveying employees so often that they stop engaging. A clear explanation of how responses inform decisions matters more than running frequent surveys without follow-through.

Should employers add a benefit because employees request it?

A request is a useful signal, not by itself a decision. Determine whether the need is widespread or specific, what problem the requested benefit would address, what it would cost, and what rules or administrative steps apply. Consider whether another solution, including clearer communication, would address the underlying issue better.

Are lifestyle benefits the same as health insurance or an HRA?

No. Lifestyle benefits are supplemental perks designed by the employer for a particular purpose. They are distinct from core medical coverage, an HRA, and voluntary insurance. Explain each offering separately and confirm its terms before describing what employees can use it for.

Can an employer promise that a benefits change will lower costs or improve retention?

Do not promise an outcome that has not been established. Employers can explain the goals of a proposed change and assumptions behind an estimate, then review the results over time. Actual costs and employee outcomes depend on the plan, participation, use, and other factors.

Schedule a conversation about your benefits strategy

Ready to Review Which Benefits Matter Most to Your Team?

Washington Health Insurance Agency (WHIA) works with Washington employers to evaluate benefits needs and plan options. If you are preparing for a renewal or want a clearer comparison of the choices, start a conversation about your workforce, priorities, and questions. You can also review WHIA’s information for small-group employers and larger employers to see how different group contexts shape the discussion.

A thoughtful review starts with listening and ends with a package employees can understand and the organization can support over time.

From Reading to Talking

Insight is useful. A conversation is better.

Reading about the options is a fine start — but the real value comes from applying them to your plan. Book a thirty-minute conversation and we'll diagnose before we prescribe, with your numbers in front of us.

Book a conversation
Washington employers · 10–200 employees