Metrics Triage After Negative Press Coverage of Your Product

Your product has just received negative coverage in the press. Before deciding how to respond, which metrics would you review first, in what order, and what would each of them tell you? ```hint Separate the story from its effect Some numbers show how far the story is spreading and whether its claim is true; others show whether users are actually changing what they do. Decide which you need within the first hour and which can wait a few days. ``` ### Clarifying Questions - What is the product, and how does it make money: subscriptions, advertising or one-off purchases? - What does the coverage claim: an outage or bug, a privacy or security lapse, a price change, a content decision, or something about the company rather than the product? - How widely has it spread so far: a single outlet, or picked up by major outlets and social media? - Am I reviewing the numbers alone, or alongside communications, support and legal teams who need answers from me? ### What a Strong Answer Covers - Establishing what the coverage claims and how far it is spreading before reading product metrics. - Checking whether the claim is true with the operational metrics that match it. - Measuring user reaction through direct signals (support contacts, reviews, sentiment) and behavior (sign-ups, cancellations, engagement), against a proper baseline and split by exposure. - Ordering the review by speed and severity, from what to check within hours to what to track over weeks, with thresholds that trigger action. - Turning the readings into a decision (fix, communicate or monitor) and tracking recovery. ### Follow-up Questions - The article is accurate, but after three days sign-ups and cancellations show no change. Do you still act, and how? - How would you tell the effect of the coverage apart from seasonality or a competitor's launch in the same week? - Which of these metrics would you put on a standing alert so the next story does not catch the team off guard?