<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=749646578535459&amp;ev=PageView&amp;noscript=1">

Your Frontline Employees Want to Hear From Their Managers. Can They?

Posted by Mark Graban

Find me on:

Nov 16, 2026, 3:00:00 AM

Frontline Manager Communication: Fix Access First
7:24

On November 4, Aptitude Research published its Frontline Workforce Report 2026, sponsored by Workday and Brilliant. One pair of numbers in the public summary is worth putting in front of any CI leader who has ever complained about low participation in improvement work:

83% of frontline workers say communication with their direct manager matters, but only 52% are satisfied with it.

That 31-point gap is a frontline manager communication problem. Read alongside a second finding, it might also be an access problem. 51% of employers in the research say fewer than three-quarters of their frontline workers have a company email or login.

If a quarter or more of your workforce has no login, some of the "disengagement" in your improvement numbers might be people who have no way to reach you.

Recently I wrote about why you should not wait for employees to speak up, and ask them instead. Asking matters. This post is about what comes after the ask: whether people have a practical way to answer, and whether anybody answers them back.

What the frontline manager communication numbers show, and what they don't

I'd hold this research a little loosely. It was sponsored by two companies that sell workforce software, and the public summary doesn't report sample sizes, how respondents were recruited, or whether results were weighted. So I wouldn't treat the percentages as a description of all US frontline workers, and nothing in the summary shows cause and effect.

Satisfaction with manager communication also isn't the same thing as participation in improvement. Someone can like how their supervisor talks to them and still never submit an idea. The reverse happens too.

Still, the direction matches what a lot of CI leaders tell me they see. And what workers asked for in the research is mundane. 46% want pay stubs and tax forms on their phone, 35% want to request time off digitally, and 27% want to see their schedule. Nobody asked for a new platform. They asked to do basic things from the device already in their pocket.

Three reasons people stay quiet, and only one is fear

When frontline participation is low, the default diagnosis is culture, usually fear. Sometimes that's right. I've written about what actually makes people speak up, and fear is real.

But silence has at least three causes that look identical in a participation report.

The first is no access. The person has no login, no shared device on the unit, no time during the shift, or the system is only reachable from a desktop in the manager's office.

The second is fear. They have a way in, but they expect speaking up to cost them something.

The third is futility. They have access and they aren't afraid. They submitted three ideas last spring, heard nothing, and drew a reasonable conclusion.

Each one calls for a different fix. Psychological safety training for managers won't help a night-shift worker who can't log in. A new kiosk won't help someone who stopped bothering in April. Treating an access problem as a culture problem is expensive, and it quietly tells employees that the problem is their attitude.

You can start telling them apart by breaking participation out by role, shift, and location instead of looking at one total. If day-shift nurses at one hospital participate and night-shift environmental services staff across every site don't, that pattern points to access or time, not attitude. If one unit's numbers dropped after a manager change, look at how that manager has been responding. And you can simply ask at a huddle: "If you had an idea, how would you submit it?" Anyone who can't answer has an access problem, whatever else might also be going on.

The hiring numbers tell the same story earlier

The same research reports that 79% of hourly workers have abandoned a job application because it took too long, and that only 22% of employers respond to 90% or more of frontline applicants.

Think about what that teaches someone before their first day: the process is tedious, and you may not hear back. I suspect many people carry that expectation straight into the idea system. That's my inference, not something the research measured. But if it's true, a new hire's first submission is being judged against a baseline of silence the organization already set.

A response is the evidence people are looking for

An acknowledgment costs a supervisor a couple of minutes. That small cost is why it works. It's proof that a person read the thing and thought about it, which a generic auto-reply can't provide.

Every unanswered submission does the opposite. It teaches the person who sent it, and everyone they mention it to, that this isn't worth the effort. That lesson spreads faster than any poster in the break room.

Response quality matters as much as speed. "We'll look into it," three weeks later, is technically a reply. "Thanks. I talked with pharmacy, here's what I learned, can you help us test a change Tuesday?" tells the person their idea went somewhere and invites them back in.

Supervisor time is a real constraint here, and a system one. The research reports that 55% of managers spend three or more hours a week building schedules. If supervisors are buried in that kind of work, response times will slip no matter how many times leaders remind them. Fix the time before you exhort the behavior.

What to measure before you buy anything

If you use KaiNexus, the data for most of this should already be in the system. If you don't, a spreadsheet can get you started. Either way, these are the measures I'd look at:

  • Participation by role, shift, and location, not just the total
  • Access: what share of each group has a login, a shared device, or another way in
  • Time from submission to first acknowledgment, by unit and by manager
  • Response quality, by reading a sample of actual replies
  • Unresolved items, and how many are older than 30, 60, or 90 days

Together, those tell you which of the three problems you mostly have. That should come before deciding what to buy, train, or announce.

Don't assume the answer is another app

Because workers say they want mobile access, it's tempting to roll out an app. Maybe that's right. But if a large share of your frontline staff has no company login, an app adds one more credential to manage.

A shared login on a unit tablet, a paper card a supervisor enters at the end of the shift, a huddle board, or a manager who asks for ideas at the start of the shift and records them might work better. The goal is the shortest path from "I noticed something" to "someone responded." Sometimes that's software. Sometimes it's a supervisor with five minutes and a pen.

This month, pick the unit or shift with your lowest participation. Ask five people there how they would submit an idea and when they last heard back about one. Those five conversations may tell you more than your next engagement survey.

If you'd like to see how KaiNexus shows participation and response time across units and sites, see KaiNexus in action.

Source: Aptitude Research, "The State of the Frontline Workforce" (Madeline Laurano, November 4, 2026).

Topics: Leadership, Employee Engagement, Continuous Improvement, Lean Leadership, Continuous Improvement Culture

Recent Posts