The system was never designed to hold all of this. But the operator is the one holding it together.
Essay No. 03
The best service you’ve ever received, you probably don’t remember. Not because it wasn’t good. Because it was invisible. The glass was refilled before you noticed it was empty. The table was ready when you arrived. The bill came when you were ready for it, not when the staff decided you were. Nothing interrupted the conversation. Nothing made you feel managed.
That’s the standard. Not impressive. Invisible.
Most software has never understood this. It announces itself constantly. It requires training, workarounds, manager overrides, IT contractors on Saturday nights. It creates the friction it was supposed to remove. And the operators who use it have learned to live with it, the way you learn to live with a bad knee. You adjust your gait. You stop running. You forget what it felt like before.
Most venue technology didn’t get complicated on purpose. It got complicated incrementally. A POS system from 2011. A rostering tool added in 2015. A booking platform bolted on after that. A payments integration. A loyalty app. Each one made sense at the time. Each one solved a real problem. And now they all live together in a patchwork that nobody fully understands and nobody can safely touch.
It’s like a VHS deck with fifteen years of additions plugged into it. CD player, MP3 player, streaming stick, HDMI adapter. It works, technically. But the wrong cable pulled at the wrong moment and the whole thing goes down on a Friday night.
The fragility isn’t obvious until it matters. A staff member hits the wrong button at the wrong moment. What should be a two-second fix requires a manager. What the manager can’t fix requires the owner. What the owner can’t fix requires an outsourced contractor who charges weekend rates and takes two hours to arrive. Meanwhile the floor is backing up and the guests are looking at their watches.
The system was never designed to hold all of this. But a complete revamp isn’t on the cards. So operators suffer through it, and staff work around it, and guests absorb the friction without ever knowing why the service felt slightly off.
The system was never designed to hold all of this. But the operator is the one holding it together.
Everyone carries a phone now. Staff, managers, guests. The infrastructure for seamless, invisible technology already exists in everyone’s pocket. The question is whether the software uses it well.
What good technology in a venue looks like is simple to describe and apparently very hard to build. Staff focused on the customer, not the system. Autonomous enough to handle the shift without manager intervention for every minor decision. Manager intervention reserved for what it should be reserved for: higher-level calls, exception handling, things that genuinely require judgment. Not password resets. Not system overrides. Not explaining to a table why the card machine is down.
Decisions at the right level. That’s it. That’s the whole thing.
When staff aren’t fighting the system, they can do the actual job. Have a conversation. Make a guest feel welcome. Notice the table that needs attention before the table notices they need attention. The technology disappears and the hospitality comes forward. That’s the standard I described at the beginning. Invisible. Seamless. The glass refilled before you noticed it was empty.
Labour and cost of goods are the two biggest variables in whether a hospitality business survives. Everyone knows this. Most people manage them reactively. They look at last week’s numbers and adjust. They roster based on last year’s patterns. They make educated guesses about how busy Friday is going to be and they’re wrong often enough that it costs them.
The data to do better than this already exists. What events are on nearby. What the weather is doing. What your competitors’ foot traffic looks like. Whether the street is busy or empty. Whether there’s a reason trade is going somewhere else tonight. None of this is unknowable. Most of it is just uncollected, or collected and sitting in a spreadsheet nobody has time to read before the roster needs to go out.
Nobody has a crystal ball. But the gap between reacting to what happened and preparing for what’s about to happen is smaller than most operators think. The question isn’t whether the information is available. It’s whether the tools are surfacing it at the right moment, in a form a duty manager can actually act on, in the thirty seconds they have between doing everything else.
That’s a design problem. Not a data problem.
The best software, like the best service, is the kind you forget is there.
Hospitality taught me that the goal was never to impress the guest. It was to take care of them so well that the care itself became invisible. No friction. No announcements. Just the feeling, at the end of the night, that everything went exactly as it should have.
Software should work the same way. It should handle the complexity so the people using it don’t have to. It should surface the right information at the right moment and then get out of the way. It should make the staff better at their jobs, not more aware of their tools.
Most of what I build at OTW Studios starts from this question: what would this look like if it worked the way a good restaurant works? Quietly. Efficiently. Without anyone having to think about it.
The best software, like the best service, is the kind you forget is there.