Nicole Collier (Back to Basics)

 Afraid someone will be threatened by what you bring, or that you're just too qualified for the role. You thought about taking credentials off your resume to get yourself through the door. You worked hard for what you have, and it shows. Present yourself as you are and be proud of what you've accomplished. You're not overqualified, and if someone feels threatened by what you bring, they were never going to let you in anyway.  Shrinking yourself doesn't open doors; it just makes you easier to overlook. The person you want to work for sees your credentials and says, "I want this person on my team." What credentials have you been tempted to take off your resume?

 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?

  Qualified vs Knowledgeable Qualified and knowledgeable get treated like the same word. They're not. Qualified means the paper is in order: the degree, the certification, the years. Knowledgeable means the person actually understands the work, how it runs, where it breaks, what to do when it does. One lives on a resume. The other shows up in the room. So there are two different gaps, and most workplaces hold both at once. People who are qualified on paper and still can't answer the question in front of them. People who know the work cold and were never considered because the paper isn't there. Qualified Isn't Knowledgeable Which one do you see more of where you are: the credential without the understanding, or the understanding without the credential?

  The knowledge penalty The person who knows the most in your department is probably also the most behind. Every question goes to them. Every problem lands on their bench. Every new hire gets pointed in their direction. They're not behind because they're slow. They're behind because they're carrying everyone else's workload on top of their own. We say we value knowledge. We reward it by burying the people who have it. Has anyone else watched their best person drown in being helpful?

  Building Your Leaders Building over demolition You wouldn't demolish a good house because of a hole in the roof. You'd cut out the part of the roof that needs work and rebuild it. Same with leaders: You wouldn't get rid of a good leader because of a weakness. You build up what needs work. Materials: Mentor them. Coach them. Support them. Challenge them. Invest in them. Turn the leader you once considered letting go of into one you can't afford to lose.

  A bad interview doesn't always mean a bad candidate. Some people are excellent at explaining their value in a high-pressure conversation. Others are excellent at doing the job. Some people can do both. But most are stronger at one than the other. You don't interview as often as you work, and speaking to the work and speaking to an interview are two different things. One you practice daily. Then the other you might do once every few years. Interviews reward quick answers, polished stories, and on-demand confidence. The work itself demands patience, judgment, consistency, and abilities you only see over time. So someone can walk out of a room knowing they were better than what they presented. Credentials on paper. Years in the work. None of it showed. That's not being unqualified. That's being bad at a format. If that's ever been you, you're not alone. Everyone has had an interview they couldn't get past. A bad interview can still be a tool. Use the question...

  Admitting a mistake doesn't make you look incompetent. Most people won't own a mistake because they're scared. Scared of looking incompetent. Scared of losing credibility. Scared of losing their job. That fear is real. So they stay silent. They redirect. They blame the team, the timeline, the resources. They build a story where it was never their fault. And they put energy into performing like they're fixing someone else's mistake instead of their own. But owning a mistake doesn't erode trust. It builds it. People would rather work with someone who says, “This was me,” than someone who never admits anything. The one who never admits anything isn't protecting their reputation. They're destroying it. Accountability isn't about blame. It's about saying, “This is mine,” when things go wrong, not just when they go right. Own it. Learn from it. Don't repeat it.

  The Phantom Job post. Some facilities are fully staffed. Every role is filled—every shift covered. Then someone leaves. The position gets posted. The interviews start. Then they stop. The posting stays up like it's alive. The work falls on the people who stayed. At first, they don't mind the extra responsibility because they believe this is temporary. Then the extra work becomes their job. Before long, nobody's talking about that position anymore. Then the posting disappears. The work doesn't. Without refilling these roles, the work gets done, which looks like success, but in reality it's testing how much one department can absorb before it breaks, and the work that was getting done stops getting done.

  Y'all vs. We When you enter a new facility, the first word you reach for tells the room something important. "How do y'all do this here?" Yall. The room hears: You don't see yourself as part of our team. "How do we do this?" We. The room hears: You're already one of us. The word you choose tells the room where you've already placed yourself. Choose the word that puts you on the team.