Diagnose and Fix a Three-Month Engagement Slump in a B2B Product

You are the product manager for a business-to-business (B2B) product, and engagement with it has been low for the last three months. Explain how you would find out why, and what solution you would propose once you know. ### Clarifying Questions - What is the product, who inside a customer company uses it, and how often should a healthy customer use it: daily, weekly, or only at month end? - How is engagement measured: active users out of licensed seats, active customer accounts, or use of specific features? - Did engagement fall three months ago from a healthier level, or has it been low since launch? - Is the weakness spread across customers, or concentrated in some accounts, such as new ones or those approaching renewal? ### Part 1 — Find the cause Describe how you would investigate the low engagement: which data you would look at, how you would break it down, which explanations you would test, and in what order. ```hint Accounts or seats? In a B2B product, an engagement number can fall because whole customer accounts went quiet or because fewer people inside each account use the product. Work out which one happened before asking why. ``` #### What This Part Should Cover - Confirming that the metric and its tracking are sound, and understanding the time shape (sudden versus gradual, seasonal or not). - Breaking engagement into accounts and seats per account, then by customer segment, signing cohort and user role. - B2B-specific internal and external hypotheses, each with the evidence that would confirm or rule it out, plus direct conversations with customers. ### Part 2 — Propose the solution Assume your investigation identified the main cause. Describe the solution you would propose, how you would prioritize among options, and how you would measure whether it worked in a B2B setting. ```hint Few accounts, slow signals B2B products have far fewer customers than consumer apps, and the cost of weak engagement often shows up only at renewal. Consider how that shapes both the fix and the way you test it. ``` #### What This Part Should Cover - Solutions matched to the confirmed cause, with owners across product, engineering and customer-facing teams. - Prioritization by revenue at risk, confidence and effort. - Measurement that works with a small number of accounts, with renewal and retention guardrails. ### What a Strong Answer Covers - A structured, ordered diagnosis rather than a list of guesses. - Recognition that buyers and users differ in B2B, and that the right level of engagement depends on how often the product's job naturally comes up. - A clear line from each cause to its response and to how success is measured. - Attention to revenue at risk, especially accounts near renewal. ### Follow-up Questions - The decline is concentrated in customers signed in the last two quarters. What does that suggest, and which teams besides product would you involve? - Engagement is low, but renewals have held steady so far. Does it still matter, and how would you make the case either way? - How would you build an account health score so the next decline is caught within weeks instead of months?