What to Discuss in 1:1s When Your Big Tech PM Team Faces Layoffs

TL;DR

In a Q3 debrief I sat through, the hiring manager pushed back on a PM candidate for the same reason this fails in layoffs: the answer was emotionally accurate and operationally useless. The candidate talked for four minutes about uncertainty and never named what they would actually do next. In a layoff period, your manager is making the same judgment. They are not scoring your anxiety. They are scoring whether you can reduce chaos.

The wrong 1:1 during layoffs is not a vent session. It is a signal test.

In a Monday 1:1 after a finance review had already slipped into rumor territory, the PM asked for reassurance and got none. The manager was not hiding a plan; he was hiding his own lack of authority. The PM who survives that moment does not ask for comfort. They ask for decision rules, scope boundaries, and the next checkpoint. Not reassurance, but operating clarity. Not rumor control, but narrative control.

What should I ask in the first 1:1 after layoffs start?

Ask for what is still real, not for a promise that nobody can legally or honestly give you.

The first counter-intuitive truth is that you should ask fewer questions, but each question should have an operational purpose. Try this sequence: “What work is protected for the next 30 days?” “What should I stop doing this week?” “What would make me a clear keep for the next review?” That is not a therapy session. It is a prioritization meeting. If your manager cannot answer, the answer is still useful. It tells you where authority stops and where your risk begins.

Use direct scripts. “Before we talk about the backlog, I want to understand what is still being funded.” “I am not asking for a promise. I am asking for the decision rule.” “If I only have one month to prove value, what should be visible by the next 1:1?” These lines work because they force a manager out of vague empathy and into concrete thresholds.

How do I read my manager’s answers without overreacting?

Read evasiveness as constraint, not automatically as betrayal.

In a layoff debrief, managers often say they “don’t know” when what they really mean is “I am not allowed to tell you yet.” That distinction matters. The problem is not the answer. The problem is the judgment signal hidden inside the answer. If a manager gives you a clean yes or no, they still have leverage. If they give you layered uncertainty, they may be trying to protect you, or they may be protecting themselves. You need to tell the difference.

The second counter-intuitive truth is that vagueness is a management signal. In organizations under pressure, people start speaking in ranges, not commitments. That is not because they suddenly became bad communicators.

It is because the cost of precision went up. When your manager says, “We are still aligning,” the real question is whether they will also tell you what assumptions are already locked. Ask, “What can I safely assume?” and “What should I not repeat to others yet?” Those two questions reveal whether you are being treated like an adult stakeholder or a rumor buffer.

Do not ask, “Can you just be honest with me?” That invites theater. Ask, “What has already been decided above your level?” Ask, “What is still in play versus what is already dead?” Ask, “Who is the next person I should expect to hear from?” Not promise-seeking, but map-making. That is the only useful posture when the org is unstable.

What should I say if I need to protect my scope?

Say what you own, what you can drop, and what you need to keep stable.

A strong PM in a layoff window does not try to look busy. They try to look legible. In one manager conversation I remember, the PM walked in with a rambling status update and left with a reputation for being hard to place. The PM who won the room instead said, “Here are the two outcomes that cannot slip, here is the work I can de-scope, and here is the decision I need from you.” That PM sounded less emotional and more expensive.

The third counter-intuitive truth is that shrinking your surface area can increase your survival odds. Managers do not reward theatrical breadth when they are forced to defend headcount. They reward the person who can explain why three projects should become one. Not more work, but clearer work. Not louder ownership, but tighter critical path. Not “I can help with anything,” but “I can keep this one thing from breaking.”

Use language that sounds like a calm operator. “If we are in protect-the-core mode, I should drop X and keep Y.” “If you need me to absorb reorg noise, I need a clear owner for Z.” “I can take on more, but only if you tell me what stops.” These are not soft lines. They are boundary-setting lines. In a layoff cycle, boundaries are a sign of judgment, not fragility.

How do I use 1:1s to decide whether to stay or leave?

Use the 1:1 to measure trust, not sentiment.

