A weekly 1:1 with no tool question is a standing manager meeting whose template still only asks about goals, blockers, and wellbeing, and never asks what the person actually tried in the AI tool this week. The calendar looks like coaching. Tuesday still starts the old way. The 1:1 is the highest-frequency people artifact in the company. A template that never names the tool cannot tell you whether the week changed.
This is the weekly-template 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. Why a skip-level with no AI question fails is the VP hour. This post stays on the standing weekly 1:1, the Google Doc or Lattice or 15Five form that still has three fields, and the tool question nobody added.
Why Did Weekly 1:1 Templates Stay Silent on the Tool?
Because the form already looked finished.
A weekly 1:1 already has a job. Goals. Blockers. How are you. Those three fields are how a good manager conversation was defined before the licenses shipped. The template lives in a shared doc, in Lattice, in 15Five. People fill it on Monday. The manager skims it at 9. Nobody added a fourth field when the tool went live, because the 1:1 is treated as a relationship ritual, not as a test of whether the work started in the new path this week.
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. 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. The weekly 1:1 is that support, or it is not. HR does not believe managers can use AI. Almost nobody supports the daily job. Then the standing form still asks "any blockers?" and never "what did you try in the tool this week."
That silence is not a missing icebreaker. It is a missing weekly observer. The manager is the one person who can ask, every Tuesday, what the person actually ran. If they do not ask, the only signals left are a workshop recap, a usage chart, and a skip-level that happens twice a year. How HR leads AI transformation already argued for building the manager layer first. The 1:1 is where that layer either inspects the week or files the relationship as handled.
The skip felt reasonable. The review form got a new row. The H2 pack got a new goal. The board had asked what People was doing about AI. Those artifacts are rare. The weekly template is not. A labeled competency answers the cycle. A slogan goal answers the slide. A fourth field on the 1:1 answers Tuesday. Most teams shipped the first two and left the form that runs all year alone.
What Happens When a 1:1 Never Asks What You Tried This Week?
They talk about the week. They miss the tool.
The hour opens. A manager has a Lattice form, or a Google Doc, or a 15Five prompt. Goals are amber. Blockers are a vendor and a headcount. Wellbeing is "busy but fine." Someone mentions the AI training was useful. None of those answers is a run. The manager writes "on track" and closes the doc.
The dangerous 1:1 is not the one that gets cancelled. It is the one that runs the old template.
A cancelled 1:1 at least admits the calendar lost. A completed 1:1 with goals, blockers, and wellbeing is how the company files coaching as handled. Both people leave feeling they did the work. L&D hears the cohort is in 1:1s. The midyear review treats a stack of "good 1:1 hygiene" notes as color. That color is where the empty template did the most work. It turned an unrun job into a healthy manager signal.
| On the template | What a weekly 1:1 about the tool needs |
|---|---|
| Goals / priorities | Which live job did you start in the tool this week |
| Blockers | What broke, and did you stay in the tool or go back |
| Wellbeing / how are you | What did you try, not only how do you feel |
| Action items | The next deliverable that starts in the tool before we meet |
The left column is what most 2026 1:1s 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 weekly pulse on AI. You have a relationship hour with a new noun in the notes.
That is why AI adoption metrics for HR cannot be a login chart pasted into the people pack. Usage answers "did they open it." A weekly 1:1 is supposed to answer "did they try it on a job they already own, this week." A system can count opens. It cannot tell you whether the person caught a miss and stayed in the tool, or dumped the draft and finished the old way.
Silent 1:1s also teach the person that the tool is optional between reviews. If the manager never asks what they tried since last Tuesday, the person copies that silence the way they copy a manager who still starts the forecast by hand.
What Should a Weekly 1:1 Ask About the Tool?
Three questions. About this week. Asked of the person, not of the portal.
A usable 1:1 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 half hour will rate mood.
Which live job did you start in the tool this week? Not "are you using AI." A job they already own: the weekly forecast, the ticket, the customer note. If they cannot name one, they did not run it. What happens between AI training sessions is the calendar version of that sentence. The weekly 1:1 is the artifact that tests whether the sentence is true before the week is gone.
What broke, and did you stay in the tool or go back? The useful answer is a miss they can say out loud. A hallucination they caught. A draft they had to rewrite. A deadline that made the old path feel safer. If the answer is "it went fine" and they cannot point at a deliverable, you do not have a run. You have politeness. Managers are the missing owner of AI adoption because the team copies what survives a tight Tuesday, not what the workshop asked them to try.
What will you run again before we meet? A 1:1 that only collects status has no next move. Name the next live deliverable, and say it starts in the tool. Then the follow-up is a coaching conversation, not a recap of blockers. What management coaching is is the mechanic. A workshop is not the same as ongoing growth. Training transfers language in a room. A weekly 1:1 is supposed to test what happened after, every week.
If the next conversation is the hard one, rehearse it once before it is live. That is optional. Practice Space is rehearsal, not a second product. The required work is still the fourth field on the template.
The enterprise AI rollout checklist is the assignable version of the human-layer work. Use it to name the workflow. Use the weekly 1:1 to ask whether anyone ran it since last Tuesday. Across programs we've 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 manager, could see in a week. A 1:1 with no tool 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 1:1 has something to ask besides "any blockers?"
Why Is a 1:1 With No Tool Question a People Problem, Not a Meeting Problem?
Because the weekly 1:1 is a people system. Meetings already had a calendar.
IT can stand up access and a usage export. Finance can add a line to the H2 pack. Neither can sit with a person every Tuesday and ask what they tried. Neither can tell a manager 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 clean Lattice history nobody can translate into a changed week.
Calling it a meeting-quality gap is how the old template survives another quarter. Another 1:1 training will not add the field. The person who still starts the work the old way does not have a listening problem. They have a weekly form that never required them to describe a run, and a manager who was asked to invent a pulse from goals and blockers.
That is why this belongs next to the 1:1 template, not next to the launch email. Coaching in that window is how a manager gets close enough to the work that the form has something to hold, and how a person gets a chance to grow the behavior before the review row is scored. Sessions stay on Zoom. Slack and Teams carry the prep and the follow-through. The template is the artifact. The coaching is what makes it honest. "Busy but fine" is not a use case. A completed 1:1 is not proof.
FAQ
What is a weekly 1:1 with no tool question?
It is a standing manager meeting whose template still only asks about goals, blockers, and wellbeing, and never asks what the person actually tried in the AI tool this week. The calendar looks like coaching. Tuesday still starts the old way.
What should you ask in a 1:1 about AI adoption?
Ask which live job they started in the tool this week, what broke and whether they stayed in the tool or went back, and what they will run again before you meet. "Are you using AI" is not that bar. Name a deliverable, a miss, and the next Tuesday.
Why do weekly 1:1 templates miss AI?
Because the form was copied from last year. Goals, blockers, and wellbeing predates the rollout. Nobody added a field when the licenses shipped, so the hour files status and never tests the run.
How is a weekly 1:1 different from a skip-level or a performance review?
A skip-level is a rare VP hour with the team, without the manager in the room. A review is a cycle rating with a 1-5. A weekly 1:1 is the manager and the person, every week, on a standing template. If that template never names the tool, you have relationship hygiene and no proof the work changed this week.
What belongs on a Lattice or 15Five 1:1 form for AI?
A fourth prompt: which live job did you start in the tool this week, what broke, and what will you run before we meet. Keep goals, blockers, and wellbeing. Add the run. A Google Doc needs the same line. The product does not matter. The missing field does.
How does coaching sit next to the weekly 1:1?
Coaching is the calendar that keeps the 1:1 on the run, and gives the person time to grow the behavior before the review scores it. It is not another status meeting. It is the conversation about the job they tried, where it got clumsy, and what next Tuesday will hear.
The 1:1 Is Not a Status Meeting
If the quarter ran and the weekly 1:1 never asked what they tried in the tool, you do not have a mysterious culture problem. You have a people-development gap that the template made official. Put the three questions on the form. Then put coaching next to that hour so the next 1:1 is about work someone ran.
Boon Adapt is the coaching calendar that sits next to that 1:1. 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 tool question. Then coach the week the 1:1 is supposed to see.