Case Study Structure in Business Management: Diagnostic vs Solution-Focused
A fundamental error frequently observed in undergraduate and postgraduate business assignments is treating a case study as an exercise in storytelling. Many students waste precious word count simply summarising the history of a company, mistakenly believing that a factual recount demonstrates strategic understanding. At the university level, a case study is not a narrative summary; it is a rigorous vehicle for applying academic theory to real-world corporate ambiguity. Whether you are investigating a high-profile corporate collapse or formulating a market entry strategy, your primary objective is to utilise established theoretical frameworks—such as PESTLE, VRIO, or Porter’s Five Forces—to untangle complex commercial problems and justify evidence-based decisions.
Decoding the Brief: Diagnostic vs Solution-Focused Formats
Misinterpreting the assignment brief is one of the most common reasons students fail to achieve upper-tier grades in business management modules. Before you begin applying frameworks or outlining your document, you must determine exactly what the examiner is assessing. UK business schools generally issue one of two distinct case study types. Applying a forward-looking structure to a retrospective brief—or vice versa—will fundamentally derail your argument and result in heavy penalisation.
The Diagnostic Case Study (The 'Why')
A diagnostic case study requires retrospective root cause analysis. In this format, you are typically presented with a historical corporate event—such as the collapse of Thomas Cook, the strategic failure of a merger, or a significant supply chain disruption—and asked to explain exactly why it occurred.
Your primary objective is diagnosis, not necessarily cure. Consequently, the vast majority of your word count must be dedicated to the analytical breakdown. You will use established theoretical frameworks to dissect the company's internal weaknesses, leadership failures, or inability to adapt to macro-environmental shifts. While a brief conclusion might touch on lessons learned, extensive forward-looking recommendations are largely irrelevant to the grading criteria.
The Solution-Focused Case Study (The 'What Next')
Conversely, the solution-focused case study is entirely forward-looking and action-orientated. Heavily favoured by the Harvard Business School teaching model, these cases typically end on a cliffhanger. A corporate protagonist is facing an active dilemma—such as a hostile takeover, a market entry decision, or a pricing war—and you are tasked with deciding what they should do next.
In this format, the analysis of the current situation is merely the foundation. The bulk of your marks are awarded for generating credible, mutually exclusive strategic alternatives, evaluating their respective risks, and decisively justifying one specific action plan.
The Core Architecture: Section-by-Section Guide
While the overall weighting of your word count will shift depending on whether your brief is diagnostic or solution-focused, the underlying skeleton of a professional business case study remains highly consistent. Assessors expect your submission to read less like a traditional university essay and more like a rigorous consultant’s report. Mastering this specific architecture is critical for presenting complex corporate data logically.
-
1. Executive Summary: The Bottom Line
The most frequent mistake students make is treating the Executive Summary like an academic abstract. An abstract is a teaser that previews what the paper will discuss; an Executive Summary is a standalone document designed for a time-poor board of directors. It must explicitly state the core problem, the primary analytical findings, and the final strategic recommendation. If a marker cannot understand your final decision and the financial or operational logic behind it purely by reading this single page, the summary has failed.
-
2. Introduction and Problem Statement
Your examiner already knows the background of the case company—they assigned the brief. Wasting valuable word count summarising the founding history of the organisation is a classic FHEQ Level 4 habit that will severely cap your grade at Level 6 or 7. Instead, your introduction should immediately define the core problem or 'burning platform'. Clearly isolate the specific dilemma the protagonist is facing, outline the scope of your analysis, and state the objective of the report.
-
3. Analysis (Applying Theory)
This is the engine room of the case study, where academic theory intersects with corporate reality. Rather than merely offering your personal opinion on the company's situation, you must use verified frameworks (such as the VRIO framework, PESTLE, or value chain analysis) to diagnose the issue. The key is seamless integration: do not waste words defining what a SWOT analysis is. Assume the examiner knows the theory, and proceed directly to applying it to the evidence provided in the case exhibits.
-
4. Strategic Alternatives and Recommendations
Particularly in a solution-focused case, you cannot simply present one idea and declare it the winner. You must propose two to three mutually exclusive strategic alternatives. Evaluate each option objectively against specific criteria, such as financial feasibility, alignment with core competencies, and macro-environmental risk. Once the alternatives are evaluated, you must make a decisive, single recommendation. Defend this final choice using robust commercial logic derived from your earlier analysis.
-
5. Implementation and Action Plan
At FHEQ Level 7 (and especially within MBA programmes), a theoretically sound recommendation is considered useless if it cannot be executed in the real world. The Implementation section is where distinction-level candidates separate themselves from the rest of the cohort. You must explicitly outline how your recommendation will be deployed. This requires a tangible action plan detailing short-term and long-term timelines (e.g., a Gantt chart or 30-60-90 day plan), estimated budgetary requirements, key performance indicators (KPIs), and a robust risk mitigation strategy.
Architectural Comparison: Diagnostic vs Solution-Focused
Although the table of contents for both assignments might look identical on paper, the physical distribution of your word count and analytical energy must pivot entirely depending on the nature of the brief. Failing to adapt the weight of your sections is a primary reason students miss out on distinction-level marks. If you submit a diagnostic breakdown when the examiner expects a forward-looking action plan, your submission will be penalised for lacking strategic foresight.
The comparison table below illustrates exactly how the focus—and the allocation of your word count—shifts across the core sections of a university-standard case study.
| Section | Diagnostic Format Focus (The 'Why') | Solution-Focused Format Focus (The 'What Next') |
|---|---|---|
| Introduction & Problem Statement | Defines the scope of the historical failure or corporate event. Outlines which specific frameworks will be used to investigate the root cause. | Isolates the active dilemma or immediate decision facing the protagonist (e.g., a hostile takeover or impending market launch). |
| Analysis (Applying Theory) | Primary Word Count Allocation (60–70%) Focuses strictly on identifying the root cause of the failure using academic literature to diagnose operational or strategic mismanagement. | Secondary Word Count Allocation (20–30%) Briefly evaluates current market conditions and internal competencies to establish a baseline before transitioning to decision-making. |
| Strategic Alternatives | Often omitted entirely, or significantly reduced to a brief 'lessons learned' section reflecting on how the failure could have been avoided. | Primary Word Count Allocation (40–50%) Proposes two to three mutually exclusive options, rigorously evaluating the financial and operational risks of each. |
| Implementation & Action Plan | Rarely required unless specifically mandated by the assignment brief, as the event has already concluded. | Crucial for securing FHEQ Level 7 marks. Requires detailed execution mechanics, including timelines (Gantt charts), budgets, and specific KPIs. |
FHEQ Level 6 & 7 Standards: The 'Narrative Trap'
Across FHEQ Level 6 and 7 modules, the most frequent criticism cited in UK external examiner reports is a student falling into the 'Narrative Trap'. This occurs when a candidate reads the provided case brief and uses their limited word count to simply retell the story of the company in chronological order. While accurately acknowledging the facts of the case is a prerequisite, treating the assignment as an exercise in reading comprehension will almost certainly cap your final grade at a low 2:2.
At the advanced undergraduate and postgraduate levels, assessors are not testing your ability to summarise corporate history; they are testing your capacity for strategic diagnosis. A First-Class or Distinction-level submission explicitly stops describing what happened and begins evaluating why it happened. You must actively diagnose the company's behaviour using peer-reviewed literature, demonstrating how specific theoretical concepts—such as market myopia, structural inertia, or core rigidities—explain the events outlined in the brief.