Every project I have taken on starts the same way.

Someone needs a checklist.

Cool. I can do a checklist.

Except when I actually look at what is going on, it was never really about the checklist. That is just what you ask for when you do not have time to diagnose what is actually broken. And what is actually broken is always something nobody wrote down, nobody owns, and everyone has been quietly working around for longer than they want to admit.

I find it anyway.

Not because I am trying to create more work for myself. Because I genuinely cannot walk past a gap. It is a blessing and a curse and my calendar reflects both.

What starts as a simple ask becomes a curriculum. A framework becomes a governance model. “Can you just put together a quick training” becomes a nine-phase onboarding architecture that gets presented to the COO.

I do not overscope work. I scope it correctly the first time.

The difference is that I am actually looking at what is broken rather than just executing what was requested. If you have ever handed someone a simple ask and gotten back something that solved three problems you did not know you had. You already know what working with me looks like.

Bad QA scores do not mean you have a QA problem.

They mean you have a training problem. A coaching problem. A documentation problem. An expectations problem. A leadership visibility problem. Possibly all five at once and nobody has connected the dots yet.

I have seen QA used as a gotcha tool. A paper trail. A checkbox that gets filed and forgotten. Evaluations completed not because anyone intends to do anything with the data, but because someone somewhere decided the number needed to exist.

That is not quality assurance. That is compliance theater with a scorecard attached.

Here is what QA is actually supposed to do: tell you the truth. It tells you whether your training is landing. Whether your coaching is working. Whether your team has what they need to succeed. Whether the expectations you think you communicated were actually understood. Whether the gap is a skill issue, a knowledge issue, a process issue, or something leadership created and the frontline is absorbing.

When I built QA frameworks, the score was never the point. The score was the signal. What you do with it is the work.

If your QA program is producing data and nothing is changing, the program is not the problem. The culture around accountability is the problem. And that one goes all the way to the top.

Fix the system. Coach the person. Lead with the data. In that order.

QA done right does not feel punitive. It feels like someone finally gave the team a mirror and said: here is where you are, here is where we are going, and here is what support looks like on the way there.

That is the version worth building.

I have inherited teams that were holding themselves together through sheer loyalty to each other.

Not to the company. Not to leadership. To each other. Because somewhere along the way, leadership had checked out. One-on-ones got cancelled. Meetings became optional. Real work quietly shifted to whoever would absorb it. And the team normalized it because they had no other choice.

When I stepped in, I never did anything extraordinary. I just did the job.

I kept the one-on-ones. I learned names. Kids names. Dogs names. The small details people share when they finally feel safe enough to share them. I looked at whoever had been carrying too much and coached them back to what their role was actually supposed to look like.

Every single time, someone on that team eventually said some version of the same thing: that I had done more for them in a short time than they had experienced in years.

That is not a compliment to me. That is an indictment of what happens when people are treated like a function instead of a priority.

Here is what I know after years of watching teams succeed and watching them quietly fall apart:

People do not underperform because they are lazy. They underperform because expectations were never clear. Because their questions went unanswered. Because they asked for help once, felt invisible, and stopped asking. Because the system around them was broken and they were absorbing the cost of it.

Cancelling the team huddle does not fix your metrics. It tells your team that their time together, their morale, and their connection to each other are expendable. And people remember that long after the quarter ends.

You cannot metric your way out of a culture problem. You cannot work people harder through a system failure. And you cannot lead from a distance and wonder why nobody is following.

My team spends 40+ hours a week with me. That is 40 hours they could have spent with their families. So if someone reports to me, I am going to make sure they do not feel like that time was wasted. That the time they sacrificed meant something.