Nicole Collier (Back to Basics)

 Speed isn't Efficient Throughput is how fast work moves through your department, and a bottleneck is any point where that flow stalls. When people constantly work around a broken workflow, it looks like productivity, but it's actually a sign the system is failing the people doing the work. Departments track how much work goes out, but nobody asks whether the process is efficient or just fast.

 What happens after Accreditation The survey found the gaps. You wrote a corrective action plan, the accreditor accepted it, and you had the pass in hand. Then everyone relaxed and went back to business as usual, and the plan that was supposed to become the new standard quietly became a performance window. It was never fixed. It was managed until the surveyor left, then old habits crept back in. A corrective action plan is not a finish line. It is how you are supposed to operate from now on. So here is the open question: when the pressure lifted, did the new plan become your practice, or did the old practices stay?

 Competency is checked once and then forgotten. Competency is often evaluated just once and then ignored. Most organizations check off training in the first year, file the certificate, and rarely revisit it. Then they run annual online training and call it "competency," but clicking through a module isn't the same as watching someone do the work today.  The problem is clear: skills decline over time, systems and regulations change, and individuals may shift roles. A person deemed competent on day one might not be competent by day three hundred, and paperwork won’t indicate this. Competency should not be a one-time event; it requires ongoing assessment. It should reflect actual performance and be re-evaluated as work evolves. Compliance failures are subtle; they happen when everyone assumes the last check still counts. So, if you pulled the competency records for a critical role in your organization today, how old would the most recent one be? 

  It's not one sterilizer going down. It's the whole department. Nothing processed, nothing moving, for hours. Sometimes days. And the room goes quiet in a way sterile processing rooms never are. Everyone standing there, waiting for someone to say what happens next. Nobody does because nobody was ever told what to do or who decides. So the improvising starts. Calls get made. Judgment calls happen with patient instruments on the line. And it works, mostly, which is exactly why nobody ever writes down what actually happened or turns it into a real, safe plan. But a complete system failure doesn't really test the staff. It tests whether a plan existed before the day everything broke. The most basic thing a department can have is a plan for the day everything stops. Who decides? Who gets called? What happens to in-cycle loads? When to stop? When to restart? Some departments have one on paper. Most don't. The ones that don't meet their plan on the worst shift of their ye...

  The Defense Health Agency is exploring outsourcing sterile processing for 21 military hospitals. In January 2025, a steam leak shut down Walter Reed's sterile processing department for two weeks. Nearly 270 procedures were delayed, rescheduled, or sent elsewhere. At Brooke Army Medical Center, instruments with bone fragments, baked-on blood, and hair reached operating rooms. Nineteen surgeons signed a memo. Surgeries were canceled. Now the option on the table is having outside providers take over processing entirely. A department doesn't fail on its own. It gets failed — underfunded, understaffed, unseen — until it breaks. Then the answer is to remove it. Back to Basics: The safest department is the one you resource before it fails, not replace after. If your department broke tomorrow, what would leadership reach for — the investment or the replacement?

  Knowing the Standard Isn't Knowing Why You can recite every standard by heart and still not understand what it's protecting. The people who memorized the rulebook and the people who understand the reasoning behind it look identical right up until something happens that doesn't fit the script. One adapts. One freezes. Knowing the standard tells you what to do. Knowing why tells you what to do when the standard doesn't cover the situation in front of you.  The most valuable person in the room isn't the one who knows the most rules. It's the one who understands what the rules were trying to prevent.  Has a standard ever saved you from something the textbook didn't cover?