4.6Presenting Bad News

Bad news does not get better with age. When you find critical issues, communicate them quickly, clearly, and with a plan.

The Bad News Framework

Step 1: Lead with the headline. Do not bury the finding in context.

"We found a critical issue that affects checkout for users with saved payment methods."

Step 2: Quantify the impact.

"This affects approximately 30% of our customer base -- about 15,000 daily active users."

Step 3: Explain what you know and what you are still investigating.

"The bug causes saved cards to be declined on the first attempt. A retry succeeds. We are investigating whether any charges are actually lost or just delayed."

Step 4: Present options.

"We have three options: (1) delay the release by one day to fix it, (2) release behind a feature flag and fix in a hotfix, or (3) release as-is and communicate the retry workaround to support."

Step 5: State your recommendation.

"I recommend option 2: the feature flag lets us get the other features out while we fix this specific issue."

What Executives Hate

• Surprises. Finding out about a critical bug from a customer complaint instead of from QA.
• Vague warnings. "There might be some issues" with no specifics.
• Problems without solutions. "This is broken" with no proposed path forward.
• Buried bad news. Hiding a critical issue in a 30-page report.