How to Write a Harvard Business School Style Case Study Analysis

01 · Definition

What is an HBS-style case study analysis?

An HBS-style case study analysis is a structured evaluation of a real or realistic business situation, written from the perspective of a decision-maker who must choose a specific course of action under real constraints and incomplete information. It is not a summary of the case, and it is not a general essay about the industry or company involved; it is an argument for what should be done next, built on evidence drawn directly from the case.

It’s useful to treat a case analysis as several distinct components rather than one undifferentiated piece of writing, because each component does a different job and is evaluated on different grounds. Situation analysis establishes the relevant facts about the company, industry, and context. The problem statement names the specific decision actually at stake. Alternatives are the realistic options available to the protagonist. Evaluation weighs those alternatives against explicit criteria. And the recommendation, supported by an action plan, states clearly what should be done and how. A strong analysis moves through these components in a logical sequence, each building on the one before it, rather than jumping straight to an opinion about what the company should do.

Why the case method treats analysis as an argument, not a summary

Business cases are deliberately written to withhold a single correct answer, often based on real companies at a real decision point, sometimes before the actual outcome was known. That design choice is central to what a case analysis is actually supposed to demonstrate: not knowledge of what happened, but the ability to reason through an ambiguous, high-stakes decision using incomplete information, exactly the kind of judgment the case method was built to train. Treating a case analysis as a factual summary, rather than a reasoned argument for a specific course of action, is one of the most common ways students misunderstand the assignment, a point returned to throughout this guide.

02 · Origins

Where the case method comes from

The case method’s use in business education dates to the early years of Harvard Business School, adapted from a teaching approach first developed in legal education, and it has since become the dominant teaching model at HBS and a widely adopted approach across business schools worldwide.

Harvard Law School, under Dean Christopher Columbus Langdell in the 1870s, pioneered the use of real legal case decisions as the primary teaching material for law students, replacing textbook lecture with the analysis of actual judicial rulings. When Harvard Business School was founded in 1908, its early faculty faced a distinct problem: unlike law, business as a field had no comparable body of established precedent or settled doctrine to teach from. HBS began developing its own original teaching cases, real business situations written up specifically for classroom discussion, a practice that expanded significantly under Dean Wallace Donham in the 1920s and became the school’s defining pedagogical approach from that point onward.

From a teaching tool to a discipline of its own

Over the following decades, HBS built an entire publishing operation, now known as Harvard Business Publishing, dedicated to researching, writing, and distributing business cases, producing a catalog that today spans tens of thousands of cases used not only at HBS but across business schools around the world. The case method’s spread beyond Harvard, and its adoption in adapted forms at business schools on every continent, reflects a broader consensus in management education that decision-making under ambiguity is a skill better developed through practiced analysis of real situations than through lecture-based instruction alone.

Why the format has remained remarkably stable

Despite a century of changes in business education more broadly, the basic case method format, a written narrative describing a company’s situation up to a specific decision point, followed by structured class discussion, has remained largely consistent, a stability that reflects how directly the format serves its original pedagogical purpose: training judgment under uncertainty rather than transmitting settled knowledge.

03 · Structure

The five components of a case analysis

A complete HBS-style case analysis moves through five distinct components in sequence, each addressed in its own section later in this guide. Understanding the sequence itself is the first step to writing an analysis that reads as a coherent argument rather than a collection of disconnected observations.

Situation analysis establishes the relevant facts: the company’s position, its industry context, and the forces bearing on the decision at hand. The problem statement names, precisely, the specific decision the protagonist actually faces, distinct from the surrounding symptoms described in the case narrative. Alternatives lay out the realistic courses of action genuinely available given the situation established earlier. Evaluation weighs those alternatives against explicit criteria, financial return, feasibility, risk, and strategic fit chief among them. And the recommendation, paired with a concrete action plan, states clearly what should be done and how it would actually be carried out.

Why sequence matters as much as content

Each component in this sequence depends logically on the one before it: a recommendation that isn’t clearly connected back to the stated problem, or a problem statement that isn’t grounded in the situation analysis, breaks the chain of reasoning that gives a case analysis its persuasive force. Reviewers and instructors evaluating a case analysis are typically looking for that visible chain of logic as much as for any single “correct” recommendation, a point that recurs throughout the sections on evaluation criteria and common mistakes later in this guide.

04 · Preparation

Reading and preparing the case

