Years ago, the people who ran computer servers noticed they treated their machines in one of two ways. Some servers were pets. They had names, like Gandalf or Big Bertha. Each one was set up by hand, a little different from the rest, and when one got sick, everyone stopped what they were doing to nurse it back to health.
Other servers were livestock. They had numbers, not names. They were all set up the same way. When one failed, you replaced it and moved on.
The same idea fits the processes in a small business remarkably well.
Pet processes and livestock processes
A pet process lives in one person's head. It runs because Sarah knows how it runs. It works well enough until Sarah is on vacation, out sick, or gone. Then it either doesn't happen, or it happens differently, and nobody's quite sure why customers are suddenly confused.
A livestock process is written down and standard. Anyone trained can run it. When something goes wrong, you fix the process, not the person. Nobody has to call Sarah at the beach.
One question to sort them
As you list your recurring processes, add one tag to each: pet or livestock. It takes seconds. Ask:
If the person who usually does this were gone for two weeks, would it still happen the same way?
If not, it's a pet.
A list full of pets tells you something before you've rated a single process. It tells you how much of your business walks out the door at five o'clock.
Some pets are worth keeping
Not every pet should become livestock. Some are pets on purpose. The owner's judgment on a tricky bid. The personal call to a customer who's been with you fifteen years. Those may be exactly why customers choose you, and standardizing them could take away the very thing that makes you different.
So every pet gets one more question: is this a pet because it should be, or because nobody ever wrote it down? Keep the first kind, and protect it on purpose. The second kind is waiting to become livestock.
Why this matters for AI
There's a simple rule hiding in this metaphor: you can only safely automate livestock. Tools that act on their own need a process that's standard, stable, and written down. Hand a pet process to an automation and you haven't automated it. You've just made the pet harder to see.
New pets are also being born every day: the personal AI helpers people build for themselves, quietly, with prompts and settings only they understand. They can be genuinely useful. They're also one more thing that leaves when the person does.
Turning a pet into livestock
The move from pet to livestock isn't a demotion for the person who carried the work. It's what finally lets them take a day off. The step is usually modest: a one-page description of the normal path, who owns it, and what to do when something unusual shows up. Put it where the team, and any AI you use, actually look.
Start with the pet that worries you most. Write down the normal path. Then ask someone else to run it once.

