A quick case is supposed to do a lot in a small space — set up a business situation, connect it to a theory, and give students something to argue about, all in a page or two. Most attempts fall short, and it’s almost always the same reason: the case describes a company instead of posing a decision.

The company-profile trap

It’s an easy trap to fall into. You start with “Company X operates in the Y industry, has Z revenue, and recently…” and before long you’ve written a solid company overview with no actual tension in it. Students read it, nod along, and have nothing to disagree about — because there’s nothing to decide.

A case with a real decision at its center reads differently. It puts a specific person in front of a specific choice, with real constraints and a deadline. Compare:

“TechCorp is a mid-size SaaS company facing increased competition in the CRM space.”

versus

“Priya, TechCorp’s VP of Product, has 72 hours to decide whether to cut the price of their flagship CRM tool by 20% before their board meeting — or risk losing three enterprise clients to a cheaper competitor this quarter.”

The first is background. The second is a case.

Four things every effective quick case needs

1. A named decision-maker. Not “the company” — a person, with a title and a stake in the outcome. Students engage with people making hard calls, not abstract entities.

2. A real deadline. Urgency forces prioritization. A decision with no time pressure invites students to gather infinite information instead of reasoning under constraint, which is closer to how real decisions actually get made.

3. At least two defensible options. If there’s an obviously correct answer, students will find it in thirty seconds and the discussion is over. The best quick cases have two or three paths that each have real costs — one option might protect margin but risk churn, another might protect the relationship but blow the quarter’s numbers.

4. Enough data to reason with, not enough to be certain. Real managers rarely have perfect information. A case that hands students a clean, complete dataset removes the most realistic (and most useful) part of the exercise: deciding despite uncertainty.

A structure that consistently works

  1. Open on the moment of decision, not the company history. Start where the tension is.
  2. Give just enough context — industry, competitors, recent trigger event — to make the dilemma legible.
  3. Name the decision-maker, the choice, and the deadline explicitly.
  4. Provide two or three pieces of illustrative data (a market trend, a customer segment breakdown, a cost comparison) — clearly labeled as illustrative if it’s not sourced from a real report.
  5. End with the decision question, plus two or three supporting questions that force students to apply a specific theory or framework.

The theory should be necessary, not decorative

A common mistake is writing a perfectly good decision case and then bolting on a theory at the end — “now apply Porter’s Five Forces to this.” If the case genuinely requires that framework to reason through, students will reach for it naturally. If it doesn’t, no amount of instruction will make the connection feel real. Build the case around the theory from the start: what does this framework actually help someone see about this decision that isn’t obvious otherwise?