Strong case analysis begins well before any writing, with a deliberate, structured approach to reading the case itself, since cases are typically dense with detail, some of it essential and some of it deliberately included as noise the analysis has to filter through.

A widely taught approach involves multiple passes through the case material rather than a single read-through. An initial skim establishes the basic situation, who the protagonist is, what industry and company are involved, and roughly what decision is looming, without yet trying to absorb every detail. A closer second read works through the case methodically, identifying and annotating the specific facts, figures, and statements that bear directly on the decision, distinguishing them from background color and context that, while useful for texture, doesn’t change the actual analysis. A final pass, often done while beginning to draft the analysis itself, returns to specific sections and exhibits, financial statements, market data, or quoted dialogue, as the specific components of the analysis require deeper support.

Reading exhibits and data as carefully as the narrative

Case exhibits, financial statements, market share tables, survey data, are frequently as important to a strong analysis as the narrative text, and are just as frequently under-read, since they require more active interpretation than prose. A case analysis that ignores or only superficially references quantitative exhibits typically misses supporting evidence that would otherwise strengthen its argument considerably, particularly in the financial reasoning and evaluation stages covered later in this guide.

Preparing for cold calls and live discussion

Because HBS classrooms are built around the possibility of a cold call, being called on without warning to open discussion of the case, preparation conventionally includes forming a tentative, defensible point of view on the central decision before class even begins, rather than arriving with only a neutral summary of the facts. This expectation shapes case preparation distinctly from other kinds of academic reading: the goal isn’t comprehension alone, it’s arriving ready to take, and defend, a position.

05 · Situation analysis

Situation analysis: understanding the company and context

Situation analysis establishes the facts a case analysis will build its argument on: the company’s current position, its industry and competitive context, and the internal and external forces most directly relevant to the decision at hand.

A strong situation analysis is selective rather than exhaustive, surfacing the facts that actually bear on the decision rather than restating everything the case describes. It typically addresses the company’s business model and current performance, the competitive and industry dynamics it operates within, and any specific internal factors, organizational structure, culture, resource constraints, that shape what courses of action are realistically available to the protagonist. Frameworks like SWOT analysis and Porter’s Five Forces, covered in their own section later in this guide, are commonly used here to organize this material systematically rather than as a list of isolated observations.

Distinguishing relevant facts from case texture

Cases are often deliberately written with extraneous detail, background texture that makes the narrative feel realistic but that doesn’t materially affect the decision under analysis, and a skilled situation analysis demonstrates judgment precisely by identifying which details matter and leaving the rest aside, rather than treating every fact in the case as equally significant. This selectivity is itself part of what a strong case analysis is meant to demonstrate: the ability to separate signal from noise in a realistically messy set of information, a skill directly transferable to real business decision-making.

06 · Problem statement

Identifying the real problem statement

The problem statement is arguably the single most consequential sentence or two in an entire case analysis, since every alternative, every piece of evaluation, and the final recommendation all need to connect back to it directly. Getting the problem statement wrong tends to undermine everything that follows, however well-reasoned the rest of the analysis is.

A precise problem statement names the specific decision the protagonist actually faces, not the negative symptoms surrounding it. Falling sales, declining market share, or rising employee turnover, common features of case narratives, are typically effects of a deeper issue rather than the problem itself; the actual problem is usually the decision the protagonist must make in response to those symptoms, such as whether to enter a new market, restructure a product line, or change a pricing strategy. A useful test for a draft problem statement is to ask what specific choice the protagonist is facing at the point the case narrative ends, and to phrase the problem statement in terms of that choice rather than in terms of the surrounding difficulty.

A problem statement is a claim, not a topic

Much like a thesis statement in academic writing, a strong problem statement makes a specific claim about what the central issue is, rather than simply naming the general subject area, “the company’s pricing strategy,” in a way vague enough that a reader can’t yet tell what decision is actually at stake. Framing the problem statement as a direct, specific question, or a direct, specific statement of the decision required, gives the rest of the analysis a clear target to build toward.

07 · Alternatives

Generating genuine alternatives

Once the problem statement is established, a strong case analysis lays out a small number of genuinely distinct, realistic alternatives, the actual options available to the protagonist given the constraints the situation analysis established, rather than a token list of options included only to be dismissed quickly in favor of a predetermined answer.

