A RESTAURANT IS NOT A SYSTEM.
IT'S ALIVE
This week’s article is somehow related to the previous one; it’s the aftermath.
Now that we have modern kitchens full of screens, dashboards, predictive tools, forecasts, and data management software, and even AI processing prep lists or office tasks—basically every movement is tracked, and everything is optimized. So it looks efficient and reassuring. It gives us a sense of control.
As I said, those tools help, and I use them.
But if we rely too much on them to the point of becoming too dependent, we are losing track of reality, and we are forgetting the unavoidable truth: A restaurant is a living organism.
It doesn’t run on numbers alone, but on people, on mood, on timing, on pace… on things that never behave the same way twice. It reacts to the outside world, to the fucking weather, to the energy in the room, or to the lack of it, and it breathes differently at every service.
For those who have never worked in a restaurant, nothing looks like the chaos of brunch. There is a huge difference between twenty guests at lunch and twenty guests at dinner because both shifts have different energies and urgencies, and both require a different instinct to manage the rush.
On one side you have lunch, which is clinical. It’s all about the clock, the pace. And the needs of this service differ wildly from the emotional theater of dinner. During the evening, the stress is not as dense; it’s not lower but more stretched, and the menu is often more complex.
So one is about time and the other is about presence.
And I would push the comparison somewhat further: a busy Friday might be you can’t compare it to a busy Saturday night.
But software or POS systems don’t recognize that difference. They just gather numbers and analyze them but don’t feel the tension; they don’t sense chaos. They can’t feel when a team is getting on its ropes or if you are understaffed because somebody called in sick. Or when the kitchen is one ticket away from being in the fucking weeds
That, my friend, your dashboard will never warn you about that.
And it’s the same thing for volume; you can argue forever about it, but a cover is not a cover.
Allow me to explain, for software, twenty covers at 1:00 PM on a Wednesday are the same data point as twenty covers at 8:00 PM on a Saturday night. But anyone who has ever worked in a dining room or a kitchen knows that it’s a whole different ball game.
Last but not least, a full dining room during the week does not feel like a full dining room on a Saturday night. Even if the numbers of guests are identical, it’s an entirely different reality.
Now of course we can use tech to help us to optimize scheduling based on weather and booking patterns, but it can’t replace the instinct or the intelligence needed to lead a stressed crew during a Saturday night rush. And yet, we keep building kitchens and dining rooms as if everything could be predicted and controlled. We want to manage a service without understanding it, without feeling it.
It’s impossible because a service moves and shifts. because it breathes with the guests and with the staff, and it’s unpredictable, so it forces people to act or react within a split second.
How useful is your POS when a server needs to speed the pace of a table or slow it down, if someone in the team is having a rough day, or if the dishwasher is buried under plates, pots, and glassware? Not much. The data you cherish so much becomes irrelevant.
We can use and stuff the kitchen with modern tools as much as we can, but it won’t change the ultimate reality of a kitchen; not every sauce is taking the same amount of time to be prepared. If today’s tomatoes are riper than yesterday's, or if the humidity is affecting the dough, or if a supplier could not deliver pineapples. Or if the case of eggs was broken during transport.
A system will tell you when a dish is late, but it cannot tell you when a service is tanking. A screen can give you the time of day or the number of reservations, even break it down hours by hours or every fifteen minutes, but it can’t feel the vibe of Table Four.
A tablet can send an order perfectly, but it won’t be able to read a guest who’s about to lose his shit because he said he was in a hurry and the food is no-show.
An algorithm can optimize staffing for the stations, but it won’t compensate for a fuck-up on the pass.
We can’t not forget and deny that hospitality has a soul, and it has a personality, a mood, and demands, so you can’t tell me that algorithms can predict when it’s going to be a success or total chaos. And now that we rely more and more on those tools, the less we are taking care of what actually matters: the human factor. So we become mechanical.
We stop adjusting; we start executing.
We stop reading the room; we start following a plan.
We stop cooking; we start assembling.
We stop reacting; we are just following.
Then we assume everything is right.
But what happens when it’s not anymore? When we ignore instinct or when we lose our ability to deal with pressure. Because let’s face it, chaos and stability are not bugs in this industry. Speaking of which, stability isn’t the goal, and chaos is not a problem to eliminate.
It comes with the fucking territory, and it is the natural habitat, the norm.
I repeat and insist that for me, a restaurant is alive because it is chaotic and unstable. That’s the whole point. It moves, shifts, and pushes you to react. It forces you to adapt all night long depending on the kind of situation you are in. But never to comply.
When you remove that, you don’t make it better or more efficient, or even more profitable for that matter; you just make it boring… and forgettable.
So yes, technology matters, and it should help make your job simpler, not make it dull and uninteresting. And right now, sometimes, it feels like we’re doing the opposite; we’re trying so hard to control everything that we forget what a restaurant actually is. A place managed by people for people. And we must fight to keep the human at the center of it.
Ultimately, a restaurant is not a system to be optimized; it is a living place. It’s an exchange of energy. If we replace the intuition of a chef with an algorithm or the theater of a server with a screen, we are improving efficiency, but we are changing the meaning of hospitality.
A spreadsheet can calculate the cost of a sauce, but it can never understand the love required to make it by hand. A management system can track a guest’s history, but it can never feel their bad mood or the spark of a celebration.
The core of hospitality lives in the chef’s ability to create a recipe or adjust the seasoning of a meal. In the server’s instinct to slow down the pace of a romantic dinner. Or to handle their section when the technology goes dark.
We need to remember that we are in the business of humanity, and we need to use our tools to support the hands, not replace our brains. Because the second or minute the lights go down and the last guest leaves, a restaurant isn’t remembered for its software. It’s remembered for the experience we gave to the guest, the impression they leave with, or the memory of a meal, a server, a team, or a moment.
So I beg you, you goddamn nerds of hospitality 2.0, let me keep the flames, the knives, the chaos, and a part of the unknown and spontaneity that makes the heart and souls of this industry. Because everything else is just noise. Because if we continue to manage restaurants where everything is efficient, predictable, and perfect on paper… it will become soulless, empty, and dead.
Then we won’t have restaurants anymore; we’ll just have factories where machines serve food, and last time I checked, machines don’t create memories.
4/27.26
AND THE BIGGEST MISTAKE IS TRYING TO CONTROL IT EVEN WHEN IT REFUSES TO BEHAVE
NEWSLETTER
YOUR SEAT AT THE TABLE STARTS HERE
NO SPAM.
NO SPIN.
THE GOOD STUFF ONLY
Sharp stories, honest conversations, and the occasional badly behaved opinion. Delivered when there’s something worth saying.
BY SIGNING UP, YOU AGREE TO RECEIVE EMAILS FROM FOODNBULLSHIT. UNSUBSCRIBE ANYTIME.
© 2026 FOODNBULLSHIT All rights reserved.
Contact:
A RESTAURANT IS NOT A SYSTEM.
IT'S ALIVE
This week’s article is somehow related to the previous one; it’s the aftermath.
Now that we have modern kitchens full of screens, dashboards, predictive tools, forecasts, and data management software, and even AI processing prep lists or office tasks—basically every movement is tracked, and everything is optimized. So it looks efficient and reassuring. It gives us a sense of control.
As I said, those tools help, and I use them.
But if we rely too much on them to the point of becoming too dependent, we are losing track of reality, and we are forgetting the unavoidable truth: A restaurant is a living organism.
It doesn’t run on numbers alone, but on people, on mood, on timing, on pace… on things that never behave the same way twice. It reacts to the outside world, to the fucking weather, to the energy in the room, or to the lack of it, and it breathes differently at every service.
For those who have never worked in a restaurant, nothing looks like the chaos of brunch. There is a huge difference between twenty guests at lunch and twenty guests at dinner because both shifts have different energies and urgencies, and both require a different instinct to manage the rush.
On one side you have lunch, which is clinical. It’s all about the clock, the pace. And the needs of this service differ wildly from the emotional theater of dinner. During the evening, the stress is not as dense; it’s not lower but more stretched, and the menu is often more complex.
So one is about time and the other is about presence.
And I would push the comparison somewhat further: a busy Friday might be you can’t compare it to a busy Saturday night.
But software or POS systems don’t recognize that difference. They just gather numbers and analyze them but don’t feel the tension; they don’t sense chaos. They can’t feel when a team is getting on its ropes or if you are understaffed because somebody called in sick. Or when the kitchen is one ticket away from being in the fucking weeds
That, my friend, your dashboard will never warn you about that.
And it’s the same thing for volume; you can argue forever about it, but a cover is not a cover.
Allow me to explain, for software, twenty covers at 1:00 PM on a Wednesday are the same data point as twenty covers at 8:00 PM on a Saturday night. But anyone who has ever worked in a dining room or a kitchen knows that it’s a whole different ball game.
Last but not least, a full dining room during the week does not feel like a full dining room on a Saturday night. Even if the numbers of guests are identical, it’s an entirely different reality.
Now of course we can use tech to help us to optimize scheduling based on weather and booking patterns, but it can’t replace the instinct or the intelligence needed to lead a stressed crew during a Saturday night rush. And yet, we keep building kitchens and dining rooms as if everything could be predicted and controlled. We want to manage a service without understanding it, without feeling it.
It’s impossible because a service moves and shifts. because it breathes with the guests and with the staff, and it’s unpredictable, so it forces people to act or react within a split second.
How useful is your POS when a server needs to speed the pace of a table or slow it down, if someone in the team is having a rough day, or if the dishwasher is buried under plates, pots, and glassware? Not much. The data you cherish so much becomes irrelevant.
We can use and stuff the kitchen with modern tools as much as we can, but it won’t change the ultimate reality of a kitchen; not every sauce is taking the same amount of time to be prepared. If today’s tomatoes are riper than yesterday's, or if the humidity is affecting the dough, or if a supplier could not deliver pineapples. Or if the case of eggs was broken during transport.
A system will tell you when a dish is late, but it cannot tell you when a service is tanking. A screen can give you the time of day or the number of reservations, even break it down hours by hours or every fifteen minutes, but it can’t feel the vibe of Table Four.
A tablet can send an order perfectly, but it won’t be able to read a guest who’s about to lose his shit because he said he was in a hurry and the food is no-show.
An algorithm can optimize staffing for the stations, but it won’t compensate for a fuck-up on the pass.
We can’t not forget and deny that hospitality has a soul, and it has a personality, a mood, and demands, so you can’t tell me that algorithms can predict when it’s going to be a success or total chaos. And now that we rely more and more on those tools, the less we are taking care of what actually matters: the human factor. So we become mechanical.
We stop adjusting; we start executing.
We stop reading the room; we start following a plan.
We stop cooking; we start assembling.
We stop reacting; we are just following.
Then we assume everything is right.
But what happens when it’s not anymore? When we ignore instinct or when we lose our ability to deal with pressure. Because let’s face it, chaos and stability are not bugs in this industry. Speaking of which, stability isn’t the goal, and chaos is not a problem to eliminate.
It comes with the fucking territory, and it is the natural habitat, the norm.
I repeat and insist that for me, a restaurant is alive because it is chaotic and unstable. That’s the whole point. It moves, shifts, and pushes you to react. It forces you to adapt all night long depending on the kind of situation you are in. But never to comply.
When you remove that, you don’t make it better or more efficient, or even more profitable for that matter; you just make it boring… and forgettable.
So yes, technology matters, and it should help make your job simpler, not make it dull and uninteresting. And right now, sometimes, it feels like we’re doing the opposite; we’re trying so hard to control everything that we forget what a restaurant actually is. A place managed by people for people. And we must fight to keep the human at the center of it.
Ultimately, a restaurant is not a system to be optimized; it is a living place. It’s an exchange of energy. If we replace the intuition of a chef with an algorithm or the theater of a server with a screen, we are improving efficiency, but we are changing the meaning of hospitality.
A spreadsheet can calculate the cost of a sauce, but it can never understand the love required to make it by hand. A management system can track a guest’s history, but it can never feel their bad mood or the spark of a celebration.
The core of hospitality lives in the chef’s ability to create a recipe or adjust the seasoning of a meal. In the server’s instinct to slow down the pace of a romantic dinner. Or to handle their section when the technology goes dark.
We need to remember that we are in the business of humanity, and we need to use our tools to support the hands, not replace our brains. Because the second or minute the lights go down and the last guest leaves, a restaurant isn’t remembered for its software. It’s remembered for the experience we gave to the guest, the impression they leave with, or the memory of a meal, a server, a team, or a moment.
So I beg you, you goddamn nerds of hospitality 2.0, let me keep the flames, the knives, the chaos, and a part of the unknown and spontaneity that makes the heart and souls of this industry. Because everything else is just noise. Because if we continue to manage restaurants where everything is efficient, predictable, and perfect on paper… it will become soulless, empty, and dead.
Then we won’t have restaurants anymore; we’ll just have factories where machines serve food, and last time I checked, machines don’t create memories.
AND THE BIGGEST MISTAKE IS TRYING TO CONTROL IT EVEN WHEN IT REFUSES TO BEHAVE
4/27.26
NEWSLETTER
YOUR SEAT AT THE TABLE STARTS HERE
NO SPAM.
NO SPIN.
THE GOOD STUFF ONLY
Sharp stories, honest conversations, and the occasional badly behaved opinion. Delivered when there’s something worth saying.
BY SIGNING UP, YOU AGREE TO RECEIVE EMAILS FROM FOODNBULLSHIT. UNSUBSCRIBE ANYTIME.
© 2026 FOODNBULLSHIT All rights reserved.
Contact:
alexandrefenot@gmail.com
NEWSLETTER
NO SPAM.
NO SPIN.
THE GOOD STUFF ONLY
Sharp stories, honest conversations, and the occasional badly behaved opinion. Delivered when there’s something worth saying.
BY SIGNING UP, YOU AGREE TO RECEIVE EMAILS FROM FOODNBULLSHIT. UNSUBSCRIBE ANYTIME.
© 2026 FOODNBULLSHIT All rights reserved.