Rethink the “systematic” label: a lightweight protocol that fits a case‑study deck
When you first heard “systematic review” you probably pictured a massive journal‑article hunt, a PRISMA flowchart, and weeks of data extraction. That image is accurate for a full‑scale literature synthesis, but it doesn’t have to be the only way to bring rigor to a 10‑minute MBA presentation. The key is to adopt the mindset of a protocol—clear questions, pre‑defined inclusion rules, and a transparent trail—while stripping away the parts that would drown a short case study in paperwork.
Consider a second‑year MBA student who rushed to collect every article about “market entry modes” and ended up with a 30‑page bibliography, half of which was irrelevant. The professor’s comment, “show me how you filtered the evidence,” felt like a rebuke, not a guide. The student’s mistake was treating the “systematic” label as a checklist of tasks rather than a framework for thinking about bias and reproducibility.
The alternative is a “mini‑protocol.” Start by writing a one‑sentence research question that mirrors your case’s strategic dilemma, for example: “What evidence supports a joint‑venture entry for Company X into the Southeast Asian consumer electronics market?” Next, define three concrete criteria that a source must meet to be considered: (1) focuses on joint‑venture entry, (2) published within the last five years, (3) provides quantitative performance outcomes. Anything that fails any of those three rules is dropped before you even read it.
This approach gives you three benefits. First, it forces you to be explicit about why you include a source, which the professor can see at a glance. Second, it caps the amount of reading—if you have 10 pages of notes, you’ll likely end up with 3‑5 high‑quality extracts. Third, it creates a reproducible audit trail: anyone could follow your short checklist and arrive at the same set of evidence.
In practice, the mini‑protocol lives on a single A4 sheet. It contains the question, the inclusion/exclusion rules, and a brief table that logs each source, the reason it was kept, and the key finding you’ll cite. That table becomes the backbone of your slide deck, turning a chaotic pile of notes into a tidy, defensible evidence base.
From chaos to clarity: building the protocol step by step
The first hurdle is to stop treating every paragraph of your 10‑page reading pack as equally valuable. Grab a highlighter and skim each source for the three criteria you set earlier. If a paragraph mentions “joint‑venture” and “market share growth” within the last five years, flag it. Anything else—historical anecdotes, unrelated industries, or purely theoretical discussions—gets a quick “X.” This rapid triage usually reduces the pool to a manageable handful.
Next, record the flagged items in a simple spreadsheet or table. The columns should be: Source, Year, Relevance Score (1‑3), Key Metric, Quote/Note, Inclusion Decision. Below is a template you can copy into any word processor.
| Source | Year | Relevance | Key Metric | Quote/Note | Keep? |
|---|---|---|---|---|---|
| Harvard Business Review, “Joint Ventures in Emerging Markets” | 2022 | 3 | Revenue growth 12 % YoY | “Joint‑venture entry yielded faster market penetration than greenfield” | Yes |
| McKinsey Insights, “Entry Strategies Overview” | 2019 | 2 | Average ROI 8 % | Broad overview, no joint‑venture focus | No |
| Company X Annual Report | 2023 | 3 | Market share 5 % after JV | Direct evidence of success | Yes |
Once the table is populated, rank the retained sources by relevance score. The top two or three become your “core evidence.” Summarize each in a single slide: state the source, the metric, and the implication for your case. For example, “Harvard Business Review (2022) shows joint‑venture entry can deliver 12 % YoY revenue growth in Southeast Asia, suggesting a faster break‑even for Company X.”
Now you have a clear audit trail. If a classmate asks, “Why didn’t you cite the 2018 case study on greenfield entry?” you can point to the inclusion rule (“must be within five years”) and show the row marked “No” in the table. That transparency satisfies the professor’s demand for systematic evaluation without the overhead of a full systematic review.
Finally, run a quick “bias check.” Ask yourself: Did you favor sources that support your preferred strategy? If yes, note the limitation on the final slide. A brief acknowledgment—“Evidence leans toward joint‑venture entry, but greenfield data are limited in the past five years”—demonstrates critical thinking and keeps the presentation honest.
Applying the mini‑protocol across different MBA projects
The same lean protocol works whether you’re analyzing a market entry, a pricing overhaul, or a digital transformation. The only variables that change are the research question and the three inclusion criteria. Below are three common scenarios and how the checklist adapts.
- Pricing strategy case: Question – “What evidence supports value‑based pricing for SaaS products?” Criteria – (1) SaaS focus, (2) pricing model described, (3) post‑implementation revenue impact reported.
- Supply‑chain redesign: Question – “Do near‑shoring initiatives improve lead‑time reliability in the automotive sector?” Criteria – (1) automotive industry, (2) near‑shoring case, (3) quantitative lead‑time data.
- Digital transformation audit: Question – “Which firms achieved >20 % productivity gains after adopting AI‑driven analytics?” Criteria – (1) AI analytics, (2) documented productivity metric, (3) implementation within the last three years.
Notice the pattern: each set of rules is narrow enough to exclude noise but broad enough to capture the most relevant evidence. When you draft the protocol, write the three rules as bullet points on your A4 sheet—this visual cue keeps the team aligned during the literature sift.
To keep the process moving in a group, assign each member one of the three criteria to watch for while reading. After the initial skim, reconvene and merge the flagged items into the master table. This division of labor mirrors the “screening” stage of a formal systematic review but finishes in an hour instead of a week.
One common mistake is to let the protocol become a bureaucratic hurdle. If you find yourself arguing over whether a source meets a criterion, step back and ask: “Would the conclusion change if we included or excluded this piece?” If the answer is no, let it go. The goal is to create a defensible, not exhaustive, evidence set for a concise presentation.
When the day of the presentation arrives, slide one can show the protocol itself—a single slide with the question and three rules. Slide two displays the evidence table (condensed to three rows). The remaining slides focus on analysis and recommendation. Professors love this layout because it makes the logical flow transparent and the work reproducible.
Take the next 15 minutes to draft your one‑sentence question and three inclusion rules. Write them on a sticky note, stick it on your laptop, and use it as a filter while you read. That tiny habit turns a mountain of notes into a clear, systematic argument you can defend in front of the class.