Effective case analyses typically present two to four alternatives, few enough to evaluate each seriously, but more than one, since presenting only the eventual recommendation without genuine competing options undermines the analysis’s persuasive force by skipping the comparison that gives a recommendation its weight. Alternatives should be meaningfully different from one another, representing genuinely distinct strategic directions rather than minor variations on the same underlying approach, and each should be realistic given the constraints, resources, and context the situation analysis has already established.

Including, and taking seriously, the status quo

“Do nothing,” or maintain the current course, is often a legitimate alternative worth including explicitly, both because it establishes a baseline against which other options can be measured and because in some cases it may genuinely be the strongest available option, particularly when proposed changes carry substantial risk or cost the case doesn’t otherwise justify. Dismissing the status quo without serious consideration is a common way case analyses weaken their own comparative evaluation before it even begins.

08 · Evaluation

Evaluating alternatives against explicit criteria

Evaluation is where a case analysis does its most substantive comparative work, weighing each alternative against a consistent, explicit set of criteria rather than describing each option in isolation and asserting a preference at the end.

Commonly used evaluation criteria include financial impact, the expected effect on revenue, cost, or profitability, often supported by the kind of quantitative reasoning covered in the section on financial analysis below; feasibility, whether the option is actually achievable given the company’s resources, capabilities, and organizational constraints; risk, both the likelihood and severity of things going wrong under each alternative; and strategic fit, whether the option aligns with the company’s broader stated goals, competencies, and market position. Applying the same criteria consistently across every alternative, rather than evaluating each option on a different, convenient basis, is what makes the resulting comparison genuinely persuasive rather than an exercise in confirming a conclusion already reached.

Being honest about trade-offs

A rigorous evaluation section acknowledges genuine downsides of the alternative it ultimately favors, alongside genuine strengths of the alternatives it doesn’t, since a comparison that makes the eventual recommendation look costless and every other option look obviously flawed reads as unpersuasive precisely because real business decisions rarely work that way. Evaluators and instructors reviewing a case analysis consistently rate honest engagement with trade-offs more highly than a one-sided comparison built to make the conclusion look inevitable.

09 · Recommendation

Making and defending a recommendation

The recommendation states, directly and specifically, what the protagonist should do, and it should follow visibly from the evaluation that precedes it rather than introducing new reasoning or new criteria the reader hasn’t already seen applied to the other alternatives.

A strong recommendation is specific enough to actually guide action, naming what should be done, not simply which general strategic direction is preferable in the abstract. “Expand into the Southeast Asian market through a joint venture with a local distributor within eighteen months” is a specific, actionable recommendation; “the company should pursue international growth” is a direction, not yet a recommendation with enough specificity to evaluate or act on. The strongest recommendations also directly answer the problem statement established earlier, closing the logical loop the analysis opened at the start.

Anticipating and addressing the counterargument

Because case discussions, whether written or in a live classroom, typically involve genuine disagreement among reasonable analysts working from the same facts, a strong recommendation briefly anticipates the strongest objection to it and addresses that objection directly, rather than presenting the recommendation as though no reasonable person could disagree. This is analogous to the way a strong academic thesis anticipates counterarguments, and it signals that the recommendation reflects genuine comparative judgment rather than an assumption reached before the alternatives were seriously considered.

10 · Action plan

Building the implementation and action plan

An action plan translates the recommendation into concrete steps: what should happen, in what sequence, over what timeframe, and it’s what separates a case analysis that simply names a preferred direction from one that demonstrates the recommendation is genuinely executable.

11 · Financial analysis

Supporting the analysis with financial reasoning

Many business cases include financial statements, unit economics, or market sizing data specifically because quantitative reasoning is expected to inform, and often decide, the strongest case analyses, particularly in the evaluation and recommendation stages covered earlier in this guide.

Common quantitative tools include basic ratio analysis, profitability, liquidity, and efficiency ratios drawn from a case’s financial statements, used to assess a company’s current position or compare alternatives’ likely financial impact; break-even analysis, useful when an alternative involves a new investment or cost structure and the case turns on how much volume or revenue would be needed to justify it; and simple market sizing, estimating the scale of an opportunity, such as a new market or product line, using the data the case provides or reasonable, clearly stated assumptions where it doesn’t.

Precision without false confidence

Because cases frequently provide incomplete financial data by design, strong quantitative reasoning in a case analysis states its assumptions explicitly rather than presenting an estimate as more precise or more certain than the underlying data actually supports. A well-reasoned estimate built on clearly stated, defensible assumptions is considered stronger analysis than either avoiding quantification altogether or presenting a number without explaining how it was derived.

