Insights
Written when something in the work turned out to be worth writing down. Usually a mistake we watched somebody make twice.
Software makes a process permanent. Fix it first.
A system encodes whatever process you hand it. If three people describe the approval step differently, you are about to buy one of those descriptions and make it the rule.
A laser safety officer is a program, not a title
Naming an LSO satisfies the box on the form. What the standard is actually asking for is the structure behind the name.
Nobody owns the handoff
Processes rarely fail in the middle of a step. They fail in the gap between two of them, where everyone did their part and the work still sat for a week.
Build the assessment before you build the course
If you cannot write the test, you do not yet know what the training is for. Writing it first is uncomfortable and saves months.
Your SOPs are not the problem. Nobody can find them.
Organizations spend months writing procedures and then store them somewhere nobody looks. The writing is the cheap part.