5 exercises — Practice vocabulary for product analytics: activation rate, retention curves, funnel drop-off, cohort analysis, and power user segments.
0 / 16 completed
1 / 16
A PM reports: "The activation rate is 45%." A new analyst asks what that means. Which explanation is correct?
Activation is the moment a new user first experiences the product's core value — the "aha moment" — and it is one of the strongest predictors of long-term retention.
Different products define activation differently: for Slack it might be "sent 2,000 messages as a team"; for Dropbox it was "put one file in the Dropbox folder on two devices." The activation event should correlate with retention — users who hit it should retain significantly better than those who don't. A 45% activation rate is the starting point: the PM's job is to understand why 55% of new users don't reach the aha moment and remove the friction causing early drop-off. Common levers include onboarding redesign, time-to-value reduction, and empty-state improvements.
Key vocabulary:
• activation rate — the % of new users who complete the event(s) that define first value delivery
• aha moment — the specific point in onboarding when a user first experiences the product's core value
• time to value — how quickly a new user can reach the aha moment from sign-up
2 / 16
In a weekly metrics review, a PM says: "The 7-day retention is 23%." A stakeholder asks what this tells us about the product. Which interpretation is correct?
D7 retention is one of the most important early-stage product health metrics — it tells you whether the core product loop is compelling enough to bring users back a week after they first experienced it.
Retention benchmarks vary by category: social/gaming apps often target D7 > 30%; B2B SaaS tools with weekly use cases might target D7 > 40%. Below-benchmark D7 is a signal that needs diagnosis: are users understanding the product's value? Is the core loop completing? Is the product too hard to use? Retention curves are typically visualised on a graph (cohort retention chart) and the "flattening" of the curve — where it stops declining — indicates the product's retained core. If the curve goes to zero, the product has no retained core.
Key vocabulary:
• D7 retention — the % of a cohort that returns on day 7 after their first session
• retention curve — a graph showing the % of a cohort still active over time; flattening indicates a retained core
• cohort — a group of users who started using the product in the same time period, tracked together
3 / 16
A PM shares a funnel analysis and says: "The funnel shows a 60% drop at the payment step." What action should the team prioritise based on this data?
A 60% drop at a single funnel step is an abnormally high friction point that warrants immediate investigation — it means more than half of users who reach the payment step abandon before completing it.
Funnel analysis tells you where users are dropping out, not why. The PM's job after seeing this data is to diagnose the cause. Qualitative tools help: session recordings (Hotjar, FullStory) show what users actually do at that step; exit surveys capture their stated reasons; usability tests reveal cognitive friction. Common payment-step problems include: price revealed for the first time (no pricing page earlier in funnel), too many required fields, lack of trust signals (SSL indicator, money-back guarantee), unclear next steps after payment. Each hypothesis gets an A/B test to measure causal impact.
Key vocabulary:
• conversion funnel — a sequence of steps users must complete to reach a goal, tracked to identify drop-off points
• funnel drop-off — the % of users who abandon the funnel at a specific step
• conversion rate optimisation (CRO) — the practice of systematically improving each funnel step to increase the overall conversion rate
4 / 16
A data analyst presents a cohort analysis and says: "The cohort analysis reveals month-3 churn." What does this finding mean for the product team?
Cohort analysis is a retention diagnostic tool — it shows not just overall churn rate but when in the lifecycle users are leaving, which points to the specific problem to solve.
Different churn points indicate different problems: Day-1 churn = onboarding/first-impression problem; Week-1 = activation or habit formation failure; Month-3 = the "sophomore slump" where initial novelty fades and competitors are evaluated at renewal; Month-12 = pricing or ROI justification at annual renewal. For month-3 churn, the PM should interview recent churners to understand the trigger ("What changed in month 3 that made you stop using the product?"), segment churners by use case or acquisition channel to find patterns, and look at usage data to see whether churners were using the product differently from retained users in months 1 and 2.
Key vocabulary:
• cohort analysis — tracking a group of users over time to understand behaviour patterns at specific lifecycle stages
• churn — the rate at which users cancel, stop using, or don't renew a product
• lifecycle stage — a defined phase of the user journey (onboarding, activation, habit, renewal) with distinct retention dynamics
5 / 16
A PM says: "The power user segment drives 80% of revenue." A stakeholder asks what this means for the product strategy. Which response is most analytically sound?
When a small segment drives the majority of revenue, it is both the most valuable asset to protect and a strategic concentration risk to actively manage.
Power users are worth understanding deeply: Who are they? What workflows do they use most? What would make them increase usage? What would cause them to churn? Often the answers reveal product expansion opportunities (features that make power users even more powerful) or new user acquisition strategies (targeting companies with more power-user-like profiles). The 80/20 revenue concentration also means the product is fragile: losing a few power users has outsized revenue impact. PMs should track power user health metrics separately and establish a direct feedback channel (customer advisory board, design partner programme) with this segment.
Key vocabulary:
• power user — a user who engages with the product at significantly above-average frequency and depth
• revenue concentration risk — the business risk of depending heavily on a small number of users or customers for the majority of revenue
• customer advisory board — a structured programme giving top users early access and a direct input channel into the product roadmap
6 / 16
Product Manager Sarah is reviewing daily user engagement metrics. She notices a significant drop in active users after launching a new feature. The data shows a 30% decrease in daily active users (DAU) over the past week. Which of the following actions should she prioritize based on this initial observation?
// Example API Response (simplified)
{
"metric": "DAU",
"current_value": 1500,
"previous_value": 2250,
"change": -30%
}
The most immediate priority is investigating technical issues. A sudden drop in DAU often indicates a problem with the feature itself – bugs or performance issues are highly likely. Rolling back immediately might be premature without understanding the root cause. User surveys and increased marketing would address symptoms rather than the core issue.
7 / 16
Slack message from Lead Engineer David: 'The conversion rate from free trial to paid subscription has plummeted – it's now only 5%. What does this suggest we need to investigate?' Which of the following is the MOST relevant next step?
// Slack Message (simplified)
{
"user": "David",
"message_text": "Conversion rate from free trial to paid subscription has plummeted – it's now only 5%."
}
A low conversion rate signals a problem with the value proposition or user experience during the free trial. Analyzing user behavior – specifically identifying where users are dropping off – is crucial for pinpointing the exact cause and informing targeted improvements. Simply redesigning or increasing sales efforts without understanding the 'why' would be inefficient.
8 / 16
A PR description reads: 'Implemented a new A/B test for the signup flow. Variant B resulted in a 15% increase in signups compared to the control.' What is the primary purpose of this experiment's result?
// PR Description (simplified)
{
"description": "Implemented a new A/B test for the signup flow. Variant B resulted in a 15% increase in signups compared to the control."
}
The purpose is to understand *why* Variant B performed better. The result (15% increase) provides data to identify the specific elements – perhaps fewer fields, clearer messaging, or a streamlined design – that drove this improvement. It's about understanding the 'how,' not simply accepting a higher number.
9 / 16
During a standup meeting, a Product Analyst reports: 'The cohort analysis reveals month-3 churn is at 18%. This means that 18% of users who started using the product in March have stopped using it after three months.' What does this finding *primarily* indicate about the product?
// Standup Report (simplified)
{
"report_type": "Cohort Analysis",
"metric": "Churn Rate - Month 3",
"value": 18%
}
High churn within a cohort (users who started together) suggests users aren't finding ongoing value after an initial period. This could be due to unmet expectations, lack of engagement, or a product that doesn't align with their needs. The other options are less directly linked – onboarding complexity might contribute, but the core issue is likely a lack of sustained value.
10 / 16
Product Manager Alex is discussing a recent spike in user engagement with the team. He states: 'We've seen a lift of +25% in Daily Active Users (DAU) over the last week.' Lead Engineer Ben asks, 'What does that actually *mean* for our infrastructure?'. Which response best reflects Alex's statement from an engineering perspective?
The question tests understanding of how 'lift' relates to technical implications. 'Insufficient' is incorrect because the statement *does* provide a quantifiable metric. 'Correct' accurately interprets the statement as an increase in user base, but misses the crucial need for further investigation into infrastructure impact. 'Potentially problematic' introduces a relevant concern – a spike could be misleading – and 'Incorrect' misinterprets 'lift'. Ben's question highlights the need to translate business metrics into technical requirements.
11 / 16
Reviewer Maria comments on a PR: 'This change introduces a new metric: 'Time to First Action'. Can you explain the rationale behind tracking this and how it will be used in reporting?'. What is the MOST appropriate response for the developer, John?
Maria's comment prompts a deeper understanding of the metric's purpose. Option 1 is dismissive and doesn't address the question's core concern. Option 2 provides an accurate explanation of 'Time to First Action' and its relevance to engagement. Option 3 is irrelevant, and option 4 seeks clarification – John should provide a meaningful explanation, not simply admit ignorance.
12 / 16
Lead Data Scientist Emily sends a Slack message to the team: 'The cohort analysis shows month-6 churn is at 35%. This means that 35% of users who started using the product in September have stopped using it after six months.' A junior developer, David, asks, 'What's the immediate implication of this number for our marketing efforts?'
The question assesses understanding of the *actionable* implications of churn data. Option 1 represents a reactive and potentially wasteful approach. Option 2 correctly identifies that high churn warrants investigation into user experience issues. Option 3 is dismissive and doesn't acknowledge the significance of the number, while option 4 shifts focus inappropriately.
13 / 16
Product Manager Liam is presenting a report on user behavior. He states: 'The session duration average is 15 minutes.' A junior developer asks, 'What does that tell us about our users?'
Which of the following interpretations is MOST accurate?
Session duration average refers to the typical length of time users spend interacting with a product during a single session. A shorter average suggests users aren't finding value quickly – perhaps the onboarding is confusing or the core functionality isn't immediately apparent. Option A correctly interprets this as a potential usability concern, while options B, C, and D misinterpret the metric's meaning.
14 / 16
Lead Engineer Chloe is reviewing an API response from our analytics platform. The response includes a field labeled 'False Positives'. What does this likely represent in the context of product usage data?
Which of the following best describes the meaning of 'False Positives'?
False Positives in analytics often refers to events that were incorrectly flagged as legitimate user actions. This can happen due to bugs in tracking or incorrect filtering rules within the analytics system. Option A describes true positives, while options B, C, and D are related to different metrics.
15 / 16
Product Manager David is writing a commit message for a PR that implemented a new tracking event. He writes: 'Added metric: 'Time until first purchase'. What's the primary goal of measuring this metric?
Time until first purchase is a key metric for assessing the efficiency of the product's value proposition. Measuring this helps identify if users are struggling to understand or experience the core benefit quickly – often pointing to usability issues or a confusing onboarding flow. Options B, C, and D represent different goals related to engagement and marketing.
16 / 16
Lead Engineer Michael is discussing a recent drop in conversion rates with his team. He says: 'The click-through rate on our call to action button has decreased by 10%.' What should the team investigate *first*?
A decrease in click-through rate (CTR) for a specific call-to-action button immediately points to potential issues with its design or messaging. Changes made to the button are the most likely cause and should be investigated first before looking at broader traffic volume, user demographics, or other page elements. Addressing this directly is crucial for quickly recovering conversion rates.
What will I practice in "Product Analytics Vocabulary — Product Management Language | CoderLingo"?
This is a Product Management Language exercise set. It walks through 16 scenario-based multiple-choice questions built around real usage of product management language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 16 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the product management language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Product Management Language exercises?
See the Product Management Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — product management language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.