What is the difference between a metric and a KPI?
Tests strategic vs operational measurement discernment. Answer: KPIs track critical goals; metrics track processes. Page views are a metric; conversion rate is the KPI. Red flag: calling all data KPIs or using page views as success proof.
What's really being asked
This question evaluates whether you understand that not all data is strategically equal. Interviewers want to see if you can distinguish between routine operational measurements and the few indicators that actually reveal whether the business is winning or losing. At the senior level, this shows product judgment and the discipline to avoid vanity metrics that waste engineering and marketing resources.
The full answer
First, define the hierarchy. A metric is any quantifiable data point collected during normal operations, such as page views, server response time, or cart additions. A KPI is a metric selected because it directly tracks progress toward a critical business objective. Second, explain the relationship. KPIs are chosen from the pool of metrics; they are the strategic subset that acts as a compass for long-term goals. Third, apply the e-commerce scenario clearly. Page views measure traffic volume, which is useful for operational diagnostics but does not prove commercial success because high traffic with zero purchases is still failure. A stronger KPI would be conversion rate or revenue per visitor, since both tie user behavior directly to financial outcomes and strategic health.
The mistakes people make
Calling page views a KPI without explaining why it fails the strategic test. Claiming that KPIs are just important metrics without articulating the goal-linkage. Offering vague definitions like KPIs are percentages and metrics are counts. Confusing leading and lagging indicators or suggesting you should track hundreds of KPIs instead of a focused set.
What usually comes next
How would you decide which metrics to promote to KPIs for a new product launch? What is the difference between a leading and a lagging indicator in this context? How do you prevent a team from chasing a vanity metric like page views when it diverges from revenue? If conversion rate drops but page views rise, what would you investigate first?
A concrete example
Imagine an e-commerce site running a holiday campaign. The marketing team celebrates a 300 percent increase in page views. A senior engineer asks what happened to conversion rate and learns it fell from 2.5 percent to 0.8 percent. The traffic metric exposed a load or targeting issue, but the KPI revealed the campaign was actually hurting revenue. The fix was to optimize page load speed and ad targeting rather than celebrate raw traffic.
Interview question
An e-commerce team sees page views surge 300% during a campaign while conversion rate drops sharply. What does this pattern reveal about the role of these two measurements?
- a.Both figures are KPIs, but the traffic growth proves the campaign succeeded operationally despite the revenue drop.
- b.Page views should be reclassified as a lagging indicator and conversion rate as a leading indicator.
- c.Page views function as an operational metric diagnosing traffic volume, while conversion rate acts as a strategic KPI tied to revenue goals.Correct
- d.The data proves that metrics like page views are vanity numbers and should never be tracked by product teams.
Why? this is the answer
Conversion rate is a KPI because it directly tracks progress toward a critical revenue objective, whereas page views are merely an operational metric useful for diagnostics. Option A is tempting but wrong because labeling page views a KPI and declaring success despite falling revenue is the vanity-metric trap described in the card.
Just read this? Test yourself on what you have been reading.
Read the original → datapad.io
- #metrics
- #kpis
- #analytics
- #product-management
- #interview
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on metrics — each one lists the topics its interview covers.
See open roles