How to Solve Product Management (PM) Cases: Frameworks & Real Examples

Product Management (PM) has emerged as one of the most sought-after careers for MBA graduates in India. From tech giants like Google, Amazon, and Microsoft to rapidly scaling startups like Flipkart, Swiggy, Paytm, and Ola, recruiting teams look for candidates who can solve complex, open-ended product problems under pressure.

Whether you are preparing for a PM role in your summer internship placements or competing in national tech case competitions (like Microsoft ACP or Flipkart WiRED), you will inevitably be asked to solve a PM case.

This guide provides a comprehensive playbook for solving product management cases. We will cover the core PM case types, deep-dive into the CIRCLES framework, outline critical product metrics (AARRR), walk through a worked design/launch example, and list common traps to avoid.

The Core Types of PM Cases

In an interview or competition, PM cases generally fall into one of three buckets:

Product Design / Product Improvement: “Design a microwave for blind people,” or “How would you improve Google Maps for tourists?” These test user empathy, prioritization, and design thinking.
Product Launch / Go-To-Market (GTM): “How would you launch a ride-sharing service for senior citizens in Bangalore?” These test market sizing, channel strategy, and launch sequencing.
Metrics & Root Cause Analysis (RCA): “Daily active users (DAU) for Instagram Stories dropped by 10% yesterday. What happened?” These test your analytical skills, data interpretation, and debugging logic.

The CIRCLES Framework™ for Product Design

Created by Lewis C. Lin, the CIRCLES framework is the industry standard for structuring product design answers. It ensures you touch upon every critical product decision-making step logically:

Step	Letter	Action
Comprehend the Situation	C	Ask clarifying questions: Goal, constraints, timeline, and context.
Identify the Customer	I	Segment the users (e.g., demographics, behavior, needs) and create a primary persona.
Report Customer Needs	R	Write user stories: “As a [User], I want to [Action], so that [Benefit].”
Cut Prioritize	C	Prioritize needs based on impact vs. effort (use a simple prioritization matrix).
List Solutions	L	Brainstorm at least 3 distinct, creative solutions (avoid generic ideas).
Evaluate Trade-offs	E	Assess the pros, cons, and engineering/operational feasibility of each solution.
Summarize Recommendation	S	Recommend a specific solution, specify key launch metrics, and outline next steps.

Measuring Success: The AARRR Metrics Framework

A product is only as good as its measurable impact. When proposing a product launch or improvement, always use the AARRR (Pirate Metrics) framework to define success:

      ┌─────────────────────────┐
      │     Acquisition         │  --> How do users find you? (Signups, CAC)
      └────────────┬────────────┘
                   ▼
      ┌─────────────────────────┐
      │     Activation          │  --> First good experience? (First-ride booked)
      └────────────┬────────────┘
                   ▼
      ┌─────────────────────────┐
      │     Retention           │  --> Do they come back? (DAU/MAU, Churn)
      └────────────┬────────────┘
                   ▼
      ┌─────────────────────────┐
      │     Referral            │  --> Do they tell others? (NPS, viral coefficient)
      └────────────┬────────────┘
                   ▼
      ┌─────────────────────────┐
      │     Revenue             │  --> How do you make money? (LTV, Avg Order Value)
      └─────────────────────────┘

Worked Example: Design a Mobile App to Book EV Charging Slots in Metro Cities

Let’s apply the CIRCLES framework to a highly relevant real-world scenario.

Step 1: Comprehend the Situation

Clarification: “Are we building this app as a standalone startup, or is it an extension of an existing EV manufacturer (like Ather/Ola Electric) or a charging network (like Tata Power)?”
Interviewer: “Build it as a standalone aggregator startup, similar to BookMyShow but for EV charging stations.”
Goal: Provide an seamless booking experience to reduce range anxiety for EV owners in Tier 1 cities.

Step 2: Identify the Customer

Let’s segment the EV owners in Indian metro cities:

Daily Office Commuters (Private Car Owners): Drive fixed routes, charge overnight at home, but need fast-charging options during occasional unexpected travel.
Commercial Fleet Drivers (Ola, Uber, BluSmart): Time-sensitive, run high mileage daily, and depend entirely on public fast chargers. Their livelihood depends on minimal idle time.
Delivery Partners (Zomato, Swiggy, Zepto on 2-Wheelers): Mostly riding electric two-wheelers, need rapid battery-swapping stations rather than plug-in charging slots.

Target Persona: Let’s focus on Commercial Fleet Drivers (Persona A) as our primary segment. They are high-frequency users, highly dependent on public infrastructure, and suffer the most financial loss during charging station wait times.

Step 3: Report Customer Needs

What does our primary persona need?

Need 1: As a fleet driver, I want to know real-time charger availability, so I don’t waste time driving to a full station.
Need 2: I want to reserve a slot 15 minutes in advance, so I am guaranteed a working charger when I arrive.
Need 3: I want a unified payment option across different charging brands (Tata Power, Statiq, Jio-bp), so I don’t need 10 different apps.

Step 4: Cut (Prioritize)

We prioritize Need 1 (Real-time availability) and Need 2 (Slot Reservation) as high-priority features for the MVP, and Need 3 (Unified payment) as a medium-priority item.

Step 5: List Solutions

Dynamic Slot Booking with Smart Queueing: Users can book a 30-minute charging slot. If they are running late, the app automatically adjusts their slot or assigns them to a nearby available charger.
Battery Swap Aggregator Network: Partner with third-party swap stations to let 2-wheeler and 3-wheeler fleet drivers swap batteries in under 2 minutes.
Predictive Fleet Route Planner: Integrated navigation that maps the driver’s pick-ups and drops and auto-reserves charging slots along their route before the battery drops below 20%.

Step 6: Evaluate Trade-offs

We select Solution 1 (Dynamic Slot Booking with Smart Queueing) for the initial launch.

Pros: Solves the core range anxiety and queue wait-time problem directly.
Cons: Requires deep API integration with fragmented charger networks (hardware-software sync).

Step 7: Summarize Recommendation

“We recommend building a unified EV Charging Aggregator MVP focused on commercial fleet drivers. The core feature will be a Dynamic Slot Reservation System that syncs with third-party charger hardware. Success will be measured by Activation (number of successful charges booked in the first month) and Retention (weekly frequency of bookings per driver).”

Common Traps in PM Case Interviews

Avoid these mistakes to score high marks with your interviewers:

Jumping to Solutions: The absolute worst mistake is hearing the prompt and instantly proposing an app or a feature. You must establish the user segment and their pain points first.
Proposing “Everything”: When asked to prioritize, don’t say, “We will build all three solutions.” A PM’s primary job is resource allocation. You must choose one and explain why the others were cut.
Ignoring Feasibility: Proposing a futuristic AI/Blockchain solution that takes 2 years to build for a basic product improvement prompt shows a lack of business maturity. Stick to realistic, high-impact features.

Build A-Grade PM Decks with CaseEdge

Succeeding in product case interviews and competitions requires a structured, logical approach to user needs and metric frameworks. CaseEdge is designed to help MBA students prepare for PM and tech roles.

Practice structured PM cases using interactive CIRCLES and AARRR metric templates.
Get AI-enabled reviews on your product design rationale, user personas, and prioritization logic.
Compare your product launch GTM frameworks with real cases solved by PMs at top tech firms.

Accelerate your PM preparation journey. Get started with CaseEdge today.