Caroline runs 1:1s with her five direct reports every Monday. She prepares for each one. She cares. And every single week, the same thing happens: her report opens the laptop, walks her through the sprint board, lists what shipped, what slipped, and what’s blocked. Caroline nods, unblocks two things, and the meeting ends three minutes early. Everyone feels vaguely productive.
Six months later, one of those reports resigns. The reasons are the usual mix: a better offer, a shorter commute, a team working closer to the product. But one line from the exit interview stays with Caroline: “I never really talked to my manager about my development.” It wasn’t why the person left. It was the reason nothing surfaced earlier, while there was still time to act on it.
Caroline had 26 one-on-ones with that person. Every one of them was a status update.
The short answer: 1:1s turn into status updates because status is the easiest thing to talk about, for both sides. To change it, move status to writing, give the meeting a simple shared agenda, and replace answer-giving with questions about obstacles, options, and growth. The manager’s job in a 1:1 is to ask, not to check.
Here is how to actually do that, including what to say when the meeting drifts back.
Why do 1:1s drift into status updates?
Because status is the path of least resistance for both people in the room. For your report, listing completed tasks is safe: it proves work happened and requires no vulnerability. For you, hearing status feels responsible: you leave with information. Nobody has to say anything uncomfortable, so nobody does.
There is a second habit hiding inside the first, and it is the more stubborn one. Most 1:1s are not just a report reciting status. They are a manager dispensing answers. The report brings questions, the manager solves them one by one, and both sides leave feeling efficient. It looks like good management. We will come back to why it isn’t.
Notice what is strange about the status half of this: in most teams, you already have the status. It’s in Jira, in Asana, in the sprint review, in Slack. When a 1:1 repeats information that exists elsewhere, the meeting isn’t producing anything. It is performing oversight. And the conversations that actually needed a private room (the frustration that has been building for weeks, the skill your report wants to develop, the decision they keep avoiding) never happen, because the status update used up the slot.
The research reflects this. The LinkedIn 2025 Workplace Learning Report names manager development as the top organisational priority, with coaching identified as the largest skill gap. That gap has a simple origin: most managers were promoted for being excellent problem-solvers, so in 1:1s they do what made them successful. They collect problems and solve them. The result is a team that escalates instead of thinking, and a manager who has quietly become the bottleneck.
What is a 1:1 actually for?
A 1:1 is the only recurring meeting that belongs to your report, not to the work. Its job is to cover the things no other meeting covers: how the person is doing, what’s getting in their way, what they’re learning, where they’re stuck on a decision, and where they want to go.
Organisational psychologist Steven Rogelberg, who has studied one-on-ones more systematically than anyone and wrote the book “Glad We Met” about them, is unambiguous on the ownership question: the meeting is for the direct report. Their topics come first, and in a good 1:1 the manager talks less than the report, not more.
A simple check: pull up your notes from your last three 1:1s. If everything you discussed could have been read off the project board, the meeting has stopped doing its real job.
How do I restructure the meeting?
Three changes, in order of impact.
1. Move status to writing. Ask each report to send you three bullet points before the 1:1: done, in progress, blocked. Two minutes of async writing replaces fifteen minutes of live recitation. Say it like this:
“I want to change how we use our 1:1s. The project updates are useful, but I can get those from the board, and I’d rather spend our time on things we can’t cover anywhere else. From next week, can you send me three bullets before we meet: done, in progress, blocked? Then the meeting itself is for everything else.”
2. Give the meeting a simple shared agenda. Not a formal document, and not a blank page either. A blank page just invites the old habit back. What works is a short, repeatable structure that serves both of you. The one we use in our labs has three questions:
- What’s the most important thing we should talk about today?
- Where do you need input, feedback, or coaching?
- What was a recent highlight or win?
Each question is doing a specific job. The first puts your report’s priorities at the top of the meeting instead of yours. The second is the quiet workhorse: by asking the person to name the kind of help they want, it stops you from defaulting to advice when what they needed was a sounding board. The third makes progress and a sense of achievement more visible, which status recitals, ironically, never do. Expect the first two or three weeks to feel awkward. People who have spent years reporting status don’t instantly trust the new format. Hold the line anyway.
3. Ask more, answer less. “What did you work on?” produces a report. These produce a conversation:
- “What’s the main challenge for you right now?”
- “Where are you stuck, and what have you already tried?”
- “What decision are you sitting on?”
- “What’s something you want to get better at this quarter?”
- “What support do you need from me?”
You don’t need all five. One, asked sincerely and followed by silence, will do more than a page of them.
What do I say when the meeting slides back into status?
It will. Habits are sticky, and your report may genuinely believe that reporting is what you want. Don’t wait for the meeting to end and feel disappointed. Redirect in the moment, kindly:
“This is all in your update, and I’ve read it. Thank you. Let’s use our time on something the board can’t tell me. What’s on your mind this week?”
If the pattern keeps returning, name it once, directly:
“I’ve noticed our 1:1s keep going back to project updates. I don’t need this meeting to check on your work; I trust that. I want this time to be useful for you: obstacles, decisions, development, frustrations. What would make this half hour genuinely worth having?”
That second script does something important: it tells your report explicitly that the meeting is not surveillance. Many people report status defensively, because no manager has ever told them otherwise.
The harder problem: when your 1:1 becomes a help desk
Status drift is easy to spot. This pattern is harder, because it masquerades as a great meeting. Your report arrives with real, legitimate questions: “What should I do about the vendor delay?” “Could you talk to the platform team for me?” “How would you handle Brian’s pushback?” You answer each one. They leave with solutions. Both of you feel the meeting was valuable.
Now look at it across three months. The same categories of question keep coming back, slightly reworded. Nothing you unblocked stayed unblocked, because the thinking that produced the blockage never changed. Every answer you gave felt generous in the moment, but its cumulative message was: don’t decide without me. You haven’t been running 1:1s. You’ve been running a help desk with one very expensive agent.
The coaching alternative is not refusing to help. It is making your report do the first pass of the thinking out loud, before your view enters the room:
- “What have you already tried?”
- “What options do you see? Walk me through them before I add mine.”
- “If I were out this week, what would you do?”
- “You’re closer to this than I am. What’s your read?”
Then comes the discipline that separates managers who develop people from managers who accumulate dependents: if their option is 80 percent as good as yours, endorse theirs. The 20 percent you lose in elegance, you gain back many times over in a report who stops queueing decisions for Monday.
And be honest about the exceptions. When there is a genuine information gap, a compliance question, or a live crisis, give the answer. Coaching is a default, not a dogma.
Frequently asked questions
How often and how long should 1:1s be? There is no single right cadence, and be wary of anyone who prescribes one. Rogelberg’s guidance is to calibrate per person: how remote they are, how experienced, how new to the organisation and to you, and how large your team is all shift the answer, within a realistic range of weekly to monthly. His rule of thumb when unsure: choose the more frequent option, then adjust it with the person rather than for them.
Should I cancel 1:1s when things get busy? Reschedule, don’t cancel. Every cancellation tells your report exactly where they rank. If you must move it, move it within the same week, and never take the slot for a project meeting.
Can I use the same questions every time? Yes. Predictability helps. Many strong managers open every 1:1 the same way. The consistency signals that the invitation is real, and reports start preparing real answers.
The three-question agenda and coaching questions in this article come from the one-page toolkit participants receive in our 90-minute lab Coaching 1:1s That Drive Ownership, where managers practice a real 1:1 using the GROW framework and leave with a structure they can use the following Monday.
Photo by www.kaboompics.com: https://www.pexels.com/photo/man-and-woman-using-laptop-together-5908485/ and by Walls.io : https://www.pexels.com/photo/colleagues-working-at-office-17737175/