Projects
Projects
In a small restaurant, employees often perform a surprisingly wide range of tasks.
Beyond serving customers, they may need to manage lighting, ventilation, climate control, equipment, reservations, opening and closing procedures, and many other small operational details.
Each additional task consumes attention.
And every task that depends on memory creates another opportunity for error.
I started developing a smart restaurant ecosystem for Taverna Lefkada with one main objective:
Reduce the number of routine decisions employees need to make, so they can focus more of their attention on the customer.
Small businesses do not always have specialized departments or dedicated personnel for every operational function.
The same employee may need to interact with customers while simultaneously remembering whether equipment has been switched on, ventilation adjusted, lights changed, reservations checked, or systems shut down correctly at the end of the day.
Individually, these tasks are simple.
Together, they create significant operational and cognitive complexity.
My approach was therefore not simply to automate devices, but to gradually transfer predictable and repetitive decisions from people to the system.
Routine actions are automated whenever human intervention adds little value.
By removing repetitive tasks from employees' daily workload, the system reduces interruptions and allows them to dedicate more attention to customer needs and service quality.
The objective is not to replace people.
It is to allow people to focus on the tasks where they create the greatest value.
Decorative and ambient lighting is controlled through automated scenarios based on time, operating conditions, and the events celebrated by Taverna Lefkada.
Different lighting environments can therefore be created without requiring employees to manually adjust multiple systems.
The restaurant's atmosphere becomes part of an automated operational routine rather than another task employees need to remember.
At the end of the evening, ambient lighting gradually changes and switches off in stages.
Instead of abruptly informing guests that closing time has passed, the environment itself communicates the transition in a subtle and natural way.
This is an example of using automation not only for operational efficiency, but also for customer experience design.
The ecosystem also manages ventilation and climate-control systems through automated scenarios.
This reduces unnecessary manual intervention while helping maintain appropriate environmental conditions inside the restaurant.
One of the risks in a busy working environment is simply forgetting to switch something off.
Automated shutdown routines help ensure that selected equipment is turned off when it is no longer required, reducing both operational risk and unnecessary energy consumption.
Frequent power fluctuations previously damaged the power supplies of several devices.
Instead of treating each failure individually, I approached the recurring cause.
Additional protection systems were introduced to reduce the risk of equipment damage caused by electrical anomalies and overload conditions.
This reflects one of the principles I use in most projects:
Do not repeatedly repair the symptom. Understand the mechanism that creates it.
The next stage of the project is significantly more ambitious.
I am developing a software layer that will communicate directly with the smart ecosystem and coordinate complete operational workflows.
The goal is to move from individual automations to integrated restaurant processes.
At one stage, opening and closing the restaurant involved approximately 15 separate actions that employees needed to remember and perform correctly.
The future system will coordinate many of these actions automatically.
Instead of operating individual devices one by one, a single workflow will be able to trigger a sequence of actions:
Start the restaurant → check conditions → activate required systems → prepare ventilation and climate → configure lighting → prepare the operational environment.
Closing procedures can follow the opposite logic, including delayed actions where equipment needs to remain active for a specific period before shutdown.
The objective is to make opening and closing procedures:
Simpler. Faster. More consistent. Less dependent on memory.
A future reservation module will also communicate directly with the restaurant ecosystem.
Reservations will no longer exist as isolated information.
They will become operational inputs that the system can use to prepare the restaurant automatically.
Over time, this could allow the ecosystem to adapt certain functions according to reservations, operating hours, occupancy, events, or other predefined conditions.
This project began with simple automation.
But the real objective is much broader:
In a small business, employees often need to perform many different functions simultaneously.
That increases mental load and inevitably increases the probability of mistakes.
Automation offers a different approach.
Predictable tasks can be handled by systems.
People can focus on customers, communication, judgment, creativity, and hospitality.
The purpose of automation is not to remove people from the restaurant.
It is to remove unnecessary decisions from their day.
Ultimately, I want the system to become almost invisible.
Employees should not need to think about the technology behind it.
They should simply experience a workplace where fewer things need to be remembered, fewer mistakes are possible, and more attention can be directed toward the people sitting at the tables.
Here you have a small demo of the system
At a push of a button the lights adjust automatically, the climate is being set to a comfortable temperature (for crouded places).
From the 6th of december up until Christmas the lights are automatically turned on in specific configuration by the system at specified hours
On the 1st of december and 24th of January and a week before lights are automatically turned on in specific configuration by the system at specified hours