It's all up here, mate

My first week as business manager, I asked to see the job schedule.

He pulled out a stack of cardboard job cards and laid them out on the glass table. Some had dates, some didn't, some had coffee stains. I asked how he knew what was due this week. He tapped his head and said, "It's all up here, mate."

That's when it hit me. If he got hit by a bus, the business would die with him.

And I want to be straight about where I was at. I was 28. No experience running a business or managing staff. The question in my head wasn't "how do I fix this." It was "can I actually pull this off?"

What paper job cards actually cost us

Nobody was being slack. That's the bit people get wrong about businesses run this way. The bloke with the schedule in his head was usually the hardest working person in the building. The problem wasn't effort. The problem was that everything ran through one person.

We had a serious problem with our job scheduling. Once those job cards were given to a glazier, we had no insight as to what was happening throughout that day or week. Was the job done? Half done? Did the glass turn up? Did the customer change the time? You found out when the card came back, or when the phone rang.

That's not a scheduling problem. That's a visibility problem. And it doesn't show up as one big disaster. It shows up as a hundred small ones: double-booked mornings, glass cut for the wrong day, a customer ringing to ask where the glazier is and nobody able to answer. Death by a million paper cuts.

The first job management system we brought in

So we started to implement a job management system, and step by step we just kept improving that workflow process.

I want to be honest about what that sentence hides: it took time, and plenty of it went wrong before it went right. But looking back, a few things made it stick, and none of them were the software.

The glaziers' feedback was integral. They helped us refine it so we could display the information they wanted to see, and the job cards were laid out properly. We didn't build the system we thought they needed. We built the one they told us they needed, one complaint at a time.

We treated it like a big company project. The staff were on board because we made it everyone's project, to get buy-in from everybody. There was a lot of change in the business right then, so we had to implement suggestions quickly and efficiently, and communicate what we were doing as we went along. The fastest way to kill a new system is to go quiet on the people using it.

We kept playing the game. It ended up being one big game where we were just finding things to fix and then trying to make them as optimal as we can. It was quite a fun time, honestly. Once the team saw their suggestions turning up in the system within days, the complaints turned into ideas.

The pattern I keep seeing

I've seen the same thing in every trade business I've worked with since. The schedule in someone's head is just the most common version. It might be the pricing. The way quotes get followed up. The one person who knows how the machine gets fixed.

The test is simple: if that person went on holiday for two weeks tomorrow, what would break first?

Whatever your answer is, that's where your first system goes. Not the flashest software. Not the thing your mate's business uses. The thing that currently lives in one head.

And in case you're wondering where this road leads: years later, the first time I realised what those systems had built me was a friend's wedding in Bali. I ran the whole business from a mobile phone for two weeks. A bit of computer work at night, that was it. Came home with a fire under me and went harder. That didn't start with anything clever. It started with getting a schedule out of one bloke's head.

The one thing to do this week

Don't buy anything yet. Just pick that one thing and write it down where the team can see it. A whiteboard works. A shared note works. Cardboard on a glass table honestly works better than a head.

Then watch what happens. The gaps you find in writing it down, the questions the team asks, the bits nobody agrees on: that's the spec for your first system. You'll choose better software in a month than you would today, because you'll know exactly what it has to do.

If your schedule lives in your head right now, you're not alone. That's exactly where I started.

I'm documenting the whole journey of getting trade businesses out of the owner's head: the systems, the mistakes, the wins, as they happen. Follow the Build and you'll get each piece as it lands.