The PM Case Study Playbook with Ashutosh Rai

A new company. A new prompt. A new panel.

PM case studies can feel completely different every time.

They aren't.

Underneath, most of them are testing the same core Product thinking.

The PM Case Study Playbook gives you a repeatable way to approach take-homes and Product case interviews without staring at a blank page wondering where to start.

Inside, you'll learn the 9-step spine:

01 · Frame the problem

Define who you're solving for, the outcome you're chasing and what's out of scope.

02 · Clarify & state assumptions

Ask the questions that actually change your answer, then make your assumptions explicit.

03 · Understand the users

Identify specific segments and their jobs-to-be-done. Don't design for "everyone."

04 · Find the real problems

Map the user's pain points before jumping to features.

05 · Prioritise

Choose what to tackle first and explain why.

06 · Propose solutions

Generate a few thoughtful solutions instead of throwing twenty features at the problem.

07 · Name the trade-offs

Show what you're deliberately giving up and why your choice is worth it.

08 · Define an MVP & metrics

Define the smallest useful version and how you'd know whether it worked.

09 · Communicate the recommendation

Lead with the answer, then show the reasoning behind it.

A worked example

The guide walks through the complete spine using a realistic take-home:

Improve onboarding for a UPI app aimed at first-time users in Tier-2 & Tier-3 India.

You'll see how the problem is framed, assumptions are stated, users are narrowed down, problems are prioritised, solutions are evaluated and trade-offs are made before arriving at a recommendation.

The numbers in the example are explicitly labelled as illustrative assumptions, not real metrics.

Learn what reviewers are actually looking for

The playbook focuses on three areas where candidates commonly freeze:

Ambiguity

Take control of vague prompts instead of asking endless clarifying questions.

Prioritisation

You can't solve everything. Make a choice and defend it.

Presentation

A tight 6–10 slide deck or clean 2–3 page document can be more effective than a 30-page essay.

Avoid the 5 traps

The guide calls out five common ways to lose a case you could have won:

→ Boiling the ocean

→ Solutioning first

→ No prioritisation

→ No trade-offs

→ No metric

The mindset behind it

I've done PM take-homes and assignments, and one thing I got wrong early was treating them like exams with a hidden "right answer."

They're not.

The goal isn't to find the cleverest feature.

It's to show judgment under ambiguity and the ability to communicate a decision.

A modest recommendation with clear reasoning and explicit trade-offs can be much stronger than a flashy idea that doesn't explain itself.

This is for you if:

→ You have a PM take-home assignment coming up

→ You're preparing for Product case interviews

→ You freeze when given an ambiguous Product prompt

→ You tend to jump into solutions too quickly

→ Your case studies become unnecessarily long

→ You struggle to explain prioritisation and trade-offs

→ You want a repeatable structure without memorising a rigid framework

Don't memorise the nine steps as a script.

Use them to make your thinking easier to follow.

Frame. Choose. Explain. Defend.