1on1 Script for Delivering Bad News to Manager at Google
TL;DR
Delivering bad news in a 1on1 at Google is not about softening the message but controlling the narrative. The best scripts preempt follow-ups, anchor to business impact, and end with a Forward-Looking Statement (FLS). Weak deliveries get buried in emotion; strong ones get escalated as signals.
Who This Is For
This is for mid-level ICs and new managers at Google who need to surface risks, delays, or failures to their skip-level without triggering a reactive spiral. If you’ve ever left a 1on1 with your manager more frustrated than aligned, this is your correction.
How do I open a 1on1 when delivering bad news at Google?
The first 10 seconds decide whether the conversation is a problem or a solution. Open with the headline, not the backstory: “The Q2 OKR for feature X is at risk due to a dependency block from team Y.” Not “I’ve been struggling with this,” not “I wanted to update you on some challenges.” The problem isn’t your tone—it’s your lack of immediate signal.
In a L4 promotion debrief last quarter, a candidate was dinged for “low executive presence” after a 1on1 where they spent 8 minutes on context before the punchline. The hiring committee’s note: “If they can’t prioritize information for their manager, they can’t prioritize for a VP.” At Google, clarity is a leadership trait.
What’s the difference between a good and bad bad-news script at Google?
A bad script focuses on blame or excuses: “Team Y keeps missing their deadlines, so we’re stuck.” A good script anchors to impact and ownership: “Because of the delay in team Y’s API, our launch is now 3 sprints behind, and I’ve already started mitigation with team Z.” The difference isn’t polish—it’s the shift from victim to owner.
In a skip-level 1on1, an L5 PM once said, “I think we might miss the deadline.” The manager’s response: “You think?” The script failed because it lacked certainty. Google rewards decisive language, even in uncertainty. Replace “might” with “will unless we course-correct by [date].” The problem isn’t the bad news—it’s the signal you’re not in control.
How do I structure the bad news in a Google 1on1?
Use the 3-part framework: Headline, Impact, FLS (Forward-Looking Statement). Headline: “The experiment showed a 20% drop in engagement.” Impact: “This risks the Q3 growth target by 5%.” FLS: “I’m pivoting to variant B, which we’ll test in the next sprint.” No fluff, no apologies—just data, stakes, and action.
During a hiring manager calibration for a senior PM role, a candidate’s 1on1 feedback was dissected. Their mistake: they buried the FLS in the middle. The HC’s note: “If they can’t close with action, they can’t lead through ambiguity.” At Google, the FLS is non-negotiable. It’s the difference between a problem and a plan.
Should I soften the bad news for my Google manager?
No. Softening is a signal of low confidence. Google managers respect directness because it saves time. In a director-level debrief, a manager recounted how an IC prefaced bad news with, “I’m not sure if this is the right time to bring this up, but…” The director’s feedback: “If you’re not sure, I’m not sure.” The problem isn’t the news—it’s the hesitation.
Counter-intuitive observation: The more senior the audience, the less they tolerate hedging. A VP at Google once cut off a PM mid-sentence with, “Just say it. I don’t need your emotional journey.” The judgment: softening undermines your credibility. Not because they’re harsh, but because they’re time-constrained.
How do I handle pushback when delivering bad news in a Google 1on1?
Anticipate the first three questions and answer them before they’re asked. If the news is “The vendor contract is delayed,” preempt with: “Legal is reviewing, finance has the budget on hold, and the backup vendor is identified.” Pushback isn’t rejection—it’s a test of your preparedness.
In a L6 calibration, a candidate was asked to replay a 1on1 where they delivered bad news. The HC noted: “They answered the pushback with ‘I don’t know,’ which is a red flag.” At Google, “I don’t know” is only acceptable if followed by “but I’ll find out by EOD.” The problem isn’t the gap—it’s the lack of a bridge.
What’s the most common mistake in bad-news 1on1s at Google?
The most common mistake is ending with the problem. A 1on1 is not a venting session; it’s a decision forum. If you finish with “So that’s where we’re at,” you’ve failed. The correct close: “So I need your input on A or B by tomorrow.” The problem isn’t the news—it’s the lack of a call to action.
During a manager training session, a director played a recording of a 1on1 where the IC ended with, “I just wanted to keep you in the loop.” The director’s response: “Looping me in is table stakes. What do you need from me?” The judgment: passive updates are noise. Google rewards agency.
Preparation Checklist
- Write the headline in one sentence and test it for clarity with a peer.
- Quantify the impact (e.g., “3-week delay,” “$500K risk”).
- Prepare the FLS with a specific next step and timeline.
- Anticipate the top 3 pushback questions and draft responses.
- Rehearse the script aloud to remove filler words (“um,” “like”).
- Confirm the meeting’s goal: alignment, decision, or escalation.
- Work through a structured preparation system (the PM Interview Playbook covers Google’s 3-part framework with real debrief examples).
Mistakes to Avoid
BAD: “I have some bad news…” (Vague, emotional, no signal.)
GOOD: “The launch is delayed by 2 weeks due to a critical bug in the payment flow.”
BAD: “Team Y isn’t cooperating.” (Blame, no ownership.)
GOOD: “Because team Y’s API is delayed, I’ve escalated to their lead and proposed a temporary workaround.”
BAD: “I’m not sure how to fix this.” (Passive, no FLS.)
GOOD: “I’ve identified two options: A (costs $10K, ships in 1 week) or B (costs $5K, ships in 2 weeks). I recommend A.”
FAQ
What if my manager reacts angrily to the bad news?
Anger is often a proxy for surprise. If you’ve followed the 3-part framework, the reaction isn’t about you—it’s about the news. Stay silent after delivering the FLS; let them process. At Google, managers respect those who don’t flinch under pressure.
How do I deliver bad news to a skip-level at Google?
Skip-levels care about two things: scale and systemic risk. Frame the news in terms of “This affects [X% of users]” or “This could delay [Y OKR].” Avoid tactical details; focus on strategic impact. In a skip-level 1on1, a senior PM once lost credibility by diving into sprint-level weeds.
Is it ever okay to delay delivering bad news at Google?
No. The only exception is if you’re still gathering data to form a complete picture. Even then, flag the risk: “I’m investigating a potential issue with [X]; I’ll have a full update by EOD.” At Google, late news is worse than bad news. The problem isn’t the timing—it’s the lack of early signal.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.