A technician finishes the day knowing exactly what he did. Twelve gages, four hours onsite, one certificate. Visible.

I finish the day having sat at a computer. From the outside that looks like nothing — and if I don't fix that, it turns into resentment. The guy in the van thinks the owner stopped working.

They see me approve estimates, chase invoices, sign certificates. What they don't see is the module I'm rebuilding so their training stops living in a spreadsheet. Or the compliance mapping that decides whether an audit is survivable. Or why hiring is taking as long as it is.

I want them to know I'm in it with them. Not because I said so in a meeting — because they can watch it happen.

So I built a weekly note. Three priorities Monday, a full recap Friday. Simple enough that I'd been not doing it for a year.

The first draft the system produced was wrong, and the way it was wrong is the useful part. I'd told it to rank by consequence and urgency. It came back with:

Clear the invoicing backlog — 20 work orders, two invoices sitting in QuickBooks unsent
Cover this week's onsites — 8 jobs, no technician assigned
33 units tested and still sitting in the lab since July 14

All three are true. All three matter. And it would have been exactly the wrong message — a list of the administrative work they've watched me do for years.

So I changed the rule. The three slots are reserved for what I'm personally driving to make this place better. Everything else — invoices, estimates, the customer problem I'm still working — goes in a short punch list at the bottom. Outlined, not featured. This week:

Rebuilding Compass, our training and competency module, before new hires start
Getting three final-stage candidates to a decision — they've been waiting since July 21
Deploying compliance mapping work that's built but not shipped

The database enforces exactly three. Position 1, 2, or 3, unique per week. There's no room for a fourth. If something feels urgent enough to make the list, it has to replace one — which is the decision I'd otherwise avoid.

Friday is the part that makes it real. It isn't a highlight reel. It's a scoreboard I can lose on.

What moved, what didn't, what I failed at. If I said I'd rebuild Compass and spent the week on invoices instead, that goes in the message. If a candidate walks because I sat on the decision too long, that goes in too.

An update that only reports wins is marketing. My team can tell the difference. So can I.

The system marks each priority done, partial, or missed. Anything not done comes back in next Monday's note with its history attached — so something I keep not doing gets harder to hide from every week it survives. That's deliberate. I'd have quietly dropped it otherwise.

I'm trying to build a company my people are proud to be part of. That doesn't happen because I announce it. It happens if they can see the work — including the weeks I don't deliver.

First one goes out tomorrow.

The Guy in the Van Thinks the Owner Stopped Working