Business subjects · Research methods

Preparing a Business Research Case Study

When your module treats the case study as a research method — not just an assignment format — preparation matters more than prose. This page walks you from research question to case selection, data collection plan and write-up, with a free design picker and an honest list of the traps that cost marks.

3design archetypes
6evidence sources covered
5preparation steps

What makes a research case study different

In a research methods module, the business research case study is a study design, not a story. You are being examined on decisions: what is your unit of analysis, why this case, which evidence, how does it all link back to the research question? Robert Yin's Case Study Research — the text most course outlines reference — frames the method around three broad purposes you can describe without misquoting anyone:

  • Exploratory — the phenomenon is new or poorly understood, so the case helps you define questions and propositions for later work.
  • Descriptive — you document a situation completely within its real-life context: what happens, who does what, in what sequence.
  • Explanatory — you test how and why outcomes occurred, matching the evidence against competing explanations.

Your marker will also expect you to defend case selection. A single case is justified when it is critical, unusual, typical, revelatory, or longitudinal in Yin's sense — not simply because the company down the road said yes. A multiple-case design borrows replication logic: each extra case is treated like a fresh experiment that either supports the pattern or forces you to revise it. Neither choice is "more scientific"; each fits a different question, which is exactly what the picker below helps you sort out.

Free tool: the research design picker

Answer three questions about your assignment and access. You'll get a suggested design, a paragraph you can adapt for your methodology section, and the risks to plan for. Everything runs in your browser.

Research Design Picker

100% private — runs in your browser

1. What is your study trying to do?

2. What data access do you realistically have?

3. How long have you got for fieldwork?

Your suggested design, methodology paragraph and risk list appear here.

The picker proposes a starting point — your module handbook and supervisor's guidance always win if they disagree.

Five steps to prepare your case study

  1. Write the research question before anything else. "How does the loyalty scheme at StoreCo affect repeat visits?" (illustrative) beats "I want to study marketing". A weak question can't be fixed by good writing later; draft alternatives and sharpen them with the thesis statement generator until one is specific, answerable and worth answering.
  2. Define the unit of analysis. Is the case one shop, one chain, one campaign, one decision? Everything you collect must sit inside that boundary — it's the discipline that keeps a research case study from becoming a general essay about the industry.
  3. Choose and justify the case. One site or several, and why this one. Write two sentences of justification now; they'll become the most-quoted part of your methodology section.
  4. Plan data collection against the question. For each source below, note what it can tell you, who grants access, and how long it takes. If a source can't answer part of your question, that's fine — note the limitation honestly.
  5. Build the chain of evidence. Number your documents, transcribe interviews as you go, keep a contact log. The write-up then traces every claim back to a named source, which is what markers mean by "rigour".

Six sources of evidence — tap to flip

Yin's standard list is a safe menu for a business research case study. Flip each card for what it's good for and what it costs you.

01

Interviews

Targeted, open-ended

Best for motives, sequences and "why" questions. Costs: scheduling, transcription time, and interviewees who tell you the official story instead of the real one.

02

Documents

Reports, emails, minutes

Stable and reviewable — you can re-read without bothering anyone. Weakness: written for other audiences, so they can mislead. Always ask who wrote this, and for whom.

03

Archival records

Sales logs, service tickets

Quantitative backbone for your narrative. Check what the record counts and what it silently omits — a ticket system shows complaints that got logged, not those that didn't.

04

Observation

Watching work happen

Catches what people no longer notice, like workarounds and dead processes. Costs time on site, and your presence itself can change behaviour — note it.

05

Physical artifacts

Tools, outputs, signage

A device, a packed box, a shelf layout — artifacts ground claims in the physical world. Photograph (with permission) and ask what each one is used for.

06

Participant observation

You inside the work

Deepest access, highest cost. If you already work in the organisation, declare it — your dual role is a strength for access and a risk for bias, and markers reward students who say so.

Worked mini-outline (illustrative)

Imagine a 3,000-word research case study on whether a corner-shop chain's new loyalty scheme changed repeat visits. The study below is illustrative throughout — swap in your own organisation and question.

1. Introduction
   Question: how did the StoreCo loyalty scheme change repeat visits at two
   branches? (Illustrative setting.) Design: descriptive, multiple-case.