People make a mistake here. They think the decision is whether they still feel loyal. It is not.

It is whether the manager can still offer you a believable path through the next 30 to 60 days. In a reorg conversation after a headcount freeze, I watched a PM spend half the meeting asking whether the company “still believed” in the team. The manager could not answer that, and the PM treated the silence as a verdict. The better question would have been: “What path exists for me here if this team is smaller, flatter, or split?”

The fourth counter-intuitive truth is that your private search starts before your public exit. Not because you should panic, but because layoff environments compress optionality. You do not announce anything to the room. You quietly preserve your narrative, your references, and your artifact trail. That means your 1:1s should surface whether your manager can still describe your value in one sentence. If they cannot, that is data. If they can, but only in abstract terms, that is also data.

Use a script that keeps you out of drama. “I want to understand whether I am in a role you can still advocate for.” “If the team changes shape, where do you see my work landing?” “What would you tell another leader if they asked why I should stay?” That is not disloyal. That is a decision audit.

What should I tell peers and cross-functional partners?

Tell them less than your anxiety wants and more than silence allows.

In layoff periods, the worst behavior is rumor amplification disguised as transparency. The second worst is fake calm. The right move is a narrow, stable line. I have seen PMs lose credibility by broadcasting speculation to design, engineering, and sales all in the same afternoon. The people who kept trust did not pretend nothing was happening. They simply refused to become a secondary news source.

Not oversharing, but stabilizing. Not pretending certainty, but refusing conjecture. That is the standard.

If a designer asks what is happening, say, “I do not have verified details, and I am not going to fill gaps with guesswork.” If a partner pushes for more, say, “I will share what is confirmed when it is confirmed.” That language sounds thin to anxious people, but it protects your name. In a small org, your reputation is not built by how much you know. It is built by how carefully you handle what you do not know.

The cleanest line I have heard in this setting was: “I am focused on keeping the work real and the noise contained.” That is the whole job. A layoff wave punishes people who become narrators. It rewards people who stay operational.

Preparation Checklist

Write down the three questions you need answered before the 1:1: what is protected, what can move, and what decision rule is in play.
Prepare one sentence on the work that cannot slip in the next 30 days.
Decide in advance what you will stop doing if your manager asks for de-scope.
Keep a private log of commitments, evasions, and dates mentioned in the conversation.
Prepare a calm line for severance, redeployment, and HR questions in case the discussion turns formal.
Work through a structured preparation system (the PM Interview Playbook covers layoff-era narrative framing and real debrief examples) so your story stays coherent while the org is not.
Have one script ready for peers that shuts down speculation without sounding evasive.

Mistakes To Avoid

The failure is not asking hard questions. The failure is asking them in a way that makes you sound unmanaged.

BAD: “Can you just tell me if I’m safe?”

GOOD: “What are the criteria you are using to decide what stays?”

BAD: “I heard the team is getting cut, is that true?”

GOOD: “What is confirmed, what is still being discussed, and what should I ignore for now?”

BAD: “I can do anything, just keep me informed.”

GOOD: “I can take on more scope, but I need a clear owner for what gets dropped.”

The first mistake is turning the 1:1 into emotional triage. That invites sympathy, not strategy. The second mistake is demanding promises your manager cannot make. That creates distance. The third mistake is becoming a rumor relay. That destroys trust faster than uncertainty does.

FAQ

Should I ask directly whether layoffs are coming?

Yes, but do it once, cleanly, and without forcing your manager into speculation. Ask, “What is confirmed, and what should I plan around?” If they cannot answer, that is already an answer about their access and your risk.

Should I tell my manager I am interviewing?

Not unless your relationship is unusually strong and the timing is safe. In a layoff window, that confession often buys you nothing and can narrow your room to maneuver. Protect your search quietly until you know where you stand.

Should I keep talking about morale with my team?

Only if you can keep it grounded in facts and work. Morale talk without facts turns into contagion. Say what is confirmed, what remains unclear, and what the next delivery point is. That is leadership.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn't have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.