Every laboratory eventually loses the person who knew how a method really worked. The difference between a minor inconvenience and a lost method is decided long before that person leaves.
Assume the next operator is competent but new
A method document should let a capable scientist who has never touched the instrument run the method without a phone call. If it needs an explanation to be useful, it is a note, not a method.
Write the exceptions down
The steps that always go slightly wrong are the most valuable lines in a protocol. We keep a short section per method titled 'known quirks', updated whenever someone solves a recurring problem.
Make handover an event with a date
Shadowing for a week beats a document plus good intentions. We schedule a formal handover: the outgoing operator observes, then the incoming one runs the method while being observed and corrected.
Review the method library annually
Methods decay. Instruments are serviced, suppliers change, software is updated. Once a year we review each method against current practice and record what changed, even when nothing did.
In practice
- Write for a competent newcomer
- Keep a 'known quirks' section per method
- Schedule a two-sided handover
- Review the method library annually
A method that cannot be handed over is not a method. It is a person.
Illustrative article written for this template.
Tell us the question. We will scope the study.
Send a short description of your material, method and deadline. You will get a written response from a scientist, not a sales sequence.