Write It Like They've Never Seen a Pipette: Inside Our Stranger-Proof Documentation Standard

Every protocol in McKnight Lab carries an invisible deadline. Within two weeks of being written, it must survive contact with a stranger — ideally an undergraduate on their first rotation, someone who has never opened our freezer, never seen our plate reader, and never heard the shorthand we use at the bench. If that person can execute the protocol without asking a question, it passes. If not, it goes back for revision.

We call it the two-week rule, and it began, like most lab policies, as a failure.

The Question That Started It All

Several years ago, a visiting student from a community college in Ohio spent a full afternoon stuck on our RNA extraction protocol. The document had been written by a postdoc who had since moved to a position on the West Coast. It read, in its entirety, 'extract per standard conditions' followed by a buffer recipe with one unlabeled component. The student did everything right: she asked around, checked the notebook archive, even emailed the author. Nothing resolved the ambiguity. The experiment died on the bench.

Her question afterward was disarmingly simple: 'Who is this written for?'

The honest answer was nobody — or rather, the author's future self, in a state of perfect recall that never actually arrives. Protocols written for the person who already knows them are not documentation. They are souvenirs.

Writing for a Stranger Changes the Writing

The two-week rule sounds like a burden, but in practice it functions as a compression test for understanding. To write for someone with no context, you must first reconstruct your own tacit knowledge — the centrifuge speeds you never think about, the precise shade of pink that signals a good lysate, the reason step seven exists at all. Articulating those details is uncomfortable in the moment and invaluable afterward.

We have noticed three concrete effects:

Fewer silent errors. Most bench mistakes are not failures of skill but failures of ambiguity. A protocol that anticipates confusion — 'note: the pellet is nearly invisible at this stage' — prevents the small deviations that compound into unreproducible data.

Faster onboarding. New members historically needed six to eight weeks before running experiments independently. Since adopting the standard, that window has shortened noticeably, because the answers new people need are already on the page rather than trapped in someone's memory.

Mentorship at scale. This is the effect we least expected. A well-written protocol is a form of teaching that persists after the teacher leaves. Every time a first-generation college student or a visiting scholar succeeds using one of our documents, the author's mentorship extends to a person they will never meet.

From Internal Habit to Public Good

Because we publish our methods openly wherever possible, the two-week rule has a second audience: the wider community. A protocol clear enough for a stranger in our lab is clear enough for a stranger at a primarily undergraduate institution without our equipment, our reagents, or our colleagues down the hall. We now include notes on common failure modes, troubleshooting decision trees, and photographs of what results should actually look like — the things we once assumed went without saying.

There is a humility built into this. Writing for a stranger means admitting how much you once didn't know, and how much you still rely on unwritten knowledge. It is easier to write 'standard conditions' and move on. But molecular biology advances on the details everyone assumes someone else will record.

A Standing Invitation

We now route every new protocol through a rotating reviewer — often the newest member of the lab — whose only job is to follow it literally and flag every moment of confusion. Their questions are not interruptions. They are the quality control.

If your lab adopts nothing else from our site, we suggest adopting the question that started ours: who is this written for? If the answer is 'me, three years ago,' it may be time to write it again.