TL;DR: If a task lives in your head, it is not a process. It is a habit. Run the four-question test below and you will see exactly where your operation is depending on your memory, mood, and bandwidth.
The fix is not more discipline. The fix is writing the thing down in a way someone else can execute, measure, and improve.
A client told me he had a process for onboarding.
When I asked to see it, he listed the steps from memory.
That is the tell.
If the only place your process exists is inside the owner, you do not own an operation. You own a set of routines that work when you are awake, present, caffeinated, and paying attention.
That can feel like competence. It is actually a ceiling.
This is not an insult. Most of us were trained this way.
Hospitality teaches you to hold the whole room in your head. Tickets, guests, tables, reservations, prep, inventory, staff mood, the one regular who is about to blow up because they think their martini is too wet. We get good at memory and improvisation.
That skill keeps the lights on.
It does not scale.
And it makes your business fragile in a way you only notice when you get sick, take a trip, have a kid, or hit a stretch where you are running on fumes.
Pick any recurring task and answer four questions. No stories. Yes or no.
Not, I could explain it if someone asked.
Written down.
Steps.
In order.
If the answer is no, it is a habit.
A process produces a consistent output because the steps are defined.
A habit produces a variable output because a person is interpreting the steps in real time.
This is where most operations fail.
If your opening checklist works on Tuesday but falls apart on Saturday, you do not have a checklist problem. You have a process definition problem.
A habit happens.
A process can be audited.
How long did it take.
Which steps were completed.
What the output looked like.
If you cannot measure it, you cannot improve it. You cannot train it. You cannot delegate it.
If you disappeared for 14 days, would the task still happen.
Would it happen correctly.
If the answer is probably not, then the business does not own the process.
You do.
And anything you personally own that the business cannot operate without is a liability disguised as leadership.
Plenty of operators have binders.
Plenty of operators have Google Docs.
Plenty of operators have a folder called SOPs.
That does not mean they have processes.
A written document that nobody can execute consistently is a permission slip to say, we did our best.
Question two is the real test because it exposes where the work is still craft knowledge instead of operational knowledge.
Craft is good. Hospitality is craft.
But craft lives in a person.
Operations live in a system.
If you want less chaos and fewer fires, you need more of the work to move from craft memory into operational definition.
That does not make your business less human.
It makes it less dependent on whether the right human is standing in the right place at the right time.
Pick one task you do every single week. The one that would hurt if it went sideways.
For most hospitality businesses, it is one of these:
Now write the process using this format.
Step: what happens / who does it / what triggers it / what the output looks like
Do not write paragraphs.
Write steps.
Here is an example from a proposal workflow. Different industry, same structure.
The point is not the tools.
The point is that you can see the work.
Once you can see it, you can decide what should be done by a person and what should be done by a system.
Most operators resist documenting because it feels like busywork.
You already know how to do the thing. Writing it down feels like you are doing work about work.
I get it.
The problem is that as long as the process lives in your head, it is not transferable.
You cannot hand it to a supervisor.
You cannot hand it to a new hire.
You cannot hand it to a tool.
You can only keep doing it yourself.
That is why so many owners feel like their business is a job they cannot quit.
They built something that runs on their presence.
Most operators are thinking about AI like a gadget.
A chatbot.
A menu description generator.
A tool that saves a little time.
That is the wrong mental model.
The real value is that once your processes are written down, you can hand chunks of the work to systems that do not forget steps.
They do not skip follow-ups because the dinner rush got ugly.
They do not vary based on mood.
They do the boring part the same way every time so your humans can do the human part.
That is the long arc here.
Hospitality does not need fewer people.
It needs fewer failure points.
The businesses that win over the next few years will be the ones that turn memory into process, then turn process into a system that runs even when the owner is not watching.
Pick the task that happens often and creates chaos when it goes wrong. High frequency, high consequence.
Every business is unique. The work is not. You are still onboarding, training, ordering, closing, and following up. Define the steps for your version.
Detailed enough that a smart person could follow them without asking you five questions. If you keep getting the same question during training, your steps are missing detail.
If the output is consistent, you can document the shared outcome and allow variation inside guardrails. The problem is variation that changes the result.
Use them in the workflow. The process is not a PDF you print. It is a checklist, a template, a short page someone can pull up in the moment.
Today, pick one weekly task.
Write it out as steps with trigger, owner, and output.
Then circle every step that does not require human judgment. Those are the first candidates to hand to a system.
If you want help turning your documented processes into a simple engine that runs in the background, Workshop is where I publish the playbook.
Jason Littrell spent 10 years behind the bar in NYC (including Death & Co) and served as USBG NYC president. He now runs his hospitality consulting firm entirely on AI. He hosts the Hospitality Strategy Lab podcast and writes The Ops Wire newsletter.
Jason