Zoom’s average meeting size is greater than 30. Good or bad?
Summary
This article demystifies a common PM interview trap: when a metric takes an unexpected turn and you’re asked, “Is that good or bad?” Using a Zoom example (“average meeting size >30”), it illustrates why this is first a diagnostic question, probing distributions, generating multiple hypotheses, and connecting causes to user behavior and business impact, before it becomes a trade-off discussion. You’ll get a crisp framework for diagnosing signals, a practical A/B test setup to validate fixes, and clear criteria for prioritizing between enterprise-scale features and small-meeting UX. If you're looking for a structured, real-world approach to root cause analysis and effective prioritization, read on.
How to Identify a Diagnostic Versus a Trade-Off Question
Problem diagnostic questions (sometimes referred to as root cause analysis) and trade-off questions can be challenging to classify because their framing is not always clear.
A typical diagnostic question presents a situation where a metric has declined or a negative outcome is occurring, and you are asked to identify the root cause and explain how you would fix it.
Sometimes, however, the question is framed around a metric that has taken an unexpected turn, neither explicitly good nor bad, and you are asked what you would do in response. This is the case with the question we will analyze:
“The average size of meetings is above 30 people. What do you think, is it good or not?”
At first glance, one might think that since the impact is not clearly positive or negative, it must be a trade-off question. In reality, it is a diagnostic question because the interviewer wants to see whether you can:
- Understand why the metric looks this way
- Break down possible explanations (is the metric inflated by a few outliers, i.e., distribution skew, or does it reflect a genuine change in user behavior across the board, i.e., actual shift).
- Connect underlying causes to user behavior and business impact
This type of question is fundamentally about diagnosing the signal before deciding what to do.
Once you have diagnosed the signal, trade-offs may emerge later, but only after the root cause analysis is complete. At that stage, the interviewer may shift to asking how you would choose between options, such as prioritizing features or allocating resources. Those follow-ups become trade-off questions, where you are expected to define trade-offs clearly and explain how you would make a balanced decision.
To illustrate this, we will walk through both cases using a simulated mock interview. In particular, we will demonstrate how to:
- Identify and answer a problem diagnostic question, including designing an A/B test
- Tackle a follow-up trade-off question
Interviewer Evaluation
For the Diagnostic Question, the interviewer will evaluate your performance as follows:
- Problem Framing: Does the candidate recognize that the task is to diagnose the issue first, rather than rushing into solutions or trade-offs?
- Hypothesis Generation: Do they propose multiple, plausible explanations for the observed outcome, showing openness to different possibilities instead of jumping to one conclusion too quickly?
- Analytical Approach: Do they outline how they would test or validate their hypotheses, using both quantitative and qualitative data, and connect their findings back to user needs and business impact?
- Action Planning: Do they propose a thoughtful set of next steps that address both risks and opportunities, instead of defaulting to a single path forward?
- Measurement and Accountability: Do they define clear success metrics and guardrails that demonstrate whether their chosen actions are effective?
For the Trade-off Question, the interviewer will evaluate your performance as follows:
- Trade-Off Framing: Does the candidate clearly articulate the trade-off as a “gain X, sacrifice Y” decision, rather than assuming both can be fully achieved?
- Balanced Perspective: Do they acknowledge the benefits and downsides of each option, including short-term and long-term implications?
- Decision Criteria: Do they specify logical criteria to guide the choice, such as impact on key metrics, alignment with strategy, and competitive context?
- Prioritization Rationale: Do they justify which option should come first based on user value, business goals, and situational context, and explain what would change their mind?
- Recommendation: Do they make a clear, defensible choice and describe how they would monitor results and adapt if conditions change?
Framework for Diagnosing Issues
The interview question: “The average size of meetings is above 30 people. What do you think, is it good or not?” is not framed as a traditional product problem with a presumed negative outcome. Instead, it presents an unexpected metric without direction. Still, to answer effectively, you must diagnose the root cause and implications to determine whether corrective action is required.
The first step is to explore the potential implications, both positive and negative. Only after outlining those possibilities should you proceed to analyze the data, validate the hypotheses, and determine the next steps.
1. Assess the Unexpected Metric Outcome
- Clarify the metric: is there ambiguity (e.g., averages vs. distributions, missing context)?
- Identify what additional analysis is required to interpret what is really happening.
2. Generate Hypotheses
Show broad thinking by considering multiple possible explanations instead of jumping to one.
- Scenario A: Positive cause (e.g., growth in a high-value use case)
- Scenario B: Negative cause (e.g., decline in a core use case)
- Scenario C (optional): Data artifact or external factor (e.g., seasonality, reporting quirks)
3. Analyze the Data
Evaluate hypotheses with quantitative and qualitative evidence to find the most likely cause.
- Segment: Break down by user type, geography, plan type, device, or time
- Compare: Look at trends, medians, and distributions
- Validate: Use qualitative inputs such as user research, feedback, or competitor signals
- Tie to business outcomes: retention, ARPU, churn, revenue mix
4. Execution Strategy
Show decisiveness by planning actions for both opportunity and risk scenarios.
- Track 1 (Opportunity): If positive, double down (features, monetization, adoption)
- Track 2 (Risk): If negative, fix friction and protect the core
- Balanced approach: Keep flexibility by balancing investments across both
5. Define Success Metrics
Ensure accountability with clear, measurable outcomes.
- Metrics for the health of the core use case
- Metrics for capturing upside from opportunities
- Guardrails to avoid regressions
6. Recommendation
Conclude by stating whether the shift is positive or negative and outlining the balanced action you would take.
Framework for Assessing Trade-Offs
1. Define the Trade-Off
Frame it as a “win some, lose some” decision. Choosing one path means gaining X but sacrificing Y. Always consider short-term and long-term effects. Show nuance, acknowledge uncertainty, and explain how you would validate which risk or opportunity matters more.
2. Decision Criteria
Lay out systematic criteria for prioritization, such as:
- Engagement and revenue metrics
- Market conditions
- Company stage and strategy
3. Recommendation Path
Make a clear recommendation, explain why, and note how you would monitor and adjust if conditions change.
Ready to See the Full Answer?
You're one step away from the complete picture. The rest of this content goes deeper, with the detail and specificity that makes the difference in your prep.
Go Premium
You'll unlock the rest of this article, plus the full StellarPeers library of PM interview prep content:
• Frameworks for answering PM interview questions
• Solved cases organized by company and question type
• Prep videos that teach you how to answer interview questions
• Deep-dive articles with techniques and strategies to strengthen your answers
Unlock the full value and go beyond the basics.
