Getting To Maybe

The heart of the book is its patient explanation of where all this ambiguity comes from. Fischl and Paul refuse to treat the perplexing exam question as a trap the professor set to be cruel. Instead they show that legal analysis produces forks in the road by its own nature — that the doubt is baked into the material, not sprinkled on top. They spend real care mapping the recurring situations where the law genuinely can't tell you what happens next, and they give these situations names so a student can recognize them on sight.

Some forks come from the rules themselves. A statute says one thing, a competing rule says another, and the facts sit squarely in the overlap. Sometimes a rule and its own exception both seem to apply. Sometimes the law offers a clear test but the test uses a fuzzy word — reasonable, foreseeable, material — and the whole case turns on how you read that single fuzzy word. Other forks come from the facts. A story can almost always be told two ways, and a lawyer's craft is precisely the ability to arrange the same events into two competing narratives, each honest, each pointing at a different result.

Knowing that ambiguity is the point doesn't yet tell a student what to write. So Fischl and Paul turn to the exam itself — the long, tangled fact pattern that most first-years read too fast and answer too soon. Their advice starts with a discipline that sounds obvious and almost no one follows under time pressure: read what is actually there, and take seriously why every detail is there. Professors, they explain, don't pad. If a fact appears in the hypothetical, it was placed there to do work — to trigger an issue, to muddy one, to let you argue both ways.

The classic mistake is what they call issue-spotting on autopilot: the student sees a keyword, fires off the associated rule, and races on, harvesting issues like a checklist. That earns a few points and misses most of them. The better move is to slow down at each fork and forgo the rush to a verdict. Instead of writing the court will find for the plaintiff, the strong answer writes on the one hand, then on the other hand, then explains what the outcome depends on. The magic words, only half-jokingly, are it depends — followed by a precise account of what it depends on.

Step back from the exam and the book is describing something larger than test strategy. The reason the law exam looks so strange is that it's a faithful miniature of how lawyers actually think, and how the legal system actually operates. In most of life we treat uncertainty as a temporary condition to be cleared away. The law treats it as the permanent working environment. A case only reaches a courtroom because reasonable people disagree about the answer; the easy ones settle or never arise. Litigation is the residue of genuine doubt, and a lawyer's job is to live there professionally.

This reframes what the exam is training. It isn't asking students to memorize law so much as to acquire a tolerance for holding two live possibilities at once without collapsing them prematurely into one. That capacity — to build the strongest case for a position you may not hold, to see the seams in a rule you'd like to be solid, to locate the exact point where a case could tip — is the intellectual muscle the whole profession runs on. Fischl and Paul's exam advice is really an initiation into a mode of thought that clients pay for later.

Return to the student holding the B-minus in October. Fischl and Paul's message to them is not work harder or read more; it's that the exam was asking a question they'd never been trained to answer. The years of right-answer schooling built a fast, confident reflex, and that reflex is precisely what a law exam is designed to catch out. The fix isn't more effort in the old direction. It's a turn toward the doubt — reading every fact as deliberate, naming the fork in front of them, arguing both sides all the way down, and reaching maybe on purpose rather than fleeing it.