Learn vocabulary for KPIs and metrics: KPI vs. metric vs. measure, north star metric, leading vs. lagging indicators.
0 / 18 completed
1 / 18
What is the difference between a 'KPI' and a 'metric'?
All KPIs are metrics, but not all metrics are KPIs. A metric is any measured quantity (page load time, daily signups). A KPI is a metric selected because it directly indicates performance against a key business objective. Having too many KPIs dilutes focus — 3–7 KPIs per team is typical.
2 / 18
What is a 'north star metric' in product and analytics vocabulary?
North star metric (popularized by growth teams): one metric that captures the core value exchange. Facebook's was Daily Active Users; Airbnb's was Nights Booked; Spotify's is Time Spent Listening. Every feature decision is evaluated by: will this move the north star? It prevents metric gaming and aligns cross-functional teams.
3 / 18
What is a 'leading indicator' vs. a 'lagging indicator'?
Leading indicators: early signals of future outcomes — e.g., demo requests (leading to sales), feature adoption rate (leading to retention). They are actionable now. Lagging indicators: outcomes already measured — revenue, churn rate. They confirm results but are too late to influence. Good dashboards track both.
4 / 18
What is 'dimension' vs. 'measure' in BI analytics vocabulary?
Dimensions: descriptive attributes for grouping/filtering (country, user segment, device type). Measures: numeric values you aggregate (SUM, AVG, COUNT). A query: 'revenue (measure) by country (dimension) and month (dimension).' This is the foundational analytical data model — used in Looker, dbt, Power BI, Tableau.
5 / 18
What is 'vanity metric' in analytics vocabulary?
Vanity metrics are impressive-looking but misleading: total registered users (includes abandoned accounts), total page views (doesn't show engagement), Twitter followers. They lack actionability — you cannot make a better decision based on them. Contrast with actionable metrics: DAU/MAU ratio, activation rate, retention cohorts.
6 / 18
Review Comment: "This PR seems to be focused on adding a new user authentication flow. While the code is well-written, I'm not seeing any metrics around adoption of this feature. How do we know if users are actually using it?"
This question examines how developers discuss feature adoption. The correct answer, tracking dailyActiveUsers, directly relates to measuring the *use* of a new feature – a key application of metrics. It's crucial to understand that 'churn rate' measures user attrition, and while conversion rates are relevant, they don't specifically address whether users are actively utilizing the newly added authentication flow. The final option highlights a common misunderstanding: code passing tests doesn't equate to successful adoption.
7 / 18
PR Description:
"Implemented new API endpoint for retrieving user profile data. Updated database schema and front-end UI."
During a standup update, your team lead asks you to quantify the impact of this change. Which of the following statements best reflects how you should describe the success of this PR?
This question tests understanding of how to frame a technical change in terms of measurable outcomes. Option 2 correctly identifies that simply deploying code isn't sufficient; you need *metrics*. The incorrect options focus on purely technical aspects (latency, schema updates) or vague positive statements without concrete evidence of impact. A good response would highlight the need for tracking metrics related to profile data usage—for example, number of users accessing profiles, frequency of access, or specific data points requested.
8 / 18
Review Comment: "This PR seems to be focused on adding a new user authentication flow. While the code is well-written, I'm not seeing any metrics around adoption of this feature. How do we know if users are actually using it?"
This question examines how developers discuss feature adoption. The correct answer, tracking dailyActiveUsers, directly relates to measuring the *use* of a new feature – a key application of metrics. It's crucial to understand that 'churn rate' measures user attrition, and while conversion rates are relevant, they don't specifically address whether users are actively utilizing the newly added authentication flow. The final option highlights a common misunderstanding: code passing tests doesn't equate to successful adoption.
9 / 18
PR Description:
"Implemented new API endpoint for retrieving user profile data. Updated database schema and front-end UI."
During a standup update, your team lead asks you to quantify the impact of this change. Which of the following statements best reflects how you should describe the success of this PR?
This question tests understanding of how to frame a technical change in terms of measurable outcomes. Option 2 correctly identifies that simply deploying code isn't sufficient; you need *metrics*. The incorrect options focus on purely technical aspects (latency, schema updates) or vague positive statements without concrete evidence of impact. A good response would highlight the need for tracking metrics related to profile data usage—for example, number of users accessing profiles, frequency of access, or specific data points requested.
10 / 18
Review Comment: "This PR seems to be focused on adding a new user authentication flow. While the code is well-written, I'm not seeing any metrics around adoption of this feature. How do we know if users are actually using it?"
This question examines how developers discuss feature adoption. The correct answer, tracking dailyActiveUsers, directly relates to measuring the *use* of a new feature – a key application of metrics. It's crucial to understand that 'churn rate' measures user attrition, and while conversion rates are relevant, they don't specifically address whether users are actively utilizing the newly added authentication flow. The final option highlights a common misunderstanding: code passing tests doesn't equate to successful adoption.
11 / 18
PR Description:
"Implemented new API endpoint for retrieving user profile data. Updated database schema and front-end UI."
During a standup update, your team lead asks you to quantify the impact of this change. Which of the following statements best reflects how you should describe the success of this PR?
This question tests understanding of how to frame a technical change in terms of measurable outcomes. Option 2 correctly identifies that simply deploying code isn't sufficient; you need *metrics*. The incorrect options focus on purely technical aspects (latency, schema updates) or vague positive statements without concrete evidence of impact. A good response would highlight the need for tracking metrics related to profile data usage—for example, number of users accessing profiles, frequency of access, or specific data points requested.
12 / 18
Review Comment: "This PR seems to be focused on adding a new user authentication flow. While the code is well-written, I'm not seeing any metrics around adoption of this feature. How do we know if users are actually using it?"
This question examines how developers discuss feature adoption. The correct answer, tracking dailyActiveUsers, directly relates to measuring the *use* of a new feature – a key application of metrics. It's crucial to understand that 'churn rate' measures user attrition, and while conversion rates are relevant, they don't specifically address whether users are actively utilizing the newly added authentication flow. The final option highlights a common misunderstanding: code passing tests doesn't equate to successful adoption.
13 / 18
PR Description:
"Implemented new API endpoint for retrieving user profile data. Updated database schema and front-end UI."
During a standup update, your team lead asks you to quantify the impact of this change. Which of the following statements best reflects how you should describe the success of this PR?
This question tests understanding of how to frame a technical change in terms of measurable outcomes. Option 2 correctly identifies that simply deploying code isn't sufficient; you need *metrics*. The incorrect options focus on purely technical aspects (latency, schema updates) or vague positive statements without concrete evidence of impact. A good response would highlight the need for tracking metrics related to profile data usage—for example, number of users accessing profiles, frequency of access, or specific data points requested.
14 / 18
Sarah (a Product Manager) sends a Slack message to the team: 'We need to track user engagement with the new reporting dashboard. Let's focus on daily active users – it's easy to measure and gives us a quick snapshot.' Which of the following best describes Sarah's approach?
Sarah's statement highlights the importance of readily available metrics. While daily active users (DAU) are easy to track, relying solely on them can be misleading as it doesn't account for user behavior nuances like churn or engagement depth. A good metric should provide actionable insights beyond a simple count.
15 / 18
David (a Senior Developer) is reviewing a PR and comments: 'The new API endpoint for order processing has been implemented. We've increased the number of successful transactions by 15% since launch.' Which term best describes the '15%' increase?
A 'lagging indicator' measures past results. In this case, the 15% increase in successful transactions represents what *has* happened after the API implementation. Leading indicators predict future performance; dimensions are attributes used to categorize data (e.g., customer segment).
16 / 18
Maria (a Data Analyst) is presenting a dashboard and explains: 'We're tracking the number of users who click on our 'Recommended Products' section. This metric shows that 80% of users are interacting with this feature.' What type of metric is Maria primarily focusing on?
A 'vanity metric' focuses on impressive numbers that don't necessarily translate into meaningful business value. While 80% interaction sounds good, it doesn't tell us if those users actually made a purchase or converted to a paying customer – the ultimate goal. Leading indicators predict future behavior.
17 / 18
John (a DevOps Engineer) is discussing monitoring with his team: 'We need to track the average response time for our API calls. If it's consistently above 200ms, we know there's a problem.' Which of the following best describes what John is measuring?
John is measuring a 'measure,' which is a quantifiable value. Response time is a crucial metric for evaluating API performance and identifying potential bottlenecks. A leading indicator would predict future availability; dimensions describe the characteristics of data (e.g., user location).
18 / 18
Emily (a Product Manager) is writing a PR description for a new feature: 'This update includes an automated process to send personalized email campaigns based on customer purchase history.' Which of the following statements best describes how this could be effectively monitored using KPIs?
While email delivery is important, it doesn't tell you if the campaigns are effective. Tracking open rates and click-through rates (CTR) provides a direct measure of how users are engaging with the personalized content – key metrics that demonstrate the impact of the new feature.
What will I practice in "KPI and Metrics — Vocabulary and Definitions"?
This is a BI Analytics Language exercise set. It walks through 18 scenario-based multiple-choice questions built around real usage of BI Analytics 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 18 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 BI Analytics 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 BI Analytics Language exercises?
See the BI Analytics 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 — BI Analytics Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.