AI and Employee Engagement: Manager Support Decides It

Written by Breakfast Leadership

AI and employee engagement are not a technology pairing. They are a management pairing, and the evidence says the manager sits in the middle of it. Gallup reported on October 28, 2026 that U.S. employee engagement fell to 29% in the third quarter, its lowest level since 2011, with 18% of employees actively disengaged and 53% not engaged. Gallup's earlier analysis from July found that engagement was far higher where managers actively supported their team's use of AI.

That finding should change how you read your own adoption numbers. If you have bought or piloted AI tools and cannot show measurable adoption, the usual response is more licenses, more training sessions and a better dashboard. The data points somewhere else. The tool matters less than whether the person who runs each team talks about it, expects it, and ties it to real work.

This article is written for leaders at mid-market nonprofits, associations, healthcare and professional services firms who need to report adoption to a board or a regulator. It covers what Gallup measured, what it does and does not prove, and the manager-level system that turns tool access into use.

What Gallup Found About AI and Employee Engagement

In its July 21, 2026 analysis, Gallup reported that engagement was six points higher among employees whose organizations had adopted AI than among those whose organizations had not. Gallup notes that this may partly reflect which industries adopt AI first, so treat it as a weak signal. The stronger findings sit inside AI-adopting organizations. Employees whose organizations have a clear plan for integrating AI had a 15-point higher engagement rate than those without one. Employees who use AI at least weekly were eight points more engaged than those who use it less often.

The largest gap belongs to the manager. Gallup found that employees who say their manager actively supports their team's use of AI have an engagement rate of 48%, compared with 30% of those who do not say so. When frequent use, a clear integration plan and active manager support were all present, engagement rose to 53%.

Notice what this is and is not. It is a correlation from a national survey of 43,262 U.S. workers, fielded in February and May 2026, not proof that manager support causes engagement. It is also not a measure of your organization. What it does give you is a precise list of three conditions to test locally: how often your people use the tools, whether a plan exists that they can describe, and whether their manager visibly backs it. Ask those three questions in your next pulse survey and cut the answers by team. The pattern across teams will tell you where your rollout is working and where it is only installed.

Tool Access Is Not Manager Support

Most AI rollouts are designed around access. Licenses are issued, a training session is scheduled, and a champions network is announced. Each of those is a program. None of them is a manager doing something on Tuesday morning.

Gallup's guidance on this is specific and unglamorous. It says managers need practical guidance on how to discuss AI in weekly conversations, and it recommends that they connect AI use to performance goals and address employee concerns. It also recommends that managers ask employees how AI is changing their work, where it helps, and where it creates confusion. That is a description of a recurring conversation, not a campaign.

For a CEO or a COO, the implication is a change in who owns adoption. If adoption sits with IT or a project team, the people who shape daily behavior have no assigned role. Name the manager layer as the owner. Give each manager one question to ask in every one-on-one, such as which task AI changed for you this week and what got in the way. Then ask your executive team to report back on the answers in aggregate, not on login counts. The question costs a manager two minutes. The pattern it surfaces is the closest thing most organizations have to a leading indicator of adoption.

The Remote and Hybrid Gap Is Closing

Gallup's October update adds a warning for leaders with distributed teams. Between the second and third quarters of 2026, engagement fell five points among fully remote employees and two points among hybrid employees, while on-site employees and those in jobs that cannot be done remotely fell about one point.

The AI engagement advantage narrowed in the same groups. Among exclusively remote employees in AI-integrated organizations, the advantage fell from five points to two. Among hybrid employees it fell from eight points to two. Gallup's data does not explain why, so avoid a confident story. What you can say is that the benefit of AI integration was not holding steady among employees who see their colleagues and managers least often.

For leaders, the sensible reading is a question about manager contact, not a verdict on remote work. A remote employee cannot observe a colleague using a tool, and cannot overhear a manager praise a good use of it. The signal has to be deliberate. Ask your managers of remote and hybrid teams to share one concrete AI example in each team meeting, and to name the person who produced it. This is a small, cheap practice. Review it in the same meeting where you review other operating rhythms, so that it does not become another initiative that quietly lapses.

