One-on-one status updates are not automatically a waste of time. Sometimes the work is exactly what someone needs to discuss with their manager. The problem starts when every recurring conversation becomes a rundown of completed tasks, pending reviews, and upcoming deadlines -- and nothing else ever gets room.
You can leave those meetings knowing what happened without understanding what support the person needs. From the employee's side, you might be explaining your work faithfully while wondering when you are supposed to ask about anything beyond it.
The answer is not to ban status or arrive next week with an entirely different personality. It is to examine the pattern together: what is this conversation doing, what is it missing, and where can routine information go without losing something important?
Why One-on-One Status Updates Can Take Over
Work is an obvious place to start. Both people know the project, there are concrete developments to discuss, and the next deadline gives the conversation a direction. Compared with explaining uncertainty about your role, reporting progress can feel straightforward.
That does not establish anyone's motives. An employee might want help with the work. A manager might need information they cannot find elsewhere. Or both people might simply have settled into a familiar conversation without discussing its purpose.
In my Code Commute discussion of one-on-one conversations, I explain why status updates can be useful while also questioning a recurring meeting that consists entirely of them. Those positions belong together. Useful work discussion and a useful recurring relationship are not mutually exclusive.
There is another complication: project pressure can change what feels urgent. When a major delivery occupies people's attention, they may naturally bring it into the meeting. Asking someone to ignore that pressure because status supposedly does not belong would miss what they are actually experiencing.
The distinction is between responding to the moment and letting that moment define every future conversation:
- A pressured week is not proof that the meeting is broken.
- A continuing pattern where other needs never surface deserves a closer look.
The same subject can therefore be useful at one point and limiting at another. Look at its place in the relationship, not only its presence on the calendar.
Look at What the Pattern Leaves Out
Do not judge the meeting only by whether an update occurred. Look at whether anything useful can happen beyond conveying that update.
Here are three ways to examine the pattern without scoring every conversation:
- Does the discussion reveal a need for support, or stop after the progress report?
- Can either person make room for something unrelated to the next deliverable?
- When another subject gets deferred, does it actually return?
These are reflection points, not a required meeting checklist. A conversation might reasonably focus on delivery and still reveal that an employee needs context or a decision. Another might sound efficient while repeatedly leaving the same uncertainty untouched.
Imagine a hypothetical engineer who mentions that a handoff is delayed. If the manager only asks when it will finish, the conversation stays at the reporting level. If they ask what is preventing agreement, they might discover that the teams understand ownership differently.
That is still a work conversation. But now there is something to understand or help resolve, rather than another date to collect. The distinction matters because replacing work discussion with a different label does not necessarily make the meeting more supportive.
You also do not need to invent an unspoken concern. If neither person knows what is missing, that is something to explore rather than evidence that the employee is withholding information. Quietness alone does not establish disengagement.
Separate Routine Reporting From Useful Work Discussion
One-on-one status updates can contain several different things at once: information about progress, uncertainty about a decision, and a request for help. Moving the entire conversation elsewhere can discard the useful parts along with the repetition.
A practical distinction is whether the manager needs to receive information or participate in working through it. A routine update tells them something. A support conversation helps clarify what that information means for the employee and what, if anything, needs to happen next.
For example, imagine an employee explaining that a review is waiting on another team. The progress information may already be visible. What is not visible is that the employee has received conflicting instructions and does not know whose expectations to follow. The one-on-one can address that uncertainty without replaying the project's entire history.
Technical questions can belong here too. If a manager has relevant architectural context, asking for an explanation may be valuable. There is no requirement to remove engineering from a conversation between engineers. The question is whether this use of time still meets the person's needs, not whether the subject sounds technical.
This is part of the balance in hands-on management: stay close enough to understand where help is needed without turning every exchange into your own direction of the work.
Neither keeping status nor moving it elsewhere is automatically better in every situation. Each has a benefit and a risk:
| Approach | What it preserves | What to watch |
|---|---|---|
| Discuss the update together | Immediate context and room for questions | Reporting can consume the conversation |
| Share routine details elsewhere | More room for individual support | The alternative may miss context or go unread |
The useful distinction is not the format alone. It is whether information reaches the right people while the employee still has access to help.
Agree Where Routine Updates Can Go
If the same information is already shared in a suitable place, you may not need to repeat it in full. But first establish that both people can actually use that place. A theoretical reporting channel is not an alternative if the manager never sees it or the employee cannot tell what information is expected.
The alternative could be a team discussion, a written update, or a chat conversation. I do not insist that everything become asynchronous. Different teams have different communication needs, and creating another report nobody uses will not repair the one-on-one.
Think about the handoff between the two conversations:
- Routine progress needs an agreed place where the relevant people will see it.
- Questions needing individual support still need somewhere to be discussed.
The manager should help make that distinction workable rather than announce that status is forbidden. If they still ask for the complete report in every one-on-one, the employee has little reason to believe the expectation changed.
If no suitable channel exists, acknowledge the gap. The meeting may be doing necessary reporting work because nothing else does. You can examine that communication need without telling the employee they have been using the meeting incorrectly.
The broader issue is how communication supports collaboration. Moving information is useful only when people retain the context needed to work together. The goal is not fewer spoken words at any cost.
Name the Drift Without Blaming the Employee
Managers have a particular responsibility here. Giving an employee room to steer does not mean waiting indefinitely for them to repair the meeting. If you notice that feedback or direction keeps disappearing, you can raise it yourself.
A manager could say, hypothetically: "We've spent most of our recent conversations on project updates. That's understandable, but I also want to make room for what you need from me beyond reporting progress."
That acknowledges the pattern without declaring the previous conversations worthless. It also puts responsibility on the manager to contribute, instead of handing the employee an assignment to become more interesting.
An employee could approach the same issue differently: "The project still matters, but there's something I haven't found room to discuss. Could we make time for it rather than use the whole conversation for the update?"
Neither example is a script to memorize or remembered dialogue. The important shift is making the meeting's purpose explicit while keeping the responsibilities distinct:
- Both people can influence the conversation.
- Their authority is not equal, and the manager's obligation to support the employee remains.
Inviting input is not the same as transferring accountability. The manager still needs to act on the invitation by leaving room and responding to what the employee brings.
In my episode about better feedback and the manager relationship, I discuss how a narrow status-only pattern can make other subjects feel unfamiliar. Trust and respect require work from the manager too. A title does not make that trust automatic.
Give One Neglected Need Real Space
The repair does not require a giant list of alternative topics. Start with something that has repeatedly been crowded out, and give it enough attention to become a conversation rather than a final-minute mention.
Perhaps an employee wants feedback on a recent interaction. Perhaps they need clarity about where their responsibilities are heading. The point is not to cycle through categories until the meeting looks balanced. It is to understand a real need that the reporting habit has left unaddressed.
For a manager, a hypothetical opening might be: "Looking ahead, is there something about your responsibilities that we haven't had enough space to discuss?" That leaves the direction open rather than assuming the person wants a particular promotion.
Development need not mean assigning more work outside working hours. If learning has been postponed repeatedly, it may help to examine whether relevant experience can fit into actual responsibilities. The distinction between learning at work and learning at home is useful context, not a requirement to pursue the same goal as everyone else.
Avoid replacing one repetitive meeting with another. There is a difference between:
- Examining something specific enough to discuss usefully.
- Requesting a fresh overall verdict when little has changed.
A weekly global assessment of progress may yield little new information. Making room for feedback should expand what is possible, not require another repetitive performance every week.
Keep Project Pressure From Becoming a Permanent Exception
During a demanding project, a manager may need to acknowledge that work really is top of mind. It is reasonable to start there. What matters is whether the neglected discussion has a way back into the relationship.
If you agree to revisit something, be clear enough that both people know it has not vanished. You might return to it in the next conversation or agree that another time makes more sense. There is no universal interval for every subject.
Managers also need room to prepare a useful response. If someone asks for feedback and you have not collected your thoughts, say that. Give what you can responsibly offer, then follow up rather than allowing the unfinished answer to become the last word.
Weekly is my usual one-on-one cadence, with the balance worked out between manager and employee. Protect that time while allowing exceptions. If a meeting is cancelled, ideally reschedule or reach a mutual understanding instead of silently losing the chance to talk.
Otherwise, the exception can become self-reinforcing: delivery absorbs the meeting, the next meeting moves, and the deferred subject never returns. The calendar is part of the repair when it determines whether promised space actually exists.
Change the Manager's Response, Not Just the Opening Question
A broader opening does not help much if the manager turns the first work update into a long response that consumes the remaining conversation. The meeting can revert to status-only even after both people agreed it should change.
I need to practice listening and asking questions instead of immediately jumping into solutions. That does not mean managers should never answer directly. Sometimes the employee needs information or a decision you can provide. Sometimes they need room to explain what is happening before you can tell what help would be useful.
My earlier writing on being a human sounding board explores that listening perspective. It is historical context, not a current standardized meeting process.
The employee does not need a complete solution before raising a problem. Nor does the manager need to turn every concern into an action immediately. Clarifying the situation can itself be useful, provided neither person mistakes that clarification for a commitment to intervene.
Keep the repair proportionate. Two signs are more useful than a perfectly documented meeting:
- Something previously overlooked actually received attention.
- An agreed next step returned to the conversation instead of disappearing.
Remember commitments and notice whether the conversation is becoming more useful. You do not need a comprehensive archive or a performance score for every meeting to recognize those changes.
Frequently Asked Questions
These questions clarify the boundaries of the repair rather than prescribe another meeting formula. The common thread is preserving useful discussion while making sure the recurring conversation does not become permanently narrower than the support the person needs.
Are one-on-one status updates always a bad use of time?
No. Work can be top of mind, especially during a pressured project, and discussing it can help. The concern is a continuing status-only pattern that leaves support, feedback, or direction without space. Judge the recurring relationship, not an individual update in isolation.
Should all status updates move to asynchronous channels?
Not necessarily. Written updates can work, but so can a suitable synchronous discussion. Agree where routine information belongs and check that the channel actually serves its purpose. Keep room for individual questions that require more than receiving a report.
Can we still discuss technical architecture in a one-on-one?
Yes. A manager with relevant context may help clarify something important. Technical discussion is not inherently misplaced. Examine whether it meets a real need and whether other needs remain addressable, rather than banning the subject.
Who should raise a recurring status-only pattern?
Either person can raise it, but the manager should not wait for the employee to fix everything. Managers can notice neglected subjects and proactively make space. Employee agency matters without making the power or accountability on both sides equal.
Do we need career feedback in every meeting instead?
No. Replacing every status report with a weekly overall verdict can become repetitive when little has changed. Specific feedback and discussion of future direction can be useful when there is something meaningful to examine. Understand the individual's goals rather than assuming advancement is everyone's priority.
Does a more personal conversation require sharing private information or recording it?
No. Personal sharing is voluntary, and volunteered information is private. Recording and AI notes are off by default in my one-on-ones. Extremely rare exceptions require mutual opt-in because note capture would help both people focus; broadening the conversation is not consent to capture it.
Restore the Purpose, Not a Perfect Meeting
Repairing one-on-one status updates is not about proving that work should never enter the conversation. It is about preventing routine reporting from becoming the only interaction available.
Keep the work discussion that helps. Agree where repeated information can go. Make real room for something that has been neglected, and let the next conversation build on what you understood. The recurring meeting becomes more useful when its purpose can expand beyond knowing what happened.