2. Case selection and unit of analysis
   Two branches of one chain, chosen for contrast: high street vs retail park.
   Unit of analysis: the branch-level scheme rollout.
3. Data collection
   Six staff interviews per branch; six months of loyalty-card sign-up records;
   store documents (briefs, posters); two observation afternoons per branch.
4. Findings
   Branch A: sign-ups high, repeat visits flat. Branch B: slower sign-ups,
   visits up. Present as a comparative table, then explain the contrast.
5. Discussion
   Match findings to the scheme's design; consider rival explanations
   (location, seasonality) before crediting the scheme.
6. Conclusion and limitations
   Two branches, one chain: no generalisation beyond the case. Say what a
   wider study would need.

Preparation pitfalls that cost marks

Markers of research-methods case studies read hundreds of designs a year. These are the ones that sink:

  • Question drift. The study starts on loyalty schemes and drifts into staff morale. Hold every paragraph against the question; if it doesn't serve it, cut it.
  • Access optimism. Planning eight interviews when your only contact is one busy manager sets you up to fail. Build the plan around your real access, and say what you'd do with more.
  • Single-source stories. If everything you claim traces to one enthusiastic interviewee, triangulate — pair the interview with a document or a record — or label the claim as one person's view.
  • Ethics as an afterthought. Consent, anonymity and data storage belong in the plan, not a late paragraph. Most universities block fieldwork without a cleared ethics form; assume yours is one of them.
  • Generalising too far. A case study generalises to theory, not to populations. "This shows what can happen when…" is safe; "all retailers therefore…" is not.

Once fieldwork ends, the write-up takes over. Keep drafts lean with the word counter, tidy your prose with the readability checker, and format sources as you go with the APA citation generator — retrofitting references at 2 a.m. is where errors breed. If your rubric wants annotated sources, the bibliography generator builds summary-plus-evaluation entries in the accepted three-part shape.

Method-match quiz

Three quick scenarios. Choose the design a methods marker would expect.

1. Nobody has studied how food-truck owners pick locations in your city. You can follow two owners for a month. Best fit?

2. You want to explain why two identical cafés adopted the same policy with opposite results. Both managers will talk. Design?

3. Your entire dataset is 10 years of published annual reports. What must your limitations section own up to?

Stuck on the methodology section?

If your design paragraph keeps reading like a wish list rather than a plan, hand the brief to a quoted, deadline-bound writer — research design, sourcing and structure included. Tell us the question, the access you have and the deadline.

Frequently asked questions

How many interviews does a case study need?+

Enough to answer the question, which is an unsatisfying but honest answer. In practice, undergraduate projects commonly run six to twelve across one or two sites; what matters more is coverage — different roles, levels and, where relevant, people who disagreed. Say in your limitations who you couldn't reach.

Is one case "enough" for a dissertation?+

Usually yes, provided it is justified — critical, unusual, typical or revelatory — and your question matches a single-case design. A single case defended well beats two cases defended badly. If your supervisor pushes for comparison, a second case can be added late in the design only if access genuinely exists.

Do I need a hypothesis in a case study?+

Explanatory designs usually state propositions — tentative answers your evidence will confront. Descriptive and exploratory designs can work with research questions alone. Follow your module's template; when it's silent, propositions for explanatory work and questions for the rest is the safe default.

How do I keep interviews anonymous?+

Assign codes (P1, P2…), store the key separately from transcripts, and remove identifying details from quotes. In small organisations, job titles can identify people even without names — so consider "a senior operations respondent" instead of "the operations director", and agree the approach before you promise it.

Can I write the case study about my own employer?+

Often yes, and access is a real advantage — but declare the dual role, get permission in writing for any company documents, and discuss bias controls with your supervisor: a second coder on a sample of transcripts, or a colleague reviewing your interpretations, goes a long way.

What's the difference between a research case study and a teaching case?+

A research case study reports a study you conducted, with methodology and findings. A teaching case is a discussion prompt built for a classroom, deliberately open-ended and usually fictionalised — our Harvard Business School case study format page covers that genre. Don't mix the two voices in one assignment.

Did this help you prepare?