These are the operating rules I run on. They are not original. They are the ones that survived contact with running real operations, real teams, and real budgets for long enough that I stopped second-guessing them.
Dashboards are downstream. The fastest way to know how an operation is doing is to be in it, often enough that the team stops pretending when you show up.
Every time you intervene one layer down, you teach the manager that you'll do their job. The harder move, and the only one that scales, is to coach them through it. Especially when you could solve it faster yourself.
Anyone can run a team when the truck shows up. The actual test is the Friday afternoon when the truck is down and two people called in sick. Watch your managers on that Friday. The ones who get quiet and calm: those are the ones you promote.
A utilization drop is fourteen different things. The number tells you something is happening. It doesn't tell you what. The discipline is to go ask the manager closest to the work.
Hit the daily basics. Pre-shift huddles. Customer touch points. Closeout. The team that does the basics consistently for a year will outperform the team running ten experiments. The margin compounds.
If your people have to "use AI," you've failed. If they fill out the inspection like always, but it's faster, you've won. Stop telling teams which parts of the workflow are AI-powered. They care that the work is easier than it was last week. The rest is plumbing.
The temptation when you're the technology person is to design what's possible. The discipline is to design what's wanted. You only learn the difference by sitting next to someone who does the work and watching them flinch.
Different people need different things to do their job well. The leader who imposes one style on everyone is solving a problem they invented.