In the first staffing review after an Uber acquisition closes, the people who rely on 1:1s to protect them are the first to get surprised. This is not a relationship problem, but a control problem. Your job is to become legible in writing before the new org chart hardens, because informal reassurance dies fast once decision rights move.
1on1 Alternatives During Company Acquisition at Uber: Protect Your Role
TL;DR
In the first staffing review after an Uber acquisition closes, the people who rely on 1:1s to protect them are the first to get surprised. This is not a relationship problem, but a control problem. Your job is to become legible in writing before the new org chart hardens, because informal reassurance dies fast once decision rights move.
If you wait for a friendly manager conversation, you will confuse politeness with security. If you want to keep your role, stop treating the 1:1 as the main channel and start treating it as a confirmation step. The people who keep scope are the ones who can show what breaks if they disappear.
Not sure what to bring up in your next 1:1? The 0→1 SWE Interview Playbook (2026 Edition) has 30+ high-signal questions organized by goal.
Who This Is For
This is for PMs, product ops, program leads, and adjacent managers on the acquired-company side who are hearing "we'll sync later" while their scope is already being redrawn. It is also for people inside Uber after a deal who can feel the temperature shift but still want to believe the old reporting line will protect them. If you need reassurance, this article will feel harsh. If you need a clean read on how acquisitions actually work, it will feel familiar.
What actually changes after an Uber acquisition closes?
The first thing that changes is not the logo. It is the chain of accountability.
In a first-week staffing review I watched, the room went silent when the new leader asked a simple question: "Which decisions become slower if this person leaves?" Nobody asked who was the nicest. Nobody asked who had been loyal. That is the real filter in an acquisition. Not whether you were visible, but whether you were structurally necessary.
This is not a morale event, but a portfolio reordering event. In the room, people stop talking about effort and start talking about replacement cost. That shift is why some people feel blindsided. They prepared their narrative. The leadership team was already building a map of dependencies.
The mistake is thinking the company wants a summary of your week. It wants a model of your leverage. If you cannot explain which launches, risks, or customer commitments sit on your work, the system will assign those assets to someone who can. That is how scope gets moved without drama.
There is a counterintuitive truth here. The more senior the audience, the less they care about your history and the more they care about your current bottleneck. People protect the work that is legible. In acquisitions, artifacts survive longer than intent.
Is asking for a 1:1 the right move, or should I use another channel?
A 1:1 is too slow and too private to protect you once the acquisition is underway.
In a Q3 debrief I sat through, the manager had strong private relationships with both sides of the deal. It did not matter. The room still moved scope because nobody could repeat, in one sentence, what that manager owned. The problem was not access. The problem was that the decision makers could not carry the argument into the next room.
This is why the 1:1 is a weak primary channel in an acquisition. It is useful for confirmation. It is weak for persuasion. Not asking for permission, but forcing clarity. Not a social check-in, but a decision request. If you want to protect your role, make the first move in writing and use the 1:1 to validate what is already visible.
The right test is simple. If the answer changes only when the conversation is private, then the answer is not stable enough to protect you. Stability in these moments comes from repeated, readable signals. That is the organizational psychology principle most people miss. Leaders inherit anxiety, so they trust what they can forward.
A good 1:1 request in this environment does not ask, "Do you have time to talk?" It says, "I want alignment on my scope, the decisions I own, and what you want me to stop doing in the next 30 days." That wording matters because it creates a record. A vague conversation creates comfort. A precise conversation creates commitment.
What should I send instead of a 1:1 request?
Send a one-page role memo, not a rambling update.
The memo should do three jobs. First, state the outcomes you own. Second, show the dependencies that break if you disappear. Third, list the risks you want decided in the next 7 days. In one acquisition review I saw, the PM who did this kept the analytics work because she made the cost of moving it obvious. Nobody could dismiss it as personality. It was operational evidence.
The point is not to look busy. It is to look structurally useful. Not a status update, but a decision memo. Not trying to be liked, but trying to be legible. In these rooms, legibility beats charm because it survives handoffs. A polished 1:1 can be forgotten by lunchtime. A concise memo gets pasted into the next staffing thread.
Use direct language. Write the work in terms the new leadership team uses: revenue, risk, launch, customer churn, platform stability, regulatory exposure, integration burden. If your role sounds abstract, it will be treated as optional. If it sounds like an input to a hard decision, it gets a seat at the table.
Include one line on what you will stop doing if priorities shift. That sounds risky to people who are still performing loyalty theater, but it signals judgment. Leaders trust the person who can name tradeoffs faster than the person who says yes to everything. The hidden rule in acquisitions is simple: the person who can trade scope gets more of it.
A useful memo format is short enough to read in under 3 minutes:
- What I own now
- What breaks if I move
- What I need confirmed this week
- What I will deprioritize if the new plan changes
That is enough. Anything longer turns into autobiography, and autobiography does not win staffing debates.
How do I stop my scope from being reassigned?
You stop reassignment by owning a workstream that senior leaders would have to recreate.
In the first 30 days after close, the people who keep scope are the ones attached to a revenue stream, a regulatory risk, a customer migration, or a launch date that cannot slip without explanation. If your work is useful but not expensive to move, it is easy to take. That is the harsh part. The organization does not assign sentimental value to effort.
This is not about being indispensable in a dramatic sense. It is about being the cheapest path to continuity. In a post-close staffing meeting, the debate usually collapses around one question: what breaks if this person is gone tomorrow? If the answer is vague, your scope is already negotiable.
There is a second layer most people miss. People are not only evaluating work. They are evaluating trust transfer. If a leader can hand your function to someone else without the audience asking questions, your role was never fully anchored. That is why the answer is not "work harder." The answer is "make ownership visible to strangers."
Build one artifact that shows your value without your presence. A decision log, a launch tracker, a customer-risk memo, or a weekly exec summary does more for your seat than ten verbal promises. Organizations do not preserve memory. They preserve the documents that explained why memory mattered at the time.
This is where the contrast matters. Not being visible, but being legible. Not being liked, but being hard to replace. Not having a loud relationship with the manager, but having a visible claim on a critical outcome.
If you want the practical test, ask yourself this: could someone new walk into the room, read one page, and repeat your value without you? If the answer is no, you are still dependent on proximity. Proximity is fragile during an acquisition. Structure is not.
When should I start interviewing elsewhere?
Start the outside search as soon as the role becomes vague, not when it becomes officially bad.
If you cannot get a clear answer on title, manager, level, or the next 60 days within 10 to 14 days after close, the internal situation is already telling you something. The delay is the signal. Leaders who want to keep you do not make you decode their silence for weeks. They name the plan, even if the plan is imperfect.
The outside market is not just an escape hatch. It is a calibration tool. If you can get through 3 to 5 interview rounds and see a cleaner scope with a real manager, the internal ambiguity stops looking noble. It starts looking expensive. That is not disloyalty. That is portfolio management.
A lot of people wait because they want one more private conversation. That is a mistake. A private conversation is not a contract. If your role is being negotiated by people who do not have to keep you, your leverage is already in the open market. The company can be polite while still shrinking your future.
The better question is not "Am I being fired?" It is "Is my future still being actively designed?" If the answer is no, you should act like a rational adult and build options. Waiting for a formal rejection is how people lose both time and confidence.
Preparation Checklist
Use artifacts, not hope, to keep your role visible.
- Write a one-page ownership memo with your top 3 outcomes, the decisions only you can make, and the risks that depend on you.
- Identify the 2 to 4 people who actually influence your scope: manager, skip, finance partner, and one cross-functional leader.
- Send a short written alignment request before asking for a 1:1. Keep it concrete: role, scope, next 30 days, decision owner.
- Convert your recent work into a simple evidence trail: launches, blockers removed, customers protected, revenue or risk reduced.
- Decide your fallback number now: the title, level, and cash floor you will accept if the new org weakens your seat.
- Work through a structured preparation system (the PM Interview Playbook covers acquisition-era scope reset and debrief examples from reorg-heavy interviews).
- Block time within the next 7 days to update your resume and LinkedIn while the facts are still current.
Mistakes to Avoid
The failure pattern is almost always the same: people mistake emotional comfort for strategic protection.
- Mistake 1: Treating the acquisition like a morale problem.
BAD: "I'll wait until everyone settles down and then ask what my role is."
GOOD: "I'll send a written role summary this week and force a decision on scope now."
- Mistake 2: Using a 1:1 to ask for reassurance.
BAD: "I just want to make sure I'm still valued."
GOOD: "I need clarity on what work stays with me, what moves, and who decides by Friday."
- Mistake 3: Confusing visibility with protection.
BAD: "I've been in every meeting, so I'm safe."
GOOD: "I have a memo that shows why removing me slows the org."
The underlying error is always the same. People optimize for being remembered. Leadership is optimizing for reducing friction. Those are not the same objective.
FAQ
These are the only three questions that matter if you are trying to protect your role.
- Should I push for a 1:1 if my manager is busy?
No. Ask for written alignment first. A busy manager can ignore a calendar hold and still read a memo. If the memo gets no response, the silence is the answer. That is not a communication issue. It is a priority issue.
- What if I’m told my role is “safe”?
Treat that as temporary until you see the new org chart and the next 30-day plan. People say safe when they mean undecided. Safe is not real until the work, the reporting line, and the decision rights are all written down.
- Is it disloyal to interview during an acquisition?
No. Loyalty does not protect your title, scope, or compensation. If the company is reassigning risk, you are allowed to reassign your own attention. That is not betrayal. That is judgment.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.