Lab protocols get memorized like recipes — step 1, step 2, step 3, in order, recited. That survives until the exam asks a question the recipe can't answer: why this step exists, what breaks without it, what a missing control makes uninterpretable. The recitation knows the order; the exam tests the function. Students who memorized the sequence freeze on the troubleshooting question that follows it.

The study method is function retrieval. For each step, write three things: its purpose, what it's measuring or separating, and the failure if it's omitted. Then run broken-protocol stems — "a classmate skipped step 4, what's now uninterpretable?" The skip-failure is the standard practical-exam item, and it's the one the numbered recipe never prepared: knowing what step 4 does means knowing what its absence breaks.

Why recipe memorization fails

Memorizing the numbered recipe trains recitation — the sequence in order, which is recognition of the list, not understanding of the steps. The exam's lab questions are why and what-if: "why centrifuge before decanting," "what happens if the incubation is shortened." Those questions need the function of each step; the recipe has the order without the function, which is why recipe-memorizers can list all nine steps and still can't say what step 3 protects.

The why-and-what-if questions are retrieval of function — pulling the purpose out of memory, which is a different memory than the sequence. A step you can place in order but can't justify is a step you only half-know, and the practical exam's troubleshooting items expose exactly that half. The broken-protocol stem is the practice version: predicting the failure is the same retrieval the exam demands, with the mess as feedback instead of points lost.

The function-retrieval workflow

For each step, three answers: purpose, target, skip-failure. Purpose — why this step exists in the protocol. Target — what it's measuring, separating, or protecting. Skip-failure — what specifically breaks or becomes uninterpretable without it. The three together convert a numbered step into a function, which is the form the exam asks for.

Chunk long protocols by phase, not step. A 20-step protocol is usually four purposes — extract, purify, amplify, read — with steps that share each job. Learn the phase purposes first, then which step inside each phase does the protecting. Four phases is a learnable structure; twenty disconnected steps is a list that collapses under exam pressure.

Then run broken-protocol stems. "Someone skipped the negative control — what's now uninterpretable?" "The wash step was doubled by accident — what changes?" Each stem is a prediction of the mess, which is the troubleshooting skill the practical exam grades. The recipe can't answer these; the function map can, because the failure is just the step's purpose read backwards.

Work backwards from the data. Take the results table and ask which step made each column possible — the standard curve column exists because of the dilution series, the blank column because of the control. The backwards pass is the second retrieval direction, and it catches the steps you know forwards but can't connect to their output.

A 40-minute session on the clock

The weak answer senses a problem but can't name it — "might not work as well" is a vibe about quality, not a prediction about interpretability. The strong answer names the exact failure: a band can't be trusted because contamination is indistinguishable from amplification without the no-template control. The control's purpose — ruling out the false positive — is what its absence destroys, which is the reasoning the exam's troubleshooting item is scoring.

Why watching the demo doesn't count

Watching the TA run the protocol is exposure — the steps happen in front of you, correctly, with the reasoning narrated over them. It feels like learning the method because the method is visible; it's spectatorship because nothing is demanded back. The practical exam doesn't ask you to watch; it asks you to predict what breaks, and prediction only comes from having generated failures yourself.

The broken-protocol stem is the generation the demo skips. Every "what if step 4 were skipped" is a failure you produced and reasoned through — the same operation the exam runs when it hands you a botched procedure and asks what went wrong. The student who's only watched has seen the protocol work; the one who's broken it on paper knows why it works, which is the knowledge the troubleshooting item actually tests.