People sometimes look at me sideways when I mention that I’ve operated quick-service restaurants and developed hotels. To them, these feel like entirely different industries; one is a $12 transaction with a two-minute service window, the other is a multi-million-dollar asset with a multi-year development timeline. The scales couldn’t be more different.
But after years of working on both sides of that equation, I’ve come to believe the opposite is true. Restaurants and hotels are more alike than they seem, and the lessons each offers are among the most transferable in all of hospitality. Operators who understand both tend to be sharper, more resilient, and better at spotting risks before they become problems.
Here’s what I’ve learned moving between the two worlds.
Restaurants Taught Me That Speed Is a System, Not an Attitude
In QSR, speed of service is everything. Customers vote with their feet, and their next visit depends on whether their order arrived in two minutes or four. Early in my restaurant career, I thought speed was about motivation: hiring faster people and pushing harder during rush. I was wrong.
Speed is a system. It’s about how the kitchen is laid out, where inventory is staged, how many steps a crew member takes between the fryer and the window, and how clearly the line of communication runs from cashier to cook. When I optimized those systems, speed improved. When I just asked people to work faster, it didn’t.
I carried that lesson directly into hotel development. The guest experience in a hotel is also a system, encompassing check-in flow, room design, housekeeping sequencing, and response time on service requests. When a hotel underperforms on guest satisfaction scores, the instinct is often to blame the staff. But nine times out of ten, the staff is working around a broken system. Fixing the front desk layout, repositioning housekeeping cart storage, or redesigning the digital check-in flow produces more consistent results than any amount of retraining.
The lesson restaurants taught me: before you blame the people, look at the system.
Hotel Development Taught Me to Think in Decades, Not Quarters
Restaurant operators live in a perpetual present tense. This week’s labor cost, this month’s food variance, this quarter’s comp sales. The urgency is constant and legitimate; restaurants are low-margin, high-velocity businesses where small operational shifts have immediate P&L consequences.
Hotel development is the opposite. When you’re underwriting a 120-room select-service property, you’re making assumptions about market conditions, brand performance, and capital costs that won’t be fully resolved for five, ten, or fifteen years. The discipline required to think that far ahead, to stress-test your assumptions across multiple scenarios and resist the temptation to force optimistic numbers, is fundamentally different from what the restaurant world demands.
That long-horizon thinking made me a better restaurant operator, too. I began asking questions I hadn’t considered before. What will this location look like in ten years? Is the trade area growing or contracting? Is the brand I’m franchising investing in its future or living off past equity? These aren’t questions most QSR operators ask regularly. They should.
Hotel development taught me to zoom out and stay there long enough to see clearly.
Both Industries Punish You for Underestimating the Real Estate
This is the one that stings most operators, in both categories.
In restaurants, I’ve watched franchisees sign leases for sites they fell in love with, sites with great visibility, strong traffic counts, and reasonable rent, only to discover that the site geometry made drive-through stacking impossible, that the co-tenancy brought the wrong demographic, or that the landlord’s center had structural vacancy issues that dragged foot traffic down. The real estate looked fine. It wasn’t fine.
In hotel development, the equivalent mistake is buying a site that looks good on paper but sits in a submarket with chronic oversupply, or acquiring land based on entitlement assumptions that later prove wrong, or underestimating the infrastructure costs buried in a seemingly attractive basis.
The common thread is this: real estate forgives very little and forgets nothing. The site you choose, in either business, shapes your ceiling and floor more than almost any operational decision you’ll make afterward. I now spend more time on real estate diligence than on almost anything else because I’ve been burned enough in both industries to know that the deal that looks obvious rarely is.
The Real Lesson: Hospitality Is One Industry
When I step back from both experiences, what I see most clearly is that restaurants and hotels are two expressions of the same core business: delivering a consistent, high-quality experience to a guest who had other options and chose you.
The metrics differ. The capital structures differ. The timelines differ enormously. But the underlying logic, understand your guest, build reliable systems to serve them, choose real estate with discipline, and invest in your people, remains identical.
The operators I most respect have usually worked both sides of hospitality. They’re harder to surprise, quicker to see operational problems at their root, and more honest about the risks hiding in plain sight. If you’re deep in one world and curious about the other, my advice is simple: go learn it. The translation is more direct than you think.