Keeping your finger on the pulse without micromanaging.
Have you watched "Flamin' Hot"? There's a scene in it I love. Clarence, the factory engineer, takes Richard up to the catwalk and tells him to stand right there and listen. Then, without moving, without inspecting anything, he calls out a loose gasket just from the sound of the factory. He can tell which machine, belt, drum, valve, or motor is off, just by listening.
Watching that scene, I had an uncomfortable realization. I used to do this. I used to have my finger on the pulse of everything. I could tell when something was off just from the vibe in Slack or the tone of an email. And somewhere along the way, I stopped.
Maybe it was because we grew. Maybe I got busy with other things. Maybe I started trusting that everything was fine until someone told me otherwise. But Clarence reminded me that keeping an ear out isn't about not trusting your team. It's about maintaining the health of the whole system.
So this is partly me reminding myself to get back to it, and partly sharing what used to work really well, in case it helps you too.
What I used to do, and need to start doing again
I had a practice I called pulse checks. Not inspecting every piece of work, not micromanaging, just listening for the hum. Here is what it looked like when I was actually doing it.
Monday mornings, I'd spend about fifteen minutes pulling up random emails from my team. Four or five, from different people, at different times. Not to critique, just to feel the tone. Were they energized? Frustrated? Was the quality holding?
Midweek, I'd spot-check a few deliverables. Whatever the team had produced, reports, processes, the actual work. Just enough to know if standards were holding.
End of week, I'd look at how they were interacting with other teams. Were the same issues coming up? Was collaboration smooth?
The whole thing took maybe fifteen minutes per person per week. And it worked. I caught things early. I celebrated wins that would have gone unnoticed. I helped people before small issues became big ones.
Then I stopped. Not on purpose. It just fell off my plate.
Why I stopped, and why that was a mistake
I think I told myself my team was experienced enough that they didn't need it. Or that they'd come to me if there were problems. Or that I had bigger things to focus on.
But watching Clarence on that catwalk, I realized something. He wasn't up there because he didn't trust his machines. He was up there because that's how you prevent catastrophes. You listen for the small changes before they become big failures.
The same is true with teams. By the time someone comes to you with a problem, it's already a problem. By the time you notice quality slipping, it has already slipped. By the time someone burns out, they're already burnt.
What I learned when I was actually doing this
When I was consistent with pulse checks, the patterns were obvious. One sloppy email is nothing, we all have off days. Three sloppy emails in a week is a conversation. Someone going from full paragraphs to one-line replies means something is wrong. Consistently great work that keeps getting sharper means it's time to recognize it, out loud.
The best part was that my team appreciated it. Not the checking-up part, the noticing part. Noticing when they handled something beautifully. Noticing when they were struggling before it got bad. Noticing the small improvements they were making.
Trust isn't about whether you check in. Trust is about what you do with what you find.
The simple framework
Pick your signals. What would tell you if your team is thriving or struggling? For me it's communication quality, work standards, and how they work with other teams.
Sample regularly. You don't need to review everything. You need to sample consistently. Same time, every week, no exceptions.
Act on patterns. One instance is nothing. Patterns are everything. Good ones get celebrated. Concerning ones get addressed before they grow.
The honest truth
When I was doing this, I was a better leader. I caught things early. I recognized good work that would have gone unnoticed. I had real conversations about small issues before they became big ones. When I stopped, I told myself it was because I trusted my team. But you can't find anything if you're not listening.
So here is what I'm doing. I'm going back to my pulse checks. Fifteen minutes per direct report per week. No exceptions. Not because I don't trust my team, but because I want to hear when something is off before it breaks. If you used to do something like this and stopped, maybe this is your reminder too. If you've never done it, maybe it's worth trying.