Comparing four common case types and the first question each one asks.

Different cases begin with different questions. Learning to recognise the type in the first few minutes saves teams from starting every case with the same generic framework.

Why recognise the case type early

Many student teams open every case with the same set of boxes and hope the case will fit. A more reliable habit is to ask what kind of problem this is. Case types are not strict categories, and real cases often blend them, but recognising the dominant type tells you what the client is really worried about and which analysis to start with.

This guide compares four common types: profitability, market entry, growth and operations. For each one it gives the first question, the first analysis and one trap to avoid. Treat it as a way to organise your thinking after the first read, and then build an issue tree for the specific case in front of you.

Profitability: what changed in profit, and why

A profitability case usually begins with a client whose profit has fallen or is lower than expected. The first question is whether the problem sits in revenue, cost or both, and where in the business it is concentrated. The first analysis is to split profit into revenue and cost and compare each part over time or against a reference.

The trap is jumping to a fix before locating the problem. If a team recommends cutting cost without checking whether revenue fell, it may solve the wrong issue. Ask for data that lets you split by product, customer group or period, and test one hypothesis about where the change is concentrated before you widen the search.

Market entry: should the client go in, and how

A market entry case asks whether a client should enter a new market, product line or region. The first question is whether the market is attractive and whether the client can compete. The first analysis often covers market size and growth, the competitive landscape and the client's capabilities, followed by the choice of entry route.

The trap is treating the size of the market as the whole answer. A large market can still be a poor fit for the client. Link every piece of market data to the client's strengths and constraints. Remember that entry options such as building, partnering or acquiring have different costs and risks, and compare them explicitly.

Growth: where can more come from

A growth case asks how a client can increase revenue or reach a target. The first question is where growth might come from: existing customers, new customers, new products or new channels. The first analysis is to break current revenue into drivers and look at which one has room to move.

The trap is offering a list of ideas with no priority. A judge wants to see why one option beats another. Use a simple basis for comparison, such as potential impact, effort and risk, and be clear about the assumptions behind each estimate. Tie the recommendation to the client's targets and timeline, and state what you would test first.

Operations: where does the process lose value

An operations case looks at how a client delivers something, such as a service, a product or a supply chain, and asks how to improve it. The first question is where the process is slow, costly or error-prone. The first analysis is usually a simple map of the steps, with time, cost or error information attached to each.

The trap is proposing technology or new staff before understanding the bottleneck. The best fix may be small and organisational. Look for the step that limits the whole process, test a change on paper and consider the effect on people, who will need to work with the new process. Include a plan for how the change would be introduced.

A quick comparison table for the first read

After the silent read, write the four types as rows with two columns: the signal in the case wording that suggests the type and the first analysis you would run. Phrases about falling margins point to profitability. Phrases about a new region or product point to entry. Phrases about targets point to growth. Phrases about delays or errors point to operations.

Then pick the dominant type, note the secondary one and write them next to your hypothesis. If the case blends two types, say so in the framing. For example, an entry case may need a short profitability check on the client's current business. Keep the table in the team notes so everyone starts from the same reading.

Reading signals in the case wording

Practise on a short prompt such as a regional bakery chain whose profit fell while sales stayed flat. The wording points to profitability, since sales are stable and profit has moved. The first question becomes whether costs rose, prices fell or the product mix changed, and the first analysis splits profit into revenue and cost drivers.

Now change one sentence so that the chain wants to open in a neighbouring city. The type shifts to market entry, and the first question becomes whether the new market is attractive and whether the chain can compete there. Small changes in wording change the starting point, which is why reading the prompt carefully pays off.

From case type to issue tree

Once you have named the type, use it to draft the top of your issue tree. For a profitability case, the first branches are likely revenue and cost. For entry, they may be market, client capability and entry route. For growth, they may be existing customers, new customers and new offers. For operations, they may be the stages of the process.

Then adapt the tree to the facts in the case. Remove branches that the case rules out and add branches the prompt suggests. The type gives you a head start and saves time, but the tree must fit this client. Check that the branches do not overlap and that together they cover the question.

Common mistakes when using case types

Avoid forcing a case into a type that does not fit. If the client's problem is not clear, ask the case giver a clarifying question rather than guessing. Avoid copying a standard framework without adapting it to the facts. The type is a starting point for an issue tree, not a replacement for one.

Practise by taking old cases and labelling the type before you read the solution. Compare your label with a teammate's and discuss where you differ. Over several cases, you will recognise signals faster, and you will start each case with a sharper first question. That saves minutes in the first hour, when minutes matter most.