Issue-spotting, reading comprehension, and speed feel like skills you can drill. The cognitive research says they are side effects of knowing enough, and that practice attempted before knowledge is not practice at all. ECHO outlining is the schema-building that has to come first.
The intuitive study plan is to read, then practice. Do enough hypos and the analysis gets better. Meyer and Noël argue that this reverses the actual dependency: analytical ability in a complex domain is downstream of knowledge in that domain, not a transferable skill that practice sharpens.
Their point is that a learner without enough stored law doesn't get a weak version of practice — they get a failed one. Facts don't signal anything. Nothing connects to anything. Working memory saturates just holding the fact pattern in mind, leaving nothing for reasoning. The hypo gets completed, an answer explanation gets read, and it feels like progress, but the thing that would have made the reasoning possible never got built.
They surveyed 358 first-year students at New England Law | Boston about study habits and compared answers against first-term GPA. Directions and significance below; p under .05 is the conventional threshold.
Two of these are worth sitting with. Practice problems showed no relationship to GPA at all — though students reporting moderate use did best, which fits the argument that a little practice on top of real knowledge is fine and a lot of practice instead of knowledge is waste. And outlines you didn't write were associated with worse outcomes, whether written by a classmate or by a commercial publisher. The authors' reading is that anything relieving you of the synthesis is relieving you of the learning.
They're careful about what this is: program evaluation at one school, self-reported study habits, not a controlled study. They say so explicitly. Treat it as a strong reason to try the method, not as proof.
Every term of art defined. Court reasoning that explains why the rule means what it means. The purpose underneath it. Meaning is what makes knowledge stick and what lets you chunk it under pressure.
Case facts filed underneath the rule they illustrate — not a stack of briefs at the end. You spot issues by recognizing problem shapes you've seen before, so the shapes have to be stored where the rule lives.
Organized by topic, with subtopics nested underneath, descending through levels of abstraction. Not by class date. Not by case name — that ranked barely better than not outlining at all.
Arranged as an ordered sequence of inquiries, so the outline is a procedure you run on new facts rather than a description you read. You write the exam answer's skeleton months early.
Common law battery, outlined at three depths. Watch what happens to the indentation.
Outline a topic once it's been discussed in class, running a week behind if you need to. Build it in the workshop tab — the structure there won't let a case float free of the rule it belongs to, and it asks for the ordered inquiry at the end so the topic ends up executable.
Then encode it. Not with flashcards, which the authors argue retrieve items in isolation and don't strengthen the connections around them. Instead, take a whole topic and explain the entire thing out loud or on paper from memory — every element, definition, reason, case, and step — then open the outline and mark what you missed. The retrieval tab runs that.
Then, and only then, practise. The survey’s best results came from moderate practice on top of real knowledge, so treat problems as a test of an outline rather than a substitute for one. Once a topic survives a cold retrieval, run it against new facts: the practice lab, which has files on torts, contracts, and property, and on the foundations: precedent, authority, jurisdiction, motions, appeals, and preemption. If a file stalls because you can’t say what the rule is, that is the signal to go back to the outline, not to do more files.
Everything above is Meyer and Noël’s method as I understand it. What follows is mine: additions that grew out of building practice tools around the method. They are labelled here, and in the workshop, so the two can be judged separately. If an addition works against their argument, their argument wins.
Each topic in the workshop can record what it gets confused with and the one question that tells them apart: dismissal or summary judgment? becomes what is the judge allowed to look at? This is elaboration aimed at the errors that actually cost marks, because most confusions that survive into an exam answer are two concepts that each feel familiar on their own. Asked first, the splitting question is often the first step of the ordered inquiry.
Retrieval now records how much of the topic you reconstructed and schedules the next cold explanation after 1, 3, 7, then 21 days. Topics that come due are flagged in the picker. The schedule is a working heuristic, not an interval the spacing research has shown to be optimal.
The practice lab can read the outlines you build here, on this device only. Each file lets you set your own outline of the topic beside the supplied rule pack, and ends by asking whether your outline would have got you there. A “no” sends you back here rather than to another file, which is the paper’s argument turned into a routing rule.
The survey’s most uncomfortable finding is that outlines you didn’t write were associated with worse results. This site now contains a lot of synthesis I wrote: a glossary, a doctrine reference, frames for telling look-alike procedures apart. By the paper’s logic, those help as a check against your own outline and hurt as a replacement for it. Build first, then compare.
Build a topic in the workshop first. Then come here, pick it, and reconstruct it cold. When you're done you'll get your own structure back as a checklist to mark against.
Topic, rule, components with their meaning and cases nested beneath, then the ordered inquiry.