Schedule mock interviews on the Meeting Board, join the latest community discussions in our Consulting Q&A and find like-minded Case Partners to connect and practice with!

Question merged

This question is read-only because it has been merged with

What's the best way to structure a revenue growth case?

Anonymous A

on Mar 06, 2018

Global

Structure revenue growth case with multiple products

Hi,

I am relatively new to case studies and just worked through the tutorials and the bootcamp. I understand that when analyzing for example a decrease in revenue, I have to know what kinds of products the client offers, but what is the best way to structure the issue-tree accordingly?

Starting with revenue on top and then having "Revenue product 1" + "Revenue Product 2" + and so on, on the next "level" and then "price product 1" * "Sales volume product 1" below revenue for product 1?

Or should I start with revenue, on the enxt level of the issue-tree "Sales Volume" * "Price" and then have "Sales volume product 1" below the total sales volume and all the prices of the products below "price".

The structure in the first example seems better, but the second structure is faster in my opinion because I could just add all the sales volumes and calculate the average price to find the revenue while in the first example I have more smaller calculations.

Thanks for your advice

2 Answers

2.8k Views

Be the first to answer!

Nobody has responded to this question yet.

Top answer

Francesco

Coach

on Mar 06, 2018

#1 Coach for Sessions (4.500+) | 1.500+ 5-Star Reviews | Proven Success (➡ interviewoffers.com) | Ex BCG | 10Y+ Coaching

Hi Anonymous,

I would suggest to use the first method, but with a switch; you won’t need indeed to know price and volume for all the segments. More specifically:

I would start dividing in revenue streams (not necessarily by product – it could also be by customer or distribution channel)
I would then ask how revenues changed for each stream
I would start from the one that had the biggest decline in revenues. For that only, I would then move to divide in price and volume to identify the issue. In case we are not able to fix the issue, I would then move to the second-worst stream

The reason I believe this method is superior to an initial division of revenues in price * volume is that will allow to understand immediately the real reason for the problem, and for which segment. With an initial division in price*volume, that may not always be the case.

Assuming for example that the problem of the company is a decline in volume of the more expensive product A by 10 units and at the same time the cheaper product B increased by 20 units, dividing in price*volume will show an increase of volume and a decrease of the average price – thus apparently a price issue. Although you may eventually identify the issue is volume for product A, and thus not price related, this would take longer than following the previous steps.

Hope this helps,

Francesco

Contact coach

Vlad

Coach

edited on Mar 06, 2018

McKinsey / Accenture Alum / Got all BIG3 offers / Harvard Business School

Hi,

First of all, In the clarifying questions, I ask proactively how many products / revenue streams we have

Then:

If I have just two products or two revenue streams I would split the products on the revenue level (e.g. revenue from product 1, revenue from product 2)
If I have 2+ products I usually go with revenues, split them into price and quantity. Under price, I use a vertical numbered list of products. e.g. 1) x 2) y 3) z. Same with the quantity
In the last case, I will end up with a table under my structure since both price and qty (and maybe variable costs per unit as well) will have a numbered vertical list

Best

Contact coach

1 comment

Justin

on Mar 06, 2018

Thanks a lot, this was really helpful

Top answer by

Ian

Coach

5 Answers

700+ Views

Issue Tree

The Issue Tree is a valuable tool for analyzing the causes of issues during a case interview. When faced with a complex issue, the Issue Tree helps you break it down into its components. By focusing on the most urgent aspects and employing a hypothesis-driven approach, you can progress more quickly—a skill highly valued in consulting. 🚀🔎 In this article, you'll learn how to effectively use the Issue Tree, understand the differences between problem-based and solution-based trees, and how to leverage this technique to excel in your case interviews. Problem-Based Tree vs. Solution-Based TreeIn case interviews, two main types of Issue Trees are utilized:Problem-Based Tree: This helps you identify and understand the root causes of the issue and why it occurred in the first place.Solution-Based Tree: This is used to develop recommendations and clarify how the issue can be resolved.Ensure that the issues are MECE (mutually exclusive, collectively exhaustive). Otherwise, it will be challenging to address each area effectively. Use a hypothesis-driven approach to tackle the most significant issues first (see Pareto Principle).In consulting, the preferred approach is "answer-first" or "results-first." This involves starting with the main solution or conclusion and then working out the rationale. This is closely related to the Pyramid Principle.💡 Prep Tip: Practice these and other essential frameworks with our drills! Issue Tree as a Foundation for Consulting ProjectsAt the start of a new project, your team typically creates an Issue Tree. Once you agree on all relevant sub-issues, you gain an overview and focus on the key questions based on your hypotheses (answer-first style). Since all branches of the Issue Tree are MECE, the project manager can efficiently distribute the workload across the team. Each branch leads to a separate workflow that can be worked on independently, avoiding unnecessary interfaces that could cause inefficiencies. This explains why a small consulting team can achieve a lot in a short time.Once the causes of an issue are identified, the team uses a solution-based tree to determine how the issue can be resolved. Example of an Issue Tree in a Case InterviewImagine you need to calculate how many people can stand simultaneously on an airport runway during a case interview.Step 1: Problem Analysis with the Top-Down ApproachIn the top-down approach, you start by structuring the main problem or the case question and systematically break it down into its individual components. The goal is to identify all relevant areas or factors that influence the problem.First, you consider the overarching components (e.g., the total area of the runway) and then break these down into more specific details (e.g., the width and length of the runway).Step 2: Solution Development with the Bottom-Up ApproachIn the bottom-up approach, you focus on concrete numbers and data at the most detailed level of the problem and work your way up. You estimate necessary values, such as the width and length of the runway, and use these in your calculations to solve the main problem.As you can see, the top-down approach allows you to systematically break down the main problem into its components and identify all relevant influencing factors. The bottom-up approach then helps to develop a well-founded solution to the main problem by analyzing specific numbers and data.💡 In our case library, you'll find over 200 cases on various topics that will help you practice creating an Issue Tree! Check them out. Key Takeaways on Issue Trees in Case InterviewsThe Issue Tree is a central tool for structuring your case and developing hypotheses.Differentiate between problem-based and solution-based Issue Trees.Use hypotheses to quickly identify the root causes of the issue.Ensure Issue Trees are MECE to avoid inefficient dependencies between branches.👉 Prep Tip: Practice your cases with peers and arrange meet-ups on our meeting board.

View article

RSM Consulting Interview Guide

Ready to kickstart your career at RSM Consulting? Discover the entire recruitment process, from assessments to interviews, with tips to help you stand out and secure your dream role in consulting.

View article