When your manager keeps cancelling one-on-ones, the problem can become bigger than an inconvenient calendar. Questions remain unanswered. A concern you meant to discuss keeps waiting. You have a recurring invitation, but you cannot reliably use it to get support. That gap matters even when every individual cancellation has an understandable explanation.
It also does not prove your manager dislikes you or is deliberately avoiding you. Managers face competing demands, and exceptions happen. The useful distinction is between moving a conversation while preserving support and repeatedly losing the conversation altogether.
My usual cadence is weekly, with the balance agreed between manager and employee. I think managers should try to protect that time while leaving room for flexibility. If a meeting is cancelled, ideally it gets rescheduled or both people reach a mutual understanding. What deserves attention is the recurring loss of access, not a rule that every calendar change is unacceptable.
Cancelling One-on-Ones: Exception or Pattern?
A meeting moved to another workable time is different from a meeting that disappears. An explained exception can be reasonable. But a series of individually reasonable exceptions can still leave you without the support the meeting was supposed to provide.
In my discussion about unsupported developers, I explain how this can creep in rather than arrive as an obvious change. At first, each disruption seems isolated. Eventually, the relationship may depend on a conversation that keeps getting pushed out of reach.
There is no useful universal cancellation count that separates acceptable from unacceptable. The circumstances and consequences matter. A moved meeting with a completed follow-up can preserve continuity. A cancelled meeting that leaves an important question unanswered can have a much more immediate impact.
Look at the relationship around the calendar:
- Does the conversation actually happen at another agreed time?
- Can you get help when something cannot wait?
- Do previously discussed concerns still receive attention?
- Is there shared understanding, or are you left guessing?
These are questions for understanding the situation, not an attendance score. You do not need to classify your manager as good or bad before noticing that access is becoming unreliable. You can acknowledge a legitimate exception and still recognize that the cumulative effect needs addressing.
What Disappears When the Meeting Disappears?
The lost time is only part of the issue. One-on-ones can provide individual context that a team meeting does not. You might understand the project's progress while still needing clarity about your own responsibilities or support with a decision.
Consider a hypothetical engineer who needs to understand an internal approval process. Their regular meeting keeps moving, and they do not know who can answer the question in the meantime. The impact is not simply disappointment about a missed conversation. They are being asked to proceed without the context they expected their manager to help provide.
Another hypothetical employee might be waiting to discuss an unresolved commitment from an earlier meeting. If the next conversation repeatedly disappears, there is no reliable point at which to learn what happened. The employee has to keep deciding whether to wait or chase an answer.
That distinction helps keep the discussion specific. The concern may be:
- Access to a decision or explanation.
- Space to discuss an individual concern.
- Continuity on something already agreed.
You do not need to claim every cancellation causes all of these problems. Identify what is actually missing in your situation. This is part of the broader responsibility described in hands-on management: staying involved enough to provide useful support without making every detail depend on the manager.
The employee also does not have to reveal private personal information to make the lost time count. A work-related support need is enough. The question is whether there is a functioning way to address it.
A Busy Manager Still Has a Support Responsibility
Managers are employees too. Their calendars can be constrained by demands they do not fully control. A scheduling conflict may reflect pressure elsewhere rather than a deliberate judgment about the employee.
I discuss scheduling pressure and the risk of losing continuity in my episode about supporting direct reports. Moving the meeting time is not necessarily the same as deprioritizing the person. But that distinction has to show up in what happens next, not just in the manager's intention.
There is a difference between explaining a constraint and treating it as a permanent exemption from supporting the team. If a manager is spread too thin to provide support, they need to raise that capacity problem with their own manager. The employee cannot solve the manager's workload simply by becoming more patient.
For managers, protecting time is a practical responsibility rather than a claim that nothing else ever matters. When an exception occurs, explain what you can, discuss the replacement conversation, and consider any need that cannot wait. You do not have to disclose private circumstances to do that.
For employees, understanding the constraint can help you make a realistic request. It does not require pretending the impact disappeared. Both statements can be true: the manager has a legitimate conflict, and the current arrangement is not providing enough support.
Repeated Moves Can Send a Message Without Proving Intent
If your conversation is repeatedly the one that moves, it can feel as though it is not valued. That interpretation deserves attention. It is not automatically evidence of malice, and it is not something a manager can dismiss merely by saying they care.
Separate what you can observe from what you are inferring. The observable part might be that conversations are not being replaced, questions remain open, or you do not know when you will have access. The inference might be that your manager does not want to hear from you.
You can discuss the first without having to prove the second. That keeps the issue attached to something both people can examine. It also leaves room to learn about constraints you cannot see.
Managers should not use that uncertainty to invalidate the employee's experience. If you intended to make a temporary calendar change but the employee has been unable to get help, your intention does not resolve their problem. Leading by example is a related leadership principle: what you demonstrate matters alongside what you say.
This is not an argument for suspiciously interpreting every schedule change. It is an argument for noticing the message a repeated pattern may send and checking whether support is being preserved.
Explain the Lost Access, Not Just the Calendar Change
When there is a workable opportunity to raise it, focus on what the recurring disruption is preventing. You do not need a general case against the manager. You need shared understanding that the support channel itself is unreliable.
For example, an employee could say: "When our meetings move without a replacement, I don't know when I can discuss the questions I've been holding. Could we work out a time that is more realistic to protect?" This is hypothetical language, not remembered dialogue or a required script.
The useful parts are the observation, the impact, and the request for a workable arrangement. You can keep the wording natural rather than treating the example as something to recite:
- Describe the lost opportunity to talk.
- Explain the support that remains unavailable.
- Ask to agree on a realistic way to connect.
A detailed explanation of every previous cancellation is not necessarily more helpful than a clear description of the unresolved need. Cancelling one-on-ones is the visible disruption; missing support is the issue to understand together.
A manager responding to that concern can ask what has been left waiting, listen, and clarify what they can commit to. Listening before supplying your answer is relevant here. That earlier perspective reinforces making room to understand the other person's experience.
This conversation differs from raising one difficult subject inside an otherwise dependable meeting. Here, you are trying to regain the place where those subjects could be discussed. If even a short conversation about access cannot happen, repeatedly preparing a better explanation is not a substitute for managerial availability.
The employee can make the impact clearer. The manager remains responsible for responding to the support gap. Those responsibilities are not equal in authority or control.
Agree on Realistic Continuity When Cancelling One-on-Ones
The aim is not a promise that another cancellation will never happen. It is an arrangement that both people understand and that the manager can realistically sustain. A more impressive calendar commitment is not useful if it keeps disappearing.
Rescheduling preserves dedicated conversation time, but it can create another round of coordination if the proposed replacement is equally fragile. A mutually understood exception can be reasonable when there is no pressing issue left waiting. It becomes less useful if "we both understand" only means the employee silently accepted the invitation disappearing.
Different adjustments address different constraints:
- A different recurring time may address a predictable scheduling conflict.
- A different agreed cadence may fit the individual's needs and the manager's available time.
Weekly is my usual balance, not a rule everyone must follow. Reducing frequency should not become a way to rename an unresolved loss of support. Before changing the arrangement, understand what the employee would still need between conversations.
An interim channel can help with something that cannot wait, provided both people know what it is for and whether a response is realistic. It need not replace every subject that benefits from a conversation. A team status meeting or an unanswered message is not automatically equivalent to individual access.
The principle behind improving collaboration applies: people need an understanding of how they will work together. In this case, that includes what happens when the usual conversation cannot happen.
Managers can take the lead by offering a workable alternative rather than leaving the employee to search every gap in the calendar. Employees can explain which needs the alternative does or does not meet. Flexibility should preserve support, not merely make repeated disruption easier to administer.
Look for Follow-Through, Not Just Reassurance
An acknowledgement is a start. It is not evidence that continuity has been restored. After discussing the recurring cancellations, look at what the agreement actually changes:
- The replacement conversation happens.
- Waiting questions receive attention.
- A further exception has a clear resolution.
These are signs of follow-through to notice, not a scorecard or a requirement to audit every interaction. The agreement should make access less uncertain.
No one needs to create a cancellation spreadsheet or a standardized notes system for this. A brief personal reminder about an agreed next step may be enough. If both people want to capture a shared action, they can agree where it belongs without documenting the entire relationship.
Imagine a hypothetical manager who agrees to move the recurring slot because it clashes with another obligation. If the new conversation happens and the unanswered topic gets attention, that is meaningful follow-through. If the new slot also disappears without discussion, the underlying problem remains despite the revised invitation.
Continuity also includes the substance of the meeting. Restoring calendar time is incomplete if the manager no longer remembers the outstanding concern and nothing progresses. The risk is not just absence; it is repeatedly losing the thread.
My earlier account of one-on-one evolution documents a historical approach, not my current notes process or a system you must adopt. The relevant connection is examining whether the arrangement is actually useful. For this problem, usefulness means dependable access and attention to what was left unresolved.
If Support Still Does Not Return
You may decide a direct conversation is worth attempting. You may also have already made the problem clear without seeing improvement. There is no obligation to keep finding a more persuasive way to ask for the same basic support.
In my discussion about developers leaving good companies, I explain why I do not see these situations as an automatic stay-or-leave decision. Your available support, the broader working environment, and the energy you want to invest matter.
Depending on the circumstances, possible directions include:
- Seeking help from another appropriate leader.
- Exploring a different team.
- Considering a different workplace.
These are possibilities, not a mandatory sequence. None comes with a guarantee of a good response, and escalating a concern is not automatically safe in every environment. Repeatedly cancelling one-on-ones does not prescribe the same decision for every employee.
Keep the issue focused if you choose to discuss it elsewhere: access is unreliable, particular support needs remain unresolved, and the agreed alternative has not worked. You do not need to turn it into a complete assessment of the manager's competence.
Managers should not interpret an employee's limited appetite for further repair as lack of commitment. The support responsibility does not transfer to the employee because they identified the gap. Nor does deciding to try again mean someone owes unlimited effort if nothing changes.
Frequently Asked Questions
The questions below concern recurring loss of access and support, not a requirement that every meeting happen exactly as originally scheduled or that every disruption receive the same response.
Is cancelling one-on-ones always a sign of a bad manager?
No. Exceptions and scheduling pressure exist. A cancellation can be handled with rescheduling or mutual understanding. Repeated lost conversations deserve attention because of their effect on access and support, but they do not by themselves establish the manager's motive.
How many cancellations are too many?
There is no universal number. Consider what is left unanswered, whether conversations are replaced, and whether support remains accessible. You do not need to reach a numerical threshold before explaining that the current arrangement is not meeting a real need.
Should one-on-ones happen every week?
Weekly is my usual cadence, with the balance agreed between manager and employee. A different arrangement may be workable. The important issue is whether it preserves dependable support, not whether it follows a universal frequency rule.
What if my manager genuinely has no time?
That constraint can be real without making lost support acceptable indefinitely. The manager should raise a capacity problem that prevents them from supporting the team. Together, you can clarify a realistic arrangement, but the employee is not responsible for fixing the manager's workload.
Can messages replace a cancelled meeting?
They may help with a specific question if there is a workable expectation of a response. They do not automatically replace every conversation or resolve an ongoing access gap. Discuss what the interim channel can provide and what still needs dedicated time.
Do I have to escalate or leave if nothing changes?
No automatic rule applies. Consider the support available, the risks, and the effort you want to invest. Further discussion, seeking other support, or exploring a change may be options. You do not owe endless repair attempts, and no escalation path is guaranteed safe.
Flexibility Should Preserve the Relationship
The point is not to make cancelling one-on-ones forbidden. It is to recognize when flexibility has stopped preserving the conversation and started erasing it. A manager can have legitimate competing demands and still need to address their effect on individual support.
A workable relationship leaves both people understanding when they can talk, what happens during an exception, and whether commitments carry forward. That continuity matters more than a reassuring invitation that remains on the calendar but rarely becomes a conversation.