Series: How to Prepare For — Global Examination Performance Edge Articles
Article P010
The case is six pages long.
There are names, dates, numbers, quotations, decisions, complaints, graphs, budgets, constraints and several details that look important.
The student reads the first page.
Then the second.
By the third page, the student has underlined almost everything.
By the fourth, the problem feels larger rather than smaller.
By the fifth, three theories seem relevant.
By the sixth, five different recommendations seem possible.
Then the examination question asks:
“What should the organisation do next, and why?”
This is the defining challenge of the case-study exam.
The answer is not sitting in one sentence waiting to be copied.
The case gives you evidence.
It may also give you noise.
It may contain missing information.
It may contain conflicting incentives.
It may contain symptoms whose underlying cause is elsewhere.
It may contain facts that support more than one interpretation.
The student has to turn all of that into a decision.
A case-study exam therefore tests more than knowledge.
It tests whether knowledge can be selected, applied, constrained by evidence, compared against alternatives and converted into justified action.
This article owns that edge condition.
It follows How to Prepare for a Practical Exam | Make Procedures Reliable Under Observation and connects to How to Prepare for an Essay Exam | Build Arguments You Can Retrieve and Adapt Under Time, How to Prepare for an Open-Book Exam | Retrieval First, Resources Second, How to Prepare for a Multiple-Choice Exam | Discrimination, Elimination and Decision Control and How Exam Questions Work | What the Question Is Really Asking You to Do.
Monash University’s current case-study guidance describes a broadly similar process: understand the task, understand the case, identify key facts and issues, analyse the problems, and—where the task is problem-solving—develop, evaluate and recommend solutions. Its annotated case materials explicitly distinguish analytical case studies from problem-solving case studies and emphasise identifying what happened, why it happened and how relevant theory applies. UNSW’s current teaching guidance likewise describes case studies as authentic assessment environments for practical reasoning, problem-solving and application, with clear learning outcomes and marking criteria.
The common lesson is simple:
A case is not a story to summarise. It is an evidence environment in which you must decide what matters.
The 50-second answer
To prepare for a case-study exam, practise converting messy case information into a structured decision.
- Read the task before reading the case deeply.
- Separate facts from interpretations and assumptions.
- Identify the decision-maker, objective, constraints and time horizon.
- Distinguish symptoms from the underlying problem.
- Use theory only where it helps explain, compare or decide.
- Map stakeholders and conflicting incentives.
- Identify what evidence supports each diagnosis.
- Generate more than one plausible option.
- Evaluate options against explicit criteria.
- Make a recommendation that fits the evidence and constraints.
- State risks, assumptions and what information would change the recommendation.
- Practise under time using unfamiliar cases.
- Review where the first weak link occurred: reading, diagnosis, theory selection, evidence use, option generation, judgement or writing.
The central rule is:
Do not ask only, “What theory applies?” Ask, “What decision does the evidence support?”
Alicia, Tricia and Kai Kai read the same case
The case concerns a growing company.
Customer complaints have risen.
Staff turnover has increased.
Revenue is still growing.
A new competitor has entered the market.
The operations team says the problem is staffing.
The finance team says the problem is cost control.
The sales team says the product is being sold faster than operations can support it.
Alicia starts matching theories.
Leadership theory.
Motivation theory.
Operations management.
Competitive strategy.
She has revised all of them, so all of them feel relevant.
Tricia starts summarising the case chronologically.
She writes two pages of background before deciding what the actual problem is.
Kai Kai starts somewhere else.
She writes:
Decision-maker: management team.
Decision: what should be changed first?
Objective: restore service quality without destroying profitable growth.
Constraint: limited capacity and rising staff turnover.
Evidence: complaint growth, turnover, sales growth, operational overload.
Possible underlying problem: growth has exceeded operating capacity.
Now the theories become tools.
Not destinations.
What this article owns
This article owns case-study examination preparation at the evidence-to-decision layer.
Specifically:
- Task framing: understanding what the case question requires.
- Fact extraction: identifying evidence without underlining everything.
- Problem diagnosis: distinguishing root causes from symptoms.
- Theory selection: choosing concepts by explanatory usefulness.
- Stakeholder analysis: seeing different incentives and consequences.
- Option generation: producing credible alternatives rather than jumping to the first answer.
- Evaluation: comparing options against explicit criteria.
- Recommendation: making a justified decision under constraints.
- Uncertainty: identifying assumptions, missing evidence and sensitivity.
- Execution under time: producing a structured answer before the clock ends.
It does not replace subject-specific frameworks in law, medicine, business, public policy, engineering, education or other domains.
Those disciplines own their specialist standards.
This page supplies the transferable examination architecture.
Case-study exams are not memory dumps
The case may activate a large amount of knowledge.
That does not mean all of it belongs in the answer.
A useful chain is:
Task → Evidence → Diagnosis → Theory → Options → Criteria → Decision → Justification.
Notice where theory sits.
Not first.
Theory is used after the problem is sufficiently framed to know what theoretical tool is needed.
First principle: read the task before getting lost in the case
Monash’s guidance begins by asking students to understand the task and identify instruction verbs before analysing the case deeply.
This matters because different questions require different reading.
Consider the same case.
“Identify the main problem.”
You are diagnosing.
“Evaluate management’s response.”
You are judging an existing decision.
“Recommend what the organisation should do next.”
You are designing and choosing action.
“Explain why the problem occurred.”
You are building causal analysis.
“Compare two possible strategies.”
You are evaluating alternatives.
Same case.
Different evidence priorities.
The task card
Before deep reading, identify:
- command verb;
- decision-maker;
- required output;
- scope;
- time horizon;
- whether recommendation is required;
- whether theory is explicitly required;
- whether calculations or exhibits must be used.
This card becomes the filter for reading.
Second principle: separate case facts from your interpretation
Fact:
Employee turnover rose from 12% to 24%.
Interpretation:
Employees are dissatisfied with management.
That interpretation may be plausible.
It is not identical to the fact.
Other explanations may exist:
- labour-market competition;
- rapid hiring;
- low pay;
- job redesign;
- location;
- seasonal effects;
- management quality.
Strong case analysis keeps evidence and inference distinguishable.
The F-I-A labels
During practice, label statements:
F — Fact.
I — Inference.
A — Assumption.
Example:
F: complaint volume doubled in six months.
I: service quality probably deteriorated.
A: complaint volume accurately represents overall customer experience.
This small discipline prevents interpretation from quietly becoming evidence.
Third principle: identify the decision-maker
Case answers often fail because the recommendation is correct in general but impossible for the person in the case to implement.
Ask:
- Who has authority?
- Who controls budget?
- Who owns the problem?
- Who can actually act?
- Who must approve?
A junior manager cannot recommend a national regulatory change as if they personally control it.
A school principal cannot change national examination policy unilaterally.
A product manager may influence engineering priorities but not rewrite the company’s capital structure alone.
Decision authority constrains recommendations.
The authority test
Before recommending:
Can the named decision-maker actually do this?
If not, rewrite the recommendation as:
- propose;
- escalate;
- pilot;
- request approval;
- coordinate with;
- change within delegated authority.
Fourth principle: identify the objective before judging options
A recommendation cannot be “best” without an objective.
Best for what?
Possible objectives include:
- profit;
- service quality;
- safety;
- learning outcome;
- equity;
- speed;
- risk reduction;
- staff retention;
- market share;
- long-term resilience.
Cases often contain competing objectives.
That is where judgement begins.
The objective hierarchy
Write:
Primary objective: what must improve.
Secondary objective: what should be protected.
Constraint: what cannot be ignored.
Example:
Primary: reduce service failure.
Secondary: preserve growth.
Constraint: limited hiring capacity.
Now options can be judged.
Fifth principle: symptoms are not always the problem
Complaint volume is a symptom.
Staff turnover may be a symptom.
Declining grades may be a symptom.
Budget overrun may be a symptom.
The underlying problem may be:
- capacity mismatch;
- poor incentive design;
- weak process;
- incorrect segmentation;
- unclear accountability;
- bad forecasting;
- inadequate training;
- conflicting goals;
- wrong assumptions.
Case-study exams often reward diagnosis because recommendations aimed only at symptoms may produce temporary improvement without fixing the system.
The five-whys caution
Asking “why?” repeatedly can be useful.
But do not force every case into exactly five layers.
Use causal questioning until the explanation becomes specific enough to test against evidence.
The symptom-to-system chain
Write:
Visible symptom → immediate cause → enabling condition → deeper system problem.
Example:
Late deliveries → production bottleneck → overloaded scheduling → sales growth not matched by capacity planning.
Now the intervention point becomes clearer.
Sixth principle: chronology can reveal causality
Cases often contain events across time.
Build a timeline.
Ask:
- What happened first?
- What changed next?
- Which variable moved before the outcome?
- Which decision preceded deterioration?
- Was the problem already present before the supposed cause?
Chronology does not prove causation.
But it can eliminate impossible causal stories.
The six-line timeline
Do not rewrite the entire case.
Capture only turning points.
| Time | Event | Why it matters |
|---|---|---|
| T1 | New product launched | Demand increases |
| T2 | Sales exceed forecast | Capacity pressure begins |
| T3 | Overtime rises | Operational strain |
| T4 | Turnover rises | Capacity falls further |
| T5 | Complaints rise | Customer impact becomes visible |
Seventh principle: stakeholder maps expose conflicting incentives
Case problems rarely affect everyone equally.
Map:
- decision-maker;
- customer;
- employee;
- owner;
- supplier;
- regulator;
- community;
- competitor;
- student;
- parent;
Use only those relevant to the case.
The stakeholder grid
| Stakeholder | Objective | Power | Risk |
|---|---|---|---|
| Management | Restore performance | High | Cost and execution failure |
| Staff | Manage workload | Medium | Burnout/turnover |
| Customers | Reliable service | Medium | Switch provider |
| Investors | Sustainable growth | High | Margin erosion |
This helps explain why a technically good option may be politically or operationally difficult.
Eighth principle: constraints are not footnotes
Cases are often built around constraint.
The obvious answer may be unavailable because:
- budget is limited;
- time is short;
- staff cannot be hired quickly;
- regulation blocks the action;
- capacity is fixed;
- data is incomplete;
- reputation risk is high;
- stakeholders resist change.
A recommendation that ignores the constraint is not a solution to the case.
The constraint card
Before generating options, list:
- money;
- time;
- authority;
- capacity;
- law/rules;
- skills;
- information;
- stakeholder acceptance.
Strike any that do not apply.
Ninth principle: use theory as a lens, not a label
Weak case answer:
“This case demonstrates Maslow’s hierarchy of needs.”
Then a paragraph explains Maslow.
The case disappears.
Stronger answer:
“Turnover appears related to workload and lack of progression rather than compensation alone. A motivation framework helps distinguish hygiene conditions from growth-related drivers, but the case evidence remains incomplete because no exit-interview data is provided.”
Now theory is doing work.
The theory-function test
Before using a framework, ask:
Does it help me:
- classify;
- explain;
- compare;
- predict;
- evaluate;
- decide?
If not, theory may be decoration.
Tenth principle: not every theory that fits belongs
Case exams often activate many concepts.
Selection matters.
Use the smallest set of theories that explains the important evidence well.
This improves depth and reduces theory dumping.
The one-framework-per-job rule
If one framework explains incentives, use it for incentives.
If another explains process bottlenecks, use it for process.
Do not stack five frameworks around the same paragraph merely to demonstrate revision coverage.
Eleventh principle: the case can disconfirm your favourite theory
Students sometimes choose a theory first and force every fact into it.
Reverse the process.
Ask:
- What evidence fits?
- What evidence does not fit?
- What alternative explanation handles the contradiction better?
A theory earns its place by explanatory power.
The falsification question
Ask:
What fact in the case would make my diagnosis weaker?
If you cannot imagine one, the diagnosis may be unfalsifiable.
Twelfth principle: generate competing diagnoses
Before committing, produce at least two plausible explanations for the central problem.
Example:
Diagnosis A: capacity failure.
Diagnosis B: management failure.
Diagnosis C: product-quality failure.
Then compare against evidence.
The diagnosis matrix
| Evidence | Capacity | Management | Product quality |
|---|---|---|---|
| Sales rose rapidly | Strong support | Neutral | Weak contradiction |
| Overtime increased | Strong support | Possible support | Neutral |
| Complaints rose | Support | Support | Support |
| Returns unchanged | Neutral | Neutral | Weakens product-quality diagnosis |
Now diagnosis is comparative.
Thirteenth principle: absence of evidence is not always evidence of absence
The case may not tell you everything.
If no employee-satisfaction survey is provided, you cannot conclude satisfaction is high.
If no competitor data is provided, you cannot assume competition is irrelevant.
State missing evidence when it affects the decision.
The missing-information question
Ask:
What information would most change my recommendation if I had it?
This identifies decision-sensitive uncertainty.
Fourteenth principle: assumptions should be visible
Some assumptions are unavoidable.
Make them explicit.
Example:
“This recommendation assumes the current complaint data is representative of the broader customer base.”
Now the examiner can see the boundary.
The assumption test
For each major recommendation, ask:
- What must be true for this to work?
- Does the case support that?
- What happens if it is false?
Fifteenth principle: generate options before choosing
Students often jump from diagnosis to one recommendation.
That skips decision-making.
Generate at least two plausible alternatives.
Better: three, if time and task allow.
For example:
- hire additional staff;
- slow customer acquisition temporarily;
- redesign workflow to increase capacity.
Now the recommendation can be compared rather than asserted.
Sixteenth principle: criteria make recommendations defensible
Do not say:
“Option B is best.”
Say:
“Option B is strongest because it improves service fastest while staying within the short-term hiring constraint, although it sacrifices some near-term revenue growth.”
The criteria are visible.
The decision criteria menu
Possible criteria include:
- impact;
- cost;
- speed;
- feasibility;
- risk;
- reversibility;
- stakeholder acceptance;
- equity;
- strategic fit;
- sustainability;
- legal or ethical acceptability.
Use only criteria relevant to the case.
The option matrix
| Option | Impact | Speed | Cost | Feasibility | Main risk |
|---|---|---|---|---|---|
| Hire rapidly | High | Medium | High | Medium | Quality of hires |
| Slow growth | Medium | High | Revenue cost | High | Market opportunity lost |
| Redesign process | High | Medium | Medium | Medium | Implementation failure |
The numbers or labels should reflect the actual evidence, not arbitrary scoring.
Seventeenth principle: recommendation means choice plus rationale
A strong recommendation usually contains:
- Decision: what should be done.
- Reason: why it fits the diagnosis.
- Evidence: what in the case supports it.
- Trade-off: what is sacrificed.
- Risk: what may go wrong.
- Mitigation: how to reduce that risk.
The six-sentence recommendation
For short case answers, practise:
1. I recommend X.
2. The central reason is Y.
3. The case supports this through A and B.
4. This is preferable to C because…
5. The main risk is…
6. Therefore implementation should begin with…
This is not a rigid exam template.
It is a reasoning scaffold.
Eighteenth principle: implementation matters
A recommendation without implementation can be too abstract.
“Improve communication.”
How?
Who?
When?
With what measure?
Better:
“For the next eight weeks, management should introduce a weekly capacity review linking sales forecasts to staffing and production limits, with complaint volume and overtime used as leading indicators.”
Now the recommendation can happen.
The implementation card
State:
- owner;
- first action;
- sequence;
- time horizon;
- resources;
- measure of success;
- review point.
Nineteenth principle: recommendations should include feedback
Case-study decisions are rarely guaranteed.
Build monitoring.
Example:
“Pilot the new scheduling process for one team, track lead time, overtime and complaints for four weeks, then expand only if all three move in the expected direction.”
Now the recommendation contains a learning loop.
Twentieth principle: use leading and lagging indicators
Lagging indicator:
annual profit.
Leading indicator:
capacity utilisation, queue length or early complaint rate.
Case recommendations often improve when you specify what should be watched before final outcomes arrive.
The measure question
Ask:
How will we know quickly whether this recommendation is working?
Twenty-first principle: risk analysis should be specific
Weak:
“There are risks.”
Better:
“If the firm slows sales before fixing operations, competitors may capture customers permanently.”
Specific risk can be mitigated.
The risk chain
Risk → trigger → consequence → mitigation.
Example:
Risk: staff resist new process.
Trigger: workflow imposed without consultation.
Consequence: low adoption.
Mitigation: pilot with frontline staff and incorporate feedback.
Twenty-second principle: sensitivity analysis strengthens judgement
A recommendation may depend on one uncertain assumption.
Ask:
What happens if this assumption changes?
Example:
“If demand growth is temporary, permanent hiring becomes less attractive; process redesign or temporary capacity may be preferable.”
This demonstrates conditional reasoning.
The if-then layer
Write one sentence:
If X is true, choose A; if X is false, reconsider B.
This is especially useful when evidence is incomplete.
Twenty-third principle: do not confuse correlation with diagnosis
Two things changed together.
That is evidence.
It is not automatically causation.
Ask:
- Which changed first?
- Is there a mechanism?
- Is there an alternative explanation?
- Does another case fact contradict it?
This protects case analysis from superficial pattern matching.
Twenty-fourth principle: quantitative evidence should be interpreted, not displayed
If the case includes numbers, use them.
But do not copy tables into prose.
Ask:
- What changed?
- By how much?
- Relative to what baseline?
- Is the change large enough to matter?
- Does it support or challenge the diagnosis?
The ratio test
Raw numbers can mislead.
Complaints rose from 100 to 150.
But customers rose from 1,000 to 2,000.
Complaint count increased.
Complaint rate decreased.
Case-study reasoning often lives in the denominator.
The baseline question
Whenever a number changes, ask:
Compared with what?
Twenty-fifth principle: graphs and exhibits are not appendices
If the case supplies an exhibit, it is usually there for a reason.
Read:
- title;
- axes;
- units;
- legend;
- time period;
- source;
- visible trend;
- outliers.
Then connect the exhibit to the decision.
The exhibit sentence
Practise:
“Exhibit 3 matters because…”
If you cannot complete the sentence, you may not yet know why the exhibit exists.
Twenty-sixth principle: source credibility can be part of the case
Not every statement in a case has equal reliability.
A chief executive defending a failed project may have incentives.
A customer survey may have selection bias.
An internal forecast may be optimistic.
A regulator’s report may use a different objective.
Ask who produced the evidence and why.
The provenance check
For important evidence:
- source;
- incentive;
- method;
- time;
- limitation.
Twenty-seventh principle: conflicting evidence is useful
If one exhibit says customers are satisfied but complaint records are rising, do not choose one and ignore the other.
Ask why they differ.
Possibilities:
- different populations;
- different time periods;
- response bias;
- different definitions;
- one measure is lagging;
- average satisfaction hides a subgroup problem.
Contradiction can be the centre of the case.
Twenty-eighth principle: average performance can hide segment failure
Overall revenue may rise while one product loses money.
Average grade may rise while struggling students fall further behind.
Overall satisfaction may remain high while a high-value customer segment deteriorates.
Disaggregate where the case permits.
The segmentation question
Ask:
Who is experiencing the problem most strongly?
Then:
Does the recommendation need to target that segment rather than the whole system?
Twenty-ninth principle: incentives explain behaviour
Case actors may behave rationally according to local incentives even when the organisation-level outcome is poor.
Sales maximises volume.
Operations minimises disruption.
Finance controls cost.
Each department may succeed locally while the system fails globally.
Look for misaligned incentives.
The local-vs-system test
Ask:
What is each actor rewarded for?
Then:
Could everyone be doing their own job while the overall outcome deteriorates?
Thirtieth principle: cases often contain bottlenecks
More input does not always create more output.
If one stage is constrained, pushing more work into the system can worsen queues.
Identify:
- slowest stage;
- capacity limit;
- queue;
- rework;
- dependency;
- handover failure.
This is especially useful in operations, education, healthcare administration and service cases.
The bottleneck test
Ask:
If we improve every other part but leave this part unchanged, does the outcome improve much?
If no, the bottleneck deserves priority.
Thirty-first principle: distinguish capacity from efficiency
A system may be inefficient.
Or it may simply have insufficient capacity for current demand.
The remedies differ.
Efficiency problem → redesign work.
Capacity problem → add capacity, reduce demand, prioritise or change service level.
Do not diagnose one as the other.
Thirty-second principle: distinguish design failure from execution failure
A strategy may be good but poorly implemented.
Or implementation may be competent but the strategy itself wrong.
Ask:
- Was the plan sensible?
- Were resources adequate?
- Was it executed as intended?
- Did conditions change?
This prevents blaming execution for a flawed design or abandoning a good design because of bad implementation.
Thirty-third principle: distinguish policy from practice
The organisation may have a strong formal policy.
The case may show weak actual behaviour.
Do not assume the existence of a rule proves its implementation.
Look for:
- compliance;
- monitoring;
- incentives;
- enforcement;
- local adaptation.
Thirty-fourth principle: recommendations should match causal depth
If the underlying problem is incentive design, communication training alone may be too shallow.
If the problem is missing capability, a motivational campaign may not solve it.
If the problem is capacity, stricter targets may worsen it.
Match intervention depth to causal depth.
The depth test
Ask:
Does my recommendation act on the cause I claimed was central?
If not, the answer is internally inconsistent.
Thirty-fifth principle: do not recommend everything
A list of eight recommendations can look comprehensive.
It may also show no prioritisation.
Case exams often reward judgement.
Choose.
Sequence.
State what comes first.
The now-next-later structure
Now: stabilise immediate risk.
Next: repair underlying cause.
Later: build durable capability.
This creates prioritisation without pretending one action solves everything instantly.
Thirty-sixth principle: opportunity cost belongs in recommendations
Choosing A means not fully choosing B.
Resources spent on hiring cannot also be spent on automation.
Time spent on curriculum redesign cannot also be spent on another initiative.
Strong recommendations acknowledge what is being postponed or sacrificed.
The opportunity-cost sentence
“The main cost of choosing X is that Y will be delayed, but this is justified because…”
This demonstrates prioritisation.
Thirty-seventh principle: reversibility affects decision quality
When uncertainty is high, reversible options can be valuable.
A pilot can generate information before a full commitment.
Ask:
- Can we test this cheaply?
- Can we reverse it?
- What information would the test produce?
This is especially useful when the case evidence is incomplete.
The pilot question
Can the recommendation be turned into a small experiment before full rollout?
Thirty-eighth principle: ethical constraints are real constraints
A financially attractive recommendation may still be unacceptable.
Cases in business, public policy, education, medicine, law and technology may include ethical trade-offs.
Ask:
- who bears the cost;
- whether consent matters;
- whether rights are affected;
- whether the action is transparent;
- whether vulnerable groups are disproportionately affected;
- whether rules or professional standards apply.
Do not treat ethics as a decorative final paragraph if it changes the decision.
Thirty-ninth principle: legal and regulatory constraints can dominate the case
A recommendation that violates law or mandatory regulation is not feasible merely because it is profitable.
When cases involve regulated domains, use the relevant legal framework supplied by the course or authoritative sources.
This article does not provide legal advice.
Fortieth principle: case-study writing should expose the reasoning path
Do not force the examiner to infer how you moved from evidence to recommendation.
A strong paragraph often has:
Evidence → interpretation → theory → implication → decision relevance.
Example:
“Overtime rose 40% before customer complaints accelerated, suggesting the system had already exceeded comfortable operating capacity. This is consistent with a bottleneck rather than a pure product-quality problem. Therefore the first intervention should reduce load or increase throughput before further demand is added.”
Every sentence moves the decision.
The case paragraph
A practical structure:
- make the analytical claim;
- cite case evidence;
- apply relevant theory or reasoning;
- explain the implication;
- connect to the decision.
Forty-first principle: background should be brief
Monash’s case-study writing guidance explicitly advises keeping the case outline brief before moving into findings, analysis, alternatives and recommendations.
In an exam, time is even tighter.
Do not retell the case.
The examiner already has it.
The summary compression test
Can you state the case problem in three sentences?
1. What changed?
2. What is the central problem?
3. What decision is now required?
If not, the case may still be cognitively uncompressed.
Forty-second principle: the first page may contain less useful evidence than the final exhibit
Do not assume narrative order equals importance.
Some cases bury the most discriminating evidence late.
Use the task to guide weighting.
The second-pass method
Pass 1:
Understand the whole case.
Pass 2:
Return to evidence relevant to the actual question.
This is more efficient than underlining every sentence equally on the first read.
Forty-third principle: annotation should encode function
Instead of highlighting everything, use a small system:
- P — problem evidence;
- C — cause;
- K — constraint;
- S — stakeholder;
- N — number/data;
- R — risk;
- ? — missing/uncertain.
Use any compact notation that helps.
The purpose is retrieval under time.
Forty-fourth principle: rereading should be targeted
After the first read, do not restart from Page 1 automatically.
Ask what evidence the emerging diagnosis still needs.
Then search the case for that evidence.
This turns rereading into investigation.
Forty-fifth principle: case analysis is an argument with evidence
A case recommendation is not just an opinion.
The answer should make a claim and support it.
This is why the case-study exam overlaps with essay exams but remains distinct.
The essay may ask you to argue about a broad topic.
The case anchors the argument inside a bounded evidence set and usually a decision context.
Forty-sixth principle: theory can be correct and still irrelevant
A framework may be accurately described.
If it does not change diagnosis, comparison or recommendation, it may not deserve exam space.
Use the relevance test:
If I remove this theory, does the analysis become weaker?
If not, remove it.
Forty-seventh principle: recommendations should be proportional to evidence
If evidence is weak, recommendation confidence should be lower.
Use phrases such as:
- the case most strongly supports;
- the evidence is consistent with;
- on the available information;
- subject to confirming;
- a pilot is preferable because uncertainty remains.
Do not claim certainty the case does not provide.
Forty-eighth principle: uncertainty is not an excuse to avoid choosing
Case exams often require a decision under incomplete information.
State uncertainty.
Then choose the best-supported action.
Decision-making means acting under bounded uncertainty, not waiting forever for perfect evidence.
Forty-ninth principle: a good recommendation can include a trigger for change
Example:
“Begin with process redesign, but if demand remains above 95% of revised capacity for four consecutive weeks, activate the hiring plan.”
Now the recommendation adapts to evidence.
Fiftieth principle: case readiness is transfer readiness
You cannot memorise the exact case in advance.
You can memorise frameworks.
But the exam tests whether you can map those frameworks onto a new situation.
Therefore case preparation must contain unfamiliar cases.
The seven-pass case method
Pass 1: task
What must I produce?
Pass 2: orientation
Who, what, when, where, objective?
Pass 3: evidence
Which facts are decision-relevant?
Pass 4: diagnosis
What is the real problem and what alternatives exist?
Pass 5: theory
Which concepts help explain or evaluate?
Pass 6: options
What can the decision-maker realistically do?
Pass 7: decision
Which option wins under the case criteria?
Then write.
The 15-minute case drill
Use a short unfamiliar case.
Three minutes:
read task and case.
Three minutes:
write facts, problem, constraint.
Three minutes:
generate three options.
Three minutes:
choose criteria and recommendation.
Three minutes:
write one analytical paragraph.
The 30-minute case drill
5 minutes: orientation and evidence.
5 minutes: diagnosis matrix.
5 minutes: theory selection.
5 minutes: options and criteria.
10 minutes: recommendation and justification.
The one-page case map
Create six boxes:
- Decision.
- Evidence.
- Problem.
- Constraints.
- Options.
- Recommendation.
If the case cannot fit conceptually on one page, you may still be summarising rather than analysing.
The diagnosis-only drill
Read five cases.
Do not write full answers.
For each, write:
- symptom;
- root problem;
- best evidence;
- alternative diagnosis;
- discriminating evidence.
This trains the centre of case reasoning quickly.
The recommendation-only drill
Given a diagnosis, produce:
- three options;
- three criteria;
- one recommendation;
- one trade-off;
- one risk;
- one trigger that would change your recommendation.
The exhibit-only drill
Take a chart or table from a case.
Answer:
- What is the visible pattern?
- What does it support?
- What does it not prove?
- Which decision does it affect?
The theory-selection drill
Given a case problem, list five theories.
Then choose only two.
Explain why the other three are less useful.
This trains disciplined selection.
The counterfactual drill
After forming a recommendation, change one case condition.
Examples:
- budget halves;
- demand growth stops;
- regulation changes;
- staff availability improves;
- customer churn doubles;
- new evidence contradicts the diagnosis.
Does the recommendation survive?
The stakeholder-switch drill
Answer the same case from different decision-makers.
CEO.
Employee.
Regulator.
Customer.
The evidence may remain the same.
The objective and feasible action can change.
The case-study error ledger
| Error | Visible symptom | First weak link | Repair |
|---|---|---|---|
| Retelling | Long background | No decision frame | Task card + 3-sentence compression |
| Theory dump | Many frameworks | No theory-function gate | One-framework-per-job |
| Weak diagnosis | Recommendation treats symptom | Cause not traced | Symptom-to-system chain |
| Unsupported claim | Inference stated as fact | Fact/inference confusion | F-I-A labels |
| One-option answer | No comparison | Alternatives not generated | Three-option drill |
| Generic recommendation | “Improve communication” | No implementation layer | Owner/action/time/measure card |
| Overconfidence | Certain claim from weak data | Uncertainty ignored | Assumption + sensitivity test |
The Green-Amber-Red case dashboard
| Mechanism | Green | Amber | Red |
|---|---|---|---|
| Task reading | Command and output clear | Minor scope misses | Answers the topic, not task |
| Evidence | Facts separated from inference | Some mixing | Assumptions treated as facts |
| Diagnosis | Root problem supported | Plausible but shallow | Symptom only |
| Theory | Selected by function | Some overuse | Framework dumping |
| Options | Several realistic alternatives | Limited comparison | First idea chosen |
| Recommendation | Specific, feasible, justified | Broad | Generic or impossible |
| Uncertainty | Assumptions and risks visible | Some acknowledged | False certainty |
| Time | Finishes with judgement | Rushed close | Analysis incomplete |
Common failure mode 1: summarising the case
Symptom: answer retells events.
Cause: no analytical question guiding reading.
Repair: task card and three-sentence case compression.
Common failure mode 2: theory first
Symptom: student begins with favourite framework.
Cause: revision memory outruns diagnosis.
Repair: evidence and problem before framework selection.
Common failure mode 3: treating correlation as causation
Symptom: two changes are assumed to be causally linked.
Cause: mechanism not tested.
Repair: chronology, alternative explanations, falsification question.
Common failure mode 4: solving the symptom
Symptom: recommendation addresses complaints rather than overloaded capacity.
Cause: shallow diagnosis.
Repair: symptom-to-system chain.
Common failure mode 5: impossible recommendation
Symptom: action exceeds authority or resources.
Cause: decision-maker and constraints ignored.
Repair: authority and constraint cards.
Common failure mode 6: one-option thinking
Symptom: first plausible idea becomes answer.
Cause: alternatives never generated.
Repair: minimum two-option comparison.
Common failure mode 7: no decision criteria
Symptom: “Option A is best” without explanation.
Cause: best not defined.
Repair: impact/cost/speed/feasibility/risk criteria.
Common failure mode 8: evidence dumping
Symptom: many facts with little analysis.
Cause: fact accumulation mistaken for reasoning.
Repair: evidence → interpretation → implication.
Common failure mode 9: unsupported certainty
Symptom: definitive recommendation from ambiguous data.
Cause: assumptions hidden.
Repair: sensitivity and missing-information tests.
Common failure mode 10: generic recommendation
Symptom: “improve training,” “communicate better,” “be more innovative.”
Cause: no implementation architecture.
Repair: owner, action, sequence, measure, review.
Common failure mode 11: ignoring trade-offs
Symptom: recommendation presented as pure gain.
Cause: opportunity cost omitted.
Repair: name cost and why it is acceptable.
Common failure mode 12: no risk mitigation
Symptom: risk listed but not managed.
Cause: evaluation ends at criticism.
Repair: risk → trigger → mitigation.
Common failure mode 13: wrong denominator
Symptom: raw counts misinterpreted.
Cause: no baseline or rate.
Repair: ratio and baseline tests.
Common failure mode 14: stakeholder blindness
Symptom: recommendation works for one group but creates severe cost elsewhere.
Cause: system viewed from one actor only.
Repair: stakeholder grid.
Common failure mode 15: running out of time before recommendation
Symptom: rich analysis, weak conclusion.
Cause: too much reading or theory exposition.
Repair: fixed reading/diagnosis budget and early provisional decision.
Case-study exam preparation for Business
Business cases may require decisions about:
- strategy;
- marketing;
- operations;
- finance;
- human resources;
- leadership;
- innovation;
- growth.
Do not write a chapter summary.
Use case evidence to decide which functional problem matters most.
The business case loop
Objective → Market/operation evidence → Diagnosis → Options → Financial/strategic trade-off → Recommendation.
Case-study exam preparation for Economics
Economics cases may provide:
- inflation data;
- employment;
- growth;
- market structure;
- policy constraints;
- elasticities;
- distributional effects.
Use models only after identifying the mechanism in the case.
State assumptions.
Consider short-run and long-run effects.
Consider winners and losers.
The economics decision structure
Shock → mechanism → model → predicted effects → trade-offs → policy judgement.
Case-study exam preparation for Public Policy
Policy cases often contain multiple objectives:
- effectiveness;
- cost;
- equity;
- administrative feasibility;
- political acceptability;
- legal constraints;
- long-term resilience.
Do not judge policy on one dimension only unless the task tells you to.
The policy grid
Evaluate each option across:
Effectiveness × Efficiency × Equity × Feasibility × Risk.
Adapt to the course framework.
Case-study exam preparation for Education
Education cases may include:
- student outcomes;
- attendance;
- curriculum;
- teacher workload;
- assessment;
- parent expectations;
- resource constraints.
Separate:
learner problem.
teaching problem.
assessment problem.
system problem.
The intervention changes depending on which layer is causal.
Case-study exam preparation for Engineering
Engineering cases may require decisions under:
- cost;
- safety;
- performance;
- reliability;
- maintenance;
- materials;
- schedule;
- regulation.
Use quantitative evidence where possible.
Do not recommend the technically optimal design if it violates the stated constraint.
The engineering trade-off
Performance → safety → cost → manufacturability → reliability → maintainability.
The exact order depends on the case.
Case-study exam preparation for Computing
Computing cases may involve:
- architecture;
- security;
- scalability;
- latency;
- cost;
- data quality;
- privacy;
- technical debt.
Separate the visible incident from the underlying architecture.
A slow application may be caused by database design, network latency, poor caching, workload spikes or client-side rendering.
Do not jump from symptom to favourite technology.
Case-study exam preparation for Law
Legal case questions are discipline-specific and must follow the course’s doctrinal framework.
A common analytical shape may include:
Issue → Rule → Application → Conclusion.
But use the exact method expected by the jurisdiction and course.
Do not import generic business-case recommendation style into a legal problem question.
Case-study exam preparation for Medicine and healthcare education
Clinical and healthcare case assessments are safety-critical and governed by professional standards.
Use official curricula, qualified supervision and authorised clinical reasoning frameworks.
This article does not provide diagnosis or treatment instructions.
The transferable examination principle is only this:
case facts must be separated from assumptions, relevant evidence must be prioritised, and decisions must remain within the required professional standard.
Case-study exam preparation for Humanities
Humanities cases may involve:
- historical actors;
- institutions;
- policy episodes;
- texts;
- social movements;
- cultural conflicts.
The “decision” may be interpretive rather than managerial.
Ask:
- Which explanation best fits the evidence?
- What alternative interpretation exists?
- What context changes the meaning?
- Which source is most reliable?
Case-study exam preparation for Ethics
Ethics cases often contain genuine value conflicts.
Do not merely name a moral theory.
Use it to evaluate:
- duties;
- consequences;
- rights;
- fairness;
- professional obligations;
- stakeholder harm.
Then make the judgement required by the course.
Open-book case-study exams
If resources are allowed, case analysis gains a lookup layer.
Use How to Prepare for an Open-Book Exam | Retrieval First, Resources Second.
The case-specific rule is:
Do not search the textbook for every possible theory.
Diagnose first.
Then retrieve or look up the small set of frameworks that serve the diagnosis.
Closed-book case-study exams
Use How to Prepare for a Closed-Book Exam | Build Knowledge That Survives Without Its Supports.
Case-specific memory should include:
- framework purpose;
- decision criteria;
- common failure patterns;
- question structures;
- core formulas where relevant.
Do not memorise long framework descriptions if you cannot apply them.
Online case-study exams
Use How to Prepare for an Online Exam | Digital Readiness, Attention and Contingency.
Case-specific digital preparation may include:
- navigating exhibits;
- searching permitted PDFs;
- typing tables;
- working across multiple windows;
- submitting structured responses.
Oral case-study exams
Some case exams are interactive.
You may receive a case and then defend a recommendation orally.
Use How to Prepare for an Oral Exam | Thinking Clearly While Speaking Under Pressure.
Prepare to answer:
- Why this diagnosis?
- What evidence supports it?
- Why not the alternative?
- What would change your recommendation?
- What is the main risk?
Timed case-study essays
Use How to Prepare for an Essay Exam for writing architecture.
The case-specific paragraph spine is:
case evidence → analytical claim → framework → implication → judgement.
The 14-day case-study runway
Days 14–12: map the format
Confirm:
- case length;
- question type;
- open/closed book;
- time;
- rubric;
- required frameworks;
- calculation expectations;
- whether recommendation is required.
Days 11–9: framework retrieval
For each major framework, learn:
- what problem it solves;
- what evidence it needs;
- what it cannot explain;
- what decision it informs.
Days 8–7: diagnosis drills
Use short unfamiliar cases.
Find symptoms, root problems, constraints and alternative diagnoses.
Days 6–5: option and recommendation drills
Generate alternatives.
Use criteria.
Write concise recommendations.
Days 4–3: timed cases
Complete representative case responses under real time.
Measure reading, analysis and writing time separately.
Day 2: repair
Identify the repeated first weak link.
Use a fresh case to retest.
Day 1: stabilise
Review framework purposes, decision criteria, common error patterns and one short case map.
Do not memorise full case answers.
The 7-day runway
Day 7: baseline case.
Day 6: theory-function map.
Day 5: diagnosis practice.
Day 4: option matrix practice.
Day 3: timed case.
Day 2: repair and fresh case.
Day 1: compact review.
The 3-day rescue
If little time remains:
- learn the exam format;
- identify the five most important frameworks and their functions;
- complete one full diagnostic case;
- practise problem vs symptom;
- practise options and criteria;
- complete one timed case;
- review the error ledger.
Do not spend three days memorising framework definitions without applying them.
The night before
Use a compact case checklist:
- task verbs;
- fact/inference/assumption;
- decision-maker;
- objective;
- constraints;
- problem vs symptom;
- theory by function;
- options;
- criteria;
- recommendation;
- risk;
- uncertainty.
Then stop.
The morning
Read one small case.
Do not write a full answer.
In five minutes identify:
- decision;
- problem;
- three facts;
- two options;
- one recommendation.
This activates the case-analysis route.
First five minutes of the exam
Read the instructions.
Confirm:
- number of cases;
- number of questions;
- mark weighting;
- time;
- permitted resources;
- required answer format.
The first read
Do not annotate every line.
Find:
- who decides;
- what changed;
- why a decision is needed now;
- what appears constrained.
Then read the evidence more deeply.
The case operating loop
Frame → Extract → Diagnose → Compare → Decide → Defend.
This is the core loop.
If the case feels overwhelming
Shrink it.
Write:
Who?
What decision?
What problem?
What constraint?
What evidence?
Five answers can compress six pages.
If several theories seem relevant
Do not choose by familiarity.
Choose by job.
Which theory best helps you explain the central mechanism?
Which best helps evaluate alternatives?
Use those.
If the evidence conflicts
Do not hide the conflict.
Explain it.
Maybe different data measures different populations.
Maybe one source is biased.
Maybe the system changed over time.
Conflict can strengthen analysis if handled explicitly.
If information is missing
State the missing information only if it matters.
Then proceed with a conditional recommendation.
Example:
“On the available evidence, X is preferable. If customer churn is actually concentrated in the premium segment, however, the priority should shift to Y.”
If you cannot choose between two options
Return to criteria.
Which option better satisfies the primary objective under the constraint?
Then name the trade-off.
If your recommendation sounds generic
Add:
- who;
- what;
- when;
- how;
- measure;
- risk.
Specificity usually improves the answer.
If you are running out of time
Protect:
- diagnosis;
- best evidence;
- recommendation;
- reason;
- trade-off.
Reduce:
- background retelling;
- framework definition;
- secondary examples;
- decorative transitions.
If you have five minutes left
Write the decision.
State why.
State the strongest supporting evidence.
State the main risk.
Do not leave the recommendation implicit.
The final check
Ask:
- Did I answer the task?
- Did I separate fact from assumption?
- Did I identify the real problem?
- Did I use theory rather than merely describe it?
- Did I compare options?
- Is the recommendation feasible?
- Did I use case evidence?
- Did I state trade-offs?
- Did I acknowledge material uncertainty?
- Did I finish with a clear judgement?
The independence test
A student is becoming case-study ready when they can:
- read an unfamiliar case without underlining everything;
- identify the decision-maker and objective;
- separate facts, inferences and assumptions;
- distinguish symptoms from root causes;
- choose theories by function;
- generate multiple feasible options;
- compare options using explicit criteria;
- make a recommendation under uncertainty;
- state trade-offs and risks;
- explain what evidence would change the decision;
- finish within the exam time.
The parent’s role
For school-age learners using case-based assessment, parents can help by asking reasoning questions rather than supplying answers.
Ask:
- What is the real problem?
- Which fact proves that?
- What else could explain it?
- What are two possible solutions?
- Why is one better?
- What might go wrong?
These questions train decision structure.
The tutor’s role
A tutor should diagnose where the case-analysis chain first breaks.
Does the student:
- misread the task;
- miss relevant evidence;
- confuse symptom and cause;
- choose theory too early;
- generate only one option;
- avoid making a judgement;
- write too much background;
- run out of time?
Repair the earliest repeated failure.
The teacher’s role
UNSW’s case-study assessment guidance emphasises that learning outcomes and marking rubrics should make clear how students are expected to analyse and solve problems in context.
Good case teaching therefore gives learners practice in:
- diagnosis;
- evidence selection;
- theory application;
- decision-making;
- reflection on alternatives.
The final case should not be the first time students are asked to think this way.
Research baseline
This article’s general architecture is consistent with current university case-study guidance:
- Monash University — Six steps to approaching a case study: understand the task, understand the case, identify key facts and problems, apply analysis, then develop and evaluate alternatives where the case is problem-solving.
- Monash University — Case study example: identify what happened and why, apply relevant theory, analyse problems, and where required evaluate solutions and make recommendations.
- UNSW — Assessment by Case Studies and Scenarios: case studies support authentic problem-solving and practical reasoning, and assessment criteria should make expected analysis and problem-solving explicit.
Course-specific instructions, disciplinary standards and marking criteria always take priority.
Return to Alicia
Alicia still knows many theories.
But she stops asking which theory she can mention.
She asks which theory resolves an uncertainty in the case.
Her answers become shorter.
They also become more analytical.
Return to Tricia
Tricia stops rewriting the case.
She writes the decision first.
Then the evidence that matters.
Her reading becomes faster because she finally knows what she is looking for.
Return to Kai Kai
Kai Kai reaches a case she has never seen.
The industry is unfamiliar.
The names are unfamiliar.
The numbers are unfamiliar.
But the reasoning pattern is familiar.
Who decides?
What is the objective?
What changed?
What is evidence?
What is assumption?
What is the root problem?
Which theory clarifies it?
What are the options?
What are the criteria?
What should be done?
What could make that decision wrong?
The surface changed.
The reasoning survived.
The deeper lesson
Case-study examinations reveal something central about education.
Knowledge becomes powerful when it can leave its chapter.
A theory learned in Topic 4 must survive contact with a problem that does not announce:
“Use Topic 4.”
A formula must survive a new context.
A framework must survive incomplete evidence.
A student must decide what matters before deciding what to say.
This is why cases are difficult.
They remove labels.
They mix signals.
They force selection.
They ask whether knowledge is portable.
What proper preparation finally means
Proper case-study preparation does not mean memorising dozens of model cases.
It means building a method that survives a new case.
You read the task before drowning in detail.
You separate evidence from interpretation.
You identify who can act.
You define the objective.
You locate constraints.
You distinguish symptoms from causes.
You use theory only where it helps.
You create alternatives.
You compare them.
You choose.
You name the cost.
You name the risk.
You state what would change your mind.
Then you write the answer as evidence-driven judgement rather than case retelling.
Where to go next
If the case includes an extended written response, use How to Prepare for an Essay Exam | Build Arguments You Can Retrieve and Adapt Under Time.
If it is open-book, use How to Prepare for an Open-Book Exam | Retrieval First, Resources Second.
If it is online, use How to Prepare for an Online Exam | Digital Readiness, Attention and Contingency.
If it involves live questioning, use How to Prepare for an Oral Exam | Thinking Clearly While Speaking Under Pressure.
If your main weakness is understanding prompts, use How Exam Questions Work | What the Question Is Really Asking You to Do.
Next in this series: How to Prepare for a New Exam Format | Train the Change Before It Counts.
Final principle
A case-study exam does not reward the student who knows the most facts automatically.
It rewards the student who can decide which facts matter.
So read the task.
Find the evidence.
Separate facts from assumptions.
Diagnose before recommending.
Use theory by function.
Generate alternatives.
Choose criteria.
Make the decision.
State the trade-off.
State the risk.
And practise this until an unfamiliar case no longer feels like an unfamiliar way of thinking.