12 · Frameworks

Common frameworks, and when each one earns its place

A small number of standard business frameworks recur across case analyses because they organize a specific kind of question efficiently, but each is a tool suited to a specific analytical job, not a checklist to apply uniformly to every case regardless of fit.

• SWOT analysis

  Organizes internal strengths and weaknesses alongside external opportunities and threats; useful for an initial, structured overview of a company’s position.

• Porter’s Five Forces

  Assesses industry attractiveness and competitive intensity through supplier power, buyer power, new entrants, substitutes, and rivalry; useful when the core issue concerns industry structure.

• Value chain analysis

  Breaks a company’s activities into primary and support functions to identify where value, or cost, is actually created; useful for operational or cost-focused cases.

• The 4Ps (marketing mix)

  Product, price, place, and promotion; useful when the central decision concerns a marketing or go-to-market strategy specifically.

• BCG growth-share matrix

  Categorizes a company’s business units or products by market growth and relative market share; useful for portfolio or resource-allocation decisions.

Choosing frameworks by fit, not habit

The most common framework-related mistake in case analyses is applying a familiar framework, most often SWOT, to every case regardless of whether it actually illuminates the specific decision at hand, producing a generic-sounding section that could apply to almost any company. A framework earns its place in an analysis when it’s the tool best suited to the specific problem statement established earlier, not simply the one most recently covered in class.

13 · Writing style

Writing style and formatting conventions

HBS-style case analyses favor a direct, evidence-grounded, business-memo register over an academic or narrative writing style, reflecting the format’s origin as a decision document meant to inform action rather than a piece of scholarly prose meant to be read for its own sake.

Effective case analyses tend to lead with conclusions rather than build toward them, stating the recommendation early, often in an executive summary or opening paragraph, and then supporting it with the detailed reasoning that follows, a structure closer to the inverted-pyramid pattern common in business and journalistic writing than to the funnel structure common in traditional academic essays. Headers, bullet points, and short paragraphs are widely used and generally expected, since a case analysis, like other business documents, is often read by someone evaluating it quickly rather than reading start to finish in one sitting.

Grounding claims in specific case evidence

Every substantive claim in a strong case analysis is traceable to specific evidence in the case itself, a figure from an exhibit, a quoted statement from a character, a specific fact from the narrative, rather than general business knowledge or outside assumptions about the industry not actually supported by the case material. This grounding in the case’s own evidence is what distinguishes a case analysis from a general opinion essay about the company or industry, and it’s a distinction instructors and reviewers consistently emphasize.

14 · Written vs. discussion

Written analysis vs. live class discussion

A written case analysis and a live classroom discussion of the same case are related but distinct exercises, and preparing effectively for each involves somewhat different priorities, even though both draw on the same underlying analytical work.

A written analysis has the advantage of time: it can present a fully worked, polished argument, with alternatives evaluated methodically and a recommendation defended in careful, organized prose. A live class discussion, by contrast, is dynamic and unpredictable, shaped heavily by an instructor’s specific questions and by disagreement and pushback from other students in real time, meaning strong classroom performance depends as much on being able to defend or adapt a position under direct challenge as on having reached a well-reasoned conclusion beforehand.

Preparing a position that can survive being challenged

Because live discussion routinely surfaces objections a written analysis might not have anticipated, effective case preparation for classroom discussion typically includes actively rehearsing the strongest counterarguments to one’s own tentative position beforehand, not just preparing to state and defend a single conclusion. This overlaps directly with the practice, described earlier, of anticipating and addressing the strongest objection within the written recommendation itself, but it matters even more acutely in a live setting where the objection may come from an instructor or classmate rather than from the analyst’s own anticipation of it.

15 · Common mistakes

Common mistakes, and how to fix each one

Most weak case analyses trace back to one of a small number of recurring problems, each tied to one of the specific components covered earlier in this guide. Naming the specific problem makes it far easier to fix than a general instruction to “analyze the case more thoroughly.”

16 · Consensus

Where do business educators broadly agree?

Across business schools that use the case method, and among instructors trained in it, there’s broad agreement on several structural points about what makes a case analysis effective, even as specific formatting expectations vary somewhat between programs and instructors.

