Day 1: Lessons from my first product thinking and product solution cases

Introduction

Our senior organized a group case session for preparation and discussed 2 cases, one on problem solution and one on product thinking. I won't add the exact excerpts till the process is completed but will include a generalized process flow I observed, along with the discussion points which pinpointed that, along with my personal observations. Hope it Helps!

 THINK BEFORE YOU SPEAK!

 

Basic Process Flow & General Tips

1. Preliminary Questioning

Ask questions to gain information and figure out the root problem. The questions today majorly focussed on:

• User Demographics, Age group, Geographics
• New v/s Old User
• Metrics of interest
• Understanding the meaning of the terms
• Platforms (Website, Mobile App (Android, iOS)
• Asking for metrics data
• Distribution of various features and changes in them over time of interest
• Change in user base
• System-level problem
• Goal

2. Reiterate to Understand

It is important to ensure that you understand the problem correctly else all efforts can go waste.

3. Root Cause

Once the root cause is reached, don't try to jump to conclusions. Like in the first case, jumping directly to reverting things may not be the best solution considering conversion rates. Synchronize the solution considering the goal.

4. Recommendations/ Solution

They can fall under various categories like in Flipkart interaction case, it could be based on changes at the algorithmic level, change in variety of recommendation or the feature commonality in recommendations. We can tell the interviewer that we are picking this class of solution and can delve deep if he/she agrees.

In second case study on product thinking, I divided the solution into 2 broad categories: motivating the solution from competitors or creating new innovative solutions (gamifying paying bills earlier, group paybacks, etc)

Solutions can also be holistic v/s user segment specific

5. Comparing Solutions

Identify some key principles on which to judge the solutions, major factors being: (i) Value Proposition to User, (ii) Value to Business, (iii) Ease of Implementation & Time constraints

6. Drawback & Loopholes

Discuss what can be the drawbacks and loopholes in the proposed solution

 

My Observations

1. Draw the product image and write down the terms discussed, it helps in keeping the points arranged and also helps in creative thinking. For example, see the image below where we were asked to devise methods to increase user interaction:

2. Structure & Framing of question matters. Ask questions which naturally lead to your proposed thoughts

3. Creativity > Structure. Though the structure is important but creative and innovative ideas are a strong positive and the idea may be refined further if the interviewer finds it in resonance with the problem. You can also tell the problems in that idea, it's not an issue. Just go that much deep to be able to compare with other solutions.

4. Questioning > Assuming, don't just assume and go ahead but clarify the validity of every assumption you make. And again, do questioning to clarify and reach root cause along with iterating the things understood so far.

5. Keep writing things down, structure in arguments will come through practice.

6. Doubt the Question. In the second case, I was doubtful whether the increase in user engagement is required as we may have significantly better engagement than our competitors. This question works better in product solution questions but still projects your deep insights, so is a positive thing!