Your manager is not “just busy”; they are signaling distance, triage, or avoidance. At Uber, repeated 1:1 ghosting is rarely a calendar issue by the second or third miss. Treat it as a management signal, not a personal injury: document the pattern, reset the meeting in writing, and escalate only after the silence becomes repeat behavior.
TL;DR
Your manager is not “just busy”; they are signaling distance, triage, or avoidance. At Uber, repeated 1:1 ghosting is rarely a calendar issue by the second or third miss. Treat it as a management signal, not a personal injury: document the pattern, reset the meeting in writing, and escalate only after the silence becomes repeat behavior.
Not sure what to bring up in your next 1:1? The Resume Starter Templates has 30+ high-signal questions organized by goal.
Who This Is For
This is for the PM, EM, analyst, operator, or program lead at Uber who has had two canceled 1:1s in a row, or three reschedules in 14 days, and is now trying to read the room without looking insecure. It is also for the person whose manager is still active in Slack, still visible in staff meetings, but somehow unavailable for the one meeting designed for actual management. If you are waiting for a warm explanation, you are already losing time.
Why is my manager ghosting my 1:1s at Uber?
Because avoidance is cheaper than honesty. In a debrief I sat through, a hiring manager described a weak candidate as “not yet ready for ownership,” then spent the next two weeks canceling the feedback conversation that would have made that sentence explicit. Managers do the same thing internally: they delay the hard talk until they have to commit to one.
The problem is not your calendar; it is their priority stack. The problem is not that they forgot; it is that your 1:1 fell below whatever they believe is urgent enough to protect. Not every cancellation is disrespect, but repeated cancellations are never neutral. They tell you where your work sits in the manager’s mental queue.
At Uber, this gets amplified because fast-moving teams normalize interruption. Reorgs, launches, incident response, and shifting metrics create a culture where leaders claim they are “swamped” and mean it. That is not the same as being available. A manager can be overwhelmed and still be responsible; what matters is whether they make space for the work of management, not just the work of execution.
The counter-intuitive truth is that ghosting often correlates with uncertainty, not busyness. When a manager knows exactly what they want to say about your priorities, they usually make time. When they are unsure whether you are delivering, unsure how to give feedback, or unsure whether your role is being reconsidered, the 1:1 becomes the meeting they keep pushing away. Not lack of bandwidth, but lack of clarity. Not scheduling friction, but judgment friction.
In one Uber-like org discussion, the room spent 20 minutes debating whether a skipped 1:1 meant the manager was overloaded or disengaged. The answer was uglier: the manager had no crisp update to deliver, and no one wanted to be the first to say the relationship had gone stale. That is organizational psychology 101. People avoid conversations that force them to define a reality they have been keeping vague.
> 📖 Related: Uber PM Interview: Product Sense Round for Mobility vs Delivery Teams
What does repeated 1:1 cancellation actually signal?
It usually signals one of four things: low trust, low urgency, low managerial confidence, or simple neglect. The first two are the ones people resist naming because they sound personal. They are personal. Management is personal. A 1:1 is where a manager proves they can track your work, your risks, and your trajectory.
Not every ghosted 1:1 means you are in trouble, but every repeated ghosted 1:1 means you are not being actively managed. That distinction matters. If your manager still gives you clear priorities in writing, still answers specific questions, and still closes loops quickly, then the silence may be logistical. If they are vague in Slack, vague in meetings, and absent in 1:1s, then the problem is structural.
A useful judgment test is this: does your manager only appear when they need output from you? If yes, then the relationship has shifted from management to extraction. I have seen this in performance calibration when a manager suddenly becomes very present right before reviews, then disappears again after the packet is locked. That pattern is not a communication style. It is a signal that the manager is managing the surface, not the person.
The organizational principle here is signal debt. Every missed meeting adds ambiguity, and ambiguity always gets paid somewhere else: in lower trust, slower feedback, and worse performance conversations. The people who think they are saving time by skipping 1:1s usually create more work later, because unresolved questions do not disappear. They just migrate into reviews, promotion packets, and skip-level complaints.
So the judgment is simple. One missed 1:1 is noise. Two missed 1:1s is data. Three missed 1:1s in a month is a pattern. At that point, stop telling yourself the calendar is the issue. The relationship is speaking.
When should I stop waiting and escalate?
You should stop waiting after the pattern is clear, not after your frustration peaks. Escalation is justified when you have two missed 1:1s in a row, or three cancellations within 14 days, and your manager still has not proposed a concrete reset. Anything less is probably too early; anything more and you are volunteering to be managed by absence.
The mistake is thinking escalation means drama. It does not. It means routing the problem to the level where someone can actually own it. In a hiring committee debrief, a strong candidate once got credit not because they complained early, but because they raised a crisp issue at the right level with evidence and no theatrics. The same standard applies here. You are not trying to punish your manager. You are trying to restore management.
Not escalation, but routing. That is the right frame. A skip-level is appropriate when your manager has stopped functioning as the bridge between your work and the organization. You are not going over their head to be clever. You are going around a broken communication path because your output, priorities, or growth path cannot stay in limbo.
There is a managerial psychology point here that people miss. Managers often tolerate vague silence until they are forced to confront specificity. A skip-level works only if you can say, plainly, “I have missed two 1:1s, I need clarity on priorities and feedback, and I want to know whether there is a better cadence for us.” That is not emotional. It is administrative. It gives leadership a decision point instead of a complaint.
If the silence continues after a written reset and one clean escalation, the judgment changes. Then you are no longer dealing with a temporary disconnect. You are dealing with a manager who either cannot or will not manage you. At that point, the right question is no longer how to fix the 1:1. It is whether this role has become a dead zone.
> 📖 Related: uber-vs-lyft-PM-interview-2026
What should I say in Slack or email?
Say less, not more. The right message is short, specific, and anchored to missed meetings and concrete asks. A needy message sounds like a check-in. A strong message sounds like a reset.
Use this shape: acknowledge the missed meeting, name the purpose, and propose a new time with a narrow agenda. For example: “We’ve missed the last two 1:1s. I need 15 minutes to align on priorities, any feedback on my current projects, and what you want me to de-risk this week. Can we do Thursday at 2:30 or Friday at 11?” That is not chasing. That is management hygiene.
Not “are you still interested in meeting,” but “here is the decision I need from you.” Not “just wanted to check in,” but “I need clarity on priorities and feedback.” The first version invites vagueness. The second version forces accountability. Managers respond better to specificity because it lowers the cost of replying and removes the social fog.
In one skip-level conversation I watched, the employee had sent four soft pings and received nothing. The fifth message finally named the problem: repeated cancellations, missed feedback, and a request for one concrete meeting within 48 hours. That message got a response within a day. The lesson was not that kindness failed. The lesson was that ambiguity protects avoidance.
If you need to escalate, keep the language clean. Do not write a diary. Do not attach emotion to every missed slot. Document the dates, the meeting purpose, and the impact on your work. The most effective internal messages read like status memos because they leave no room for a manager to pretend the issue is your tone.
How do I protect my career if the pattern continues?
You stop depending on one manager for all your signal. That is the real career protection. If your manager is inconsistent, you build parallel visibility through documented wins, cross-functional relationships, and one or two people who can verify your impact when your manager is absent.
At Uber, where teams move quickly and priorities reset often, silence is not harmless. A manager who disappears from your 1:1s can still influence your review, your scope, and your reputation. So the job is to create an evidence trail. Keep your weekly updates tight. Save the dates of canceled meetings. Record decisions, asks, and blockers in writing. When the review season comes, memory will be political. Notes will not.
There is a harder judgment here. If your manager is ghosting you while still appearing energetic elsewhere, the issue may be local to the relationship, not global to the company. That matters because people sometimes overread one bad manager as a reason to leave immediately. Not always wrong, but often premature. A bad manager is a risk. A structurally bad role is a different problem. You need enough evidence to tell the difference.
The practical test is whether the situation improves after one clean reset. If your manager schedules the next 1:1, shows up prepared, and gives you clear feedback, then the relationship was degraded but salvageable. If they keep canceling after a direct written note, then you are not in a temporary rough patch. You are in a management failure. At that point, protect your upside by looking sideways internally or externally.
The deeper principle is that career risk compounds in silence. When no one is speaking plainly, people make assumptions, and assumptions harden into narratives. If your manager is absent, your narrative becomes whatever other leaders infer. That is why documentation is not bureaucracy. It is defense.
Preparation Checklist
- Count the missed meetings and write down the exact dates, the reschedule pattern, and whether your manager proposed new times or left you hanging.
- Send one direct reset message with a narrow agenda: priorities, feedback, blockers, and next steps.
- Keep your update crisp enough to be forwarded without embarrassment. If your manager cannot summarize your work after reading it, the message is too loose.
- Ask for one concrete decision in the next 1:1: what matters most this week, what can wait, and what risk they want you to own.
- Save every cancellation and reschedule in one place. When the story gets fuzzy later, dates are what hold.
- If the pattern persists for 7 to 10 days after your reset note, request a skip-level or partner manager conversation.
- Work through a structured preparation system (the PM Interview Playbook covers manager-skip conversations, escalation framing, and debrief-style feedback examples that map well to this kind of internal reset).
Mistakes to Avoid
- Turning it into a personal accusation.
BAD: “You never make time for me.”
GOOD: “We’ve missed two 1:1s in 14 days. I need 15 minutes to align on priorities and feedback.”
The first line invites defensiveness. The second line forces a professional response.
- Escalating after one cancellation.
BAD: Sending a skip-level note after the first reschedule.
GOOD: Reset once in writing, then escalate only if the pattern continues.
The issue is not that you are impatient. The issue is that you are confusing inconvenience with evidence.
- Using the 1:1 to ask for vague reassurance.
BAD: “Am I doing okay?”
GOOD: “What are the two outcomes you need from me before the next review cycle?”
The first asks your manager to comfort you. The second asks them to manage you.
FAQ
- Should I assume I’m being managed out if my manager ghosts my 1:1s?
Not after one or two misses. Treat it as a risk signal only when the pattern persists after a direct reset. If the silence continues for 3 weeks and they still avoid clear feedback, then the relationship is no longer healthy.
- Should I go straight to HR?
No. HR is not the first stop for ordinary management absence. Start with a direct written reset, then use a skip-level or partner manager if the pattern continues. HR matters when there is policy abuse, retaliation, or harassment, not routine avoidance.
- How do I tell the difference between overload and disengagement?
Look at response quality, not just response time. A genuinely overloaded manager may still answer specific questions and reschedule quickly. A disengaged one stays vague, cancels repeatedly, and only appears when they need output. That is not overload. That is low management investment.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.