Why Engagement Is an Adoption Risk, Not a Morale Metric

Executives often file engagement under culture and adoption under technology. The Gallup numbers argue for treating them as one system. If 53% of employees are not engaged and 18% are actively disengaged, then most of the people you are asking to change their working habits are not investing discretionary effort in their jobs. Asking them to learn a new tool is asking for exactly that effort.

This matters more in regulated settings. When adoption is partial, oversight burden rises, because work happens in two ways at once: some inside the approved tool, with logging and review, and some outside it. A healthcare or professional services firm that cannot show who used what, for which decisions, carries a compliance exposure that a high login count will not repair. Low engagement widens that gap quietly. People do not refuse the tool. They simply keep working the old way, and the dashboard looks fine until an audit asks a question it cannot answer.

The practical step is to put engagement and adoption on the same page of your board reporting. Report weekly active use by team next to the share of employees who say their manager supports AI use and the share who can describe the plan. When two of the three move together, you have a real picture. When use rises and the other two do not, treat the number as fragile and ask which teams are producing it.

Build the Manager Layer Into Your Leadership OS

A Leadership OS is the set of decisions, owners and review rhythms that keep execution consistent without depending on one leader's memory. Manager support for AI is a clear candidate for it, because it is the kind of behavior that exists when a leader is paying attention and disappears when they are not.

Start by deciding what AI is allowed to decide and what a person must decide in each workflow, and write it down. Managers cannot support a tool whose boundaries they cannot state. Next, assign one executive as owner of the manager layer, with a monthly review of three measures: weekly use by team, the share of employees who can describe the plan, and the share who report manager support. Finally, remove something. If managers are to hold a weekly AI conversation, take an approval step, a status meeting or a report off their plate. Gallup found that engagement rose to 53% when frequent use, a clear plan and manager support were all present. A manager who is already over capacity cannot supply the third condition.

Keep the design modest. One question, one owner, one monthly review, and a single written statement of what the tool decides versus what a person decides. If you cannot get that into place in 30 days, the obstacle is probably decision rights, not enthusiasm, and that is worth knowing before you buy another license.

Conclusion

The evidence from Gallup gives leaders a short, testable sequence. Measure the three conditions locally: frequent use, a clear plan, and manager support. Make the manager the owner of the weekly conversation instead of treating adoption as an IT project. Watch your remote and hybrid teams, where the AI engagement advantage narrowed this year. And report engagement and adoption together, so the board sees whether use is real or only recorded.

None of this requires a new platform. It requires a decision about who owns the behavior that makes the platform worth having. A CEO who makes that decision, funds the manager capacity to carry it, and reviews three numbers a month will learn more about adoption in a quarter than a license report can show in a year.

If you lead an organization that has bought or piloted AI without measurable adoption, start by asking your executive team who owns the manager layer today. If the answer is no one, book a call and we will map the owner, the measures and the first review together.

One manager who backs AI is good coaching. Every manager doing it every week is a system.

The practices in this article are the right ones, and they are fragile. They depend on each manager remembering the weekly AI conversation while approvals, status meetings and reports crowd it out. Without an owner and a monthly review, the habit drifts, adoption reporting slides back to login counts, and the teams that matter most go quiet first.

Leadership Operating System

Uneven manager support is a structural gap in ownership and capacity, not a discipline problem, and a Leadership OS gives it an owner and a review rhythm. See how a Leadership OS review works.

AI Adoption Advisory

An adoption scorecard that reports logins without manager support or plan clarity cannot tell your board whether use is real. See how fractional AI adoption advisory works.

Book a call Either track starts the same way.

Michael D. Levitt is the founder of Breakfast Leadership Network and the author of Burnout Proof and Workplace Culture. More writing at the Breakfast Leadership blog.

Additional Resources

Sources

Breakfast Leadership
Next

How Leaders Can Build a Culture of Accountability