I was twenty-two and a part-owner of a cabinet shop with six people on the floor. I had no idea what I was doing, and neither did the shop.
We were good at the work. That is the trap. When the work is good, nobody notices that there is no system underneath it — until the week when two jobs land on the same install date, the finish order hasn't arrived, and the person who knows where the hardware is happens to be off.
Everything lived in somebody's head
Job status was in my head. The order list was in a notebook that lived in a drawer. Which supplier had which lead time was tribal knowledge, and it was wrong about a third of the time because lead times move and nobody updates the notebook.
The shop ran because six people were paying close attention. That works until anyone is tired, sick, or on holiday — which is to say, most weeks.
Here is the thing about a shop like that: it looks calm from the outside. Jobs go out. Clients are happy. Nobody is shouting. The failure is invisible because the slack is being absorbed by people, and people don't report that they are the buffer. They just get quieter, and then one day somebody hands in notice and takes a whole job's worth of knowledge out of the building with them.
What we tried, in order
First a whiteboard. It worked for about three weeks, until the whiteboard became another thing to maintain and someone erased a job to make room for a note about a delivery.
Then a spreadsheet. Better, but only if somebody updated it, and the person with the most reason to update it was always the busiest person in the building.
Then a rule, which is the only one that stuck: no job moves to the next stage without a name and a date against it. Not status, not a colour, not a feeling. A person and a date.
It sounds bureaucratic. It was the opposite of bureaucratic. It took about ninety seconds per job and it ended the "I thought you were doing that" conversation, which used to happen weekly and cost hours.
The mistake I made for the first year
I treated every one of those fixes as a communication problem. The whiteboard was going to fix communication. The spreadsheet was going to fix communication. I kept buying better surfaces to write the same missing information on.
The problem was never the surface. It was that no job had an owner. Not a team, not a stage, not "the shop" — a person whose name was on it. Once a name was attached, the communication sorted itself out, because there was someone who would notice.
That is the mistake I see small businesses make constantly, including mine: they go looking for a tool to fix a problem that is actually about who is answerable. A tool cannot assign responsibility. It can only record it after a human has decided.
Process is not paperwork
People hear "process" and picture forms. What process actually is: the part of the work that still happens correctly when you are tired.
A shop with no process is not a flexible shop. It is a shop held together by whoever is paying the most attention that day, and it degrades quietly every time that person is unavailable.
The test I use now is simple. Pick any job in the building and ask: if the person who usually does this step were off sick tomorrow, would it still happen, and would anyone know it had been missed? If the answer is no, that is not a personality failing of the person. That is a hole in the shop.
Why this matters if you want to automate anything
You cannot automate a process that only exists in someone's head. You can only codify chaos, and codified chaos is worse than the original — it now fails silently, at machine speed, without anyone noticing.
So when someone asks me to automate their quoting, my first question is not what tools they use. It's: show me the last quote you wrote, step by step, including the parts you did from memory.
Almost every time, the answer reveals that the process isn't one process. It's three different versions depending on the day, the customer, and how busy the shop is. Automating any of those versions would be automating the wrong one.
The tell is always the same: when the person describes the process, they say "usually" and "normally" and "if it's a big one". Those words are where the exceptions live, and the exceptions are the work.
What I do instead
One week of notes. Not a workshop, not a discovery engagement — a notebook and the discipline to write the job down as it happens, every step, including the stupid ones.
At the end of the week you have something no consultant can sell you: the actual process, with all its exceptions, in your own handwriting.
Then — and only then — you can decide what to remove, what to simplify, and what to automate. Half the time the answer is that three steps disappear and nothing needs building at all.
That is not a disappointing outcome. That is the cheapest possible fix, found before anyone wrote a line of code.