Business Case Studies β
Think Like an Analyst
Master the frameworks that crack case study interviews at Google, Amazon, Flipkart, Swiggy and every top product company. Drop-off funnels, North Star Metrics, revenue analysis, retention and data-backed decision making β all in one place.
The 6 Business Case Frameworks That Appear in 90% of Interviews
These frameworks are used by analysts at every product company worldwide. Master all 6 and you can crack virtually any case study question thrown at you.
π Drop-off Funnel Analysis β Complete Guide
Funnel analysis is the most commonly asked case study type. It requires you to identify why users are leaving at a specific step and recommend a data-backed fix.
The 5-Step Funnel Drop-off Framework
Clarify the Funnel & Drop-off Step
Ask: Which specific step is dropping? Over what time period? Is it a sudden drop or gradual decline? Which platform (iOS, Android, Web)? What is the baseline conversion rate? Never start analysing without clarifying the exact scope.
Check for Technical Issues First
Before assuming user behaviour, rule out bugs. Check: Did a new app release coincide with the drop? Are error rates elevated at that step? Is latency unusually high? Is the drop consistent across all users or only specific device/OS versions? Technical issues explain 30β40% of sudden drop-offs.
Segment the Drop-off
Segment by: Platform (iOS vs Android vs Web), Geography (Tier 1 vs Tier 2 cities), User cohort (new vs returning users), Traffic source (organic vs paid), Time of day/week. The segment with the highest concentrated drop-off is your priority target.
Form & Validate Hypotheses
For each segment showing drop-off, form 2β3 hypotheses. Example for checkout drop-off: H1 β Too many payment steps (UX friction). H2 β Preferred payment method not available. H3 β Trust signals missing (no return policy shown). Validate each with session recordings, heatmaps, and support ticket analysis.
Recommend Fix + A/B Test
Never recommend a change without proposing a test. State: the specific change, which segment to test on, the primary metric (conversion rate), guardrail metrics (order value, returns), sample size, and test duration. This shows interviewer you think in controlled experiments, not gut instinct.
Visualising a Real Funnel β E-commerce Example
Priority: Fix the Cart β Checkout drop (54%). Even a 10% improvement here = +820 daily orders.
β North Star Metrics β Design & Defend
The North Star Metric is the single measure that best captures the core value your product delivers. Every team’s work should ultimately move this one number.
North Star Metrics of Top Companies
π° Revenue Analysis & Decomposition
Revenue problems are among the most common case study questions. Always break revenue into its components before proposing solutions.
Revenue = Volume Γ Price Γ Frequency Γ Retention
Or more specifically: Revenue = Number of Active Users Γ Average Order Value Γ Orders per User per Month Γ (1 – Churn Rate). When revenue drops, segment each component to find which lever broke β then drill deeper into that specific one.
Revenue Diagnosis Framework
Identify Which Revenue Component Dropped
Segment total revenue into: New user revenue vs Returning user revenue β Price change vs Volume change β Which product category β Which geography. Each split narrows the scope by 50%. After 3β4 splits, you’ve isolated the exact driver.
Check External vs Internal Factors
External: Competitor launched a discount, market downturn, seasonal effect, macro event. Internal: Pricing change, product bug, marketing campaign ended, supply issue. Ask: “Did only we decline, or did the whole market?” If whole market declined, it’s external β your solution changes completely.
Quantify the Impact
Always attach numbers. “If AOV dropped from βΉ480 to βΉ420 for 50,000 orders this month, that’s βΉ3M revenue shortfall.” Interviewers want to see you think in business impact, not just percentages. Estimate order of magnitude even when exact data isn’t given.
Recommend Levers to Pull
Volume lever: Increase traffic (marketing), improve conversion (UX). Price lever: Remove discounts, improve perceived value. Frequency lever: Loyalty programme, push notifications, habit formation features. Retention lever: Onboarding improvement, re-engagement campaigns, subscription models.
π Retention & Cohort Analysis
Retention is the most important long-term health metric for any subscription or repeat-purchase product. Poor retention makes every acquisition investment worthless.
| Retention Type | Definition | Formula | Best For |
|---|---|---|---|
| Day-1 Retention | % of users who return on day after install/signup | DAU(D1) / New Users(D0) | Mobile Apps |
| Day-7 Retention | % of users still active 7 days after first use | DAU(D7) / New Users(D0) | Games, Social |
| Day-30 Retention | % of users active 30 days after first use | DAU(D30) / New Users(D0) | SaaS, E-comm |
| Monthly Retention Rate | % of last month’s active users who are active this month | (Current MAU – New Users) / Prior MAU | Subscriptions |
| Net Revenue Retention | Revenue retained + expansion from existing customers | Ending MRR / Starting MRR | B2B SaaS |
“Acquisition brings users in. Retention keeps the bucket from leaking. If your Day-30 retention is below 20%, no amount of marketing spend will fix your growth problem.”
β Core principle, product analytics at scaleCohort Analysis β What It Shows and How to Use It
A cohort analysis groups users by the time they first used your product, then tracks how that group behaves over subsequent periods. It reveals whether your product is getting better or worse at retaining users over time β something aggregate metrics completely hide.
π§ͺ A/B Testing β Design to Decision
A/B testing (controlled experimentation) is how product companies make data-backed decisions. You must be able to design, run and interpret an A/B test end-to-end in interviews.
The Complete A/B Test Design Framework
Define the Hypothesis
“We believe that [change] will [increase/decrease] [metric] by [X%] because [reason]. We will know this is true when [specific measurable outcome].” Example: “We believe showing estimated delivery time on the cart page will increase checkout conversion by 8% because users are uncertain about delivery and abandon.”
Choose Primary & Guardrail Metrics
Primary metric: The one metric you’re trying to move β checkout conversion rate. Secondary metrics: AOV, session duration. Guardrail metrics: Metrics you must NOT hurt β cart abandonment rate, return rate, customer support tickets. If primary improves but a guardrail degrades significantly, do not ship.
Calculate Required Sample Size
Use: n = (Z_Ξ±/2 + Z_Ξ²)Β² Γ 2ΟΒ² / δ². In practice: set baseline conversion (e.g. 8%), minimum detectable effect (e.g. 0.5pp lift = 6.25% relative), significance level Ξ±=0.05, power 80%. For most product changes, you need 10,000β50,000 users per variant to detect meaningful effects reliably.
Run the Test Correctly
Randomise at user level (not session β same user should always see same variant). Run for at least 1β2 full business cycles (minimum 1 week, ideally 2β4 weeks). Never peek at results and stop early β this inflates false positive rate drastically. Use sequential testing or pre-register your stopping rule.
Analyse & Decide
Check statistical significance (p-value < 0.05). Check practical significance (is the lift large enough to matter for the business?). Segment results: does the effect hold across platforms, geographies, user cohorts? Check for novelty effects (lift may fade as users get used to the change). Then: Ship, Iterate, or Kill.
π Solved Case Studies β Real Company Questions
These are real case study questions asked at product companies in India in 2024β2026, with complete structured answers you can adapt.
π Step 1 β Clarify
π Step 2 β Segment
π‘ Hypotheses
β Recommendation
Immediate: Check Crashlytics/Sentry for errors in payment screen on Android. Check payment gateway latency dashboard. Roll back the feature causing new friction step if H3 is confirmed. A/B Test: Test the payment flow with vs without the new “delivery instruction” step β primary metric: checkout completion rate, guardrail: return rate. Success metric: Conversion back to β₯70% within 48 hours of fix deployment.
π’ Revenue Decomposition
π Segmentation
β Recommendation
If AOV mix shifted: Launch targeted “upgrade nudge” for users browsing mid-tier phones β show premium features, EMI options prominently. If competitor price advantage: Real-time competitive pricing alerts for top 50 electronics SKUs. Metric to track: Smartphone + TV purchase rate (high-AOV categories) as leading indicator of GMV recovery. A/B test: EMI-first display on product pages β primary metric: AOV, guardrail: return rate.
π Metric Design β KPIs, Leading & Lagging Indicators
When asked to “design metrics for a new feature”, you need a structured framework β not a random list of numbers. Here is the complete approach.
Define the Feature Goal
What user problem does it solve? What business outcome does it drive? Example: “New onboarding flow for first-time users β goal is to increase Day-7 retention by getting users to their first value moment faster.”
Choose Your North Star (Primary KPI)
The one metric that tells you if the feature succeeded. For the onboarding example: Day-7 retention rate. This is the lagging indicator β it takes time to measure but is directly tied to the goal.
Define Leading Indicators
Metrics that predict the North Star before you can measure it. For onboarding: Onboarding completion rate, Time to first core action (e.g., first order placed), Number of features explored in session 1. These are measurable immediately and tell you if you’re on track.
Set Guardrail Metrics
Metrics you must NOT hurt. For onboarding: Session duration (don’t make it slower), Error rate (no bugs introduced), Customer support contacts (new flow shouldn’t be confusing). If the primary KPI improves but a guardrail degrades significantly β the change fails.
Define Success Thresholds
State what “success” looks like in numbers. “We’ll call this successful if Day-7 retention improves from 24% to 28% (16.7% relative lift) with no degradation in session duration (guardrail) β validated in an A/B test with 95% statistical significance.”
β Key Takeaways β Business Case Studies
- Always clarify before analysing β scope, time period, platform, baseline are essential to solving any case correctly
- Funnel drop-off: Rule out technical first β segment by platform/cohort/time β form hypotheses β validate β recommend with A/B test
- North Star Metric must reflect user value, predict revenue, and be actionable by all teams β never pick revenue itself as NSM
- Revenue = Volume Γ Price Γ Frequency Γ Retention β decompose before diagnosing
- Retention is the most important health metric β fix retention before spending more on acquisition
- A/B test design: Hypothesis β Primary metric β Guardrail metrics β Sample size β Duration β Analysis β Ship/Kill decision
- Metric design: NSM (lagging) + Leading indicators + Guardrail metrics + Success thresholds = complete metric framework
- Every recommendation must end with: “I’d validate this with an A/B test targeting X metric, expecting Y% lift in Z weeks”
Practice Case Studies with a Real Mentor
Our mock case study sessions simulate actual interviews at Swiggy, Flipkart, Amazon and more. Real questions, live structured thinking feedback, written report.
Book Free Case Study Session