Case Study Report Writing: Analysis Framework

Written By

Evan McConnell

✔️ 97% Satisfaction | ⏰ 97% On Time | ⚡ 8+ Hour Delivery

Case Study Report Writing: Analysis Framework

Three things that students confuse: a case study as a research methodology (Yin's definition, used in dissertations), a case study as a teaching tool (Harvard Business School case studies, used in business education), and a case study report as an assessment format (a written report presenting analysis of a given case).

This post focuses on the third. You've been given a case. You analyse it using a specified framework. You write a report presenting your analysis. This is different from conducting case study research for a dissertation.

Typical Structure of a Case Study Report Assignment

The assignment specifies the case and often specifies the analytical framework. "Analyse Kodak's failure to adapt to digital photography using the innovator's dilemma framework." You're not inventing the framework. You're applying it.

The report structure is typically standard. Executive summary (150 to 250 words) synthesising key findings. Case background (200 to 300 words) establishing context and key facts. Analysis section (the bulk of the report) applying the specified framework to the case. Identification of key issues (what problems did the organisation face, and why did they arise?). Recommendations (what should the organisation have done differently, grounded in your analysis). Limitations (what constraints limited your analysis? What information was unavailable?).

The executive summary is brief and punchy. It's designed for readers who have limited time. It includes the key problem, your main findings, and principal recommendations. Nothing more.

Case background establishes facts. Who was the organisation? What was the industry? What happened chronologically? When did decline begin? What were early warning signs? You're not analysing yet. You're establishing the case clearly so your reader understands what you're analysing.

Applying Analytical Frameworks to Cases

The analytical framework is your lens. Different frameworks reveal different things.

SWOT analysis examines strengths (internal advantages), weaknesses (internal disadvantages), opportunities (external possibilities), and threats (external risks). You examine the case and identify each category. For a company facing market disruption, weaknesses might be outdated technology and missed innovation. Threats might be new competitors. Strengths might be established brand and customer loyalty. Opportunities might be entering adjacent markets. SWOT makes visible the company's position relative to its environment.

PESTLE analysis examines political, economic, social, technological, environmental, and legal factors shaping the business environment. You analyse how each factor affected the organisation. For a company operating internationally, political risk might include trade barriers or regime changes. Economic factors might include currency fluctuations or recessions. Technological factors might include digital disruption. PESTLE positions the organisation within its broader environment.

Porter's Five Forces examines competitive dynamics: threat of new entrants, bargaining power of suppliers, bargaining power of buyers, threat of substitutes, and intensity of competition. You assess each force and evaluate how it affected the company. Strong buyer bargaining power (when customers have alternatives) erodes profits. This framework reveals the competitive structure shaping outcomes.

Lewin's change management model examines unfreezing (destabilising the status quo), moving (implementing change), and refreezing (stabilising the new state). You apply this to organisational change initiatives in the case. Did the organisation unfreeze sufficiently? Did it communicate the need for change? Did it support the moving stage?

Diagnostic frameworks vary by discipline. Clinical case reports use diagnostic frameworks specific to the condition. Financial case studies might use ratio analysis. careful management cases might use value chain analysis.

The key principle is the same: the framework structures your analysis. It ensures you examine the case systematically rather than randomly identifying issues.

Seeking support during the dissertation process is a sign of academic maturity, not weakness, and most universities provide a range of resources specifically to help students manage the demands of independent research. Your dissertation supervisor is your most important source of academic guidance, but the support available to you extends well beyond that one-to-one relationship to include library services, academic skills workshops, and student welfare provisions. Many universities also run peer study groups and writing communities where dissertation students can share their experiences, read each other's work, and provide mutual support during what can be a challenging and isolating period. Taking full advantage of the support structures available to you is one of the most sensible things you can do to protect both your academic performance and your mental wellbeing during the dissertation writing process.

Presenting Findings from Case Analysis Clearly

Your analysis section applies the framework to the case data. You're not just listing SWOT factors. You're explaining why each factor mattered. For the Kodak case, yes, Kodak had strengths: established brand, vast resources. But why didn't these strengths prevent decline? Because the disruption came from a different business model (digital versus film), and Kodak's strengths (film manufacturing, distribution networks) became liabilities in a digital market. Your analysis shows how the framework illuminates the case.

Use evidence from the case. Quote the CEO's statements. Reference specific decisions. Show that your analysis is grounded in the case details, not generic application of theory.

Avoid vagueness. "Kodak lacked innovation" is generic. "Kodak's executives dismissed digital photography as a niche market unsuitable for Kodak's business model, leading them to delay investment in digital technology until competitors had already established dominant market positions" is specific analysis grounded in case detail.

Recommendations Grounded in Analysis

Your recommendations follow from your analysis. You're not providing general business advice. You're saying "given this case and this analysis, here's what the organisation should have done differently."

For Kodak, you might recommend "Earlier recognition that digital photography represented a basic business model shift, not a niche technology, would have justified investment in digital imaging regardless of short-term profitability. The company should have treated digital as a careful threat requiring diversification rather than a specialty market separate from core business." This recommendation is grounded in your analysis. It's not "innovate more" (generic). It's "recognise disruptive threats earlier" (specific to the case analysis).

Recommendations should be realistic. They should account for what was knowable at the time. Saying "Kodak should have abandoned film in 1985" ignores that film remained profitable for decades. Saying "Kodak should have invested more substantially in digital imaging even though it didn't understand the market" is more realistic.

Avoiding Common Errors

Error one: purely descriptive accounts with no analysis. You describe Kodak's history, its products, its decline. You've summarised the case. You haven't analysed it. Analysis means applying your framework and explaining how the framework illuminates the case.

Error two: generic framework application disconnected from case detail. You apply SWOT without connecting it to specific decisions or events in the case. You produce a SWOT matrix with nothing grounding it in Kodak's actual experience. Framework application requires dialogue with case detail.

Error three: recommendations disconnected from analysis. You've analysed the case using one framework, but then your recommendations rest on different reasoning. Your analysis emphasises competitive positioning, but your recommendations focus on internal culture change. Your recommendations should follow from your analysis.

Error four: ignoring limitations. Every analysis works with incomplete information. You don't have internal company memos. You don't know what alternatives decision-makers considered. You don't know what decision-makers genuinely believed at the time. Acknowledging these limitations strengthens your analysis. It shows you understand that your analysis is one interpretation of incomplete evidence.

A case study report is applied analysis. You're not describing a case. You're using analytical frameworks to understand why things happened the way they did and what might have been different. This is intellectual work, not summary.

The process of editing and proofreading your dissertation is just as important as the process of writing it, and students who neglect this final stage of the work often find that their mark is lower than it might otherwise have been. Editing involves reviewing your dissertation at the level of argument and structure, checking that each chapter fulfils its purpose, that your argument is logically sequenced, and that the transitions between sections are clear and effective. Proofreading is a more detailed process that focuses on surface-level errors such as spelling mistakes, grammatical errors, inconsistent punctuation, and incorrectly formatted references that can distract your reader and undermine the professionalism of your work. Leaving sufficient time between completing your draft and submitting the final version will allow you to approach the editing and proofreading process with fresh eyes, making it easier to spot errors and inconsistencies that you might otherwise overlook.

Frequently Asked Questions

Q: What if I disagree with the assigned analytical framework? A: Apply it anyway. The assignment specifies the framework you should use. Your job is to apply it competently, not to argue that a different framework would be better. If you believe a different framework is more useful, you might briefly acknowledge this in your limitations section. But your analysis should use the assigned framework.

Q: Can I use multiple frameworks? A: Check your assignment instructions. Some assignments specify one framework. Others invite multiple frameworks or allow you to choose. If you use multiple, apply each systematically and show how different frameworks reveal different aspects of the case.

Q: How do I handle cases that are still developing? A: Analyse what's happened to date. Acknowledge that the case is ongoing. You're analysing the situation as it stands, not predicting future outcomes.