Three pieces of restaurant counsel crossed my desk this week. One from an experience-management platform, one from a payroll vendor, one from a trade site. Different companies, different topics, no coordination between them. Every one recommended a transactional instrument, described it in relational language, and never named which architecture it served.
That is not three failures. Three failures would imply a fourth piece somewhere that got it right. In 44 years I have never seen a piece of industry counsel separate the two roads before recommending an instrument.
The experience platform argued, correctly, that measurement after the fact cannot produce the thing being measured. Then it listed the upstream decisions that matter — menu, pricing, layout, promotions, loyalty structure — and every item on the list was an artifact you can commission rather than an architecture decision. Design of what, against what standard, never came up. With the standard unspecified, the piece handed authority to an aggregated customer panel. Earlier design without the road named is not correction. It is acceleration.
The trade site proposed staff scorecards: average check and upsells, turn time, satisfaction scores, product knowledge quizzes, daily leaderboards tied to bonuses. Every metric is throughput or compliance. Not one can register whether a cast member saw the party in front of them. You cannot run a Connection Floor and an upsell board in the same shift and expect the Floor to win. The board pays. The Floor does not.
The payroll vendor was the most technically competent and the most instructive. Its facts about the FICA tip credit were largely right. Its arithmetic assumed all fifty employees were tipped servers working identical weeks all year, and it omitted the requirement to reduce your deductible payroll tax expense by the credit amount. The credit was the hook. The subject was procurement. And it closed on my own argument — that the tax return reflects the quality of the operation behind it — in a vendor’s mouth, to sell a system.
Here is the condition underneath all three. The industry carries one dictionary. Hospitality, experience, relationship, connection, loyalty, engagement — those are the only words available for describing what an operation does, so they get applied to transactional mechanisms as a matter of course. I call it Transactional Default: transaction is the unnamed setting at every operating fork, so Road 1 architecture gets installed without anyone registering that an architecture was chosen.
Nobody is lying. Concealment requires an alternative the concealer declined to use, and there is no alternative in the room. The instruments arrive pre-installed measuring throughput. The benchmarks compare you to operations running identical physics, so conformity reads as health. The Guest cannot flag it either, because they have never been held — only served competently. So satisfaction reports clean, and then most of your first-time Guests never come back and nobody can locate the cause.
You are still choosing. A default is a choice that does not feel like one while you are making it.
The full prosecution, with all three specimens taken apart at the mechanism level and five tests you can run on your own operation: https://hacksterism.jeffreysummers.com/the-industry-only-owns-one-dictionary/
The build — vocabulary first, then the arc, then capacity, then the arc read, then the ledger that compounds: https://physics.jeffreysummers.com/transactional-default/