Strategy vs Operations Cases

Hi,

First of all, you need to clarify the objective and the context of the case. A good objective is measurable (has some metric and timeline) E.g. for pricing it may be - "What should be the price for the new product?" or "What should be the pricing strategy for the portfolio of products?" or "Our competitors increase the price, what should we do". As you can see all these cases will have a different structure.

The general framework for pricing a new product is: Cost base - Value based - Competitor based - pricing strategy

1. Cost based - you actually check what are the costs and apply standard industry / target markup

2. Value based pricing can be done in 2 ways:

• You compare the value proposition and features of your product vs. the VP of the closest product of your competitors. If you have a significant difference in value prop - you have to define how much value you propose to the customer in $ terms.
• Another way is to calculate the closest alternatives and think how much additional value we provide by replacing them. Think of the discount airlines compared to trains or buses

3. Competitor based pricing - basically it's benchmarking against competitors if you have a product with a very similar value prop. Make sure you take into account the segment (i.e. in premium higher price may be the proxy for quality).

4. Pricing strategy - here you define how you will price the product taking into account 1,2,3 and your company strategy. Maybe you decide to have a zero margin if you can crossell other services. Or maybe you would like to subsidize to win the competition. Also, think of price differentiation and having different pricing tiers (e.g. basic, premium or even freemium) and how it helps to drive price perception and fulfill strategic goals

There are several types of operational cases that you have to master:

1) Operational math problems. (e.g. Should we increase the speed of the elevator or just buy a second one? How should we reduce the queues? How should we increase the output of a factory?).

Structuring:

• Usually, you have to look at the process. Even the most complicated systems have the inflows and outflows

The key concepts that you have to learn:

• Capacity and utilization (both machine and people)
• Cycle time, Throughput time, Little's Law
• How the does lowest cycle time influence the production? (Lead time = cycle time of the slowest process)
• How can we mitigate the bottlenecks with low cycle time? (Buffer, Parallel process, speeding up)

2) Cost cutting cases

Structuring:

• What is the cost composition and what are the biggest costs
• Benchmarking of the biggest costs to find the improvement potential
• Process improvements to meet the benchmarks
• Costs and benefits of the proposed initiatives

The key concepts that you have to learn:

• Internal / external benchmarking
• Idle time
• Core processes (usually are optimized) and the supporting processes (usually are cut)
• Math structures (Frequency of operations * time per operation)
• Other useful structures (e.g. people - process - technology)

3) Bottleneck cases (e.g. Huge write-offs in the meat store or bottleneck on the bridge)

Structuring:

You draw a value chain and go through it to find a bottleneck.

E.g. for the meat write-offs it will be:

• Supplier issues (packaging, meat quality, warehousing)
• Transportation (Length, fridges)
• Store (Refrigerators in the warehouse, in-store fridges, demand for the meet)

Feel free to reach me for further help with these cases.

Best