There is broad agreement that a case analysis should be evaluated on the quality and coherence of its reasoning, not on whether it matches a single predetermined “correct” answer, since most cases are deliberately written to support multiple defensible recommendations. There is broad agreement that grounding every claim in specific case evidence, rather than general outside knowledge or assumption, is a core standard of case analysis quality, one of the clearest, most consistently applied evaluation criteria across programs. There is also broad agreement, reflected in guidance published by Harvard Business Publishing for both instructors and students, that active, prepared participation, whether in a written analysis or live discussion, is central to what the case method is designed to teach, distinguishing it clearly from a lecture-based model built around passive absorption of material.

A case analysis isn’t judged on whether you reach the same conclusion the instructor has in mind; it’s judged on whether someone reading only your reasoning, without knowing your conclusion in advance, would find it genuinely persuasive. Pattern reflected across case method teaching guidance

17 · Contested ground

Where does genuine debate continue?

Not every question about the case method and case analysis has a settled answer. Several genuinely contested questions recur in discussions among business educators, and an honest guide names them rather than resolving them by assertion.

Does the case method adequately prepare students for real business ambiguity?

Supporters argue that even a somewhat simplified, retrospectively written case still trains the core skill real decision-making requires: reasoning under incomplete information toward a defensible course of action, a skill that transfers even when specific case details don’t perfectly mirror live business conditions. Critics argue that a written case, however realistic, is still a bounded, curated version of a business problem, with a defined set of facts and a clear endpoint, in ways that understate the far messier, more open-ended nature of actual business decisions, where the “facts” of a situation are rarely handed to a decision-maker in a tidy narrative to begin with.

How much should quantitative rigor be weighted against strategic reasoning?

Some instructors and reviewers place heavy weight on quantitative precision, break-even calculations, ratio analysis, sizing estimates, as the clearest, most objectively assessable component of a case analysis. Others argue that overemphasizing quantitative polish can reward analyses that look rigorous on the surface while missing the deeper strategic judgment the case method is meant to develop, and that a well-reasoned qualitative argument, clearly grounded in the case, can be just as strong as one built around more extensive numerical modeling. This tension between quantitative and strategic emphasis recurs across programs and even across individual instructors within the same program.

Are older, historical cases still pedagogically useful?

Because many widely used cases were written years or even decades ago, some educators argue their value lies specifically in the reasoning process they train, which remains relevant regardless of how dated the specific industry details have become. Others argue that cases should be refreshed more frequently to reflect current industry structures and technologies, since students may reasonably discount the exercise’s relevance when a case’s technological or competitive assumptions feel visibly outdated, an ongoing tension in case-method curriculum design rather than a fully resolved question.

18 · Checklist

A preparation checklist at a glance

Because a case analysis is built from several distinct, sequential components, a targeted checklist is more useful during preparation and revision than a general instruction to “analyze more deeply.”

• Situation analysis

  Have I surfaced the facts that actually bear on the decision, rather than restating everything the case describes?

• Problem statement

  Does it name the specific decision the protagonist faces, rather than the surrounding symptoms?

• Alternatives

  Are they genuinely distinct and realistic, including a fair treatment of the status quo?

• Evaluation

  Are all alternatives assessed against the same explicit criteria, with honest trade-offs acknowledged?

• Recommendation

  Is it specific enough to act on, and does it directly answer the problem statement?

• Action plan

  Does it sequence concrete steps, a realistic timeframe, key risks, and a measure of success?

• Evidence

  Is every major claim traceable to specific facts, figures, or exhibits from the case itself?

Closing

Key takeaways on writing an HBS-style case analysis

An HBS-style case study analysis is best understood as a structured argument for a specific course of action, not a summary of a business situation, built from five sequential components: a selective situation analysis grounded in the facts that actually matter, a precise problem statement naming the real decision at stake, a set of genuinely distinct and realistic alternatives, an honest evaluation of those alternatives against explicit criteria, and a specific, defensible recommendation paired with a concrete action plan for carrying it out. Frameworks like SWOT and Porter’s Five Forces, and quantitative tools like ratio and break-even analysis, are most effective when applied because they genuinely clarify the specific decision at hand, not out of habit or convention. Business educators broadly agree that a case analysis should be judged on the coherence and evidence behind its reasoning rather than on matching a single predetermined answer, even as real, ongoing debate continues over how well the case method mirrors genuine business ambiguity and how quantitative rigor should be weighed against strategic judgment. Writing a strong analysis, in the end, means treating every section as part of one continuous argument, from the facts established at the start to the recommendation defended at the end, rather than a set of disconnected exercises completed in sequence.

19 · Notes

Frequently asked questions