Did You Read the SOP? Procedure Writing for the Laboratory
summary
Claim: well written SOPs cut troubleshooting time and make rare or complex tasks repeatable after a machine upgrade. Evidence: a departmental survey finds less than 10% time spent on docs and 80% find flowcharts helpful but only 30% use them, and a 50/50 split on whether people read all SOPs. Work done: new procedures and quick references are written for an Emylite 2000 replacement, a worklist and troubleshooting logs are created and iterated, and repeated revisions produce usable workflows that actually speed up go‑live.
AI-written summary · about
chapters (10)
- 0:00Introduction to laboratory documentation
- 1:08Why procedure writing matters
- 2:56Clarity, conciseness, accuracy
- 5:02SOPs: lab's backbone
- 15:39Story time the death of an analyzer
- 19:31Helping non-writers write
- 23:52Process mapping before writing
- 26:44Editing and testing procedures
- 30:55Culture of good docs
- 33:26Q&A
related talks
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
43mThe 7 Deadly Sins of Documentation
44mCreating a Culture of Documentation
30mTechnical Documentation
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
29mTaking Stock of Your Documentation
20mDo Docs Better: Practical Tips on Delivering...
01h 24mWriting Documentation - Practices and Theory