A skip-level with no AI question is a meeting a senior leader runs with a manager's team that never asks whether anyone saw the manager use AI on live work. The calendar looks like listening. The week still runs the old way. The skip-level is a pulse check. A pulse check that never names a use case cannot tell you whether the manager went first.
This is the skip-level query. Why AI adoption fails already covered the stall. Managers are the missing owner already covered who the team copies. What happens between AI training sessions is the days after the workshop. How to practice a difficult conversation is the rehearsal. Why AI competency on the review form fails is the 1-5 with no rubric. Why an AI goal with no use case fails is the H2 slogan. This post stays on the skip-level agenda and the AI question nobody asked.
Why Did Skip-Levels Stay Silent on AI?
Because the agenda was copied from last year.
A skip-level already has a job. Hear the team without the manager in the room. Ask about workload, career, and whether people feel supported. Write three themes for the VP pack. That script predates the AI rollout. Nobody added a question when the licenses shipped, because the skip-level is treated as an engagement ritual, not as a test of whether the work changed.
On October 8, 2025, Gartner published Gartner Research Finds Only 8% of HR Leaders Believe Their Managers Have the Skills to Effectively Use AI. Only 8% of HR leaders believe their managers have the skills needed to use AI effectively. The same research, from a July 2025 survey of 114 HR leaders, found that one in three organizations already expect higher performance from employees who use AI. An August 2025 Gartner survey of 114 HR leaders found that only 14% of organizations reported providing support to managers on how to integrate generative AI into their daily tasks. HR does not believe managers can use AI. The company already expects more from people who do. Almost nobody supports managers on the daily job. Then the skip-level still asks "how is the team" and never "what AI job did you watch your manager run."
That silence is not a missing icebreaker. It is a missing observer. The VP is the one person who can ask a team, without the manager present, whether the new path is real. If they do not ask, the only signal left is a workshop recap and a usage chart. How HR leads AI transformation already argued for building the manager layer first. The skip-level is where that layer either gets inspected or gets a polite hour.
The skip felt reasonable. The tool was bought. The session had run. The board had asked what People was doing about AI. A scheduled skip-level answers the listening slide. A named use case answers Tuesday. Most teams shipped the first one and called the quarter updated.
What Happens When a Skip-Level Never Asks About AI?
They hear mood. They miss the job.
The hour opens. A VP has eight people and a list: workload, career, what would help. Someone says they are busy. Someone says they want to grow. Someone mentions the AI training was interesting. None of those answers is a use case. The VP writes "team is engaged, interested in AI" and files the notes.
The dangerous skip-level is not the one that skips the meeting. It is the one that checks the pulse and never checks the work.
A cancelled skip-level at least admits the calendar lost. A pulse check is how the company files listening as handled. Both the VP and People leave feeling they did the work. L&D hears the cohort is on track. Calibration later treats a stack of "engaged" skip-level notes as color. That color is where the empty agenda did the most work. It turned an unrun job into a healthy culture signal.
| On the agenda | What a skip-level about AI needs |
|---|---|
| How is workload | Which live job starts in the tool now |
| How can I support you | What did you watch your manager run |
| Career and growth | What "done" looks like on that job this month |
| Any other feedback | What broke, and who caught it |
The left column is what most 2026 skip-levels still run. The right column is the minimum for a meeting you can act on. If you cannot fill the right column, you do not have a pulse on AI. You have an engagement hour with a new noun in the notes.
That is why AI adoption metrics for HR cannot be a login chart pasted into the VP pack. Usage answers "did they open it." A skip-level is supposed to answer "did the manager go first on a job the team can name." A system can count opens. It cannot tell you whether anyone saw the miss get caught.
Silent skip-levels also teach the team that AI is optional. If the most senior person in the room never asks what they watched, the team copies that silence the way they copy a manager who still starts the forecast the old way.
What Should a Skip-Level Ask About AI?
Three questions. About a job. Asked of the team, not of the slide.
A usable skip-level needs the same specificity how to build an AI adoption strategy starts with: a business problem, not a tool tour. The meeting needs that or the hour will rate vibe.
What live job starts in the tool now? Not "are you using AI." A job they already own: the weekly forecast, the ticket, the customer note. If the team cannot name one, the manager has not made a path. What happens between AI training sessions is the calendar version of that sentence. The skip-level is the artifact that tests whether the sentence is true without the manager in the room.
What did you watch your manager run? The team copies what the manager does after the meeting, not what the workshop asked them to try. Managers are the missing owner of AI adoption because that copy is the program. If nobody watched a run on live work, "meets" on the review form is a guess, and the H2 goal is a slogan. Ask for a deliverable, a miss they heard named out loud, and whether the old way is still the default when the deadline is tight.
What will "done" look like on that job this month? A skip-level that only collects complaints has no next move. Name the behavior someone else can see: first draft starts in the tool, and they edit. Then the VP's follow-up with the manager is a coaching conversation, not a recap of morale. What management coaching is is the mechanic. A workshop is not the same as ongoing growth. Training transfers language in a room. A skip-level is supposed to test what happened after.
If the next conversation with the manager is the hard 1:1, rehearse it once before it is live. That is optional. Practice Space is rehearsal, not a second product. The required work is still the three questions on the agenda.
The enterprise AI rollout checklist is the assignable version of the human-layer work. Use it to name the workflow. Use the skip-level to ask whether anyone saw it. In programs Boon has run since 2023, competency scores improve 23 percent on average through coaching. That line only means something because the competency had a behavior a coach, and a team, could see. A skip-level with no AI question cannot move 23 percent. It can only produce notes. AI transformation coaching is the conversation that sits with the clumsy phase so the next skip-level has something to ask besides "how is the team."
Why Is a Skip-Level With No AI Question a People Problem, Not an Engagement Problem?
Because the skip-level is a people system. Engagement already had a survey.
IT can stand up access and a usage export. Finance can add a line to the H2 pack. Neither can sit with eight people and ask what they watched their manager do on a Tuesday. Neither can tell a VP which job is still starting the old way. Those are People and L&D jobs. When they go unfinished, the failure shows up as a healthy skip-level writeup nobody can translate into a changed week.
Calling it an engagement gap is how the silent agenda survives another quarter. Another eNPS item will not name the job. The manager who still starts the work the old way does not have a listening problem. They have a skip-level that never required the team to describe a use case, and a senior leader who was asked to invent a pulse in the room.
That is why this belongs next to the skip-level calendar, not next to the launch email. Coaching in that window is how a manager gets close enough to the work that the team has something to say, and how a person gets a chance to grow the behavior before the VP hour. Sessions stay on Zoom. Slack and Teams carry the prep and the follow-through. The skip-level is the artifact. The coaching is what makes it honest. "Interested in AI" is not a use case. A green pulse is not proof.
FAQ
What is a skip-level with no AI question?
It is a meeting a senior leader runs with a manager's team that never asks whether anyone saw the manager use AI on live work. The calendar looks like listening. The week still runs the old way.
What should you ask in a skip-level about AI adoption?
Ask which live job starts in the tool now, what the team watched their manager run, and what "done" looks like on that job this month. "Are you using AI" is not that bar. Name a deliverable, a miss, and whether the old way is still the default under a deadline.
Why do skip-level meetings miss AI adoption?
Because the agenda was copied from last year. Workload, career, and support predates the rollout. Nobody added a question when the licenses shipped, so the hour files mood and never tests the job.
How do you know if a manager is actually using AI with their team?
Ask the team, without the manager in the room, what they watched. A license report and a workshop recap are not observation. If nobody can name a live-job run, the manager has not gone first.
Is a skip-level the same as a pulse survey?
No. A survey scores mood at scale. A skip-level is the one hour a senior leader can ask for a use case the team saw. If that hour never names AI, you have engagement data and no proof the work changed.
How does coaching sit next to a skip-level?
Coaching is the calendar that gets a manager close enough to the work that the team has something to say, and gives the person time to grow the behavior before the VP hour. It is not another listening session. It is the conversation about the job they tried, where it got clumsy, and what the skip-level will hear next.
The Skip-Level Is Not a Pulse Check
If the quarter ran and the skip-level never asked what AI job the team watched, you do not have a mysterious culture problem. You have a people-development gap that the calendar made official. Put the three questions on the agenda. Then put coaching next to that hour so the next skip-level is about work someone saw.
Boon Adapt is the coaching calendar that sits next to that skip-level. It sits with SCALE, GROW, EXEC, and TOGETHER as one operating system for people development that lives in Slack, Teams, and MCP, and gets measured. Ask the AI question. Then coach the week the skip-level is supposed to see.